Object-Oriented Software Engineering

Using UML, Patterns, and Java Chapter 1: Introduction

Requirements for this Class

 You are proficient in a programming language, but you have no

experience in analysis or design of a system

 You want to learn more about the technical aspects of analysis and
design of complex software systems

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2
Objectives of the Class

 Appreciate Software Engineering:

 Build complex software systems in the context of frequent change
 Understand how to
 produce a high quality software system within time
 while dealing with complexity and change
 Acquire technical knowledge (main emphasis)
 Acquire managerial knowledge

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3
Acquire Technical Knowledge

 Understand System Modeling

 Learn UML (Unified Modeling Language)
 Learn different modeling methods:
 Use Case modeling
 Object Modeling
 Dynamic Modeling
 Issue Modeling
 Learn how to use Tools:
 CASE (Computer Aided Software Engineering)
 Tool: Together-J
 Component-Based Software Engineering
 Learn how to use Design Patterns and Frameworks

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4
Acquire Managerial Knowledge
 Understand the Software Lifecycle
 Process vs Product
 Learn about different software lifecycles
 Greenfield Engineering, Interface Engineering, Reengineering

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5
Readings

 Required:
 Bernd Bruegge, Allen Dutoit: “Object-Oriented Software Engineering:
Using UML, Patterns, and Java”, Prentice Hall, 2003.
 Recommended:
 I. Sommerville. Software Engineering. Prentice Hall
 UML e Unified Process. Analisi e Progettazione Object Oriented. J. Arlow
e I. Neustadt. McGraw-Hill
 J. Rumbaugh,I. Jacobson, G. Booch. The Unified Modeling Languge
Reference Manual. Addison Wesley

 (Per studenti v.o.) A. Guidi, D. Bordolò. Guida a SQL. Apogeo

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6
Outline of Today’s Lecture

 High quality software: State of the art

 Modeling complex systems
 Functional vs. object-oriented decomposition
 Dealing with change:
 Software lifecycle modeling
 Concluding remarks

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7
Can you develop this?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8
Limitations of Non-engineered Software

Requirements

Here is the problem!!

Software

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9
Software Production has a Poor Track Record
Example: Space Shuttle Software
 Cost: $10 Billion, millions of dollars more than planned
 Time: 3 years late
 Quality: First launch of Columbia was cancelled because of a
synchronization problem with the Shuttle's 5 onboard computers.
 Error was traced back to a change made 2 years earlier when a
programmer changed a delay factor in an interrupt handler from 50 to 80
milliseconds.
 The likelihood of the error was small enough, that the error caused no
harm during thousands of hours of testing.
 Substantial errors still exist.
 Astronauts are supplied with a book of known software problems
"Program Notes and Waivers".

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10
Software Engineering: A Problem Solving Activity

 Analysis: Understand the nature of the problem and break the

problem into pieces
 Synthesis: Put the pieces together into a large structure

For problem solving we use

 Techniques (methods):
 Formal procedures for producing results using some well-defined
notation
 Methodologies:
 Collection of techniques applied across software development and unified
by a philosophical approach
 Tools:
 Instrument or automated systems to accomplish a technique

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11
Software Engineering: Definition

Software Engineering is a collection of techniques,

methodologies and tools that help with the production of

 a high quality software system

 with a given budget
 before a given deadline

while change occurs.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12 20
Scientist vs Engineer

 Computer Scientist
 Proves theorems about algorithms, designs languages, defines knowledge
representation schemes
 Has infinite time…
 Engineer
 Develops a solution for an application-specific problem for a client
 Uses computers & languages, tools, techniques and methods
 Has finite (usually enough) time…
 Software Engineer
 Works in multiple application domains
 Has only 3 months...
 …while changes occurs in requirements and available technology

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13
Factors affecting the quality of a software system

 Complexity:
 The system is so complex that no single programmer can understand it
anymore
 The introduction of one bug fix causes another bug

 Change:
 The “Entropy” of a software system increases with each change: Each
implemented change erodes the structure of the system which makes the next
change even more expensive (“Second Law of Software Dynamics”).
 As time goes on, the cost to implement a change will be too high, and the
