 |
Iterative Requirements Development
This three-day workshop provides instruction in managing requirements
in an iterative development process. Includes writing, revising
and utilization of use cases; mapping requirements to specifications;
feedback management; reinforcing the training with hands-on experience
in use case and scenario design and creation.
The techniques and experiences acquired in this course are useful
in any development environment, object-oriented or not, which utilizes
an iterative process.
Audience
Analysts, designers, developers, system testers, and project managers/management
involved in software development
Prerequisites
- Previous exposure to use cases helpful, but not required
- Requirements and/or analysis experience helpful, but not required
Course Topics
Day 1
-
Workshop Overview
-
Iteration Essentials
-
What is iteration?
-
What does iteration
do for the stakeholders?
-
How big is an
iteration?
-
Requirements Essentials
-
What is a requirement?
-
Where do requirements
come from?
-
How are requirements
recorded?
-
Use Case Essentials
-
What is a use
case?
-
What does a use
case look like?
-
What purposes
do use cases serve?
-
When in a project
should use cases appear
-
Specifications Essentials
-
What is a functional
specification?
-
How is it recorded?
-
How is it updated?
-
What is the relationship
to Requirements and Use Cases?
-
Use Case Diagrams
in UML
-
What does a use
case diagram look like?
-
How does a use
case diagram help organize use cases?
-
When in a project
should use case diagrams appear?
-
How is a use
case diagram constructed?
-
Scenarios
-
What is a scenario?
-
What does a scenario
look like?
-
How do scenarios
relate to use cases?
Day 2
-
Writing The Primary
Scenario
-
How are scenarios
classified as primary or secondary?
-
What purpose
does this classification serve?
-
What techniques
are useful when writing primary scenarios?
-
Use Cases and Requirements
-
How do use cases
relate to requirements?
-
Do use cases
replace requirements?
-
Can use cases
be written without requirements?
-
Requirements and
change management
-
Requirements
prioritization
-
Tools
-
Task management
-
Bugzilla
-
Wikis
-
Commercial
tools
-
Artifact management
-
Code control
-
Document
Control
-
Intra- and inter-team
communication
-
Task changes
-
Process
changes
Day 3
-
Feedback Incorporation
-
Feedback – the
reason for iterating
-
Feedback sources
-
Bugs
-
Beta tests
-
Stakeholder
input
-
Peer review
-
Progress rates
-
Incorporating
feedback
-
Adjusting the
plan
-
Testing and Reviewing
Use Cases
-
What information
should appear in a use case?
-
How can use
cases be verified and validated?
-
What common
errors occur in use case development?
-
Managing Use Case
Complexity
-
How can use
cases be organized?
-
How many use
cases and scenarios should be written?
-
How can use
case development be scheduled?
-
What are the
benefits and risks of use case development?
-
Use Cases in Testing
-
How do use
cases and scenarios affect software testing?
-
Do use cases
provide complete system testing coverage?
-
How are test
cases generated from use cases and scenarios?
-
Workshop Wrap-up
|
|
