Lecture 1

 TextBooks:

❖ Software Engineering: A Practitioner's Approach, 8th Edition, Roger Pressman

& Bruce Maxim, ISBN:9780078022128 © 2015 McGraw-Hill.

❖ Software Engineering,10th Edition, Ian Sommerville, ISBN: 9780133943030 ©

2016 Thompson.

2 1. Introduction to SWE
 What is Software?
 What is Software Engineering?
 Software Engineering Layers.
 Software Engineering benefits.
 Software attributes and issues.
 Software Products.
 Software Application Types.
 Web-based Software.
 Software Engineering Ethics.

3 1. Introduction to SWE
1. Set of Instructions (computer programs) that when
executed provide desired features, function, and
performance.

2. Data structures that enable the programs to adequately

manipulate information.

3. Documentation that describes the operation and use of the

programs.

4 1. Introduction to SWE
 Software is developed or engineered, it is not manufactured in the
classical sense.

 Software doesn't "wear out."

 Although the industry is moving toward component-based

construction, most software continues to be custom-built.

5 1. Introduction to SWE
 The economies of ALL developed nations are dependent on
software and more systems are software controlled.

 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 to get economically software that is reliable and works
efficiently on real machines.
◦ Engineering discipline
 Using appropriate theories, methods and tools 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.

6 1. Introduction to SWE
 tools

methods

process model

a “quality” focus

Software Engineering

7 1. Introduction to SWE
 Process framework
Framework activities
work tasks
work products
milestones & deliverables
QA checkpoints
Umbrella Activities

8 1. Introduction to SWE
 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 1. Introduction to SWE
 Communication and Planning
◦ A concerted effort should be made to understand the problem before a software
solution is developed.
◦ Who has a stake in the solution to the problem?
◦ What data, functions, and features are required to properly solve the problem?
◦ Is it possible to represent smaller problems that may be easier to understand?
◦ Can the problem be represented graphically?

 Software Modelling
◦ Have you seen similar problems before?
◦ Are there patterns that are recognizable in a potential solution?
◦ Has a similar problem been solved?
◦ If so, are elements of the solution reusable?
◦ Can sub-problems be defined?
◦ If so, are solutions readily apparent for the sub-problems?
◦ Can a design model be created?

10 1. Introduction to SWE
 Code generation
◦ Does the solution conform to the plan?
◦ Is each component part of the solution provably correct?
◦ Has the design and code been reviewed, or better, have correctness proofs been
applied to algorithm?

 Testing and quality assurance

◦ Is it possible to test each component part of the solution?
◦ Has a reasonable testing strategy been implemented?
◦ Does the solution produce results that conform to the data, functions, and features
that are required?
◦ Has the software been validated against all stakeholder requirements?

11 1. Introduction to SWE
 Software project management.

 Formal technical reviews.

 Software quality assurance.

 Software configuration management.

 Work product preparation and production.

 Reusability management.

 Measurement.

 Risk management.

12 1. Introduction to SWE
 There are many different types of software system and there is no
universal set of software techniques that is applicable to all of these.
 Systems should be developed using a managed and understood
development process. Of course, different processes are used for
different types of software.
 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.
 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.

13 1. Introduction to SWE
 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.
◦ 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.

14 1. Introduction to SWE
 Increasing system complexity.
◦ As new software engineering techniques help us to build larger, more
complex systems, the demands change. Systems have to be built
and delivered more quickly; larger, even more complex systems are
required; systems have to have new capabilities that were previously
thought to be impossible.
 Failure to use software engineering methods
◦ It is fairly easy to write computer programs without using software
engineering methods and techniques. Many companies have drifted
into software development as their products and services have
evolved. They do not use software engineering methods in their
everyday work. Consequently, their software is often more expensive
and less reliable than it should be.

15 1. Introduction to SWE
16 1. Introduction to SWE
 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 security

◦ Software dependability includes a range of characteristics 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.

17 1. Introduction to SWE
 Efficiency
◦ Software should not make wasteful use of system resources such as
memory and processor cycles.
◦ Efficiency includes responsiveness, processing time, memory
utilization, 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.

18 1. Introduction to SWE
 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.

19 1. Introduction to SWE
 Security and trust
◦ As software is intertwined with all aspects of our lives, it is essential
that we can trust that software.

 Scale
◦ Software has to be developed across a very wide range of scales,
from very small embedded systems in portable or wearable devices
through to Internet-scale, cloud-based systems that serve a global
community.

20 1. Introduction to SWE
 Generic products
◦ Stand-alone systems that are marketed and sold to any customer
who wishes to buy them.
◦ The specification of what the software should do is owned by the
software developer and decisions on software change are made by
the developer.
◦ Examples – PC software such as graphics programs, project
management tools; CAD software; software for specific markets such
as appointments systems for dentists.

21 1. Introduction to SWE
 Customized products
◦ Software that is commissioned by a specific customer to meet their
own needs.
◦ 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.
◦ Examples – embedded control systems, air traffic control software,
traffic monitoring systems.

22 1. Introduction to SWE
 Stand-alone Applications
◦ They are 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

◦ They execute on a remote computer.
◦ They are accessed by users from their own PCs or terminals.
◦ They include web applications such as e-commerce applications.

23 1. Introduction to SWE
 Embedded control systems
◦ They Control and manage hardware devices.
◦ Numerically, there are probably more embedded systems than any
other type of system.

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

24 1. Introduction to SWE
 Entertainment systems
◦ These are systems that are primarily for personal use.
◦ They 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.
◦ They include many, separate, interacting objects.

25 1. Introduction to SWE
 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.

26 1. Introduction to SWE
 The Web is now a platform for running application.
 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.

27 1. Introduction to SWE
 Web-based systems are complex distributed systems.

 The fundamental principles of software engineering

apply to web-based software in the same way that they
apply to other types of software system.

28 1. Introduction to SWE
 Software reuse
◦ When building these systems, you think about how you can
assemble them from pre-existing software components and systems.
 Incremental and agile development
◦ Web-based systems should be developed and delivered
incrementally.
 Service-oriented systems
◦ Software may be implemented using service-oriented software
engineering, where the software components are stand-alone web
services.
 Rich interfaces
◦ Interface development technologies such as AJAX and HTML5 have
emerged that support the creation of rich interfaces within a web
browser.

29 1. Introduction to SWE
 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.

30 1. Introduction to SWE
 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.

31 1. Introduction to SWE
 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).

32 1. Introduction to SWE
 Process Models

33