Architecture Requirements Management
Architecture Requirements Management is critical to the creation of architectures that are fit for purpose and that address the concerns, drivers, constraints, goals and other forces that express the needs of the enterprise or its organizations. These requirements effectively define the design problem that the architecture needs to solve. Each architecture domain will have requirements defined that will be the result of architectural analysis of the high level domains. The requirements will have a variety of sources, and requirements need to reference these sources or the more primitive elements from which they are derived.
Enterprise Architect is a sophisticated platform that can be used for architectural Requirements development and management. The powerful text-based Specification Manager helps you create, view and manage Requirements in a word processor or spreadsheet-like interface that provides a compelling alternative to viewing requirements in the Browser window or in diagrams. Any number of Requirements diagrams can be created and used to visually represent the relationship between requirements and other elements, including other requirements. Baselines provide a snapshot of the requirements and then, as time goes on, you can compare the current model to this or any other baseline and display the differences visually. If a publication such as a Request for Tender or a requirements specification is needed, it can be conveniently generated automatically using the Documentation engine.
This section lists the main tools available in Enterprise Architect that can be used to perform Architecture Requirements Management. There is also a wide range of additional tools that a modeler might find suitable when applying the technique in a particular context. The complete list of tools is available from the topics: Meet the Enterprise Architecture Tools and Additional Enterprise Architecture Tools.
The Specification Manager is the central tool for working with Requirements; it provides a Word Processor or Spreadsheet interface for entering, maintaining and viewing Requirements. Architecture Requirements can be viewed as a catalog and detailed descriptions and a range of properties can be added directly through the interface. Changing Requirements in the Specification Manager will change them in all other places in the repository, such as diagrams and windows. The Specification Manager can be used with any set of model elements such as business drivers or applications where viewing the elements in a list is preferred, but it is particularly useful for creating and managing Architectural Requirements.
Learn More: Specification Manager
The Requirements diagram can be used to create a visual representation of the relationship between requirements and other elements in the model, including Principles, Business Drivers, Constraints, Business Rules, Use Cases, User Stories, design Components and more. For architects who are accustomed to working with requirements in a text based tool it will provide a powerful and expressive visual representation allowing the requirements to be tied to elements of the business, information, application and technology architectures.
Learn More: Requirements Diagram
Enterprise Architect has a powerful and flexible documentation generator that can produce Docx and RTF Word Processor files, PDF and HTML reports. Architectural Requirements stored in the repository can be conveniently generated and included in documentation. The formatting in an element's Notes and diagrams can also be carried through to the documentation. A sophisticated template facility exists that provides a range of built-in templates and also allows the user to create their own templates, defining styles, cover pages, tables of contents, images and a wide range of other formatting options.
Learn More: Documentation
Requirement properties are metadata about each Requirement. They allow a series of aspects of the Requirement to be specified, which are used to manage the Requirements as a set. Properties such as Status, Priority, Difficulty, Author, Phase and Version can be used to prioritize and group Requirements for the purpose of defining work Packages, releases and architecture work allocation.
Learn More: Requirement Properties
The Traceability Window displays a dynamic hierarchical view of a model element's relationships to other elements in the model. An architect will find the tool indispensable for examining how requirements trace to items higher up in the architecture such as Business Drivers and lower level items such as designs and solution options.
Learn More: Traceability Window
The Baseline Tool can capture a snapshot of the Architectural Requirements at a point in time and a comparison can be made between this or any other snapshot and the model at a later point in time. The comparison tool will enable an architect to visualize what has changed and if necessary revert back to content contained in the baseline. Any Package in the requirements hierarchy can be baselined and any number of baselines can be created.
Learn More: Baseline Tool