Object-Oriented Software

Development using UML

Dr. Nagy Ramadan

Email: nagyrd@[Link]

1
 Professional Diploma in Software Engineering
‫دبلوم مهني في هندسة البرمجيات‬
‫الفصل الدراسي األول‬
‫ البرمجة في األنظمة الكبيرة‬-1
1- Programming in the Large
‫ مبادئ نظم الحاسب والبرمجة‬-2
2- Computer Systems Principles and Programming
‫ نظم قواعد البيانات العالقية‬-3
3- Relational Database Systems
‫ تطوير البرمجيات شيئية التوجه‬-4
4- Object-Oriented Software Development using UML
‫ ادارة مشروعات البرمجيات‬-5
5- Software Project Management
 Professional Diploma in Software Engineering
‫دبلوم مهني في هندسة البرمجيات‬
‫الفصل الدراسي الثاني‬
‫ تصميم بينية المستخدم‬-1
1- The User Interface Design
‫ تصميم مواقع الويب‬-2
2- Web Design and Architecture
‫ عملية البرمجة‬-3
3- The Software Process
‫ التطوير الرشيق للبرمجبات‬-4
4- Agile Software Development
‫ مشروع‬-5
5- Project
Object-Oriented Software Development using UML
Course Aims
 This course focuses on the organizing ideas of software
design and construction.
 Because software systems are highly complex structures,
special effort and techniques are needed to control that
complexity and make them understandable by humans, not
simply machines.
 Taking this course will teach such techniques, which are
common to good software engineering design, independent
of the programming language, and include building
abstractions to hide details, separating specification from
implementation and establishing conventional interfaces to
allow the creation of standard modules.
 References

Lethbridge and Laganiere, “Object-Oriented

Software Engineering: Practical Software
Development Using UML and Java”, Second
Edition, McGraw Hill, 2005.

UML Notes based on Bruegge, Bernd and Dutoit,

Allen H., “Object-Oriented Software Engineering: Using
UML, Patterns, and Java”, Second Edition, Pearson
Education Limited, 2004.

5
 Evaluation Scheme
Evaluation Item Marks Total

Final Exam 40 40

Mid-Term Exam 30

Quiz 10
60
Assignments/Projects 15

Attendance/Class Participation 5

6
 Object-Oriented Software Engineering
Practical Software Development using UML and Java

Chapter 1:
Software and Software Engineering
1.1 The Nature of Software...

Software is intangible
• Hard to understand development effort
Software is easy to reproduce
• Cost is in its development
—in other engineering products, manufacturing is the
costly stage
The industry is labor-intensive
• Hard to automate

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 8

Types of Software...

Custom
• For a specific customer
Generic
• Sold on open market
• Often called
—COTS (Commercial Off The Shelf)
—Shrink-wrapped
Embedded
• Built into hardware
• Hard to change

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 9

Types of Software

Real time software

• E.g. control and monitoring systems
• Must react immediately
• Safety often a concern
Data processing software
• Used to run businesses
• Accuracy and security of data are key

Some software has both aspects

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 10

1.2 What is Software Engineering?...

The process of solving customers’ problems by the

systematic development and evolution of large, high-
quality software systems within cost, time and other
constraints

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 11

What is Software Engineering?…

Solving customers’ problems

• This is the goal of software engineering
• Sometimes the solution is to buy, not build
• Adding unnecessary features does not help solve the
problem
• Software engineers must communicate effectively to
identify and understand the problem

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 12

What is Software Engineering?…

Systematic development and evolution

• An engineering process involves applying well
understood techniques in a organized and disciplined
way
• Many well-accepted practices have been formally
standardized
—e.g. by the IEEE or ISO
• Most development work is evolution

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 13

What is Software Engineering?…

Large, high quality software systems

• Software engineering techniques are needed because large
systems cannot be completely understood by one person
• Teamwork and co-ordination are required
• Key challenge: Dividing up the work and ensuring that the
parts of the system work properly together
• The end-product must be of sufficient quality

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 14

What is Software Engineering?

Cost, time and other constraints

