| PHASE | DSCR |
| INPUTS |
| RISKS |
| IA DELIVERABLE |
| OUTPUTS |
| Defintion | Map business needs & goals to projected use of project or product. |
| Team: Business developers, project owners, developers, domain experts.
Information: Business reasoning, statistical &/or heuristic analysis |
| Team: Inappropriate contributors or too many contributors.
Information: Underestimation of complexity, lack of consideration for users. |
|
Project Defifntion Document
includes use cases. |
| PDD goes to developement team for specification. |
| |
| Specification | Specify what features will be built, what the user experience will be. |
| Team: Project owner, producer, developers, domain experts.
Information: Technical & developmental constraints, statistical &/or heuristic analysis |
| Team: Feature creep; time budget over-runs, lack of appropriate validation of design, lack of resources.
Information: Lack of specificity. |
| FSD includes process models, interaction flows, feature maps & wireframes. |
| Functional specification goes to technical team for construction. |
| |
| Realization | Construct a working prototype for usability testing, document technical elements. |
| Team: Project owner, producer, developers, visual designer, usability analyst.
Information: Technical & developmental constraints, formal usability or heuristic analysis |
| Team: Insufficient resources, unclear goals.
Information: Lack of time built into schedule to effectively use information gleaned from users. |
| Prototype
TSD
Usability analysis |
| Prototype will be used as model for production or the basis for further iteration.
Technical specification documents scripting, database modifications, systemic interdependencies.
Usability test & analysis helps determine whether project is further iterated or goes into production. |