Software Engineering

Aida Bitri, PhD

[email protected]
Course Objective

- This course presents contemporary issues related to the field of

software engineering.

- It deeply examines the software life cycle models, including

phases of requirements specification, design, development, test,
and maintain.

- Object-oriented design methods (UML) and practices, their

application to the development of computer-based systems.

- Particular emphasis is on a team project in which a group of

students implement a system from its specification.
Course Outline

Week Topic Weeks

1 Intro to software engineering, Software processes. 20.02.2024

2 SDLC/ Waterfall Model & Boehm Spiral. 27.02.2024
3 Agile Development. Extreme Programming & Scrum software process. 05.03.2024
Requirements Engineering. Understanding of functional and non-functional
4 12.03.2024
requirements.
5 Requirements Modeling. Composition of the requirements document. 19.03.2024
6 System Modeling. Model Driven Engineering. 26.03.2024
7 System Modeling. Model Driven Engineering. II 02.04.2024
8 Architectural Design 09.04.2024
9 Mid-term 15-20.04.2024
10 Software Testing. System testing & component testing. 23.04.2024
Maintenance and Reengineering. Connecting software lifecycle with software 30.04.2024
11
evolution.
12 Project Management 07.05.2024
13 Project planning 14.05.2024
14 Project Presentations 21.05.2024
Course Description: Materials

Course Materials

TextBook: PPT Lecture Notes

Other references:
- Software Engineering by Ian Sommerville,10th edition Pearson,2015; Software
Engineering : A practitioner’s Approach, 8th Edition by Roger Pressman.
Course Description

Course Materials
• Plagiarism will not be tolerated. You may discuss class material and general
solution strategies with classmates, but when it comes to formulating/programming
homework problems solutions, you must work alone.

• Instances of academic dishonesty will be dealt with harshly.

• If necessary, disciplinary actions will be taken.
• Disturbing behavior in the class is not allowed, disciplinary actions will be
taken.
• Misbehavior reports during examinations means that automatically you will
be graded 0 points.

• If you have a disability and need any accommodation, please let me know.
Course Evaluation Criteria

Your final grade is determined by a weighted average of the grades you receive on the
following activities:

COURSE EVALUATION CRITERIA

Method Quantity Percentage
Midterm Exam 1 40
Final Exam 1 30
Project 1 30
Total Percent: 100%
Chapter 1- Introduction

Lecture 1
Software engineering

 The economies of ALL developed nations are

dependent on software.
 More and more systems are software controlled
 Software engineering is concerned with theories,
methods and tools for professional software
development.
 Expenditure on software represents a
significant fraction of GNP in all developed countries.
Software costs

 Software costs often dominate computer system costs.

The costs of software on a PC are often greater than the
hardware cost.
 Software costs more to maintain than it does to develop.
For systems with a long life, maintenance costs may be
several times development costs.
 Software engineering is concerned with cost-effective
software development.
Software products

 Generic products
▪ Stand-alone systems that are marketed and sold to any customer who
wishes to buy them.
▪ Examples – PC software such as graphics programs, project management
tools; CAD software; software for specific markets such as appointments
systems for dentists.
▪ The specification of what the software should do is owned by the software
developer and decisions on software change are made by the developer.
 Customized products
▪ Software that is commissioned by a specific customer to meet their own
needs.
▪ Examples – embedded control systems, air traffic control software, traffic
monitoring systems.
▪ The specification of what the software should do is owned by the customer
for the software and they make decisions on software changes that are
required.
Chapter 1 Introduction 11
Essential attributes of good software

Product characteristic Description

Maintainability Software should be written in such a way so that it can evolve to

meet the changing needs of customers. This is a critical attribute
because software change is an inevitable requirement of a
changing business environment.
Dependability and Software dependability includes a range of characteristics
security including reliability, security and safety. Dependable software
should not cause physical or economic damage in the event of
system failure. Malicious users should not be able to access or
damage the system.
Efficiency Software should not make wasteful use of system resources such
as memory and processor cycles. Efficiency therefore includes
responsiveness, processing time, memory utilisation, etc.

Acceptability Software must be acceptable to the type of users for which it is

designed. This means that it must be understandable, usable and
compatible with other systems that they use.

Chapter 1 Introduction 12
Software engineering

 Software engineering is an engineering discipline that is

concerned with all aspects of software production from
the early stages of system specification through to
maintaining the system after it has gone into use.
 Engineering discipline
▪ Using appropriate theories and methods to solve problems
bearing in mind organizational and financial constraints.
 All aspects of software production
▪ Not just technical process of development. Also project
management and the development of tools, methods etc. to
support software production.

Chapter 1 Introduction 13
Importance of software engineering

 More and more, individuals and society rely on advanced

software systems. We need to be able to produce
reliable and trustworthy systems economically and
quickly.
 It is usually cheaper, in the long run, to use software
engineering methods and techniques for software
systems rather than just write the programs as if it was a
personal programming project. For most types of
system, the majority of costs are the costs of changing
the software after it has gone into use.

