- What: Work of Analysis -> "What" the system will do.
- How: Work of Design -> "How" the system will do.
- If you want to talk about "what" a computer system does you must talk about the domain of its application and use, and not about the computer system itself.
- If you are talking about the processes and the data streams inside the computer, or if you are talking about the structure and states of the database, you are not talking about the "what": you are talking about the "how".
- User Requirements Document (URD)
- Part 1: General Description.
- Information that relates to the overall capability need, the background and the operational context.
- It contains information that relates to the overall capability need and records the background and operational context.
- It also provides sufficient information about the project management context that will be used to deliver it, including any assumptions and constraints.
- Part 2: Key User Requirements
- Part 3: Individual Capability Requirements and Constraints
- The complete, structured, set of individual user requirements and constraints.
- A hierarchical structure to organise the individual requirements.
- The complete set of individual user requirements and constraints.
- Evidence that the Single Statement of User Need (SSON) is fully described and based on capability planning.
- Part 4: Context Documents
- Context documents and supporting papers that make the URD self-contained.
- Doctrine papers.
- Concept of Employment
- Requirements Definition Study
- Use Study
- Needs and Numbers Studies
- Other supporting gap analysis or force development studies, Operational Analysis (OA), Exercise and Operation Reports etc.
- The related Through Life Management Plan (TLMP) and Master Data and Assumptions List (MDAL).
- Part 5: Glossary
- Definitions and explanations for all terms that could cause confusion.
- The Glossary should include definitions and explanations for all terms that could cause confusion, as well as references and acronyms.