system will then be unable to support its intended task. This is true of all
systems, independent of their application domain or technological base.

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14
Why are software systems so complex?

 The problem domain is difficult

 The development process is very difficult to manage
 Software offers extreme flexibility
 Software is a discrete system
 Continuous systems have no hidden surprises (Parnas)
 Discrete systems have!

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 15
Dealing with Complexity

1. Abstraction
2. Decomposition
3. Hierarchy

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 16
1. Abstraction

 Inherent human limitation to deal with complexity

 The 7 +- 2 phenomena
 Chunking: Group collection of objects
 Ignore unessential details: => Models

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 18
Models are used to provide abstractions

 System Model:
 Object Model: What is the structure of the system? What are the objects
and how are they related?
 Functional model: What are the functions of the system? How is data
flowing through the system?
 Dynamic model: How does the system react to external events? How is the
event flow in the system ?
 Task Model:
 PERT Chart: What are the dependencies between the tasks?
 Schedule: How can this be done within the time limit?
 Org Chart: What are the roles in the project or organization?
 Issues Model:
 What are the open and closed issues? What constraints were posed by the
client? What resolutions were made?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 19
Interdependencies of the Models

System Model (Structure,

Functionality,
Dynamic Behavior)

Issue Model
(Proposals, Task Model
Arguments, (Organization,
Resolutions) Activities
Schedule)

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 20
Model-based software Engineering:
Code is a derivation of object model
Pr oblem Statement : A stock exchange lists many companies.
Each company is identified by a ticker symbol
Analysis phase results in cbject model (UML Class Diagram):
StockExchange * * Company
Lists tickerSymbol

Implementation phase results in code

public class StockExchange
{

public Vector m_Company = new Vector();

};

public class Company

{

public int m_tickerSymbol

public Vector m_StockExchange = new Vector();

};

AAgood
goodsoftware
softwareengineer
engineerwrites
writesas
aslittle
littlecode
codeas
aspossible
possible
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 22
2. Decomposition

 A technique used to master complexity (“divide and conquer”)

 Functional decomposition
 The system is decomposed into modules
 Each module is a major processing step (function) in the application
domain
 Modules can be decomposed into smaller modules
 Object-oriented decomposition
 The system is decomposed into classes (“objects”)
 Each class is a major abstraction in the application domain
 Classes can be decomposed into smaller classes

Which decomposition is the right one?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 25
Functional Decomposition
System
Function Top Level functions

Produce
Read Input Transform Level 1 functions
Output

Produce Level 2 functions

Read Input Transform
Output

Load R10 Add R1, R10 Machine Instructions

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 26
Functional Decomposition

 Functionality is spread all over the system

 Maintainer must understand the whole system to make a single
change to the system
 Consequence:
 Codes are hard to understand
 Code that is complex and impossible to maintain
 User interface is often awkward and non-intuitive

 Example: Microsoft Powerpoint’s Autoshapes

(see next page)

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 27
Functional Decomposition: Autoshape
Autoshape

Mouse Change Draw

click

Change Change Change

Rectangle Oval Circle

Draw Draw Draw

Rectangle Oval Circle

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 28
What is This?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 29
Model of an Eskimo
Eskimo
Size
Dress()
Smile()
Sleep()

Shoe
* Coat
Size Size
Color Color
Type Type
Wear() Wear()

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 30
Iterative Modeling then leads to ....
lives in
Eskimo
Size Outside
Dress() moves Temperature
Cave around Light
Smile()
Lighting Sleep() Season
Enter() Hunt()
Leave() Organize()

*
Entrance

Windhole MainEntrance
Diameter Size

but is it the right model?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 31
Alternative Model: The Head of an Indian

Indian
Hair
Dress()
Smile()
Sleep()

Face Mouth
Ear Nose NrOfTeeths
Size * smile() Size
open()
listen() close_eye()
speak()

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 32
Class Identification

 Class identification is crucial to object-oriented modeling

 Basic assumption:
1. We can find the classes for a new software system: We call this
Greenfield Engineering
2. We can identify the classes in an existing system: We call this
Reengineering
3. We can create a class-based interface to any system: We call this
Interface Engineering
 Why can we do this? Philosophy, science, experimental evidence
 What are the limitations? Depending on the purpose of the system