Chapter 1 Introduction 14
Software process activities

 Software specification, where customers and engineers

define the software that is to be produced and the
constraints on its operation.
 Software development, where the software is designed
and programmed.
 Software validation, where the software is checked to
ensure that it is what the customer requires.
 Software evolution, where the software is modified to
reflect changing customer and market requirements.

Chapter 1 Introduction 15
General issues that affect most software

 Heterogeneity
▪ Increasingly, systems are required to operate as distributed
systems across networks that include different types of computer
and mobile devices.
 Business and social change
▪ Business and society are changing incredibly quickly as
emerging economies develop and new technologies become
available. They need to be able to change their existing software
and to rapidly develop new software.
 Security and trust
▪ As software is intertwined with all aspects of our lives, it is
essential that we can trust that software.

Chapter 1 Introduction 16
Software engineering diversity

 There are many different types of software system and

there is no universal set of software techniques that is
applicable to all of these.
 The software engineering methods and tools used
depend on the type of application being developed, the
requirements of the customer and the background of the
development team.

Chapter 1 Introduction 17
Application types

 Stand-alone applications
▪ These are application systems that run on a local computer,
such as a PC. They include all necessary functionality and do
not need to be connected to a network.
 Interactive transaction-based applications
▪ Applications that execute on a remote computer and are
accessed by users from their own PCs or terminals. These
include web applications such as e-commerce applications.
 Embedded control systems
▪ These are software control systems that control and manage
hardware devices. Numerically, there are probably more
embedded systems than any other type of system.

Chapter 1 Introduction 18
Application types

 Batch processing systems

▪ These are business systems that are designed to process data
in large batches. They process large numbers of individual
inputs to create corresponding outputs.
 Entertainment systems
▪ These are systems that are primarily for personal use and which
are intended to entertain the user.
 Systems for modeling and simulation
▪ These are systems that are developed by scientists and
engineers to model physical processes or situations, which
include many, separate, interacting objects.

Chapter 1 Introduction 19
Application types

 Data collection systems

▪ These are systems that collect data from their environment using
a set of sensors and send that data to other systems for
processing.
 Systems of systems
▪ These are systems that are composed of a number of other
software systems.

Chapter 1 Introduction 20
Software engineering fundamentals

 Some fundamental principles apply to all types of

software system, irrespective of the development
techniques used:
▪ Systems should be developed using a managed and understood
development process. Of course, different processes are used
for different types of software.
▪ Dependability and performance are important for all types of
system.
▪ Understanding and managing the software specification and
requirements (what the software should do) are important.
▪ Where appropriate, you should reuse software that has already
been developed rather than write new software.

Chapter 1 Introduction 21
Software engineering and the web

 The Web is now a platform for running application and

organizations are increasingly developing web-based
systems rather than local systems.
 Web services allow application functionality to be
accessed over the web.
 Cloud computing is an approach to the provision of
computer services where applications run remotely on
the ‘cloud’.
▪ Users do not buy software buy pay according to use.

Chapter 1 Introduction 22
Web-based software engineering

 Web-based systems are complex distributed systems

but the fundamental principles of software engineering
discussed previously are as applicable to them as they
are to any other types of system.
 The fundamental ideas of software engineering,
discussed in the previous section, apply to web-based
software in the same way that they apply to other types
of software system.

Chapter 1 Introduction 23
Software engineering ethics

 Software engineering involves wider responsibilities than

simply the application of technical skills.
 Software engineers must behave in an honest and
ethically responsible way if they are to be respected as
professionals.
 Ethical behaviour is more than simply upholding the law
but involves following a set of principles that are morally
correct.
Issues of professional responsibility

 Confidentiality
▪ Engineers should normally respect the confidentiality of their
employers or clients irrespective of whether or not a formal
confidentiality agreement has been signed.
 Competence
▪ Engineers should not misrepresent their level of competence.
They should not knowingly accept work which is outwith their
competence.
Issues of professional responsibility

 Intellectual property rights

▪ Engineers should be aware of local laws governing the use of
intellectual property such as patents, copyright, etc. They should
be careful to ensure that the intellectual property of employers
and clients is protected.
 Computer misuse
▪ Software engineers should not use their technical skills to
misuse other people’s computers. Computer misuse ranges from
relatively trivial (game playing on an employer’s machine, say) to
extremely serious (dissemination of viruses).
Key points

 Software engineering is an engineering discipline that is

concerned with all aspects of software production.
 Essential software product attributes are maintainability,
dependability and security, efficiency and acceptability.
 The high-level activities of specification, development,
validation and evolution are part of all software
processes.
 The fundamental notions of software engineering are
universally applicable to all types of system
development.

Chapter 1 Introduction 27
Key points

 There are many different types of system and each

requires appropriate software engineering tools and
techniques for their development.
 The fundamental ideas of software engineering are
applicable to all types of software system.

Chapter 1 Introduction 28
Questions ?

Chapter 1 Introduction 29