Lecture 2 Software Processes
description
Transcript of Lecture 2 Software Processes
![Page 1: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/1.jpg)
LECTURE 2SOFTWARE PROCESSES
1
![Page 2: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/2.jpg)
OBJECTIVES To describe outline process models for
requirements engineering, software development, testing and evolution
To introduce CASE technology to support software process activities
2
![Page 3: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/3.jpg)
TOPICS COVERED Process activities Computer-aided software engineering
CH4 starting from p.74
3
![Page 4: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/4.jpg)
THE SOFTWARE PROCESS A structured set of activities required to
develop a software system
A software process model is an abstract representation of a process. It presents a description of a process from some particular perspective.
4
![Page 5: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/5.jpg)
PROCESS ACTIVITIES1. Software specification2. Software design and implementation3. Software validation4. Software evolution
5
![Page 6: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/6.jpg)
SOFTWARE SPECIFICATION The process of establishing what services are
required and the constraints on the system’s operation and development.
Requirements engineering process1. Feasibility study;2. Requirements elicitation and analysis;3. Requirements specification;4. Requirements validation.
6
![Page 7: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/7.jpg)
THE REQUIREMENTS ENGINEERING PROCESS
Feasibilitystudy
Requirementselicitation and
analysisRequirementsspecification
Requirementsvalidation
Feasibilityreport
Systemmodels
User and systemrequirements
Requirementsdocument
7
![Page 8: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/8.jpg)
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.
8
![Page 9: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/9.jpg)
DESIGN PROCESS ACTIVITIES1. Architectural design2. Abstract specification3. Interface design4. Component design5. Data structure design6. Algorithm design
9
![Page 10: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/10.jpg)
THE SOFTWARE DESIGN PROCESS
Architecturaldesign
Abstractspecification
Interfacedesign
Componentdesign
Datastructuredesign
Algorithmdesign
Systemarchitecture
Softwarespecification
Interfacespecification
Componentspecification
Datastructure
specificationAlgorithm
specification
Requirementsspecification
Design activities
Design products
10
![Page 11: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/11.jpg)
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.
Will be covered in chapters 10, 1411
![Page 12: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/12.jpg)
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.
12
![Page 13: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/13.jpg)
THE DEBUGGING PROCESS
Locateerror
Designerror repair
Repairerror
Re-testprogram
13
![Page 14: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/14.jpg)
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.
14
![Page 15: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/15.jpg)
THE TESTING PROCESS
Componenttesting
Systemtesting
Acceptancetesting
15
![Page 16: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/16.jpg)
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.
16
![Page 17: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/17.jpg)
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.
17
![Page 18: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/18.jpg)
SYSTEM EVOLUTION
Assess existingsystems
Define systemrequirements
Propose systemchanges
Modifysystems
Newsystem
Existingsystems
18
![Page 19: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/19.jpg)
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.19
![Page 20: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/20.jpg)
EXAMPLES
20
![Page 21: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/21.jpg)
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.
21
![Page 22: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/22.jpg)
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.
22
![Page 23: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/23.jpg)
TOOLS, WORKBENCHES, ENVIRONMENTS
Single-methodworkbenches
General-purposeworkbenches
Multi-methodworkbenches
Language-specificworkbenches
Programming TestingAnalysis anddesign
Integratedenvironments
Process-centredenvironments
FilecomparatorsCompilersEditors
EnvironmentsWorkbenchesTools
CASEtechnology
23
![Page 24: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/24.jpg)
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.
24
![Page 25: Lecture 2 Software Processes](https://reader036.fdocuments.us/reader036/viewer/2022070500/56816881550346895ddefa3e/html5/thumbnails/25.jpg)
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.
CASE technology supports software process activities.
25