Software process models
This presentation is the property of its rightful owner.
Sponsored Links
1 / 61

Software Process Models PowerPoint PPT Presentation


  • 132 Views
  • Uploaded on
  • Presentation posted in: General

Software Process Models. Objectives. To introduce software process models To describe three generic process models and when they may be used To outline process models for requirements engineering, software development, testing and evolution To explain the Rational Unified Process model

Download Presentation

Software Process Models

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Software process models

Software Process Models


Objectives

Objectives

  • To introduce software process models

  • To describe three generic process models and when they may be used

  • To outline process models for requirements engineering, software development, testing and evolution

  • To explain the Rational Unified Process model

  • To introduce CASE technology to support software process activities


Topics covered

Topics covered

  • Software process models

  • Process iteration

  • Process activities

  • The Rational Unified Process

  • Computer-aided software engineering


The software process

The software process

  • A structured set of activities required to develop a software system

    • Specification;

    • Design;

    • Validation;

    • Evolution.

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


Generic software process models

Generic software process models

  • The waterfall model

    • Separate and distinct phases of specification and development.

  • Evolutionary development

    • Specification, development and validation are interleaved.

  • Component-based software engineering

    • The system is assembled from existing components.

  • There are many variants of these models e.g. formal development where a waterfall-like process is used but the specification is a formal specification that is refined through several stages to an implementable design.


Waterfall model

R

equir

ements

definition

S

ystem and

software design

Implementa

tion

and unit testing

Integ

r

a

tion and

system testing

Oper

a

tion and

maintenance

Waterfall model


Waterfall model phases

Waterfall model phases

  • Requirements analysis and definition

  • System and software design

  • Implementation and unit testing

  • Integration and system testing

  • Operation and maintenance

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


Waterfall model problems

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.

  • Few business systems have stable requirements.

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


Evolutionary development

Concurr

ent

acti

vities

Initial

Specifica

tion

v

ersion

Inter

media

te

Outline

De

v

elopment

v

ersions

description

Final

V

alida

tion

v

ersion

Evolutionary development


Evolutionary development1

Evolutionary development

  • Exploratory development

    • Objective is to work with customers and to evolve a final system from an initial outline specification. Should start with well-understood requirements and add new features as proposed by the customer.

  • Throw-away prototyping

    • Objective is to understand the system requirements. Should start with poorly understood requirements to clarify what is really needed.


Evolutionary development2

Evolutionary development

  • Problems

    • Lack of process visibility;

    • Systems are often poorly structured;

    • Special skills (e.g. in languages for rapid prototyping) may be required.

  • Applicability

    • For small or medium-size interactive systems;

    • For parts of large systems (e.g. the user interface);

    • For short-lifetime systems.


Component based software engineering

Component-based software engineering

  • Based on systematic reuse where systems are integrated from existing components or COTS (Commercial-off-the-shelf) systems.

  • Process stages

    • Component analysis;

    • Requirements modification;

    • System design with reuse;

    • Development and integration.

  • This approach is becoming increasingly used as component standards have emerged.


Reuse oriented development

Reuse-oriented development


Topics covered1

Topics covered

  • Software process models

  • Process iteration

  • Process activities

  • The Rational Unified Process

  • Computer-aided software engineering


Process iteration

Process iteration

  • System requirements ALWAYS evolve in the course of a project so process iteration where earlier stages are reworked is always part of the process for large systems.

  • Iteration can be applied to any of the generic process models.

  • Two (related) approaches

    • Incremental delivery;

    • Spiral development.


Incremental delivery

Incremental delivery

  • Rather than deliver the system as a single delivery, the development and delivery is broken down into increments with each increment delivering part of the required functionality.

  • User requirements are prioritised and the highest priority requirements are included in early increments.

  • Once the development of an increment is started, the requirements are frozen though requirements for later increments can continue to evolve.


Incremental development

Assign requirements

Design system

Define outline

to increments

requirements

ar

chitectur

e

Develop system

V

alida

te

Integ

r

a

te

V

alida

te

incr

ement

incr

ement

incr

ement

system

Final

system

S

ystem incomplete

Incremental development


Incremental development advantages

Incremental development advantages

  • Customer value can be delivered with each increment so system functionality is available earlier.

  • Early increments act as a prototype to help elicit requirements for later increments.

  • Lower risk of overall project failure.

  • The highest priority system services tend to receive the most testing.


Incremental development disadvantages

Incremental development disadvantages

  • Increments should be relatively small and still deliver some functionality

  • Might be difficult to map customer requirements into increments

  • High level requirements may not be sufficient to define system architecture


Agile software development

