How is a feature expressed?

• A. As a phrase
• B. In a formal requirement document
• C. As a diagram
• D. As a numeric metric

Answer: (C)

Expressing a feature with a diagram helps teams see how it behaves and how it connects to the rest of the system. A diagram lays out the feature’s boundary, the users or actors, any external systems, and the data or control flows between components. This visual model provides a shared understanding across multiple teams, which is crucial for planning, integration, and validation on an Agile Release Train. While naming the feature with a phrase or detailing it in a formal document or relying on numeric metrics for measurement can be useful in some contexts, they don’t communicate the interactions and boundaries as effectively as a diagram does. A diagram quickly conveys how the feature fits into the architecture and how different parts of the solution will collaborate to deliver value.