Lecture 1- Introduction

Textbook – Ch. 1

Most contents in this material are borrowed from the textbook

(Ian Sommerville, Software Engineering)’s slides in Pearson.
Topics
• Professional software development
• What are software, software development, software process, and
software engineering.

• Software engineering ethics

• A brief introduction to ethical issues that affect software engineering.

• Case studies
• An introduction to examples in the textbook.

1. Introduction 2
I. Professional Software Development

1. Introduction 3
I.1 Software
• Definition
• Computer programs, procedures, and possibly associated
documentation and data pertaining to the operation of a computer
system.

• Importance
• Essential for the functioning of government, society and national and
international businesses and institutions.
• The economies of ALL developed nations are dependent on software.
• More and more systems are software controlled.

1. Introduction 4
I.1.2 Software development
• A professional activity in which software is developed for
business purposes or as software products (e.g., information
systems and computer-aided design systems).

1. Introduction 5
I.1.2 Software development
• Intended for use by someone apart from its developer(s). It is
maintained and changed throughout its life.

1. Introduction 6
I.1.3 Software costs
• Often dominate computer system costs.
• The costs of software on a PC are often greater than the hardware
cost.

• Maintenance costs more that development.

• For systems with a long life, maintenance costs may be several times
development costs.

• Software engineering is concerned with cost-effective

software development.

1. Introduction 7
I.1.4 Software development difficulties
• No constraint by the
properties of materials,
physical laws and
manufacturing processes
• Software systems can be
extremely complex, difficult to
understand, expensive to
change. Source: WA Contents

1. Introduction 8
I.1.4 Software development difficulties
• There are many different types of software systems

1. Introduction 9
I.1.5 Software products
• Generic products
• Stand-alone systems that are marketed and sold to any customer who
wishes to buy them.
• Examples: PC software, project management tools, CAD software, software for
specific markets (e.g., appointments systems)
• Specification is owned by the software developer and decisions on
software change are made by the developer.

1. Introduction 10
I.1.5 Software products
• 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.
• Specification is owned by the customer for the software and they make
decisions on software changes that are required.

1. Introduction 11
I.1.6 Essential attributes of good software
Product characteristic Description
Acceptability Software must be acceptable to the type of users for which it is
designed: Must be understandable, usable and compatible with
other systems that they use.
Dependability and Software dependability includes a range of characteristics including
security 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 utilization, etc.
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.

1. Introduction 12
I.1.7 Software process activities
Software specification
• Customers and engineers define the software that is to
be produced and the constraints on its operation

Software development
• The software is designed and programmed

Software validation
• The software is checked to ensure that it is what the
customer requires

Software evolution
• The software is modified to reflect changing customer
and market requirements
1. Introduction 13
I.1.8 General issues that affect 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.

1. Introduction 14
I.1.8 General issues that affect software
• 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.

1. Introduction 15
I.1.9 Software (project) failure
• 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, and larger, even more complex systems are
required.
• Failure to use software engineering methods
• 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.
1. Introduction 16
I.2 Software engineering
• IEEE definition: The application of a systematic, disciplined,
quantifiable approach to the development, operation, and
maintenance of software, that is, the application of engineering
to software.

1. Introduction 17
I.2 Software engineering
• An engineering discipline that is concerned with all
aspects of software production from the early stages of
system specification through to maintaining the system.
• Use appropriate theories, methods and tools to solve problems bearing
in mind organizational and financial constraints.
• Not just technical process of development. Also project management
and the development of tools, methods, and theories to support
software production.

1. Introduction 18
I.2.1 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.
• For most types of system, the majority of costs are the costs of
changing the software after it has gone into use.

1. Introduction 19
 I.2.2 Software engineering vs. computer science

Programming
Foundation based on Computer skills Software Foundation based on
mathematics and theory. problem solving.
Why does it work? Science Engineering How does it work?

1. Introduction 20
I.2.3 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.

1. Introduction 21
I.2.4 Application types
• Stand-alone applications
• These are application systems that run on a local computer. They
include all necessary functionality and do not need to be connected to
a network.
• Office applications, CAD, photo manipulation software, …

