Requirements Engineering

Processes
1

. 2011


Definition of Requirements
: Requirements

Functional
.

Non-Functional
.
Constraints
.

Domain Req. .
. 2011

Requirements Engineering processes

System
Req

Application Domains

organization

developing the requirements

people involved
2011 .

RE

inception

.1

Developer &
Customer
Eliciting

2011 .

.2

Elicitation Work Products

HW,SW,HR Req. & Feasibility of system

product or system scope

stakeholder

technical environment
functional Req.

Domain Req.
throwaway prototype
Use cases

User scenarios
2011 .

Elaboration
Functional Req.

.3

Prototype
non functional
negotiation

.4

Win-win
2011 .

RE activities
non functional

Specification
Functional Req.
CBIS
validation

.5

.6

Formal technical review

Req. documents

2011 .

Requirements Engineering Processes

Analysis
Discover
System Req
management

Validation
Documentation

Feasibility Study

.1

Req. Elicitation

.2

Req. Analysis & Specifications

.3

Req. Validation

.4

Req. Management

.5

req. documentation
2011 .

.6
8

. 2011

10

. 2011

Feasibility studies

Legacy Sys
2011 .

11

Feasibility studies

12

what is required
(information collection

)..

Report Writing
. 2011

Feasibility studies

facilities must be supported

2011 .

13

Elicitation and analysis

requirements
elicitation or requirements discovery.

Domain req.
Functional Req.
Constraints or non-Functional Req.
2011 .

14

Elicitation and analysis

Elicitation and analysis

end-users

managers
engineers

domain experts

trade unions

stakeholders.

2011 .

15

Elicitation and analysis

analysis process problems

analysis process

2011 .

16

The requirements spiral

Requ iremen ts
class ifi cat io n an d
org ani s at i on

Requ iremen ts
pri orit i zat io n an d
nego ti ati on

Requ iremen ts
di s co very

Requ iremen ts
do cu ment at i on

2011 .

17

requirements analysis process

Requirements discovery-

Domain understanding

Requirements classification and

organisation
Prioritisation

and

negotiation
Resolve Req. conflict & contradiction

Requirements documentation-specification
. :
2011 .

18

requirements analysis process

.1

Req. Collection : Requirements

.2

discovery

user and system requirements

.3

2011 .

19

requirements analysis process

Conflict resolution

prioritization
Req.Validation

Req. Specifications

.4

.5
.6
.7

2011 .

20

The requirements analysis

process
Requir ements
definition and
specification

Requirements
validation

Process
entry

Domain
understanding

Prioritization

Requirements
collection

Conflict
resolution

Classification

2011 .

21

Types of viewpoint

viewpoint

Stakeholders
Stakeholders

viewpoint

2011 .

22

Types of viewpoint

multi-perspective VORD
Stakeholders

viewpoint

2011 .

23

Types of viewpoint

- : Inter-actor viewpoints

. ATM
Inter-actor VPs
: Indirect viewpoints
Stakeholders
: influence the requirements ATM
Indirect viewpoints

:Domain viewpoints:

. ATM

standards for inter-bank communications.

24

. 2011

VORD

viewpoint

viewpoint

viewpoint

.viewpoint

viewpoint
viewpoint System Mapping

2011 .

25

The VORD method

Viewpoint
identification

Viewpoint
structuring

Viewpoint
documentation

2011 .

Viewpoint
system mapping

26

Viewpoint identification
Viewpoint identification
Providers and receivers

Regulations and standards

business and

non-functional requirements
Engineers who have .
to develop and maintain
.

2011 .

27

LIBSYS viewpoint hierarchy

All VPs

Ind irect

Library
manager

Fin ance

Stu den ts

Interactor

Article
providers

Staff

Users

External

2011 .

Do main

Library
staff

System
managers

UI
stand ards

Classificatio n
system

Catalog uers

28

The VORD method

viewpoint

identifications

viewpoint-Structuring
viewpoint

viewpoint

Functions
Documentation

System Mapping

viewpoint
Object

oriented Design
2011 .

29

VORD standard forms

Reference

attributes

Events
:
Services

Sub
view
points
30

viewpoint Template

CID -
-
:
:
.

:
.

. 2011

Services
Template
reference

rational

Specifications

Viewpoints

Receivers :

Nonfunctional

constraint
:

Providers

31

. 2011

