l processes used to discover, analyse and validate system ...scharff/cs389/ref/ch6cs389.pdftypes of...

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1

Requirements Engineering Processes

l Processes used to discover,analyse and validate systemrequirements

Objectives

l To describe the principal requirementsengineering activities

l To introduce techniques for requirementselicitation and analysis

l To describe requirements validation

l To discuss the role of requirements managementin support of other requirements engineeringprocesses

Topics covered

l Feasibility studies

l Requirements elicitation and analysis

l Requirements validation

l Requirements management

Requirements engineering processes

l The processes used for RE vary widelydepending on the application domain, the peopleinvolved and the organisation developing therequirements

l However, there are a number of generic activitiescommon to all processes• Requirements elicitation

• Requirements analysis

• Requirements validation

• Requirements management

The requirements engineering process

Feasibilitystudy

Requirementselicitation and

analysisRequirementsspecification

Requirementsvalidation

Feasibilityreport

Systemmodels

User and systemrequirements

Requirementsdocument

Feasibility studies

l A feasibility study decides whether or not theproposed system is worthwhile

l A short focused study that checks• If the system contributes to organisational objectives

• If the system can be engineered using current technology andwithin budget

• If the system can be integrated with other systems that are used

Feasibility study implementation

l Based on information assessment (what isrequired), information collection and reportwriting

l Questions for people in the organisation• What if the system wasn’t implemented?

• What are current process problems?

• How will the proposed system help?

• What will be the integration problems?

• Is new technology needed? What skills?

• What facilities must be supported by the proposed system?

Elicitation and analysis

l Sometimes called requirements elicitation orrequirements discovery

l Involves technical staff working with customersto find out about the application domain, theservices that the system should provide and thesystem’s operational constraints

l May involve end-users, managers, engineersinvolved in maintenance, domain experts, tradeunions, etc. These are called stakeholders

Problems of requirements analysis

l Stakeholders don’t know what they really want

l Stakeholders express requirements in their ownterms

l Different stakeholders may have conflictingrequirements

l Organisational and political factors may influencethe system requirements

l The requirements change during the analysisprocess. New stakeholders may emerge and thebusiness environment change

The requirements analysis process

Requirementsvalidation

Domainunderstanding

Prioritization

Requirementscollection

Conflictresolution

Classification

Requirementsdefinition andspecification

Processentry

Process activities

l Domain understanding

l Requirements collection

l Classification

l Conflict resolution

l Prioritisation

l Requirements checking

System models

l Different models may be produced during therequirements analysis activity

l Requirements analysis may involve threestructuring activities which result in thesedifferent models• Partitioning. Identifies the structural (part-of) relationships

between entities

• Abstraction. Identifies generalities among entities

• Projection. Identifies different ways of looking at a problem

l System models covered in Chapter 7

Viewpoint-oriented elicitation

l Stakeholders represent different ways of lookingat a problem or problem viewpoints

l This multi-perspective analysis is important asthere is no single correct way to analyse systemrequirements

Banking ATM system

l The example used here is an auto-teller systemwhich provides some automated banking services

l I use a very simplified system which offers someservices to customers of the bank who own thesystem and a narrower range of services to othercustomers

l Services include cash withdrawal, messagepassing (send a message to request a service),ordering a statement and transferring funds

Autoteller viewpoints

l Bank customers

l Representatives of other banks

l Hardware and software maintenance engineers

l Marketing department

l Bank managers and counter staff

l Database administrators and security staff

l Communications engineers

l Personnel department

Types of viewpoint

l Data sources or sinks• Viewpoints are responsible for producing or consuming data.

Analysis involves checking that data is produced and consumedand that assumptions about the source and sink of data are valid

l Representation frameworks• Viewpoints represent particular types of system model. These

may be compared to discover requirements that would bemissed using a single representation. Particularly suitable forreal-time systems

l Receivers of services• Viewpoints are external to the system and receive services from

it. Most suited to interactive systems

External viewpoints

l Natural to think of end-users as receivers ofsystem services

l Viewpoints are a natural way to structurerequirements elicitation

l It is relatively easy to decide if a viewpoint isvalid

l Viewpoints and services may be sued to structurenon-functional requirements

Method-based analysis

