0% found this document useful (0 votes)
71 views9 pages

OOAD Lec 1

This document discusses modeling and why it is important for software development. It makes three key points: 1. Modeling is a proven technique that helps visualize, specify, and document systems. Through modeling, complex systems can be better understood by focusing on one aspect at a time. 2. A good model simplifies reality and provides a blueprint of a system. Modeling aims to help visualize systems, specify their structure and behavior, guide system construction, and document design decisions. 3. Modeling is important for complex systems because the human ability to comprehend complexity is limited. Models allow developers to narrow their focus and illuminate problems to find better solutions.

Uploaded by

Shanto
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
0% found this document useful (0 votes)
71 views9 pages

OOAD Lec 1

This document discusses modeling and why it is important for software development. It makes three key points: 1. Modeling is a proven technique that helps visualize, specify, and document systems. Through modeling, complex systems can be better understood by focusing on one aspect at a time. 2. A good model simplifies reality and provides a blueprint of a system. Modeling aims to help visualize systems, specify their structure and behavior, guide system construction, and document design decisions. 3. Modeling is important for complex systems because the human ability to comprehend complexity is limited. Models allow developers to narrow their focus and illuminate problems to find better solutions.

Uploaded by

Shanto
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/ 9

Lecture 1: Why we model

Chapter 1
The Unified Modeling Language User Guide
SECOND EDITION
By Grady Booch, James Rumbaugh, Ivar Jacobson
What is a System?
• A system has a specific set of objectives.
• Components of a system work together to achieve those
objectives within a limited boundary.
• Components are given a specific set of tasks/
responsibilities.
• Components are related with each other and communicate
with each other based on the type of the relationships.
Quality of a System
• Objectives must be well defined and specific
• Components must have well defined and specific
responsibilities that they can perform independently.
• Communication among components should be as minimum as
possible; only on need basis to transfer the output of one
component to another component.
Why we model?
• Modelling is a proven and well-accepted engineering
technique.
• Unsuccessful software projects fail in their own unique ways,
but all successful projects are alike in many ways.
• There are many elements that contribute to a successful
software organization; one common thread is the use of
modelling.
• We do model so that we can better understand the system we
are developing.
What is a Model?
• A model is a simplification of reality
• A model provides the blueprints of a system.

• Benefits of Model:
• Through modelling we achieve four aims:
1. Models help us to visualize a system as it is or as we want it to be
2. Models permit us to specify the structure or behaviour of a system
3. Models give us a template that guides us in constructing a system
4. Models document the decisions we have made
Limitation of Human Ability
• The larger and more complex the system, the more important
modelling becomes, for one very simple reason:
– We build models of complex systems because we cannot comprehend
such a system in its entirety.
• There are limits to the human ability to understand complexity.
Through modelling we narrow the problem we are studying by
focusing on only one aspect at a time.
Principles of Modelling
1. The choice of what models to create has a profound influence on how a
problem is attacked and how a solution is shaped.
• In other words, choose models intelligently. The right models will illuminate
the wicked development problems.
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, one has to get down and dirty with the
bits. In any case, the best kinds of models are those that let you choose your
degree of detail, depending on who is viewing and why they need to view it.
Principles of Modelling
3. The best models are connected to reality.
– A Model connected to reality makes it more understandable and
presentable. The more abstract a model is the more it needs to be
closer to reality.
4. No single model is sufficient.
– Every nontrivial system is best approached through a small set of
nearly independent models.
Perspective of design - example

You might also like