Viewpoint identification

2011 .

32

Viewpoint identification
Query
balance
Machine
supplies

Get
transactions

Customer
database

Account
holder
Remote
diagnostics

Card
returning

Manager
Message
log

Account
information
User
interface

System cost
Stolen
card

Reliability

Cash
withdrawal

Software
size

Foreign
customer

Order
statement

Printe
r
Hardware
maintenance

Update
account

2011 .

Funds
transfer

Transaction
log

Remote
software
upgrade

Order
cheques

Bank
teller

Invalid
user

Security
Message
passing

Card
retention
Card
validation
33

 ATM stakeholders

Bank customers
Representatives of other banks
Bank managers
Counter staff
Database administrators
Security managers
Marketing department
Hardware and software maintenance
engineers
Banking regulators

2011 .

34

Viewpoint service information

ACCOUNT
HOLDER
Service list
Withdraw cash
Query balance
Or der cheques
Send message
Transaction list
Or der statement
Transfer funds

FOREIGN
CUSTOMER
Service list
Withdraw cash
Query balance

2011 .

BANK
TELLER
Service list
Run diagnostics
Add cash
Add paper
Send message

35

 Viewpoint data/control
-

ACCOUNT
HOLDER

Control input
Start transaction
Cancel transaction
End transaction
Select service

2011 .

Data input
Card details
PIN
Amount required
Message

36

Viewpoint hierarchy

2011 .

37

Viewpoint hierarchy
All VPs

Services
Query balance
Withdraw cash

Services

Customer

Account
holder

Foreign
customer

Bank staff

Teller

Manager

Engineer

Order cheques
Send message
Transaction list
Order statement
Transfer funds
2011 .

38

 ( )
System mapping

39

. 2011

Scenarios

Req.

Scenarios

Election

Req. Specifications

2011 .

40

Scenario descriptions
pre condition

event flow

Exception description

Post conditions
2011 .

41

Event scenarios

VORD

2011 .

42

Event scenario - start transaction

Card present
Valid card
User OK

Card
Request PIN
PIN

Timeout
Return card

Account
number
PIN

Validate user

Account
number

Select
service

Incorrect PIN
Re-enter PIN

Invalid card
Return card
Incorrect PIN
Stolen card

Return card

Retain card
2011 .

43

Notation for data and control analysis

2011 .

44

Exception description

Time out

return
card>
Invalid card
return card
Stolen card

retain card
2011 .

45

Use cases
User scenarios

:Use cases
Use

interaction cases

Actors
Use cases

2011 .

46

 -
Use cases description

47

. 2011


Use cases description

R2.3; R7.1

if then

48

. 2011


Use cases description

][A1
][A1

)(E1

49

. 2011

][E1

Lending use-case
:

Lending services
50

. 2011

Library use-cases.

Lending services
Library
User

Library
Staff

51

User administration

Catalog services

. 2011

Supplier

 use-cases:ATM

52

. 2011

 Good note

Sequence Diagram

Use cases

2011 .

53

Catalogue management Sequence diagram

Item:
Library Item

Books:
Catalog
Cataloguer:
Library Staff

Bookshop:
Supplier
Acquire

New
Catalog Item
Dispose

Uncatalog Item

2011 .

54

Social and organisational factors

Context

2011 .

55

Requirements validation

2011 .

56

Requirements checking
Validity

Consistency
Completeness
Realism
Verifiability
2011 .

57

Requirements reviews

2011 .

58

Review checks
Verifiability

Comprehensibility

.
Traceability
origin of the requirement clearly .
stated
Adaptability

2011 .

59

Requirements management

Requirements change

2011 .

60

Requirements management

Requirements

evolution

2011 .

61

Requirements evolution

Initial
understanding
of problem

Changed
understanding
of problem

Initial
requirements

Changed
requir ements

Time
2011 .

62

Enduring and volatile requirements

Enduring requirements

Volatile requirements

2011 .

63

Classification of requirements
Mutable requirements

Emergent requirements

Consequential requirements

Compatibility requirements

2011 .

64

Requirements management planning

Requirements identification

A change management process

.
Traceability policies
.
CASE tool support

65

. 2011

CASE tool support

2011 .

66

67

. 2011

dentified
problem

Requirements change management

Problem analysis and

change specification

Change analysis
and costing

2011 .

Change
implementation

Revised
requirements

68