Requirements Development and Management (4 Days)
Who Needs to Attend
Systems analysts, business analysts, requirements analysts, developers, software engineers, IT project managers, project managers, project analysts, project leaders, senior project managers, team leaders, program managers, testers, and QA specialists.
Prerequisites
Software Engineering Fundamentals is highly recommended as a prerequisite.
Follow-On Courses
- Business Skills for IT Professionals
- Project Management Fundamentals (PM01)
- IT Project Management (PM11)
- Applied Project Management (PM08)
Develop effective requirements specifications that meet business and
This course is not currently offered by Global Knowledge. Information here is provided for reference only.
Numerous studies have concluded that failure to effectively develop and document project requirements is directly related to project failure.
By following the logical methodology for the requirements process presented in this course, you'll learn to develop effective requirements, including business objectives as well as business, end-user, system, and software requirements. By working through the requirements process using walkthroughs, reviews, prototyping, and storyboarding, you'll discover the importance of and types of requirements, examine information-gathering methodologies, and learn to conduct effective interviews, workshops, and surveys.|
Global Knowledge is recognized by PMIŽ as a Global REP. You will earn 24 contact hours or PDUs upon completion of this course. |
Global Knowledge is a Charter Endorsed Education Provider (EEP) of the International Institute of Business Analysts (IIBA) |
What You'll Learn
- Business objectives and business, end-user, system, and software requirements
- Identify and document end-user functional requirements
- Capture/document a comprehensive set of non-functional requirements
- Conduct effective interviews, group workshops, and questionnaires
- Data mining
- Define and effectively document business rules
Hands-on Exercises
- Develop effective business objectives and ensure a true foundation for the project
- Identify all the relevant stakeholders
- Elicit and document business requirements
- Elicit and capture end-user process requirements
- Recognize and document business rules
- Identify user types and connect them to effective user interface requirements
- Capture and write non-functional requirements
- Translate the business/user requirements into system and software requirements
- Write and review effective requirements specifications
Course Outline
1. Introduction to Requirements
- Requirements defined
- Importance of requirements
- Bridge between business and technology, users and developers
- Types of requirements
- Functional vs. non-functional requirements
- Requirements engineering phases
- Requirements management
2. Requirements Skills, Part 1
- Interviewing
- Group techniques
- How to ask questions
- Other techniques; questionnaires
- Secondary data sources
3. Understanding Different Types of Users-No One Size Fits All
- For interviewing/gathering
- For user interface
- For documentation and training
4. Requirements Engineering Methodology, Part 1
- Understanding business needs and cost/benefit
- Getting user requirements for ConOps
- Business (non-end-user stakeholders) requirements
- End-user requirements
- Use cases
- Business rules
5. Requirements Engineering Methodology, Part 2
- Gap analysis
- Writing business requirements specification or Concept of Operations
6. Requirements Engineering Methodology, Part 3: Analysis
- Allocating to system requirements
- Allocating to software requirements
- Prioritization Derivation
- Partitioning and allocation
- Classification, organization strategies
- Additional requirements for system
- Two IEEE specifications
7. Requirements Engineering Methodology, Part 4: Writing System and Software Requirements Specifications
- Traceability
- Templates
- Checklists
- Grammar, diction and style for
requirements
- Using style guides, templates and checklists
8. Requirements Skills, Part 2
- Techniques for confirming correctness
- Reviews, walkthroughs, screenshots, prototypes, storyboarding
9. After Engineering: Requirements Management
- Traceability
- Managing throughout life cycle
- Change control
10. Support
- CMM and CMMI as aids
- Three IEEE standards for requirements
- SWEBOK
- Zachman Framework
- Books, web sites
- Tools for other aspects of requirements
11. Next Steps
- How to go from requirements to analysis and design modeling
- Relationship between requirements and testing, test cases
Course Schedule
For dates after July 1, please see Requirements Development and Management (3 Days).
Classroom Dates and Locations
Date |
Location Details |
To request a location or date, use our By Request service.
Course Code: 6956
Registration Information
$2395 USD
4 Day Course
24 PMI PDUs
RSS