Beruflich Dokumente
Kultur Dokumente
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
existing system C D
browsing courses
browsing courses
room allocation
room allocation
registering
exam scheduling registering
exam scheduling
fee payment
fee payment
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
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
xxxxxxxxxxxxxxx xxxxxxxxxxxxxx
xxx xxx
xxxxxxxxxxx
xxxxxxxxxxxxxxx
xxxxx
xxxxxxxxxxxxx
xxxxxxx
sub-subsystems xxx
xxxxxxxxxxxxxxx
Requirements
Requirements Requirements
Requirements Definition Definition
Definition Definition xxxx
xxxx
xxxx
xxxxxxx
xxxx
xxxxxxx
xxx Requirements
xxx Requirements
xxxxxxx
xxxxxxx
xxx Requirements
xxx Requirements
xxxxxxxxxxx xxxxxxxxxxx
sub-subsystems
xxxxxxxxxxx xxxxxxxxxxx xxxxx Specification
xxxxx Specification
Specification
Specification
xxxxx xxxx
xxxxxxxxxxxxx Requirements
xxxxx xxxx xxxxxxxxxxxxx
xxxx xxxxxxx
xxxxxxxxxxxxx
xxxx xxxxxxxxxxxxx xxxxxxx
xxxxxxx xxxxxxx Requirements Requirements
xxxxxxx xxx xxx Requirements Definition
xxxxxxx xxxxxxx
xxxxxxx xxx xxx xxx xxxxxxxxxxx Definition
Definition
xxx xxx xxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxx xxxxx Definition xxxx
xxxxxxxxxxx
xxxxxxxxxxxxxxx xxxx xxxx xxxxxxx
xxxxxxxxxxxxxxx
xxxxxxxxxxx xxxxx xxxxx xxxxxxxxxxxxx xxxx xxxxxxx
xxxxx xxxxxxx xxx Requirements
xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxx xxxxxxx xxx Requirements
xxx Requirements
xxxxxxxxxxxxx xxxxxxx xxxxxxx xxx Requirements xxxxxxxxxxx xxxxxxxxxxx
xxxxxxx xxx
xxx
xxxxxxxxxxx xxxxxxxxxxx xxxxx Specification
xxxxx Specification
Specification
xxx xxxxxxxxxxxxxxx xxxxx
Specification xxxx
xxxxxxxxxxxxx
xxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxx xxxx xxxxxxxxxxxxx
xxxx xxxxxxx
xxxxxxxxxxxxxxx xxxxxxxxxxxxx
xxxx xxxxxxxxxxxxx xxxxxxx xxxxxxx
xxxxxxx
xxxxxxx xxx xxx
xxxxxxx xxxxxxx
xxxxxxx xxx xxx
xxx xxx xxx xxx xxxxxxxxxxxxxxx
xxxxxxxxxxx
xxxxxxxxxxx
xxxxxxxxxxxxxxx
xxxxxxxxxxx
xxxxxxxxxxxxxxx xxxxx
xxxxxxxxxxxxxxx
xxxxxxxxxxx xxxxx xxxxx xxxxxxxxxxxxx
xxxxx xxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxx
xxxxxxxxxxxxx xxxxxxx xxxxxxx xxx
xxxxxxx xxx xxx xxxxxxxxxxxxxxx
xxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxx
• Traceability:
Requirements
document
rationale Design
1.1 XXXX
document
.... because
1.2 YYYY
....due to
requirement 1.2
A. Problem
B. Background information
C. Environment and system models
D. Functional Requirements
E. Non-functional requirements