In any development of projects, the main focus of analysis and design activities is
on models, which are usually both abstract and visible. Many of the products are
themselves abstract in nature. Most s/w is not tangible for the user. Generally a s/w is
usually constructed by teams of people who need to see each others models. So we
need to prepare models understandable by everyone in the development team.
- A model is a quicker and easier to build.
- A model can be used in simulations to learn more about things in representation.
- A model gives clear understanding of a problem.
- A model is an abstraction ,mean we can choose which are to be represented, and
which are to be suppressed.
- A model can represent real or imaginary things from any domain.
- A useful model has just the right amount of detail and structure.
The main purpose of a model is to represent functional and non-functional
requirements. The whole requirement model must be accurate, complete and
unambiguous. This does not include premature conditions about how new
system fulfils user requests.
These diagrammatical models are helpful
- To communicate ideas.
- To generate new ideas and possibilities.
- To test ideas and more predictions.
- To understand structures and relationships.
If a system is very simple it may be possible to model it with a single diagram
and supporting textual descriptions. But most systems are complete and may
require many diagrams fully to capture that complexity.
Now bringing you back...
Does that email address look wrong? Try again with a different email.