Course Length: 3 Days
Class Hours: 8 hours/day


The goal of this workshop is to teach students how to be an effective Business Analyst and how to develop different types of requirements (Customer requirements, System Requirements, etc.) that are required in different phases of Software Development Life Cycle (SDLC). Students will also learn how to ensure the product quality by developing quality requirements and managing requirements growth or changes efficiently.

During this workshop, a standard set of tools, templates and techniques will be offered to all students so that they can start writing requirements as soon as they get back to work. Moreover, free on-line help will be available for all students who need to communicate to the instructor for some clarification or help to start writing the real requirements. This free on-line support will be available for 30 days after students complete this workshop successfully. If necessary, on-site consultation can be arranged based on the project type and the group size.


Upon completing the 3 days hands-on workshop, students will learn:

  • What is a requirement?
  • What is Requirements Engineering (RE)?
  • What is Requirements Development (RD)?
  • How to elicit customer’s needs?
  • How to develop requirements ?
  • What is Requirements Management (RM) and why do we need to manage requirements?
  • How to manage requirements?
  • How to create Requirements Engineering Plan (REP)?
  • How to create Requirements Traceability Matrix?
  • Pros & Cons between Text-based vs. Object-based Requirements Development (RD) Approach.
  • How to be an effective Requirements Engineer or Business Analyst?



  • Define Business Analysis
  • Give Software Development Process (SDP) overview
  • Introduce Software Development Life Cycle and different phases
  • Define Business Analyst’s role and responsibilities in entire SDLC
  • Define Requirements Engineering (RE)
  • Describe importance of RE in different phases of SDLC
  • RE and SEI’s CMMI model
  • Introduce Rational Unified Process (RUP)
  • Importance of SQA in Requirements Engineering
  • Introduce Software Quality Review process in accordance with RE
  • Importance of Configuration Management (CM) process in RE
  • Define Process Asset Library (PAL)
  • Introduce other established RE processes, tools and technologies are used in the industry

Requirements Planning

  • Identify SMEs (Subject Matter Expert) and other Stakeholders
  • Define project scope
  • Identify deliverables
  • Estimate work products
  • Work with Project Manager and development team
  • Create Requirements Management Plan (RMP)

Requirements Development (RD)

  • RD Process and CMMI Model overview
  • Elicit Customer’s needs
  • Gather, analyze and process requirements
  • Validate, refine, verify and record requirements
  • Define characteristics of good requirements
  • Describe different elicitation techniques
  • Describe standard requirements documentation techniques
  • Develop Customer Requirements
  • Develop Systems Requirements
  • Develop System Interface Requirements
  • Describe standard requirements documentation techniques
  • Develop Customer Requirements
  • Develop System Interface Requirements

Requirements Management (REQM)

  • REQM and CMMI model overview
  • Describe requirements review, signoff and baseline process
  • Manage and track requirements growth/changes efficiently
  • Identify importance of requirements traceability
  • Describe Requirements Traceability Matrix (RTM)
  • Use RTM to track/monitor entire SDLC
  • Manage requirements changes using established CM process.


  • Importance of Use Cases and Use Case Analysis
  • How to manage requirements with Use Case
  • Developing Use Case using standard template
  • Unified Modeling Language (UML)
  • Object-Oriented Modeling with UML
  • Show how different tools (like business process, workflow and data modeling techniques) can be used to improve communication among different stakeholders.


  • What is BA’s role in testing?
  • When to start introducing testing in requirements?
  • How to build quality requirements?
  • How to drive the testing process through requirements?
  • How to introduce test strategies, plans and quality goals upfront?
  • Identify automated testing criteria if required.