1. Introduction 22
I.2.4 Application types
• Interactive transaction-based
applications
• Applications that execute on a remote
computer and are accessed by users
from their own PCs or terminals.
• Web applications (e.g., e-commerce
applications and business systems
through a web browser) or special-
purpose client program and cloud-based
services (e.g., mail and photo sharing)

1. Introduction 23
I.2.4 Application types
• Embedded control systems
• These are software control systems that
control and manage hardware devices.
Numerically, there are probably more Embedded
systems
embedded systems than any other type
of system.
• Software in a mobile phone, software
that controls antilock braking in a car,
software in a microwave oven to control
the cooking process.
1. Introduction 24
I.2.4 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.
• Periodic billing system (phone billing systems,
salary payment systems)

1. Introduction 25
I.2.4 Application types
• Entertainment systems
• These are systems that are primarily for personal use and which are intended
to entertain the user.
• Games which run on special-purpose console hardware, quality of the user
interaction is important.

• 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.
• Computationally intensive and require high-performance
parallel systems for execution.
1. Introduction 26
I.2.4 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.
• Have to interact with sensors and often is installed in a hostile environment
such as inside an engine or in a remote location.

• Systems of systems
• These are systems, used in enterprises and other large organizations, that
are composed of a number of other software systems.

1. Introduction 27
I.2.5 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.
• 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, we should reuse software that has already been
developed rather than write new software.

1. Introduction 28
I.3 Internet-based software
• The web is now a platform for running applications.
• Organizations are increasingly developing web-based systems
rather than local systems.
• Web services allow application functionality to be accessed over the
web.
• Cheaper to change and upgrade the software, no need to install.

1. Introduction 29
I.3 Internet-based software
• Web-based systems are complex distributed systems.
• The fundamental ideas of software engineering apply to web-based
software in the same way that they apply to other types of software
system.
• Web-based systems are getting larger and larger, so software
engineering techniques that deal with scale and complexity are
relevant for these systems.

1. Introduction 30
I.3 Internet-based software
• 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.

1. Introduction 31
I.3.1 Web-based software engineering
• Software reuse
• Software reuse is the dominant approach for constructing web-based
systems. When building these systems, we think about how we can
assemble them from pre-existing software components and systems.
• Incremental and agile development
• 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.

1. Introduction 32
I.3.1 Web-based software engineering
• 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.

1. Introduction 33
I.4 FAQs about software engineering
Question Answer
What is software? Computer programs and associated documentation. Software products
may be developed for a particular customer or may be developed for a
general market.
What are the attributes of good Good software should deliver the required functionality and performance to
software? the user and should be maintainable, dependable and usable.
What is software engineering? Software engineering is an engineering discipline that is concerned with all
aspects of software production.
What are the fundamental software Software specification, software development, software validation and
engineering activities? software evolution.
What is the difference between Computer science focuses on theory and fundamentals; software
software engineering and engineering is concerned with the practicalities of developing and
computer science? delivering useful software.
What is the difference between System engineering is concerned with all aspects of computer-based
software engineering and system systems development including hardware, software and process
engineering? engineering. Software engineering is a part of this more general process.

1. Introduction 34
I.4 FAQs about software engineering
Question Answer
What are the key challenges facing Coping with increasing diversity, demands for reduced delivery times and
software engineering? developing trustworthy software.

What are the costs of software Roughly 60% of software costs are development costs, 40% are testing
engineering? costs. For custom software, evolution costs often exceed development
costs.
What are the best software While all software projects have to be professionally managed and
engineering techniques and developed, different techniques are appropriate for different types of
methods? system. For example, games should always be developed using a series
of prototypes whereas safety critical control systems require a complete
and analyzable specification to be developed. You can’t, therefore, say that
one method is better than another.
What differences has the web made The web has led to the availability of software services and the possibility
to software engineering? of developing highly distributed service-based systems. Web-based
systems development has led to important advances in programming
languages and software reuse.

1. Introduction 35
II. Software engineering ethics

1. Introduction 36
II.1 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.

1. Introduction 37
II.1.1 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 outside their competence.

1. Introduction 38
II.1.1 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).

