Software Engineering

Introduction
Mira Balaban Department of Computer Science Ben-Gurion university

Based on slides of Igor Potapov: http://www.csc.liv.ac.uk/~igor/COMP201 Ian Sommerville:

http://www.comp.lancs.ac.uk/computing/resources/IanS/SE7/Presentations/index.html Alexander Borgida: http://www.cs.rutgers.edu/~borgida/431/
Software Engineering, 2006 Introduction 1

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 Software products may be
Generic - developed to be sold to a range of different customers Bespoke (custom) - developed for a single customer according to their specification
Software Engineering, 2006 Introduction 2

What is Engineering?
Application of a systematic, disciplined, quantifiable approach to
structures, machines, products, systems, processes.

Software Engineering, 2006

Introduction

What is Software Engineering?

That form of engineering that applies
a systematic disciplined quantifiable approach the principles of computer science, design, engineering, management, mathematics, psychology, sociology, and other disciplines as necessary and sometimes just plain invention

to creating, developing, operating and maintaining costeffective, reliably correct, high-quality solutions to software problems [Berry 92] SE requires the identification of a problem, a computer to carry execute a software product, and a user environment (composed of people, tools, methodologies, etc.)
Software Engineering, 2006 Introduction 4

The task of software engineers?

Software engineers should
adopt a systematic and organised approach to their work use appropriate tools and techniques depending on
the problem to be solved, the development constraints and the resources available

Software Engineering, 2006

Introduction

Origin of Software Engineering?

Software engineering deals with the development of high-quality software systems. Software engineering is abstract no physical limitations: leads to unlimited complexity.

Software engineering coined in 1968: within discussion of software crisis.

Software Engineering, 2006 Introduction 6

What is the software crisis?

Major projects are meaningfully late. Software costs more than predicted. Software is unreliable. Software is difficult to maintain. Poor performance. While hardware costs were decreasing, software costs were rising. requires techniques to control the complexity of large software systems.
Software Engineering, 2006 Introduction 7

Why Software Engineering is Needed?

Software development is hard ! Important to distinguish easy systems (one developer, one user, experimental use only) from hard systems (multiple developers, multiple users, products). Experience with easy systems is misleading: One person techniques do not scale up. Analogy with bridge building:
Over a stream = easy, one person job. Over a big River ? (the techniques do not scale)
Software Engineering, 2006 Introduction 8

Why is SE hard?
Different kinds of problems:
we are used to problems where there are pre-stated specifications (e.g. ,write a program to find the shortest path...), where it makes sense to talk about the correctness of a solution
real world problems: (e.g., software to help people control nuclear reactors): acceptability is defined by user satisfaction (validation vs verification). Implies evolution is intrinsic wicked problems:
define and solve concurrently no unique definition or solution always room for improvement in defn and soln new problem, not previously encountered many stakeholders, with different goals
Software Engineering, 2006 Introduction 9

Essential Difficulties of SE: [Brooks]

COMPLEXITY:
software is more complex for its size than any other human construct; no two parts are alike (vs. car, microchips,...); science advances by simplifying, while software cannot ignore/simplify details of real world

CONFORMITY:
among {hardware, software, people, organizations} it is software which is chosen to bend or adapt because it is more malleable, last to arrive on the scene, usually only one developed on site,...

CHANGEABILITY:
once delivered, most engineered products (hardware, cars, buildings) are rarely changed because the cost to change would be a large fraction of the cost to make. The (unfortunate) perception is that software is cheap to change. And pressure to change comes from successful use, and aging hardware platform.

INVISIBILITY:
since it has no physical reality, software is not properly visualizable with diagrams, etc. in the way in which houses, circuits, etc are.
Software Engineering, 2006 Introduction 10

Why Software Engineering Is Hard?

The main problem is complexity Many sources, but size is key:
UNIX contains 4 million lines of code Windows 2000 contains 108 lines of code

Software engineering is about managing this complexity.

Software Engineering, 2006 Introduction 11

What will (not) make a big difference: [Brooks1987]

Minor
Ada or Java or C# or Python or ... Object-Oriented Programming Artificial Intelligence Automatic Programming Graphical programming Program verification Environments and tools Workstations

Major
Buy vs build Requirements refinement and prototyping Incremental development Great designers (Unix, Pascal,Smalltalk vs Cobol,PL/I.Ada,MS-DOS)
Software Engineering, 2006 Introduction 12

Software engineering as a discipline within computer science

Computer Science
theory fundamentals

Software Engineering
the practicalities of developing delivering useful software

is concerned with

Computer science theories are currently insufficient to act as a complete underpinning for software engineering, BUT it is a foundation for practical aspects of software engineering

Software Engineering, 2006

Introduction

13

What is the difference between software engineering and system engineering?

Software engineering is part of System engineering System engineering is concerned with all aspects of computer-based systems development including
hardware, software and process engineering

System engineers are involved in system specification, architectural design, integration and deployment
Software Engineering, 2006 Introduction 14

SE: Processes, Models, and Tools

Processes: Systematic ways of organizing teams and tasks so that there is a clear, traceable path from customer requirements to the final product. (e.g.,:Waterfall, Prototyping, Spiral etc.) Processes help organize and co-ordinate teams, prepare documentation, reduce bugs, manage risk, increase productivity, etc. Models: Well-defined formal or informal languages and techniques for organizing and communicating arguments and decisions about software. e.g:
specification languages (Z, etc), design models (UML, etc)

