Software Engineering

Quaid-e-Awam University of Engineering, Science & Technology Nawabshah

Text Book
“Software Engineering, 10th Edition”, Ian Sommerwile

Tuesday, November 26, 2024 2

 Software Overview
• Software is more than just a program code
– A program is an executable code, which serves some
computational purpose.
– Software is considered to be collection of executable
programming code, associated libraries and
documentations.
– Software, when made for a specific requirement is called
software product.
• Engineering on the other hand, is all about
developing products, using well-defined, scientific
principles and methods.
3
 Software Overview

Software engineering is an engineering branch associated with

development of software product using well-defined scientific
principles, methods and procedures.
The outcome of software engineering is an efficient and reliable
software product. 4
 Software Overview
• IEEE defines software engineering as:
– The study of approaches / application of a
systematic, disciplined, quantifiable approach to
the development, operation, and maintenance of
software; that is, the application of engineering to
software.

5
 Software Overview
• Fritz Bauer, a German computer scientist,
defines software engineering as:
– Software engineering is the establishment and
use of sound engineering principles in order to
obtain economically software that is reliable and
work efficiently on real machines.

6
 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.

7
 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.
8
 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.
9
 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.
10
 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.
11
 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.
12
 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 modelling and simulation
– These are systems that are developed by scientists and
engineers to model physical processes or situations, which
include many, separate, interacting objects.
13
 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.

14
 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 writing new software.
15
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 but pay according to use.

16
 Web software engineering
• Software reuse is the dominant approach for constructing web-
based systems.
– When building these systems, you think about how you can assemble
them from pre-existing software components and systems.
• Web-based systems should be developed and delivered
incrementally.
– It is now generally recognized that it is impractical to specify all the
requirements for such systems in advance.
• User interfaces are constrained by the capabilities of web browsers.
– Technologies such as AJAX allow rich interfaces to be created within a web
browser but are still difficult to use. Web forms with local scripting are
more commonly used.

17
 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.
18
Software Evolution
• The process of developing a software product
using software engineering principles and
methods is referred to as Software Evolution.
• This includes the initial development of
software and its maintenance and updates, till
desired software product is developed, which
satisfies the expected requirements

19
Software Evolution

20
Software Evolution
• Evolution starts from the requirement gathering process.
• After which developers create a prototype of the
intended software and show it to the users to get their
feedback at the early stage of the software product
development
• The users suggest changes, on which several consecutive
updates and maintenance keep on changing too
• This process changes to the original software, till the
desired software is accomplished

21
Software Evolution
• Even after the user has the desired software in
hand, the advancing technology and the
changing requirements force the software
product to change accordingly.
• Re-creating software from scratch and to go
one-on-one with the requirement is not feasible
• The only feasible and economical solution is to
update the existing software so that it matches
the latest requirements
22
Software Evolution Laws
• Lehman has given laws for software evolution. He
divided the software into three different categories:
1. Static-type (S-type) - This is a software, which works
strictly according to defined specifications and
solutions. The solution and the method to achieve it,
both are immediately understood before coding.
The s-type software is least subjected to changes
hence this is the simplest of all. For example,
calculator program for mathematical computations

23
Software Evolution Laws
2. Practical-type (P-type) - This is a software
with a collection of procedures. This is
defined by exactly what procedures can do.
In this software, the specifications can be
described but the solution is not instant. For
example, gaming software

24
Software Evolution Laws
3. Embedded-type (E-type) - This software
works closely as the requirements of real-
world environment. This software has a high
degree of evolution as there are various
changes in laws, taxes etc. in the real world
situations. For example, Online trading
software