1. Introduction 39
II.1.2 ACM/IEEE code of ethics
• The professional societies in the US have cooperated to produce a
code of ethical practice.
• Members of these organizations sign up to the code of practice when
they join.

1. Introduction 40
II.1.2 ACM/IEEE code of ethics
Software Engineering Code of Ethics and Professional Practice

ACM/IEEE-CS Joint Task Force on Software Engineering Ethics and Professional

Practices

PREAMBLE
The short version of the code summarizes aspirations at a high level of the abstraction; the
clauses that are included in the full version give examples and details of how these
aspirations change the way we act as software engineering professionals. Without the
aspirations, the details can become legalistic and tedious; without the details, the
aspirations can become high sounding but empty; together, the aspirations and the details
form a cohesive code.
Software engineers shall commit themselves to making the analysis, specification, design,
development, testing and maintenance of software a beneficial and respected profession.
In accordance with their commitment to the health, safety and welfare of the public,
software engineers shall adhere to the following Eight Principles:

1. Introduction 41
II.1.2 ACM/IEEE code of ethics
1. PUBLIC - Software engineers shall act consistently with the public interest.
2. CLIENT AND EMPLOYER - Software engineers shall act in a manner that is in the best interests
of their client and employer consistent with the public interest.
3. PRODUCT - Software engineers shall ensure that their products and related modifications meet
the highest professional standards possible.
4. JUDGMENT - Software engineers shall maintain integrity and independence in their professional
judgment.
5. MANAGEMENT - Software engineering managers and leaders shall subscribe to and promote an
ethical approach to the management of software development and maintenance.
6. PROFESSION - Software engineers shall advance the integrity and reputation of the profession
consistent with the public interest.
7. COLLEAGUES - Software engineers shall be fair to and supportive of their colleagues.
8. SELF - Software engineers shall participate in lifelong learning regarding the practice of their
profession and shall promote an ethical approach to the practice of the profession.

1. Introduction 42
II.1.3 Rationale for the code of ethics
• Computers have a central and growing role in commerce, industry,
government, medicine, education, entertainment and society at
large. Software engineers are those who contribute by direct
participation or by teaching, to the analysis, specification, design,
development, certification, maintenance and testing of software
systems.
• Software engineers have significant opportunities to do good or
cause harm, to enable others to do good or cause harm. To ensure,
software engineers must commit themselves to making software
engineering a beneficial and respected profession.

1. Introduction 43
II.1.3 Rationale for the code of ethics
• The code contains eight principles related to the behavior of and
decisions made by professional software engineers, including
practitioners, educators, managers, supervisors and policy makers,
as well as trainees and students of the profession.

1. Introduction 44
III. Case studies (from the textbook)

1. Introduction 45
III. Case studies
1. A personal insulin pump
• An embedded system in an insulin pump used by diabetics to maintain blood glucose
control.

2. A mental health case patient management system (Mentcare)

• An information system used to maintain records of people receiving care for mental
health problems.

3. A wilderness weather station

• A data collection system that collects data about weather conditions in remote areas.

4. iLearn: a digital learning environment

• A service-oriented system to support learning in schools.

1. Introduction 46
III.1 Insulin pump control system
• Collects data from a blood sugar sensor and calculates the amount
of insulin required to be injected.
• Calculation based on the rate of change of blood sugar levels.
• Sends signals to a micro-pump to deliver the correct dose of insulin.
• Safety-critical system as low blood sugars can lead to brain
malfunctioning, coma and death; high-blood sugar levels have long-
term consequences such as eye and kidney damage.

1. Introduction 47
III.1 Insulin pump hardware architecture

1. Introduction 48
III.1 Activity model of the insulin pump

1. Introduction 49
III.1 Essential high-level requirements
• The system must be designed and implemented to ensure that
• The system shall be available to deliver insulin when required;
• The system shall perform reliably and deliver the correct amount of
insulin to counteract the current level of blood sugar.