Models help stake-holders communicate: customers with developers, designers and developers, developers and testers etc. If they are formal, they also can help support automation Tools: Programs which automate or otherwise support software development tasks: e.g., Eclipse, Make, CVS, etc. Tools increase productivity, quality and can reduce costs
Software Engineering, 2006 Introduction 15

Software Engineering Activities

1. Problem statement
needs analysis requirements specification: functional, non-functional

2. Design
architectural detailed (communication, database)

3. Implementation
coding testing: module integration documentation

4. Maintenance
corrective adaptive enhancement
Software Engineering, 2006 Introduction 16

What is a software process?

A set of activities whose goal is the development or evolution of software. Generic activities in all software processes are:
Specification - what the system should do and its development constraints. Development - production of the software system Validation - checking that the software is what the customer wants. Evolution - changing the software in response to changing demands.
Software Engineering, 2006 Introduction 17

What is a software process model?

An abstraction of a software process, presented from a specific perspective. Examples of process perspectives:
Workflow perspective represents inputs, outputs and dependencies. Data-flow perspective represents data transformation activities. Role/action perspective represents the roles/activities of the people involved in software process.

Generic process models:

Waterfall Iterative development Formal transformation Integration from reusable components
Software Engineering, 2006 Introduction 18

What are the costs of software engineering?

Roughly 60% of costs are development costs, 40% are testing costs. For custom software, evolution costs often exceed development costs. Costs vary depending on the type of system being developed and the requirements of system attributes such as performance and system reliability.
Distribution of costs depends on the development model that is used.
Software Engineering, 2006 Introduction 19

What is CASE ? (Computer-Aided Software Engineering)

Software systems which are intended to provide automated support for software process activities, such as requirements analysis, system modelling, debugging and testing.

Upper-CASE
Tools to support the early process activities of requirements and design.

Lower-CASE
Tools to support activities such as programming, debugging and testing.
Software Engineering, 2006 Introduction 20

What are the attributes of good software?

The software should deliver the required functionality and performance to the user and should be maintainable, dependable, efficient and usable Maintainability
Software must evolve to meet changing needs.

Dependability
Software must be trustworthy.

Efficiency
Software should not make wasteful use of system resources.

Usability
Software must be usable by the users for which it was designed.
Software Engineering, 2006 Introduction 21

What are the key challenges facing software engineering?

Software engineering in the 21st century faces three key challenges:
Heterogeneity
Systems are distributed and include a mix of hardware and software. Legacy systems (old valuable systems) must be maintained, updated and integrated into new systems.

Delivery
There is an increasing pressure for faster delivery of software.

Trust
Software must be trusted by its nave users.
Software Engineering, 2006 Introduction 22

Professional and ethical responsibility (1)

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.
Software Engineering, 2006 Introduction 23

Issues of professional responsibility (2)

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 out with their competence.
Software Engineering, 2006 Introduction 24

Issues of professional responsibility (3)

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. Software engineers should not use their technical skills to misuse other peoples computers. Computer misuse ranges from relatively trivial (game playing on an employers machine, say) to extremely serious (dissemination of viruses).
Introduction 25

Computer misuse

Software Engineering, 2006

ACM/IEEE Code of Ethics

The professional societies in the US have cooperated to produce a code of ethical practice. Members of these organisations sign up to the code of practice when they join. The Code contains eight Principles related to the behaviour 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.
Software Engineering, 2006 Introduction 26

Code of ethics - principles

1. PUBLIC
Software engineers shall act consistently with the public interest. Software engineers shall act in a manner that is in the best interests of their client and employer consistent with the public interest.
Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.
Introduction 27

2. CLIENT AND EMPLOYER

3. PRODUCT

Software Engineering, 2006

Code of ethics - principles

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.
Software engineers shall advance the integrity and reputation of the profession consistent with the public interest.
Introduction 28

6. PROFESSION

Software Engineering, 2006

Code of ethics - principles

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.
Software Engineering, 2006 Introduction 29

Ethical dilemmas
Disagreement in principle with the policies of senior management. Your employer acts in an unethical way and releases a safety-critical system without finishing the testing of the system. Participation in the development of military weapons systems or nuclear systems.
Software Engineering, 2006 Introduction 30

Summary: Key points (1)

Software engineering is an engineering discipline that is concerned with all aspects of software production. Software products consist of developed programs and associated documentation. Essential product attributes are maintainability, dependability, efficiency and usability. The software process consists of activities that are involved in developing software products. Basic activities are software specification, development, validation and evolution. Methods are organised ways of producing software. They include suggestions for the process to be followed, the notations to be used, rules governing the system descriptions which are produced and design guidelines.
Software Engineering, 2006 Introduction 31

Summary: Key points (2)

CASE tools are software systems which are designed to support routine activities in the software process such as editing design diagrams, checking diagram consistency and keeping track of program tests which have been run. Software engineers have responsibilities to the engineering profession and society. They should not simply be concerned with technical issues. Professional societies publish codes of conduct which set out the standards of behaviour expected of their members.

Software Engineering, 2006

Introduction

32