Course Length:

4 Days

Course Description:

This course introduces the student to requirements management and requirements development concepts. The Business Analyst will gain in-depth insights into the responsibilities and processes of requirements management. Beginning with an overview of project phases and software development lifecycle, the audience is taken through the essential process of requirements management such as requirements documentation, change management, requirements traceability, and the role of the BA in the process. In the requirements development process, students gain understanding of requirement levels and types, requirements flow, characteristics of good requirements, writing good requirements, and requirements elicitation techniques. In a combined lecture and workshop format, students will study these concepts and techniques. They will apply them by creating the relevant artifacts, with emphasis on customizing the approach and artifacts to fit their organization’s needs.

Who Should Attend:

This course is for Business Analysts, Project Managers, and Business Staff involved in Application Development projects.

Benefits of Attendance:

Upon completion of this course, students will be able to:

• Explain the process of managing requirements.
• Perform the various elicitation techniques used in gathering and documenting requirements.
• Understand the content of the artifacts created in gathering and documenting requirements.
• Produce relevant artifacts needed for documenting requirements.
• Translate business requirements into appropriate technical specifications.
• Identify and discuss the advantages of flow charting using Unified Modeling Language (UML) Activity Diagrams.

Prerequisites:

Students should come to this course with a basic understanding of the role of the Business Analyst. This awareness of the BA responsibilities can be gained from the course entitled “Introduction to Business Analysis.” However, no specific experience in this role is required. A general understanding of the software development lifecycle (SDLC) is beneficial, but not necessary.

Course Outline:

• Introduction
  1. Business Analyst as part of the project team
  2. Industry related roles and knowledge areas for Business Analysts
  3. The role and purpose of the IIBA
• Project Overview
  1. Project Phases
  2. Software Development Life Cycle (SDLC)
  3. Project tools
  4. Software Project Artifacts
• Introduction to Requirements Engineering
  1. Requirements engineering
  2. Terms and Definitions
  3. What are good Requirements Engineering practices?
• Introduction to Requirements Management
  1. Requirements Management Defined
  2. Benefits of a quality RM Process
  3. Risks of a poor RM Process
  4. Components of the RM Process
  5. Change Management Process
  6. Requirements Traceability
  7. The BA role in Requirements Management Activities
• Requirement Levels and Types
  1. The purpose of Requirements
  2. Requirements Defined
  3. Requirement Levels
  4. Requirement Types
  5. Characteristics of Quality Requirements
• Requirements Management Artifacts
  1. Requirements Management Templates
  2. Scope and Vision Documents
  3. Requirements Plan
• Change Management and Traceability
  1. What is Change Management?
  2. What does Change Control Management do for us?
  3. Requirements Change Management Process
  4. Establishing a Change Control Management Process
  5. Change Control Charter
  6. Change Control Board
  7. Change Control Process
  8. Impact Analysis
  9. What is Requirements Traceability?
  10. What does Requirement Traceability do for us?
  11. Establishing Requirements Traceability
  12. The Traceability Matrix
  13. Impact Analysis
• Requirements Development
  1. Requirements Elicitation Techniques
  2. Identifying User Classes
  3. Writing effective requirements
  4. Characteristics of quality requirements
  5. Verifying and Validating Requirements
• Chapter 9: Communication Skills
  1. Speaking, Writing, and Listening in the Workplace
• Chapter 10: Visual Modeling
  1. Introduction to Business Modeling
  2. Notations and Symbols
  3. Activity Diagram
  4. Process Diagram
  5. Context Diagram
  6. Use Case Diagram