Agile software development

  • Lightweight process for incremental delivery

  • Manifesto:

    We are uncovering better ways of developing software by doing it

    and helping others do it. Through this work we have come to value:

    Individuals and interactions over processes and tools

    Working software over comprehensive documentation

    Customer collaboration over contract negotiation

    Responding to change over following a plan

    That is, while there is value in the items on the right,

    we value the items on the left more.


Extreme programming

Extreme programming

  • An agile method

  • “Extreme” because:

    • Extreme customer involvement

      • On-site customer

    • Extreme iterative development

      • Incremental planning, small releases, continuous integration, sustainable pace

    • Extreme teamwork

      • Pair programming, collective ownership

    • Extreme defect prevention

      • Simple design, test-first development, refactoring


Extreme programming practices 1

Extreme programming practices 1


Extreme programming practices 2

Extreme programming practices 2


Spiral development

Spiral development

  • Process is represented as a spiral rather than as a sequence of activities with backtracking.

  • Each loop in the spiral represents a phase in the process.

  • No fixed phases such as specification or design - loops in the spiral are chosen depending on what is required.

  • Risks are explicitly assessed and resolved throughout the process.


Spiral model of the software process

Deter

mine objecti

v

es,

Ev

alua

te alterna

ti

v

es,

alterna

ti

v

es and

identify

, r

esolv

e risks

constr

aints

Risk

anal

ysis

Risk

anal

ysis

Risk

Oper

a-

anal

ysis

Pr

ototype 3

tional

pr

oto

ype

Pr

ototype 2

Risk

Pr

oto-

anal

ysis

R

EVI

EW

type 1

R

equir

ements plan

Sim

ula

tions

, models

, benchmar

ks

Life-cy

cle plan

Concept of

Oper

a

tion

S/W

Pr

oduct

r

equir

ements

Detailed

design

design

R

equir

ement

De

v

elopment

v

alida

tion

plan

Code

Unit test

Design

Integ

r

a

tion

V&V

Integ

r

a

tion

and test plan

Plan ne

xt phase

test

Acceptance

test

De

v

elop

, v

erify

Service

ne

xt-le

v

el pr

oduct

Spiral model of the software process


Spiral model sectors

Spiral model sectors

  • Objective setting

    • Specific objectives for the phase are identified.

  • Risk assessment and reduction

    • Risks are assessed and activities put in place to reduce the key risks.

  • Development and validation

    • A development model for the system is chosen which can be any of the generic models.

  • Planning

    • The project is reviewed and the next phase of the spiral is planned.


Topics covered2

Topics covered

  • Software process models

  • Process iteration

  • Process activities

  • The Rational Unified Process

  • Computer-aided software engineering


Process activities

Process activities

  • Software specification

  • Software design and implementation

  • Software validation

  • Software evolution


Software specification

Software specification

  • The process of establishing what services are required and the constraints on the system’s operation and development.

  • Requirements engineering process

    • Feasibility study;

    • Requirements elicitation and analysis;

    • Requirements specification;

    • Requirements validation.


The requirements engineering process

R

equir

ements

F

easibility

elicitation and

stud

y

anal

ysis

R

equir

ements

specification

R

equir

ements

F

easibility

validation

r

epor

t

S

ystem

models

User and system

requirements

R

equir

ements

document

The requirements engineering process


Software design and implementation

Software design and implementation

  • The process of converting the system specification into an executable system.

  • Software design

    • Design a software structure that realises the specification;

  • Implementation

    • Translate this structure into an executable program;

  • The activities of design and implementation are closely related and may be inter-leaved.


Design process activities

Design process activities

  • Architectural design

  • Abstract specification

  • Interface design

  • Component design

  • Data structure design

  • Algorithm design


The software design process

The software design process


Components of a design method

Components of a design method

  • A set of system models

  • Rules that apply to these models

  • Guidelines for ‘good’ design

  • Design process model

  • Format of design document


Structured methods

Structured methods

  • Systematic approaches to developing a software design.

  • The design is usually documented as a set of graphical models.

  • Possible models

    • Object model;

    • Sequence model;

    • State transition model;

    • Structural model;

    • Data-flow model.


Programming and debugging

Programming and debugging

  • Translating a design into a program and removing errors from that program.

  • Programming is a personal activity - there is no generic programming process.

  • Programmers carry out some program testing to discover faults in the program and remove these faults in the debugging process.


The debugging process

The debugging process


Software validation

Software validation

  • Verification and validation (V & V) is intended to show that a system conforms to its specification and meets the requirements of the system customer.

  • Involves checking and review processes and system testing.

  • System testing involves executing the system with test cases that are derived from the specification of the real data to be processed by the system.


The testing process

S

ystem

Acceptance

Component

testing

testing

testing

The testing process


Testing stages