25
E-Type Software Evolution
• Lehman has given eight laws for E-Type software
evolution
1. Continuing change - An E-type software system
must continue to adapt to the real world
changes, else it becomes progressively less
useful.
2. Increasing complexity - As an E-type software
system evolves, its complexity tends to increase
unless work is done to maintain or reduce it.
26
E-Type Software Evolution
3. Conservation of familiarity - The familiarity with
the software or the knowledge about how it was
developed, why was it developed in that
particular manner etc., must be retained at any
cost, to implement the changes in the system.
4. Continuing growth - In order for an E-type
system intended to resolve some business
problem, its size of implementing the changes
grows according to the lifestyle changes of the
business
27
E-Type Software Evolution
5. Reducing quality - An E-type software system declines in
quality unless rigorously maintained and adapted to a
changing operational environment.
6. Feedback systems - The E-type software systems constitute
multi-loop, multi-level feedback systems and must be treated
as such to be successfully modified or improved.
7. Self-regulation - E-type software evolution processes are self-
regulating with the distribution of product and process
measures close to normal.
8. Organizational stability - The average effective global activity
rate in an evolving E-type system is invariant over the lifetime
of the product.
28
Software Paradigms
• Software paradigms refer to the methods and
steps, which are taken while designing the
software.
• There are many methods proposed and are
implemented.
• But, we need to see where in the software
engineering concept, these paradigms stand.

29
Software Paradigms
• These can be combined into various categories,
though each of them is contained in one another:

30
Software Development Paradigms
• This paradigm is known as software
engineering paradigm; where all the
engineering concepts relating to the
development of software are applied.
• It includes various researches and
requirement gathering methods which help
the software product to be built

31
Software Development Paradigms
• It consists of:
– Requirements gathering
– Software design
– Programming

32
Software Design Paradigms
• This paradigm is a part of Software
Development and includes:
– Design
– Maintenance
– Programming

33
Programming Paradigms
• This paradigm is closely related to the
programming aspects of software development.
• Programming paradigm includes:
– Coding
– Testing
– Integration

34
Need of Software Engineering
• The need of software engineering arises
because of higher rate of change in user
requirements and environment on which the
software is working
• Following are some of the needs stated:
– Large software: It is easier to build a wall than a
house or building, likewise, as the size of the
software becomes large, engineering has to step
in to give it a scientific process.

35
Need of Software Engineering
– Scalability: If the software process were not based
on scientific and engineering concepts, it would be
easier to re-create new software than to scale an
existing one.
– Cost: As hardware industry has shown its skills
and huge manufacturing has lower down the price
of computer and electronic hardware. But, cost of
the software remains high if proper process is not
adapted

36
Need of Software Engineering
– Dynamic Nature: Always growing and adapting
nature of the software hugely depends upon the
environment in which the user works. If the
nature of software is always changing, new
enhancements need to be done in the existing
one. This is where the software engineering plays
a good role
– Quality Management: Better process of software
development provides better and quality software
product
37
Characteristics of good software
• A good software is one that meets the needs
of its users, performs its intended functions
reliably, and is easy to maintain.
• There are several characteristics of good
software that are commonly recognized by
software engineers, which are important to
consider when developing a software system.

38
Characteristics of good software
• Software must satisfy the following goals:
– Operational
– Transitional
– Maintenance

39
Characteristics of good software

40
Operational
• In operational categories, the factors that decide the software
performance in operations.
• It can be measured on:
 Budget
 Usability
 Efficiency
 Correctness
 Functionality
 Dependability
 Security
 Safety
41
Transitional
• When the software is moved from one
platform to another, the factors deciding the
software quality:
 Portability
 Interoperability
 Reusability
 Adaptability

42
Maintenance
• In this categories all factors are included that
describes about how well a software has the
capabilities to maintain itself in the ever
changing environment:
 Modularity
 Maintainability
 Flexibility
 Scalability

43
Software Characteristics

44
Software Characteristics (Functionality)
• Functionality refers to the set of features and
capabilities that a software program or system
provides to its users.
• It is one of the most important characteristics
of software, as it determines the usefulness of
the software for the intended purpose.

