Validating enterprise architecture against requirements
You can validate the enterprise architecture against architecture requirements by associating appropriate definitions with model elements.
There are two basic methods you can use to attach requirement-type definitions to model elements, such as a UML Use Cases, Use Case Steps, tables in a data model, or a business process or function:
1 Address them using a built-in addressable facility
2 Embed them into the definition using the customizable metamodel facility, such as user properties or USRPROPS.
Using addressables
The built-in addressable requirements facility enables you to select any symbol on any diagram and “address” a requirement-type definition to it.
You do this by selecting a symbol on an open diagram, and selecting Dictionary > Addresses. These definition types are available as addressables:
With TOGAF option selected
▪Risk
▪Issue
Other addresssable type definitions available
▪Business Objective
▪Business Process
▪Change Request
▪Critical Success Factor
▪Current Data Collection
▪Data Class
▪Deliverable
▪Geographic Location
▪Functional Organization
▪Information Requirement
▪Issue
▪Organizational Goal
▪Requirement
▪Test Plan
You can run reports later to show what requirement-types have been attached (and which have not) to what symbols, and so on (Reports, Reports, Report Generator, File, Open Report File, and then select Address.rpt). These “addressables” can also be displayed on symbols through a modification to USRPROPS.TXT.
Adding new requirement type definitions
In addition, the customizable repository metamodel enables you to add new definition types to a project, and to add properties to any definition type. So you can decide, for example, that you want to add the definition types Software Requirement, Technology Requirement, and Really Silly Requirement to the project. You can do this with USRPROPS.TXT. You can even add these new requirement types to the list of “Addressables” above.
Validating that architecture meets requirements
Validation of what requirements (or other addressable-type definitions) are addressed by what parts of the architecture is performed using standard System Architect Reporting.