|
|
|
Requirements Management for IT Professionals
…Managing project scope from concept to completion
The cause of the majority of failed IT projects can be traced to
poor definition and understanding of requirements. Changing
requirements, cause more delays than any other cause. If you
want to improve project performance, you must improve the way
you define and manage requirements. They are the bridge between
the customer who will describe, pay for and use the system and
the technical community who will specify and provide the system.
Prerequisite
Basic understanding of projects and project management
Course Level
Intermediate
Duration
2 Days
Who should attend?
The workshop is designed for systems professional or business
associates who will take part in defining requirements for computer
system development, business reengineering procedural change and
other activities that require the analysis of a business system.
There are no technical prerequisites. Participants do not need prior
experience in business analysis.
Performance Focus
- You will cultivate the skills needed to identify and get
full business information from the right sponsors, clients,
users and others
- You will get structured and object-oriented modeling
techniques and templates to identify and present business
and systems requirements clearly and effectively
What You Will Learn
- Determine who the stakeholders are, and establish roles
and appropriate requirements gathering techniques
- Differentiate between business, user, functional and
system requirements
- Gather requirements for, and create the User
Requirements Specification (URS) document
- Develop user and functional Use Cases
- Create the Software Requirements Specification (SRS)
document
Content
Basic Outline of the course:
Introduction to Requirements
Management
Objectives of projects
The project environment
Classifying project
Requirements for systems
Levels of requirements
Requirements documents
User Requirements Specification
Voice of the Customer
Documenting the beginning of the project
Stakeholder assessment
Roles and responsibilities of stakeholders
Creating the URS
Requirements development
Five levels of requirements maturity
Requirements development and the major activities
Detailed description of type of requirements
Quality attributes and example of requirements in traditional
“shall” statements
Requirements prioritization
Requirements repository and requirements baselining
Requirements Elicitation Tools
Interviewing
Objects and classes
Class, package and sequence diagram
What does a Use Case look like?
Elements of a use case
Use case and requirements collection
Prototyping
Storyboarding
Brainstorming
Requirements workshop |
Requirements Analysis
Structured analysis
Context diagrams
Data flow diagrams
Entity relationship diagrams
Structured English
Data Dictionary
Decision table and decision tree
Requirements Specification
Software requirements specification (SRS)
Identifying sources of requirements
Labeling requirements
Organizing requirements information
Documenting business rules
Creating a requirements traceability matrix
Requirements Verification and Control
Requirements analysis and verification
Requirements pre-reviews
Requirements review
Requirements checklists
Test cases for verification
Requirements testing
Requirements change control
Recap & Closing |
| |
|
|
|
