During Requirement Management the generic requirements as stated in the BC, PSA, PROSA, PID, etc. is enriched with the solution requirements as defined by Product Owners, (Super) Users, Security and Privacy Officers, System Management, and technical specialist. When necessary or available EPICS and User Stories can be either defined and/or used.
Problems and Solutions
The contemporary approach is challenged with incomplete architecture models, principles, design and development documentation. This leads to tiresome gathering of functional and non-functional requirements for new innovation solutions. Almost every time a project starts, a new collection of requirements must be defined for the transition processes.
Within the Enterprise Architects approach most of the necessary requirements have already been defined or can be retrieved based on the initial solutions as defined by the detailed PSA.
Tools to support Requirement Management
To support Requirement Management Enterprise Architects offers the following solutions and tools:
||Maintaining the PROSA requirements for each Knowledge Function of the solution|
||Maintaining details of Principles, Requirements, design Objectives, Standards & Agreements for the solution|
||Maintaining the PSA|
||Supporting the Transition during different phases|
||Supporting modeling EPICs, User Stories, Interaction Design and Presentation Services – Also see ISE|
Advantages of the Enterprise Architects approach
- Maintaining and managing functional and non-functional requirements as derived by BC, PSA, PID, PROSA and interaction support, defining EPICs, User Stories, etc. in a central repository
- The SAFe™ Core Values are safeguarded and improved as follows
- Program Execution