Testing stages

  • Component or unit testing

    • Individual components are tested independently;

    • Components may be functions or objects or coherent groupings of these entities.

  • System testing

    • Testing of the system as a whole. Testing of emergent properties is particularly important.

  • Acceptance testing

    • Testing with customer data to check that the system meets the customer’s needs.


Testing phases

R

equir

ements

S

ystem

S

ystem

Detailed

specifica

tion

specifica

tion

design

design

S

ystem

Sub-system

Module and

Acceptance

integ

r

a

tion

integ

r

a

tion

unit code

test plan

test plan

test plan

and test

Acceptance

S

ystem

Sub-system

Service

test

integ

r

a

tion test

integ

r

a

tion test

Testing phases


Software evolution

Software evolution

  • Software is inherently flexible and can change.

  • As requirements change through changing business circumstances, the software that supports the business must also evolve and change.

  • Although there has been a demarcation between development and evolution (maintenance) this is increasingly irrelevant as fewer and fewer systems are completely new.


System evolution

System evolution


Topics covered3

Topics covered

  • Software process models

  • Process iteration

  • Process activities

  • The Rational Unified Process

  • Computer-aided software engineering


The rational unified process

The Rational Unified Process

  • A modern process model derived from the work on the UML and associated process.

  • Normally described from 3 perspectives

    • A dynamic perspective that shows phases over time;

    • A static perspective that shows process activities;

    • A practice perspective that suggests good practice.


Rup phase model

RUP phase model


Rup phases

RUP phases

  • Inception

    • Establish the business case for the system.

  • Elaboration

    • Develop an understanding of the problem domain and the system architecture.

  • Construction

    • System design, programming and testing.

  • Transition

    • Deploy the system in its operating environment.


Rup good practice

RUP good practice

  • Develop software iteratively

  • Manage requirements

  • Use component-based architectures

  • Visually model software

  • Verify software quality

  • Control changes to software


Static workflows

Static workflows


Dynamic phases and static workflows

Dynamic Phases and Static Workflows


Topics covered4

Topics covered

  • Software process models

  • Process iteration

  • Process activities

  • The Rational Unified Process

  • Computer-aided software engineering


Computer aided software engineering

Computer-aided software engineering

  • Computer-aided software engineering (CASE) is software to support software development and evolution processes.

  • Activity automation

    • Graphical editors for system model development;

    • Data dictionary to manage design entities;

    • Graphical UI builder for user interface construction;

    • Debuggers to support program fault finding;

    • Automated translators to generate new versions of a program.


Case technology

CASE technology

  • CASE technology has led to significant improvements in the software process. However, these are not the order of magnitude improvements that were once predicted

    • Software engineering requires creative thought - this is not readily automated;

    • Software engineering is a team activity and, for large projects, much time is spent in team interactions. CASE technology does not really support these.


Case classification

CASE classification

  • Classification helps us understand the different types of CASE tools and their support for process activities.

  • Functional perspective

    • Tools are classified according to their specific function.

  • Process perspective

    • Tools are classified according to process activities that are supported.

  • Integration perspective

    • Tools are classified according to their organisation into integrated units.


Functional tool classification

Functional tool classification


Activity based tool classification

Activity-based tool classification


Case integration

CASE integration

  • Tools

    • Support individual process tasks such as design consistency checking, text editing, etc.

  • Workbenches

    • Support a process phase such as specification or design, Normally include a number of integrated tools.

  • Environments

    • Support all or a substantial part of an entire software process. Normally include several integrated workbenches.


Tools workbenches environments

Tools, workbenches, environments

C

ASE

technolo

g

y

W

or

kbenches

En

vir

onments

T

ools

File

Integ

r

a

ted

Pr

ocess-centr

ed

Editors

Compilers

compar

a

tors

en

vir

onments

en

vir

onments

Anal

ysis and

Pr

o

g

r

amming

T

esting

design

Multi-method

Single-method

Gener

al-purpose

Langua

ge-specific

w

or

kbenches

w

or

kbenches

w

or

kbenches

w

or

kbenches


Key points

Key points

  • Software processes are the activities involved in producing and evolving a software system.

  • Software process models are abstract representations of these processes.

  • General activities are specification, design and implementation, validation and evolution.

  • Generic process models describe the organisation of software processes. Examples include the waterfall model, evolutionary development and component-based software engineering.

  • Iterative process models describe the software process as a cycle of activities.


Key points1

Key points

  • Requirements engineering is the process of developing a software specification.

  • Design and implementation processes transform the specification to an executable program.

  • Validation involves checking that the system meets to its specification and user needs.

  • Evolution is concerned with modifying the system after it is in use.

  • The Rational Unified Process is a generic process model that separates activities from phases.

  • CASE technology supports software process activities.


  • Login