l Widely used approach to requirements analysis.Depends on the application of a structuredmethod to understand the system

l Methods have different emphases. Some aredesigned for requirements elicitation, others areclose to design methods

l A viewpoint-oriented method (VORD) is used asan example here. It also illustrates the use ofviewpoints

The VORD method

Viewpointidentification

Viewpointstructuring

Viewpointdocumentation

Viewpointsystem mapping

VORD process model

l Viewpoint identification• Discover viewpoints which receive system services and identify

the services provided to each viewpoint

l Viewpoint structuring• Group related viewpoints into a hierarchy. Common services are

provided at higher-levels in the hierarchy

l Viewpoint documentation• Refine the description of the identified viewpoints and services

l Viewpoint-system mapping• Transform the analysis to an object-oriented design

VORD standard forms

Viewpoint template Service templateReference: The viewpoint name. Reference: The service name.Attributes: Attributes providing

viewpoint information.Rationale: Reason why the service is

provided.Events: A reference to a set of event

scenarios describing howthe system reacts toviewpoint events.

Spec i f i ca t ion : Reference to a list of servicespecifications. These maybe expressed in differentnotations.

Serv ices A reference to a set ofservice descriptions.

Viewpoint s : List of viewpoint namesreceiving the service.

Sub-VPs: The names of sub-viewpoints.

Non-funct ionalrequirements:

Reference to a set of non-functional requirementswhich constrain the service.

Provider: Reference to a list of systemobjects which provide theservice.

Viewpoint identification

Querybalance

Gettransactions

Cashwithdrawal

Transactionlog

Machinesupplies

Cardreturning

Remotesoftwareupgrade

Ordercheques

Userinterface

Accountinformation

Messagelog

Softwaresize Invalid

userSystem cost Printe

r Security

Cardretention

Stolencard

Orderstatement

Remotediagnostics Reliability

Updateaccount

Fundstransfer

Messagepassing

Cardvalidation

Customerdatabase

Manager

Accountholder

Foreigncustomer

Hardwaremaintenance

Bankteller

Viewpoint service information

FOREIGNCUSTOMER

Withdraw cashQuery balance

Service list

Withdraw cashQuery balanceOrder chequesSend messageTransaction listOrder statementTransfer funds

Service list

Run diagnosticsAdd cashAdd paperSend message

Service list

ACCOUNTHOLDER

BANKTELLER

Viewpoint data/control

Start transactionCancel transactionEnd transactionSelect service

Card detailsPINAmount requiredMessage

Control input Data inputACCOUNTHOLDER

Viewpoint hierarchy

EngineerManagerTellerForeigncustomer

Accountholder

Services

Order chequesSend messageTransaction listOrder statementTransfer funds

Customer Bank staff

All VPs

Services

Query balanceWithdraw cash

Customer/cash withdrawal templatesCustomer

Account numberPINStart transactionSelect serviceCanceltransactionEnd transaction

Cash withdrawalBalance enquiry

Account holderForeigncustomer

Reference:

Attributes:

Events:

Services:

Sub-VPs:

Cash withdrawal

To improve customer serviceand reduce paperwork

Users choose this service bypressing the cash withdrawalbutton. They then enter theamount required. This isconfirmed and, if funds allow,the balance is delivered.

Customer

Deliver cash within 1 minuteof amount being confirmed

Filled in later

Reference:

Rationale:

Specification:

Non-funct.requirements:

Provider:

Scenarios

l Scenarios are descriptions of how a system isused in practice

l They are helpful in requirements elicitation aspeople can relate to these more readily thanabstract statement of what they require from asystem

l Scenarios are particularly useful for adding detailto an outline requirements description

Scenario descriptions

l System state at the beginning of the scenario

l Normal flow of events in the scenario

l What can go wrong and how this is handled

l Other concurrent activities

l System state on completion of the scenario

Event scenarios

l Event scenarios may be used to describe how asystem responds to the occurrence of someparticular event such as ‘start transaction’

l VORD includes a diagrammatic convention forevent scenarios.• Data provided and delivered

• Control information

• Exception processing

• The next expected event

Event scenario - start transaction

Validate user

Request PIN

Selectservice

Timeout

Return card

Invalid card

Return card

Stolen card

Retain card

