Академический Документы
Профессиональный Документы
Культура Документы
Requirements Elicitation I
Organizational
Requirements
Engineering
Prof. Dr. Armin B. Cremers
Sascha Alda
Overview
z
Elicitation Techniques
This lesson
Scenarios
Interviews
Observation
Prototyping
Identifying actors
Best practice for modeling use cases
Refinement of use cases
Conclusions
Armin B. Cremers, Sascha Alda
Analysis
System
Design
Object
Design
Implementation
Testing
Expressed in
Terms of
Structured
by
Realized
by
Implemented
by
Verified
by
class...
class...
class...
Use Case
Model
Application
Domain
Objects
Armin B. Cremers, Sascha Alda
Subsystems
Solution
Domain
Objects
?
class....?
Source
Code
3
Test
Cases
Requirements Elicitation
First view
z
Requirements Elicitation
Further aspects
z
Standard SE
Agile assumption
time
Traditional view
Costs of changes develop exponentially due to time
Complexity of software increases over project time (and phases)
Problem understanding
Business understanding
Application
Domain
Stakeholder
needs and
constraints
Problem to
be solved
Business
Context
Draft
statement of
requirements
Requirements
elicitation
Requirements
analysis
Requirements
problems
Requirements
document
Requirements
Negotiation (with client)
Establish
Objects
Understand
Background
Organize
Knowledge
Collect
Requirements
Business
Goals
Organizational
structure
Stakeholder
Identification
Stakeholder
requirements
Problem to
be solved
Application
Domain
Goal
Priorization
Domain
requirements
System
Constraints
Existing
Systems
Organizational
Requirements
Establish
Objects
Understand
Background
Organize
Knowledge
Collect
Requirements
Business
Goals
Organizational
structure
Stakeholder
Identification
Stakeholder
requirements
Problem to
be solved
Application
Domain
Goal
Priorization
Domain
requirements
System
Constraints
Existing
Systems
Organizational
Requirements
10
Consistency And
Completeness Checking
Feasibility
Checking
Unnecessary
Requirements
Conflicting And
Incomplete Requirements
Infeasable
Requirements
Requirements
Discussion
Requirements
Priorization
Requirements
Agreement
Requirements Negotiation
Necessity checking
Feasibility checking
11
Consistency And
Completeness Checking
Feasibility
Checking
Unnecessary
Requirements
Conflicting And
Incomplete Requirements
Infeasable
Requirements
Requirements
Discussion
Requirements
Priorization
Requirements
Agreement
Requirements Negotiation
Requirements discussion
Requirements highlighted as problematical are discussed
the stakeholders involved present their views about the requirements
Requirements prioritization
Requirements agreement
A compromised set of requirements are agreed
changes
to some of the requirements
Armin B. Cremers, Sascha Alda
Organizational Requirements Engineering
12
Problem
Statement
Requirements
Elicitation
Requirements specification:
functional and
non-functional
requirements
Requirements
Analysis
Analysis Model:
dynamic model
object model
Organizational Requirements Engineering
13
14
15
z
z
A few pages
Project Schedule
Target environment
Major milestones that involve interaction with the client including deadline for
delivery of the system
The environment in which the delivered system has to perform a specified set
of system tests
16
authorization
Change
communication
17
functional
requirement
Implementation
requirement
performance
requirement
availability
requirement
Security
requirement
Armin B. Cremers, Sascha Alda
18
Validation
As-Is Scenarios
Interviewing
users and clients
Use Cases +
Refinements
Visionary
Scenarios
Validation
Prototypes
Validation
Functional Requirements
Non-Functional Requirements
Use Cases
Scenarios
20
Identifying Actors
Identifying Scenarios
Abstractions of Scenarios
(Many possible cases)
Scenarios
Next Lesson
Use Case
(=class of scenarios)
21
Sources of information
Documents
User Participation
Interviews
Closed Interviews: User answer a predefined set of questions
Open Interviews: No predefined agenda
Work Practice
User
Describing Scenarios
Armin B. Cremers, Sascha Alda
22
Validation
As-Is Scenarios
Interviewing
users and clients
Use Cases +
Refinements
Visionary
Scenarios
Validation
Prototypes
Validation
Functional Requirements
Non-Functional Requirements
Use Cases
Scenarios
23
24
Selection Criteria
z
z
z
Budget/Time
Degree of User Participation
Greenfield Engineering
Reengineering
Interface Engineering
Time
Experience of users
. (many more)
25
Scenarios
Interviews
Next lesson:
z
Prototyping
26
Interviews
Essentials
z
z
z
a question
a requirements proposal
an existing system
Different perspectives
global understanding of their requirements
27
Interviews
Different Techniques
z
No predefined agenda
28
Interviews
Oral interviews:
Written interviews
29
Interviews
30
Interviews
Transcription
z
Loudness of speech
Speech intermission
Gesture, facial expression
Emphasis of special words or phrases
Repeat of phrases
External factors
31
Interviews IV:
Different Goals
z
During analysis
32
Scenarios Overview 1
Motivation (Observation):
z System stakeholder find it more intuitive to reason about concrete
examples rather than abstract descriptions of the functions
provided by a system (use cases)
Solution: Scenario
z A narrative description of what people do and experience as they
try to make use of computer systems and applications [M. Carrol,
Scenario-based Design, Wiley, 1995]
z A concrete, focused, informal description of a single feature of the
system used by a single actor
z Discovering scenarios exposes possible system interactions and
reveals system facilities which may be required
33
Scenarios Overview 2
z
34
Scenarios:
Different Types
z
As-is scenario
Visionary scenario
Evaluation scenario
Training scenario
35
Scenarios:
36
Scenarios:
What are the primary tasks that the system needs to perform?
Do you know about any kind of system or service that already fulfills
some task?
What data will the (main) actor create, store, change, remove or add
in the system?
Are there other actors in the system (explain the term actor!)
37
Scenarios:
Heuristics for finding Scenarios
z
z
Ask to speak to the end user, not just to the software contractor
Expect resistance and try to overcome it
38
Scenarios:
39
Scenario:
Example - Warehouse on Fire
z
Bob, driving down main street in his patrol car notices smoke
coming out of a warehouse. His partner, Alice, reports the
emergency from her car by using the SYSTEM.
40
Scenarios:
Concrete scenario
Participating actors
41
Example:
Use Case
ReportFireIncident
Scenario
Warehouse on Fire
Scenario
Flat on Fire
ReportFireIncident
Scenario
Car on Fire
42
Summary
43