Professional Documents
Culture Documents
Lloseng CH 04 E2
Lloseng CH 04 E2
Chapter 4:
Developing Requirements
4.1 Domain Analysis
A. Introduction
B. Glossary
C. General knowledge about the domain
D. Customers and users
E. The environment
F. Tasks and procedures currently performed
G. Competing software
H. Similarities to other domains
New
development A B
green field project
Evolution of C D
existing system
Functional requirements
• Describe what the system should do
Quality requirements
• Constraints on the design to meet specified levels of
quality
Platform requirements
• Constraints on the environment and technology of the
system
Process requirements
• Constraints on the project plan and development
methods
Register in Course
Add Course Offering
Enter Grade
for Course
Student
Professor Actor
Steps:
Actor actions System responses
1. Choose ‘Open…’ command 2. File open dialog appears
3. Specify filename
4. Confirm selection 5. Dialog disappears
Steps:
Actor actions System responses
1. Choose ‘Open…’ command 2. File open dialog appears
3a. Select text field
3b. Type file name
4. Click ‘Open’ 5. Dialog disappears
Steps:
Actor actions System responses
1. Choose ‘Open…’ command 2. File open dialog appears
3. Browse for file
4. Confirm selection 5. Dialog disappears
Steps:
Actor actions System responses
1. If the desired file is not displayed, 2. Contents of directory is
select a directory displayed
3. Repeat step 1 until the desired file is
displayed
4. Select a file
Brainstorming
• Appoint an experienced moderator
• Arrange the attendees around a table
• Decide on a ‘trigger question’
• Ask each participant to write an answer and pass the
paper to its neighbour
! !
! !
!
Prototyping
• The simplest kind: paper prototype.
—a set of pictures of the system that are shown to
users in sequence to explain what would happen
• The most common: a mock-up of the system’s UI
—Written in a rapid prototyping language
—Does not normally perform any computations,
access any databases or interact with any other
systems
—May prototype a particular aspect of the system
requirements specification
xxxxxxx
xxx
xxxxxxxxxxx
xxxxx
xxxxxxxxxxxxx
xxxxxxx
xxx
xxxxxxxxxxxxxxx
arranged in a hierarchy
xxxxxxxxxxxxx
xxxxxxx xxxxx
xxxx
xxxxxxxxxxxxx
xxx xxxxxxx
xxxxxxxxxxxxxxx xxxxxxx
xxx xxx
xxxxxxxxxxx
xxxxxxxxxxxxxxx
xxxxx
xxxxxxxxxxxxx
xxxxxxx
sub-subsystems xxx
xxxxxxxxxxxxxxx
Requirements
Requirements Requirements
Requirements Definition Definition
Definition Definition xxxx
xxxx
xxxx
xxxxxxx
xxx Requirements
xxxx
xxxxxxx
xxx
xxxxxxx
xxx Requirements
Requirements
xxxxxxx
xxx Requirements
xxxxxxxxxxx xxxxxxxxxxx Specification
sub-subsystems
xxxxxxxxxxx xxxxxxxxxxx xxxxx
xxxxx Specification
Specification xxxx
xxxxx Specification
xxxxx
xxxx xxxxxxxxxxxxx
xxxx xxxxxxxxxxxxx
xxxxxxx Requirements
Requirements
xxxxxxxxxxxxx
xxxx xxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxx Requirements
xxxxxxx xxx xxx Requirements Definition
xxxxxxxxxxxxxx xxxxxxx xxx xxx xxx xxxxxxxxxxx Definition
Definition
xxx xxx xxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx
xxxxxxxxxxx Definition xxxx
xxxxxxxxxxx
xxxxxxxxxxxxxxx xxxxx xxxx xxxx xxxxxxx
xxxxxxxxxxxxxxx
xxxxxxxxxxx xxxxx xxxxx xxxxxxxxxxxxx xxxx xxxxxxx
xxxxx xxxxxxx xxx Requirements
xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxx xxxxxxx xxx Requirements
xxx Requirements
xxxxxxxxxxx
xxxxxxxxxxxxx xxxxxxx xxxxxxx xxx xxx Requirements xxxxxxxxxxx Specification
xxxxxxx xxx xxxxxxxxxxx xxxxxxxxxxx
Specification xxxxx
xxxxx Specification
xxx xxxxxxxxxxxxxxx xxxxx xxxx
xxxxxxxxxxxxx
xxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx Specification xxxx xxxxxxxxxxxxx
xxxx xxxxxxx
xxxxxxxxxxxxxxx xxxxxxxxxxxxx
xxxx xxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxx
xxxxxxx xxx xxx
xxxxxxxxxxxxxx xxxxxxx xxx xxx xxx xxxxxxxxxxx
xxx xxx xxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx
xxxxxxxxxxx
xxxxxxxxxxx
xxxxxxxxxxxxxxx xxxxx
xxxxxxxxxxxxxxx
xxxxxxxxxxx xxxxx xxxxx xxxxxxxxxxxxx
xxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxx
xxxxxxxxxxxxx xxxxxxx xxxxxxx xxx
xxxxxxx xxx xxx xxxxxxxxxxxxxxx
xxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxx
• Traceability:
Req uirements
documen t
rationa le Des ign
1.1 XXXX
documen t
.... because
1.2 YYYY
....due to
requ irement 1.2
A. Problem
B. Background information
C. Environment and system models
D. Functional Requirements
E. Non-functional requirements