Incorrect PIN

Re-enter PIN

Incorrect PIN

Return card

Card present

Accountnumber

Valid card

User OK

Notation for data and control analysis

l Ellipses. data provided from or delivered to aviewpoint

l Control information enters and leaves at the topof each box

l Data leaves from the right of each box

l Exceptions are shown at the bottom of each box

l Name of next event is in box with thick edges

Exception description

l Most methods do not include facilities fordescribing exceptions

l In this example, exceptions are• Timeout. Customer fails to enter a PIN within the allowed time

• Invalid card. The card is not recognised and is returned

• Stolen card. The card has been registered as stolen and isretained by the machine

Use cases

l Use-cases are a scenario based technique in theUML which identify the actors in an interactionand which describe the interaction itself

l A set of use cases should describe all possibleinteractions with the system

l Sequence diagrams may be used to add detail touse-cases by showing the sequence of eventprocessing in the system

Lending use-case

Lending services

Library use-cases

Lending services

User administration

Supplier Catalog services

LibraryUser

LibraryStaff

Catalogue management

Bookshop:Supplier

Cataloguer:Library Staff

Item:Library Item

Books:Catalog

Acquire New

Catalog Item

Uncatalog Item

Dispose

Social and organisational factors

l Software systems are used in a social andorganisational context. This can influence or evendominate the system requirements

l Social and organisational factors are not a singleviewpoint but are influences on all viewpoints

l Good analysts must be sensitive to these factorsbut currently no systematic way to tackle theiranalysis

Example

l Consider a system which allows seniormanagement to access information without goingthrough middle managers• Managerial status. Senior managers may feel that they are too

important to use a keyboard. This may limit the type of systeminterface used

• Managerial responsibilities. Managers may have nouninterrupted time where they can learn to use the system

• Organisational resistance. Middle managers who will be maderedundant may deliberately provide misleading or incompleteinformation so that the system will fail

Ethnography

l A social scientists spends a considerable timeobserving and analysing how people actuallywork

l People do not have to explain or articulate theirwork

l Social and organisational factors of importancemay be observed

l Ethnographic studies have shown that work isusually richer and more complex than suggestedby simple system models

Focused ethnography

l Developed in a project studying the air trafficcontrol process

l Combines ethnography with prototyping

l Prototype development results in unansweredquestions which focus the ethnographic analysis

l Problem with ethnography is that it studiesexisting practices which may have somehistorical basis which is no longer relevant

Ethnography and prototyping

Ethnographicanalysis

Debriefingmeetings

Focusedethnography

Prototypeevaluation

Generic systemdevelopment

Systemprotoyping

Scope of ethnography

l Requirements that are derived from the way thatpeople actually work rather than the way I whichprocess definitions suggest that they ought towork

l Requirements that are derived from cooperationand awareness of other people’s activities

Requirements validation

l Concerned with demonstrating that therequirements define the system that the customerreally wants

l Requirements error costs are high so validation isvery important• Fixing a requirements error after delivery may cost up to 100

times the cost of fixing an implementation error

Requirements checking

l Validity. Does the system provide the functionswhich best support the customer’s needs?

l Consistency. Are there any requirementsconflicts?

l Completeness. Are all functions required by thecustomer included?

l Realism. Can the requirements be implementedgiven available budget and technology

l Verifiability. Can the requirements be checked?

Requirements validation techniques

l Requirements reviews• Systematic manual analysis of the requirements

l Prototyping• Using an executable model of the system to check requirements.

Covered in Chapter 8

l Test-case generation• Developing tests for requirements to check testability

l Automated consistency analysis• Checking the consistency of a structured requirements

description

Requirements reviews

l Regular reviews should be held while therequirements definition is being formulated

l Both client and contractor staff should beinvolved in reviews

l Reviews may be formal (with completeddocuments) or informal. Good communicationsbetween developers, customers and users canresolve problems at an early stage

Review checks

l Verifiability. Is the requirement realisticallytestable?

l Comprehensibility. Is the requirement properlyunderstood?

l Traceability. Is the origin of the requirementclearly stated?

l Adaptability. Can the requirement be changedwithout a large impact on other requirements?

Automated consistency checking

Requirementsdatabase

Requirementsanalyser