different objects might be found
 How can we identify the purpose of a system?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 33
What is this Thing?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 34
Modeling a Briefcase

BriefCase

Capacity: Integer
Weight: Integer

Open()
Close()
Carry()

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 35
A new Use for a Briefcase

BriefCase

Capacity: Integer
Weight: Integer

Open()
Close()
Carry()
SitOnIt()

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 36
Questions

 Why did we model the thing as “Briefcase”?

 Why did we not model it as a chair?
 What do we do if the SitOnIt() operation is the most
frequently used operation?
 The briefcase is only used for sitting on it. It is never
opened nor closed.
 Is it a “Chair”or a “Briefcase”?
 How long shall we live with our modeling mistake?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 37
3. Hierarchy

 We got abstractions and decomposition

 This leads us to chunks (classes, objects) which we view with object model
 Another way to deal with complexity is to provide simple
relationships between the chunks
 One of the most important relationships is hierarchy
 2 important hierarchies
 "Part of" hierarchy
 "Is-kind-of" hierarchy

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 38
Part of Hierarchy

Computer

I/O Devices CPU Memory

Cache ALU Program

Counter

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 39
Is-Kind-of Hierarchy (Taxonomy)

Cell

Muscle Cell Blood Cell Nerve Cell

Striate Smooth Red White Cortical Pyramidal

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 40
So where are we right now?

 Three ways to deal with complexity:

 Abstraction
 Decomposition
 Hierarchy
 Object-oriented decomposition is a good methodology
 Unfortunately, depending on the purpose of the system, different objects
can be found
 How can we do it right?
 Many different possibilities
 Our current approach: Start with a description of the functionality (Use
case model), then proceed to the object model
 This leads us to the software lifecycle

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 41
Software Lifecycle Activities ...and their models

Requirements System Object Implemen-

Analysis Testing
Elicitation Design Design tation

Implemented
Expressed in Terms By
Structured By Realized By
Of Verified
By

class...
class...
class... ?
class....?
Use Case Application Solution
Domain Subsystems Source Test
Model Domain
Objects Code Cases
Objects

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 42
Software Lifecycle Definition

 Software lifecycle:
 Set of activities and their relationships to each other to support the
development of a software system

 Typical Lifecycle questions:

 Which activities should I select for the software project?
 What are the dependencies between activities?
 How should I schedule the activities?

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 43
Reusability

 A good software design solves a specific problem but is general

enough to address future problems (for example, changing
requirements)
 Experts do not solve every problem from first principles
 They reuse solutions that have worked for them in the past

 Goal for the software engineer:

 Design the software to be reusable across application domains and designs

 How?
 Use design patterns and frameworks whenever possible

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 44
Design Patterns and Frameworks

 Design Pattern:
 A small set of classes that provide a template solution to a recurring
design problem
 Reusable design knowledge on a higher level than datastructures (link
lists, binary trees, etc)
 Framework:
 A moderately large set of classes that collaborate to carry out a set of
responsibilities in an application domain.
 Examples: User Interface Builder
 Provide architectural guidance during the design phase
 Provide a foundation for software components industry

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 45
Patterns are used by many people

 Chess Master:  Software Engineer

 Openings  Composite Pattern: A collection of
 Middle games objects needs to be treated like a
single object
 End games
 Adapter Pattern (Wrapper):
 Writer Interface to an existing system
 Tragically Flawed Hero (Macbeth,  Bridge Pattern: Interface to an
Hamlet) existing system, but allow it to be
 Romantic Novel extensible
 User Manual
 Architect
 Office Building
 Commercial Building
 Private Home

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 46
Summary

 Software engineering is a problem solving activity

 Developing quality software for a complex problem within a limited time
while things are changing
 There are many ways to deal with complexity
 Modeling, decomposition, abstraction, hierarchy
 Issue models: Show the negotiation aspects
 System models: Show the technical aspects
 Task models: Show the project management aspects
 Use Patterns: Reduce complexity even further
 Many ways to do deal with change
 Tailor the software lifecycle to deal with changing project conditions
 Use a nonlinear software lifecycle to deal with changing requirements or
changing technology
 Provide configuration management to deal with changing entities

Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 47