Content deleted Content added
→Stage 3 - Requirements specification: This has been bad for some while - someone should reread the whole thing from time to time! |
|||
Line 98:
This is probably the most complex stage in SSADM. Using the requirements developed in stage 1 and working within the framework of the selected business option, the analyst must develop a full logical specification of what the new system must do. The specification must be free from error, ambiguity and inconsistency. By logical, we mean that the specification does not say how the system will be implemented but rather describes what the system will do.
To produce the logical specification, the analyst builds the required logical models for both the [[Data flow diagram|data-flow diagrams]] (DFDs) and the [[Entity-relationship model|entity relationship diagrams]] (ERDs). These are used to produce function definitions of every function which the users will require of the system, entity life-histories (ELHs) and effect correspondence diagrams, these are models of how each event interacts with the system, a complement to entity life-histories. These are continually matched against the requirements and where necessary, the requirements are added to and completed.
The product of this stage is a complete Requirements Specification document which is made up of:
| |||