|
|
Analysis (CMMI Level 2 : PP 1.1 )
Architect |
|
|
Participating Roles
Responsible:
Architect
User Experience Architect
User Education Specialist
Tester
Developer
Accountable:
Architect
Consult:
Business Analyst
Subject Matter Expert |
Analyze the requirements, change requests, domain model, user interface flow model, and existing architecture to determine a list of individual tasks for team members.
Entry Criteria
- The scenarios selected for the iteration.
- The quality of service requirements selected for the iteration.
- The functional requirements selected for the iteration.
- The operational requirements selected for the iteration.
- The security requirements selected for the iteration.
- The change requests accepted for the iteration.
- A flow or interaction wireframe model of the proposed user interface.
- An object or data domain model describing the product domain.
- Any available documentation on the existing product and enterprise architecture into which the code from the current iteration must be deployed.
- The tests created along with the requirements to validate the accurate delivery of the requirements.
When:
Activities
|
1 |
Design and Development Analysis |
- Analyze the requirements and change requests along with the existing architecture, domain model, and user interface flow model; then determine a list of developer tasks for design and development of the code for the iteration.
|
2 |
Test Planning |
- Analyze the requirements and change requests along with the existing architecture, domain model, and user interface flow model; then determine a list of test tasks for the quality assurance team to perform in order to validate the specification for the iteration.
|
3 |
User Experience Work Breakdown Analysis |
- Analyze the scenarios, functional requirements, and quality of service requirements; then determine a list of user interface design and usability testing tasks required to validate the user experience requirements for the iteration.
|
4 |
User Education Work Breakdown Analysis |
- Analyze all the requirements and change requests along with the user interface flow model and the domain model; then determine all the user education (technical writing) tasks required to adequately document the specification for the iteration.
|
Exit Criteria
|
Task work items of type "development task" describing design, coding, and unit testing for the iteration. |
|
Task work items of type "test task" describing validation testing for the iteration. |
|
Task work items of type "user experience" describing user interface design and usability testing tasks for design and validation of the functionality in the iteration. |
|
Task work items of type "user education" describing all the technical writing tasks required to document the deliverable from the iteration. | |
|