PROJECT DRIVERS |
1 | The Purpose of the Project |
| | 1a | The user business or background of the project effort |
| | 1b | Goals of the project |
2 | Client, Customer, and Other Stakeholders |
| | 2a | The client |
| | 2b | The customer |
| | 2c | Other stakeholders |
3 | Users of the Product |
| | 3a | The hands-on users of the product |
| | 3b | Priorities assigned to users |
| | 3c | User participation |
| | 3d | Maintenance users and service technicians |
PROJECT CONSTRAINTS |
4 | Mandated Constraints |
| | 4a | Solution constraints |
| | 4b | Implementation environment of the current system |
| | 4c | Partner or collaborative applications |
| | 4d | Off-the-shelf software |
| | 4e | Anticipated workplace environment |
| | 4f | Schedule constraints |
| | 4g | Budget constraints |
5 | Naming Conventions and Definitions |
| | 5a | Definitions of all terms, including acronyms, used in the project |
| | 5b | Data dictionary for any included models |
6 | Relevant Facts and Assumptions |
| | 6a | Facts |
| | 6b | Assumptions |
7 | The Scope of the Work |
| | 7a | The current situation |
| | 7b | The context of the work |
| | 7c | Work partitioning |
8 | The Scope of the Product |
| | 8a | Product boundary |
| | 8b | Product use case list |
| | 8c | Individual product use cases |
FUNCTIONAL REQUIREMENTS |
9 | Functional and Data Requirements |
| | 9a | Functional requirements |
| | 9b | Data requirements |
NONFUNCTIONAL REQUIREMENTS |
10 | Look and Feel Requirements |
| | 10a | Appearance requirements |
| | 10b | Style requirements |
11 | Usability and Humanity Requirements |
| | 11a | Ease of use requirements |
| | Fit Criterion |
| | 11b | Personalization and internationalization requirements |
| | 11c | Learning requirements |
| | 11d | Understandability and politeness requirements |
| | 11e | Accessibility requirements |
12 | Performance Requirements |
| | 12a | Speed and latency requirements |
| | 12b | Safety critical requirements |
| | 12c | Precision or accuracy requirements |
| | 12d | Reliability and availability requirements |
| | 12e | Robustness or fault tolerance requirements |
| | 12f | Capacity requirements |
| | 12g | Scalability or extensibility requirements |
| | 12h | Longevity requirements |
13 | Operational and Environmental Requirements |
| | 13a | Expected physical environment |
| | 13b | Requirements for interfacing with adjacent systems |
| | 13c | Productization requirements |
| | 13d | Release requirements |
14 | Maintainability and Support Requirements |
| | 14a | Maintenance requirements |
| | 14b | Supportability requirements |
| | 14c | Adaptability requirements |
15 | Security Requirements |
| | 15a | Access requirements |
| | 15b | Integrity requirements |
| | 15c | Privacy requirements |
| | 15d | Audit requirements |
| | 15e | Immunity requirements |
16 | Cultural and Political Requirements |
| | 16a | Cultural requirements |
| | 16b | Political requirements |
17 | Legal Requirements |
| | 17a | Compliance requirements |
| | 17b | Standards requirements |
PROJECT ISSUES |
18 | Open Issues |
19 | Off-the-Shelf Solutions |
| | 19a | Ready-made products |
| | 19b | Reusable components |
| | 19c | Products that can be copied |
20 | New Problems |
| | 20a | Effects on the current environment |
| | 20b | Effects on the installed systems |
| | 20c | Potential user problems |
| | 20d | Limitations in the anticipated implementation environment that may inhibit the new product |
| | 20e | Follow-up problems |
21 | Tasks |
| | 21a | Project planning |
| | 21b | Planning of the development phases |
22 | Migration to the New Product |
| | 22a | Requirements for migration to the new product |
| | 22b | What data has to be modified/translated for the new system? |
23 | Risks |
24 | Costs |
25 | User Documentation and Training |
| | 25a | User documentation requirements |
| | 25b | Training requirements |
26 | Waiting Room |
27 | Ideas for Solutions |
