According to the insights of the authority Alan Davis in demand, only a single need to provide completeness of demand.
Solution (Davis 1995), you need to combine the needs of the text and the needs of the graphic representation, and draw the expected expectations.
The complete description of the system and helps you detect inconsistency, fuzziness, errors, and omissions. These graphical representations or points
Analysis models can enhance your understanding of system requirements. Between the participants of the project, for some types of information, graphical delivery
Comparative text interaction is more efficient and can clear language and vocabulary between languages between different development group members.
Software Demand Specifications (SRS) did not fully tell us to ensure that all aspects required for understanding the system are not guaranteed
We have not missed a need or not to make any mistakes.
Models of graphical representation of demand include:
(1) Data flow map (D f d), (2) entity relationship diagram (E R d), (3) state transformation map (S t D), (4) dialog Figure (5) class diagram.
