Define Requirements Architecture
The purpose of Define Requirements Architecture is to create a repository where requirements and the relationships between them can be managed, as well as capturing any information related to their context.
Guidelines/Tools and Techniques
Define Requirements Architecture - Uses Data Modeling, Functional Decomposition, Interviews, Organizational Modeling, Scope Modeling and Workshop techniques to define the requirements architecture.
The Requirements Architecture – Uses Architecture Management Software, Legal/Regulatory Information, and Methodologies and Frameworks tools and guidelines.
The relationships between these guidelines, tools, techniques and the Requirements Architecture are detailed in the BABOK under the Guidelines and Tools and Techniques sections of the Define Requirements Architecture task.
Workers
The people involved with defining the requirements architecture.
The relationships between these roles and the Requirements Architecture Name, are detailed in the BABOK under the Stakeholders section of Define Requirements Architecture task.
Any Stakeholder - Uses the requirements architecture to assess the completeness of the requirements.
Domain Subject Matter Expert - Assist with defining and confirming the requirements architecture.
Implementation Subject Matter Expert - Assist with defining and confirming the requirements architecture.
Project Manager - Assists with defining and confirming the requirements architecture.
Sponsor - Assist with defining and confirming the requirements architecture.
Tester - Assists with defining and confirming the requirements architecture