The analysis model and requirements specification provide a means for assessing quality
once the software is built. Requirements analysis results in the specification of software‘s
operational characteristics.
The analysis model is a bridge between the system description and the design model.
Objectives Analysis model must achieve three primary objectives: Describe Customer
needs Establish a basis for software design Define a set of requirements that can be
validated once the software is built.
Analysis Rules of Thumb
The model should focus on requirements that are visible within the problem or
business domain. The level of abstraction should be relatively high.
Each element of the analysis model should add to overall understanding of software
requirements and provide insight into the information, function, and behavior
domains of the system.
Delay consideration of infrastructure and other non-functional models until design.
For example, a database may be required, but the classes necessary to implement
it, the functions required to access it, and the behavior that will be exhibited as it
is used should be considered only after problem domain analysis has been
completed.
Minimize coupling throughout the system.
The level of interconnectedness between classes and functions should be reduced
to a minimum.
Be certain that the analysis model provides value to all stakeholders.
Each constituent has its own use for the model.
Keep the model as simple as it can be.
Ex: Don't add additional diagrams when they provide no new information.
Only modeling elements that have values should be implemented.