|
|
|
|
|
|
|
|
|
MSF for CMMI Process Improvement > Wiki Pages > Activity - User Education Work Breakdown Analysis
|
Activity - User Education Work Breakdown Analysis
|
|
|
|
|
|
Activity Information User Education Work Breakdown Analysis
DescriptionAnalyze 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. Attributes| Element Categories | [CMMI Track 3] Build, [CMMI Level 2] PP SP 1.1 | | Entry Criteria | Scenarios:
A list of scenarios accepted for the iteration.
QoS Requirements:
A list of quality of service requirements accepted for the iteration.
Functional Requirements:
A list of functional requirements accepted for the iteration.
Operational Requirements:
A list of operational requirements accepted for the iteration.
Change Requests:
A list of change requests accepted for the iteration.
User Interface Flow Model:
The user interface flow or interaction wire frame model.
Domain Model:
An object or data domain model describing the product domain.
Existing Architecture:
Any documentation describing the existing logical architecture and physical data center or deployment environment.
User Acceptance Tests:
The set of validation tests that were written with the requirements. | | Exit Criteria | User Education Tasks:
Task work items of type User Education describing all the technical writing work required in the iteration. | | Is Required | Yes |
StepsAnalyze User Guide Requirements (Optional):
Use the scenarios, quality of service requirements, and user interface flow model and break out a table of contents for the User's Guide.
Brainstorm the topics for the User's Guide table of contents.
Create a writing task for each topic in the table of contents. Analyze Online Help (Optional):
Use the scenarios, quality of service requirements, and user interface flow model and break out a topic list for online help.
Create a writing task for each online help topic. Analyze Create Operator's Guide (Optional):
Use the operational requirements, and user interface flow model to break out a table of contents for an Operator's Guide.
Brainstorm a list of detailed topics for the Operator's Guide table of contents.
Create a writing task for each operator's guide topic. Analyze Maintenance Manual (Optional):
Use the functional requirements, user acceptance tests, security requirements, domain model, and user interface flow model to break out a table of contents for a maintenance manual. The audience for the maintenance manual is the team working on future iterations and releases of the product.
Brainstorm a detailed topic list for the table of contents.
Create a writing task for each topic in the table of contents. Analyze Training Manual (Optional):
Use the scenarios, operational requirements, and user interface flow model to break out a table of contents for a training manual.
Brainstorm a detailed list of topics for the training manual table of contents.
Plan a writing task for each topic on the table of contents.
Inputs and Outputs| WorkProduct | Input | Output | Allowable States |
|---|
| Task |  |  | Proposed |
|
Last modified at 12/19/2007 10:37 AM by Administrator
|
|
|
|
 |
|
|
|
|