Skip to main content

Architecture and Design

Powersheet Architecture — How the server extension, client application, and YAML configuration layers fit together inside Siemens Polarion ALM. Core Components — The four building blocks of every powersheet: domain model, sheet configuration, Powersheet Drive, and the document entry point. Model-Driven Design — Why Powersheet uses a declarative domain model to abstract Polarion work item types and link roles into a portable configuration layer.

Configuration

Data Model vs Sheet Configuration — Understanding the separation between what data exists (domain model) and how it is displayed (sheet configuration). YAML Configuration System — How YAML files are discovered, loaded, and applied at global and project levels. Global vs Project-Specific Configuration — Scoping rules that control where domain models and sheet configurations are stored and inherited.

Domain Modeling

Entity Types and Relationships — Defining domainModelTypes, mapping them to Polarion work item types, and declaring relationships with from, to, cardinality, and linkRole. Navigation Properties — How fromNavPropName and toNavPropName create traversable paths used in expansion paths and column binding paths. Link Cardinality — The meaning of one-to-one, many-to-one, one-to-many, and many-to-many cardinality values and how they affect the sheet UI. Hierarchy and Traceability — How expansion paths let you navigate multi-level entity hierarchies such as, for example, UserNeed to SystemRequirement to DesignRequirement in an RTM model.

Constraints and Rules

Process Constraints — Enforcing engineering methodology through load, create, and pick constraints that go beyond what Polarion provides natively. Document Rules — Restricting where work items can be created or selected using moduleFolder, moduleName, type, and component constraints.

Platform Integration

Polarion Integration — How Powersheet embeds inside Polarion as a server extension, registers administration pages, and stores configuration in SVN.
If you are new to Powersheet, begin with Powersheet Architecture and Core Components to build a mental model of the system. Then move to Entity Types and Relationships to understand the domain model that drives everything else.

See Also

  • Getting Started — Hands-on tutorials for your first domain model and sheet configuration
  • Reference — Complete YAML property reference for domain models and sheet configurations
  • FAQ — Answers to common configuration and setup questions
Source Code
  • DomainModelTypeV2.java