Requirementsproblem report

Requirementsprocessor

Requirementsin a formal language

Requirements management

l Requirements management is the process ofmanaging changing requirements during therequirements engineering process and systemdevelopment

l Requirements are inevitably incomplete andinconsistent• New requirements emerge during the process as business needs

change and a better understanding of the system is developed

• Different viewpoints have different requirements and these areoften contradictory

Requirements change

l The priority of requirements from differentviewpoints changes during the developmentprocess

l System customers may specify requirements froma business perspective that conflict with end-userrequirements

l The business and technical environment of thesystem changes during its development

Requirements evolution

Changedunderstanding

of problem

Initialunderstanding

of problem

Changedrequirements

Initialrequirements

Enduring and volatile requirements

l Enduring requirements. Stable requirementsderived from the core activity of the customerorganisation. E.g. a hospital will always havedoctors, nurses, etc. May be derived from domainmodels

l Volatile requirements. Requirements whichchange during development or when the system isin use. In a hospital, requirements derived fromhealth-care policy

Classification of requirements

l Mutable requirements• Requirements that change due to the system’s environment

l Emergent requirements• Requirements that emerge as understanding of the system

develops

l Consequential requirements• Requirements that result from the introduction of the computer

system

l Compatibility requirements• Requirements that depend on other systems or organisational

processes

Requirements management planning

l During the requirements engineering process, youhave to plan:• Requirements identification

» How requirements are individually identified

• A change management process» The process followed when analysing a requirements change

• Traceability policies» The amount of information about requirements relationships that is

maintained

• CASE tool support» The tool support required to help manage requirements change

Traceability

l Traceability is concerned with the relationshipsbetween requirements, their sources and thesystem design

l Source traceability• Links from requirements to stakeholders who proposed these

requirements

l Requirements traceability• Links between dependent requirements

l Design traceability• Links from the requirements to the design

A traceability matrix

Req.id

1.1 1.2 1.3 2.1 2.2 2.3 3.1 3.2

1.1 U R1.2 U R U1.3 R R2.1 R U U2.2 U2.3 R U3.1 R3.2 R

CASE tool support

l Requirements storage• Requirements should be managed in a secure, managed data

l Change management• The process of change management is a workflow process

whose stages can be defined and information flow betweenthese stages partially automated

l Traceability management• Automated retrieval of the links between requirements

Requirements change management

l Should apply to all proposed changes to therequirements

l Principal stages• Problem analysis. Discuss requirements problem and propose

change

• Change analysis and costing. Assess effects of change on otherrequirements

• Change implementation. Modify requirements document andother documents to reflect change

Requirements change management

Changeimplementation

Change analysisand costing

Problem analysis andchange specification

Identifiedproblem

Revisedrequirements

Key points

l The requirements engineering process includes afeasibility study, requirements elicitation andanalysis, requirements specification andrequirements management

l Requirements analysis is iterative involvingdomain understanding, requirements collection,classification, structuring, prioritisation andvalidation

l Systems have multiple stakeholders with differentrequirements

Key points

l Social and organisation factors influence systemrequirements

l Requirements validation is concerned withchecks for validity, consistency, completeness,realism and verifiability

l Business changes inevitably lead to changingrequirements

l Requirements management includes planning andchange management

l processes used to discover, analyse and validate system ...scharff/cs389/ref/ch6cs389.pdftypes of...

Documents

scaling properties of dimensionality reduction for neural...

object-oriented design designing systems using self...

chapter 8 – software...

system models l abstract descriptions of systems whose...

formal software verification christelle scharff scharff may...

beverly hills dental...

from: mark scharff, liaison to cc:da from the

chapter 3 – agile software...

mark scharff, gaylord music library washington university in...

richard scharff värmelager - en översikt 20170517

mr. scharff name

alexander scharff - Ägyptische sonnenlieder (1922)

waste macro-management henrik lid scharff. what is waste?

from: mark scharff, liaison to cc:da from the...

alexander scharff agyptische sonnenlieder 1922

terapia di coppia secondo il modello delle relazioni...

design with reuse l building software from reusable...

systemfeld - profil stephan scharff-rahn - java, core media,...

a report prepared by spencer g. scharff and scott caplan

chapter 9 – software...