|
Requirement Document
This follows the IEEE/ANSI 830-1993 standarts
- Introduction
- Purpose of the requirements document:
- who this will help
- why this project is important
- why it was requested
- Scope of product
- what it is suppose to do
- what is it not going to do
- Definitions, acronyms and abbreviations
- References
- Overview of remainder of the document
- General description
- Product overview
- Introductary paragraph
- Data flow diagram
- Paragraph(s) descriptins of every part of the data flos diagram
- Product functions
- Structure chart
- Paragraph description of every node in the structure chart.
describe what it is, what it does and why it is important
- Simple table of all features with discussion
- User characteristics
- General constraints
- Assumptions and dependencies
- Risks
- risk assesment
- risk control
- Specific requirements ***
- Interface requirement
- User interface
- Menu map
- Picture of all major windows
- Hardware interface
- Software interface
- Communication interface
- Functional requirement
- Performance requirement
- Logical database requirement
-for each database, we must give the following:
- Database name
- Rationale
- Where it will be used
- Data dictionnary
- Entity relationship diagram
- Design constrains
- Software and system attributes
- Organizational requirements
- Formal cost, time and ressources estimate
- Appendices (optional)
- Index
*** In this section, everything should be written following this "Style"
i.0 Title
i.1 One sentence description
i.2 Paragraph description
i.3 List of steps or points (optional)
i.4 Rationale
i.5 Optional diagram
|