Scribd
Upload
47 views8 pages

Software Processes: ©ian Sommerville 2006

Uploaded by

Qaiyum Azad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
47 views8 pages

Software Processes: ©ian Sommerville 2006

Uploaded by

Qaiyum Azad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 8

Software Processes

©Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 1


The software process

A structured set of activities required to develop a
software system(fundamental activities)
• Specification;
• Design;
• Validation;
• Evolution.

©Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 2


Software process model

A software process model is an abstract
representation of a process. It presents a
description of a process from some
particular perspective.

Some sw process models are

The waterfall model

The evolutionary development model

Component-based swe

Incremental delivery;

Spiral development
©Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 3
The waterfall model(software life cycle)


This takes the fundamental process activities of
specification, development, validation and evolution
and represents them as separate process phases
such as requirements specification, software design,
implementation, testing and so on.

©Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 4


Waterfall model

Requir ements
definition

System and
software design

Implementa tion
and unit testing

Integ ration and


system testing

Oper ation and


maintenance

©Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 5


Waterfall model phases/Principal stages:

Requirements analysis and definition
 The system's services, constraints and goals are ,established by consultation with system
users. They are then defined in detail and serve as a system specification.

System and software design
 The systems design process partitions the requirements to either hardware or software
systems. It establishes an overall system architecture. Software design involves identifying
and describing the fundamental software system abstractions and their relationships.

Implementation and unit testing

During this stage, the software design is realised as a set of programs or program units.
Unit testing involves verifying that each unit meets its specification.

Integration and system testing

The individual program units or programs are integrated and tested as a complete system
to ensure that the software requirements have been met. After testing, the software
system is delivered to the customer.

Operation and maintenance

Normally (although not necessarily) this is the longest life-cycle phase. The system is
installed and put into practical use. Maintenance: involves correcting errors which were not
discovered in earlier stages of the life cycle, improving the implementation of system units
and enhancing the system's services as new requirements are discovered.

©Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 6


Advantage of Waterfall model

Documentation is produced at each phase and

It fits with other engineering process models.

©Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 7


Waterfall model problems

Inflexible partitioning of the project into distinct stages makes it
difficult to respond to changing customer requirements.

Therefore, this model is only appropriate when the
requirements are well-understood and changes will be fairly
limited during the design process.

The waterfall model is mostly used for large systems
engineering projects where a system is developed at several
sites.

The main drawback of the waterfall model is the difficulty of
accommodating change after the process is underway. One
phase has to be complete before moving onto the next phase.

©Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 8

You might also like