1. Introduction 50
III.2 Mentcare
• A medical information system to support mental health care that maintains
information about patients suffering from mental health problems and the
treatments.
• Mentcare is intended for use in clinics. To make it easier for patients to attend,
these clinics may also be held in local medical practices or community centers.
• It makes use of a centralized database of patient information but has also been
designed to run on a PC, so that it may be accessed and used from sites that do
not have secure network connectivity.
• When the local systems have secure network access, they use patient
information in the database but they can download and use local copies of patient
records when they are disconnected.

1. Introduction 51
III.2 Mentcare goals
• To generate management information that allows health service
managers to assess performance.
• To provide medical staff with timely information to support the
treatment of patients.

1. Introduction 52
III.2 Organization of Mentcare

1. Introduction 53
III.2 Key features of the Mentcare system
• Individual care management
• Clinicians can create records for patients, edit and view the information in the system.
The system supports data summaries so that doctors can quickly learn about the key
problems and treatments that have been prescribed.
• Patient monitoring
• The system monitors the records of patients that are involved in treatment and issues
warnings if possible problems are detected. It keeps track of patients who have been
sectioned and to ensure that the legally required checks are carried out at the right
time.
• Administrative reporting
• The system generates monthly management reports showing the number of patients
treated at each clinic, the number of patients who have entered and left the care
system, number of patients sectioned, the drugs prescribed and their costs, etc.
1. Introduction 54
III.2 Mentcare system concerns
• Privacy
• It is essential that patient information is confidential and is never disclosed to
anyone apart from authorised medical staff and the patient themselves.
• Safety
• Some mental illnesses cause patients to become suicidal or a danger to other
people. Wherever possible, the system should warn medical staff about
potentially suicidal or dangerous patients.
• The system must be available when needed otherwise safety may be
compromised and it may be impossible to prescribe the correct medication to
patients.

1. Introduction 55
III.3 Wilderness weather station
• The government of a country with large areas of wilderness decides
to deploy several hundred weather stations in remote areas.
• Weather stations collect data from a set of instruments that
measure temperature and pressure, sunshine, rainfall, wind speed
and wind direction.
• A number of instruments that measure weather parameters (wind speed and
direction, ground/air temperatures, barometric pressure and rainfall)
• Each of these instruments is controlled by a software system that takes
parameter readings periodically and manages the data collected from the
instruments.

1. Introduction 56
III.3 The weather station’s environment

1. Introduction 57
III.3 Weather information system
• The weather station system
• This is responsible for collecting weather data, carrying out some initial data
processing and transmitting it to the data management system.
• The data management/archiving system
• This system collects the data from all of the wilderness weather stations,
carries out data processing and analysis and archives the data.
• The station maintenance system
• This system can communicate by satellite with all wilderness weather stations
to monitor the health of these systems and provide reports of problems.

1. Introduction 58
III.4 iLearn: A digital learning environment
• Specially designed tools for learning may be embedded plus a set of
applications that are geared to the needs of the learners using the
system.
• The tools included in each version of the environment are chosen by
teachers and learners to suit their specific needs.
• These can be general applications such as spreadsheets, learning
management applications such as a Virtual Learning Environment (VLE) to
manage homework submission and assessment, games and simulations.

1. Introduction 59
III.4 iLearn: A digital learning environment
• The system is a service-oriented system with all system
components considered to be a replaceable service.
• This allows the system to be updated incrementally as new services
become available.
• It also makes it possible to rapidly configure the system to create
versions of the environment for different groups such as very young
children who cannot read, senior students, etc.

1. Introduction 60
III.4 iLearn services
• Utility services that provide basic application-independent functionality and
which may be used by other services in the system.
• Application services that provide specific applications such as email,
conferencing, photo sharing etc. and access to specific educational
content such as scientific films or historical resources.
• Configuration services that are used to adapt the environment with a
specific set of application services and do define how services are shared
between students, teachers and their parents.

1. Introduction 61
III.4 iLearn architecture

1. Introduction 62
III.4 iLearn service integration
• Integrated services are services which offer an API (application
programming interface) and which can be accessed by other services
through that API. Direct service-to-service communication is therefore
possible.
• Independent services are services which are simply accessed through a
browser interface and which operate independently of other services.
Information can only be shared with other services through explicit user
actions such as copy and paste; re-authentication may be required for
each independent service.

1. Introduction 63