DT offers a core set of courses aimed at covering the Application Lifecycle, from requirements gathering, analysis and design to development, testing, process and project management.

Defining Requirements

Course Overview
Defining Requirements is a practical hands-on course that addresses all aspects of requirement development from elicitation, to gathering, to verification, to validation and finally refinement.
 

What will I learn?

A three-day course, Defining Requirements introduces the concepts and processes for developing sound and traceable requirements. The course teaches you how to elicit, gather, validate and refine requirements using the proven best practices of Subject-Matter Experts. The heart of the course is a series of comprehensive activities built around a realistic sample software project.
 

Course Style
Lecture style with hands-on labs

This course is designed for students who want to improve their requirements elicitation and facilitation skills, especially for conducting use case sessions. These roles include: Business Analysts, Requirements Analysts, Technical Director, QA Manager
 

Course Contents

Introduction

• Exploring a Requirement Structure…Organization
• Exploring a Requirements Process
• Meeting Expectations…Things That Get in the Way

Defining Business Requirements

• Identifying stakeholders and users
• Determining vision/constraints…where to start
• Defining business requirements and constraints
• Discovering the Process/People/Technology perspective
• Defining Scope

Determining User Requirements and Functional Requirements

• Defining user roles and constituencies
• Planning stakeholder and user involvement
• Identifying user tasks with a Use Case Diagram
• Identifying user tasks steps and other related information with a Use Case
• Deriving functional requirements from use cases
• Documenting requirements

Determining Nonfunctional application Requirements

• Defining types of nonfunctional requirements
• Deriving nonfunctional and other requirements from a use case
• Selecting requirements gathering techniques

Validating…Verifying…Experimenting

• Developing test cases based on requirements
• Validating and verifying to prove stated requirements meet customer needs
• Experimenting to help establish a preliminary architecture
• Establishing criteria for sound requirements

Establishing an Agreement

• Establishing relative importance (prioritization)
• Determining achievable outcomes (feasibility)
• Documenting an agreement (baseline)
• Discovering symptoms of non-agreement

Refining Requirements

• Elaborating Requirements
• Validating…Verifying… Experimenting Again
• Establishing an Agreement for Implementation

Next Steps: Making the Case for Requirements Engineering

• Talking to the PAIN … the cost of doing requirements badly
• Categorizing typical requirements challenges…content/process problems
• Understanding requirements-related risks for projects and how a requirements process will help you overcome them
   

Prerequisites
None

Recommended Follow-On Courses
Requirements Management with Use Cases

Duration
3 days