Scribd
Upload
6 views4 pages

Presentation 2

Uploaded by

mrai48851
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views4 pages

Presentation 2

Uploaded by

mrai48851
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Importance of Modeling

We build models so that we can better understand the system we are developing.
Through modeling, we achieve four aims:

• Models help us to visualize a system as it is or as we want it to be.


• Models permit us to specify the structure or behavior of a system.
• Models gives us a template that guides us in constructing a system.
• Models document the decisions we have made.
A model is a simplification of reality.

We build models so that we can better understand the system we are


developing.

We build models of complex systems because we cannot comprehend such a


system in its entirety.

Every project can benefit from modeling. Modeling can help the
development team better visualize the plan of their system and allow them
to develop more rapidly by helping them build the right thing. The more
complex your project, the more likely it is that you will fail or that you will
build the wrong thing if you do on modeling at all.
Principles of Modeling
1. The choice of model is important
The choice of what models to create has a profound influence on how a problem is attacked and how
a solution is shaped. We need to choose your models well.

• The right models will highlight the most critical development problems.
• Wrong models will mislead you, causing you to focus on irrelevant issues.
For Example: We can use different types of diagrams for different phases in software development.

2. Every model may be expressed at different levels of precision.

Sometimes, a quick and simple executable model of the user interface is exactly what you need. At
other times, you have to get down to complex details such as cross-system interfaces or networking
issues etc.

In any case, the best kinds of models are those that let you choose your degree of detail, depending
on who is viewing it. An analyst or an end user will want to focus on issues of what and a developer
will want to focus on issues of how.
3.The best models are connected to reality.

In software, the gap between the analysis model and the system’s design model must be less. Failing to bridge this gap
causes the system to diverge over time. In object-oriented systems, it is possible to connect all the nearly independent views
of a system into one whole.

4.No single model is sufficient.

Every non-trivial system is best approached through a small set of nearly independent models.

In the case of a building, you can study electrical plans in isolation, but you can also see their mapping to the floor plan and
perhaps even their interaction with the routing of pipes in the plumbing plan.

You might also like