45
Software Characteristics (Functionality)
• Examples of functionality in software include:
1. Data storage and retrieval
2. Data processing and manipulation
3. User interface and navigation
4. Communication and networking
5. Security and access control
6. Reporting and visualization
7. Automation and scripting
46
Software Characteristics (Functionality)
• The more functionality a software has, the
more powerful and versatile it is, but also the
more complex it can be.
• It is important to balance the need for
functionality with the need for ease of use,
maintainability, and scalability.

47
Software Characteristics (Functionality)
Required functions are:

48
Software Characteristics (Reliability)
• Reliability is a characteristic of software that
refers to its ability to perform its intended
functions correctly and consistently over time.
• Reliability is an important aspect of software
quality, as it helps ensure that the software
will work correctly and not fail unexpectedly.

49
 Software Characteristics (Reliability)
• Examples of factors that can affect the reliability of
software include:
1. Bugs and errors in the code
2. Lack of testing and validation
3. Poorly designed algorithms and data structures
4. Inadequate error handling and recovery
5. Incompatibilities with other software or
hardware

50
Software Characteristics (Reliability)
• To improve the reliability of software, various
techniques and methodologies can be used,
such as testing and validation, formal
verification, and fault tolerance.
• A software is considered reliable when the
probability of failing is low and it is able to
recover from the failure quickly, if any.

51
Software Characteristics (Reliability)
Required functions are:

52
Software Characteristics (Efficiency)
• Efficiency is a characteristic of software that
refers to its ability to use resources such as
memory, processing power, and network
bandwidth in an optimal way.
• High efficiency means that a software program
can perform its intended functions quickly and
with minimal use of resources
• Low efficiency means that a software program
may be slow or consume excessive resources
53
Software Characteristics (Efficiency)
• Examples of factors that can affect the
efficiency of software include:
1. Poorly designed algorithms and data structures
2. Inefficient use of memory and processing power
3. High network latency or bandwidth usage
4. Unnecessary processing or computation
5. Un-optimized code

54
Software Characteristics (Efficiency)
• To improve the efficiency of software, various
techniques and methodologies can be used, such
as performance analysis, optimization, and
profiling.
• Efficiency is important in software systems that are
resource-constrained, high-performance, and real-
time systems.
• It is also important in systems that need to handle
a large number of users or transactions
simultaneously.
55
Software Characteristics (Efficiency)
Required functions are:

56
Software Characteristics (Usability)
• It refers to the extent to which the software
can be used with ease
• The amount of effort or time required to learn
how to use the software

57
Software Characteristics (Maintainability)
• It refers to the ease with which the
modifications can be made in a software
system to extend its functionality, improve its
performance, or correct errors

58
Software Characteristics (Portability)
• A set of attributes that bears on the ability of
software to be transferred from one
environment to another, without or minimum
changes

59
Characteristics of software in Software
Engineering
• Software is developed or engineered; it is not
manufactured in the classical sense:
– Although some similarities exist between
software development and hardware
manufacturing, few activities are fundamentally
different.
– In both activities, high quality is achieved
through good design, but the manufacturing
phase for hardware can introduce quality
problems than software.
60
Characteristics of software in Software
Engineering
• Software is developed or engineered; it is not
manufactured in the classical sense:
– Although some similarities exist between
software development and hardware
manufacturing, few activities are fundamentally
different.
– In both activities, high quality is achieved
through good design, but the manufacturing
phase for hardware can introduce quality
problems than software.
61
In short:
• Software engineering is a branch of computer science,
which uses well defined engineering concepts required
to produce:
o Efficient
o Durable
o Scalable
o In-budget
o On-time software products.
• Software engineering is the process of designing,
developing, testing, and maintaining software
62
 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 concepts of software engineering are
universally applicable to all types of system
development.

63
 Key points
• There are many different types of systems and
each requires appropriate software
engineering tools and techniques for their
development.
• The fundamental concepts of software
engineering are applicable to all types of
software system.

64