• Finite resources
• The benefit must outweigh the cost
• Others are competing to do the job cheaper and faster
• Inaccurate estimates of cost and time have caused many
project failures

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 15

1.3 Software Engineering and the
Engineering Profession
The term Software Engineering was coined in 1968
• People began to realize that the principles of engineering
should be applied to software development

Engineering is a licensed profession

• In order to protect the public
• Engineers design artifacts following well accepted
practices which involve the application of science,
mathematics and economics
• Ethical practice is also a key tenet of the profession

In many countries, much software engineering does not

require an engineering licence, but is still engineering

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 16

Software Engineering and the Engineering
Profession
Ethics in Software Engineering:

Software engineers shall

• Act consistently with public interest
• Act in the best interests of their clients
• Develop and maintain with the highest standards possible
• Maintain integrity and independence
• Promote an ethical approach in management
• Advance the integrity and reputation of the profession
• Be fair and supportive to colleagues
• Participate in lifelong learning

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 17

1.4 Stakeholders in Software Engineering

1. Users
• Those who use the software
2. Customers
• Those who pay for the software
3. Software developers
4. Development Managers

All four roles can be fulfilled by the same person

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 18

1.5 Software Quality...
Usability
• Users can learn it and fast and get their job done easily
Efficiency
• It doesn’t waste resources such as CPU time and
memory
Reliability
• It does what it is required to do without failing
Maintainability
• It can be easily changed
Reusability
• Its parts can be used in other projects, so reprogramming
is not needed
© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 19
Software Quality and the Stakeholders
Customer: User:
solves problems at easy to learn;
an acceptable cost in efficient to use;
terms of money paid and helps get work done
resources used

QUALITY
SOFTWARE

Developer: Development manager:

easy to design; sells more and
easy to maintain; pleases customers
easy to reuse its parts while costing less
to develop and maintain

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 20

Software Quality: Conflicts and Objectives

The different qualities can conflict

• Increasing efficiency can reduce maintainability or
reusability
• Increasing usability can reduce efficiency
Setting objectives for quality is a key engineering
activity
• You then design to meet the objectives
• Avoids ‘over-engineering’ which wastes money
Optimizing is also sometimes necessary
• E.g. obtain the highest possible reliability using a fixed
budget

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 21

1.6 Software Engineering Projects

Most projects are evolutionary or maintenance projects,

involving work on legacy systems
• Corrective projects: fixing defects
• Adaptive projects: changing the system in response to
changes in
—Operating system
—Database
—Rules and regulations
• Enhancement projects: adding new features for users
• Reengineering or perfective projects: changing the
system internally so it is more maintainable

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 22

Software Engineering Projects

‘Green field’ projects

• New development
• The minority of projects

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 23

Software Engineering Projects

Projects that involve building on a framework or a set of

existing components.
• A framework is an application that is missing some
important details.
—E.g. Specific rules of this organization.
• Such projects:
—Involve plugging together components that are:
- Already developed.
- Provide significant functionality.
—Benefit from reusing reliable software.
—Provide much of the same freedom to innovate
found in green field development.

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 24

1.7 Activities Common to Software
Projects...
Requirements and specification
• Includes
—Domain analysis
—Defining the problem
—Requirements gathering
- Obtaining input from as many sources as possible
—Requirements analysis
- Organizing the information
—Requirements specification
- Writing detailed instructions about how the software should
behave

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 25

Activities Common to Software Projects...

Design
• Deciding how the requirements should be implemented,
using the available technology
• Includes:
—Systems engineering: Deciding what should be in
hardware and what in software
—Software architecture: Dividing the system into
subsystems and deciding how the subsystems will
interact
—Detailed design of the internals of a subsystem
—User interface design
—Design of databases

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 26

Activities Common to Software Projects

Modeling
• Creating representations of the domain or the software
—Use case modeling
—Structural modeling
—Dynamic and behavioural modeling
Programming
Quality assurance
• Reviews and inspections
• Testing
Deployment
Managing the process

© Lethbridge/Laganière 2005 Chapter 1: Software and Software Engineering 27