Components Based Design and Development

Computer Engineering Studies

Universidad Carlos III de Madrid

Unit 2: Software Engineering Quick Overview

Juan Llorens
Högskolan på Åland – Finland / Universidad Carlos III de Madrid - Spain
[Link]@[Link]

Juan Llorens– Software Engineering Overview 1

 Software Engineering
• Engineering...
“the profession in which
a knowledge of the mathematical and natural sciences gained by study,
experience and practice
is applied with judgment
to develop ways to utilize, economically, the materials and forces of
nature for the benefit of mankind.” (Accreditation Board for Engineering
and Technology, 1996).

• Particularities of software engineering

– The “product” (software)
– A lot of development, little engineering discipline
– Frequent changes in the product
– It is not seen as necessary by the “so called” software engineers
From Gonzalo Genova

Juan Llorens– Software Engineering Overview 2

 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.

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 1

Juan Llorens– Software Engineering Overview 3
 The systems engineering process

Requirements System
definition decommissioning

System System
design evolution

Sub-system System
development installation

System
integration

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 2

Juan Llorens– Software Engineering Overview 4
 Inter-disciplinary involvement

Software Electronic Mechanical

engineering engineering engineering

Structural ATC systems User interface

engineering engineering design

Civil Electrical
Architecture
engineering engineering

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 2

Juan Llorens– Software Engineering Overview 5
 What is a software process?

Objectives, needs, ideas

problems, failures,..

How is a software project done?

“Software application”
BNot a Software system
Juan Llorens– Software Engineering Overview 6
 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.

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 1

Juan Llorens– Software Engineering Overview 7
 What is a software process model?

• A simplified representation of a software process, presented from a specific

perspective.

• Examples of process perspectives are

– Workflow perspective - sequence of activities;
– Data-flow perspective - information flow;
– Role/action perspective - who does what.

• Generic process models

– Waterfall;
– Iterative development;
– Component-based software engineering.

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 1

Juan Llorens– Software Engineering Overview 8
 Usual workflow Activities

Req. analysis design implementation tests

Not so Usual workflow Activities

Vocabulary Id. Project Mgmt Estimation Debriefing

Sw For Reuse Risk Mgmt. Project Plan. Indexing

Juan Llorens– Software Engineering Overview 9

 Types of Software Processes : the waterfall process

Need

A single iteration
analysis of requirements

design

implementation

is an idealization never
realized in this pure form
tests Final product

Juan Llorens– Software Engineering Overview 10

 Iterative process [spiral]

Requirements analysis design

N iterations

final product
need

N versions
of the product,
documentation...

tests implementation

Juan Llorens– Software Engineering Overview 11

 Iterative and incremental process
• Enables the evolution in parallel of several workflows, and by that the work
in parallel of several teams of people
• the different versions of the documents produced in each iteration are not
necessarily compatible between them: organize well the documentation

iteration 1 iteration 2 iteration 3

analysis analysis analysis

(version 1) (version 2) (version 3)
design design
(version 1) (version 2)
implementation
(version 1)

Juan Llorens– Software Engineering Overview 12

 UP: Phases, iterations and workflows
Phases of the life cycle
Workflows Inception Elaboration Construction Transition

requirements
an iteration in the
phase of Elaboration
analysis

design

implementation

tests

Preliminary Iter. Iter. Iter. Iter. Iter. Iter. Iter.

iteration(s) #1 #2 #n #n+1 #n+2 #m #m+1

iterations
Juan Llorens– Software Engineering Overview 13
New Project My Favorite workflow structure for Development
Voc
PMgnt
Find + Reuse
Req Cap

Software with Reuse

Risk
Software for Reuse

Sw for reuse Plan-Est

Req Ana
Document
CM Arc. Des Mngmnt.
WG Traceability D Des
Dev
Tes
Db
Ix
New Solution

Juan Llorens– Software Engineering Overview 14

 My Favorite dataflow structure for Development
Ontology
Voc
PMgnt Document Templates

Req Cap Text based Requirements

Risk Text Based Risks

Plan-Est Gantt Diagrams

Spreadsheets

Req Ana Requirements Models

Documents

Arc. Des Architectural Models

Documents

D Des
Documents

Dev Software Models

Code

Tes
Documents Acknowledged Db
Reports
Reports
Ix
Documents

Juan Llorens– Software Engineering Overview 15

 Other frameworks and nomenclatures

Terminology of UP Classical terminology

requirements
requirements analysis
analysis

design design

implementation
implementation
integration

tests tests

Eric Braude, Software Engineering. An Object-Oriented Perspective, John Wiley & Sons, 2001, p. 30.

Juan Llorens– Software Engineering Overview 16

 How to perform an Iterative Software Process

• divide a project in mini-projects, easier to manage and complete

• each mini-project is an iteration
• each iteration contains all the elements of a normal project:
– planning
– analysis and design
– construction
– integration and tests
– generate a version of the product (internal or external)
• each iteration generates a baseline that includes a partially completed
version of the final system, and all the associated documentation
• the successive iterations build on top of each other until the final system is
finished
• the difference between two baselines is known as an increment

Juan Llorens– Software Engineering Overview 17

 What are software engineering methods?

• Structured approaches to software development which include system

models, notations, rules, design advice and process guidance.

• Model descriptions
– Descriptions of graphical models which should be produced;
• Rules
– Constraints applied to system models;
• Recommendations
– Advice on good design practice;
• Process guidance
– What activities to follow.

Based on Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 1

Juan Llorens– Software Engineering Overview 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.

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 1

Juan Llorens– Software Engineering Overview 19
 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.

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 1

Juan Llorens– Software Engineering Overview 20
 Activity cost distribution
Waterfall model
0 25 50 75 100

Specification Design Development Integration and testing

Iterative development

0 25 50 75 100

Specification Iterative development System testing

Component-based software engineering

0 25 50 75 100

Specification Development Integration and testing

Development and evolution costs for long-lifetime systems

0 10 200 30 400

System development System evolution

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 1

Juan Llorens– Software Engineering Overview 21
 Product development costs

©Ian Sommerville 2004 - Software Engineering, 7th edition. Chapter 1

Juan Llorens– Software Engineering Overview 22
The maturity of the Software Engineering discipline (swing)
1. Real need: what the customer really wanted.
2. Client side: what the client was able to describe
as his/her clear need.
3. Sale process: what the software manufacturer
promised the client.
4. Requirements: the final understanding of what
the customer described as requirements.
5. Analysis: how was planned that the system
should finally work at the client side.
6. Design: how the system should perform the
analysed functionality.
7. Coding: what the programmer finally produced.
8. On-site installation: what was really installed in
the client site.
9. Test: what the responsibles saw in the system.

Juan Llorens– Software Engineering Overview 23