Audience
This course is targeted towards project managers, technical leaders, architects, development
staff and test engineers.
Length of Course
3 days
Course Goals
By the end of the course the student will be able to understand
what must happen prior to analysis, define requirements efficiently
and effectively and create analysis artifacts, such as use-cases
and domain models, using the UML notation.
Through course exercises the student will understand how requirements
are used to follow an iterative-incremental use-case driven process.
Course Components
Systems Development Life Cycle
- Requirements versus analysis
- Complexity and decomposition
- Iterative, incremental processes
- Development cycles
- Steps in a process
Requirements
- Steps in specifying requirements
- Project mission and scope
- Project goals
- Identification of participants
- System functions
- System attributes
- Facilitated meetings
- Effective meetings
- Tracing requirements
- Ambiguity
- Questionnaires
- Interviews
- Brainstorming
- Dealing with conflict
Use Cases
- Business processes and use cases
- High-level vs. expanded
- Essential vs. real
- Uses and extends relationships
- Conversational style
|
Domain Models
- Domain concepts
- UML type diagrams
- Attributes & Associations
- Generalization
- Associative types
- Roles
- Multiplicity
System Behavior
- System events and operations
- System sequence diagrams
- Operation contracts
Prototype Analysis
- Requirements exploration
- Real use cases and story boards
- Successful use of prototypes
State Models
- When to analyze state
- Determining scope of state analysis
- Internal and external events
- Identifying relevant states
- State transition
Analysis Patterns
- Common types of patterns
- Sources of useful patterns
- How to use analysis patterns
- Building and using a pattern repository
|
|
