top header
top gradation HOME top vertical line top vertical line top vertical line top vertical line top vertical line top vertical line top vertical line menu gray
black line 2
menu gray tab More About ATI
menu blue ATI — Who We Are
white line
menu blue Contact ATI Courses
white line
menu blue List Of ATI Courses
white line
menu blue Attendees Testimonials
white line
menu blue The ATI FAQ Sheet
white line
menu blue Suggestions/Wait List
white line
menu blue New Courses
white line
menu blue Become an ATI Instructor
menu gray tab site resources
menu blue Acoustics & Sonar
white line
menu blue Rockets & Space
white line
menu blue GPS Technology
white line
menu blue ATI Blog
white line
menu blue ATI Space News
white line
menu blue ATI Site Map
white line
menu blue ATI Staff Tutorials
white line
menu blue ATI Sampler Page
white line
menu gray tab bar
menu gray tab courses
white line
menu blue Current Schedule
white line
menu blue Onsite Courses
white line
menu blue Register Online
white line
menu blue Request Brochure
white line
menu blue Free On-Site Price Quote
white line
menu blue Download Catalog
white line
menu blue Distance Learning
black line

Capturing Systems Requirements

Share |


Technical Training Short On Site Course Quote This course prepares the student to properly identify, define and confirm the customer's true requirements when they are needed - prior to the design and development of the system. The key to every project's success, accurately captured requirements are not only essential for meeting stakeholders' expectations, but also to avoid costly delays, added cost for rework, and poor customer relations.

What You Will Learn

  • Detect early errors in analysis, design, and development (when it costs the least to correct)
  • Define solutions that meet stakeholder needs
  • Use modeling techniques to document and confirm functional requirements
  • Create an effective change management process
  • Develop and use a framework for the requirements development process
  • Employ validation and verification methods to ensure correctness
  • Minimize scope creep
  • Contribute to the development of best practices in requirements management for an organization
  • Identify key challenges to the requirements development process
  • Write clear and concise requirements
  • Develop a requirements traceability matrix and a requirements specification document


    • Project Managers
    • Systems/Business Analysts
    • Systems Engineers
    • QA/Testing Specialists
    • Technical Leads and Programmers

    Course Outline

    • What is a requirement?
    • Needs versus wants
    • Functional versus non-functional
    • Categories of information
    • Function
    • Form
    • Criteria
    • Constraint
    • Classes of requirements
    • Business
    • User
    • Technical
    • How the requirements process fits into the product/application development lifecycle
    • Why its important to establish requirements early
    • The importance of getting requirements right
    • Challenges to creating quality requirements
    • Sources of Requirements
    • Characteristics of high-quality requirements
    • IEEE criteria
    • Traceability
    • Change management the key to minimizing scope creep
    • The Requirements Process
    • Elicitation Whos got them; how to get them
    • Stakeholder analysis
    • Identifying internal and external stakeholders
    • Conducting stakeholder analysis
    • Forming stakeholder classes
    • Understanding Personas
    • Fact gathering methods: pros, cons, when to use
    • Interviewing
    • Observation
    • Questionnaires
    • Research: Studying policies and procedures, results of other studies
    • Collaboration methods (JAD, JRP, etc.
    • Interviewing
    • Definition -- contrasting interviews with other face-to-face data gathering methods
    • The Interview framework purpose and substance
    • Introduction
    • Body
    • Summary
    • Planning the Interview using the 5 Ws
    • Preparation
    • The art of questioning
    • Devising questions to accomplish the interview objectives
    • Effectively using probes
    • Techniques to control the Interview
    • Documenting the Interview
    • Verifying Information using the follow-up memo (email)
    • Analysis and Specification
    • Building the Users' Model
    • Developing output mockups or prototypes
    • Identifying requirements
    • The information model
    • Sequence
    • Exceptions
    • Layout
    • Process Modeling
    • Data flow diagrams
    • Evolution: Resolving Communication Problems
    • Uses in the system development method
    • External entities-establishing boundaries and interfaces
    • Identifying events and triggers
    • Constructing context, overview, and detail data flow diagrams
    • Identifying appropriate detail level
    • Storyboarding
    • Capturing and Refining Use Cases
    • Creating use cases
    • Identifying stakeholders and actors
    • Naming and scoping use cases
    • Extending use cases
    • Verifying use cases with stakeholders
    • Capturing Data Requirements
    • Developing the conceptual model
    • Relational concepts
    • Entities
    • Attributes
    • Associations
    • Graphic representation
    • Entity-relationship diagrams
    • Maintaining the glossary/Use of the data dictionary
    • Determining business rules
    • The need for specification tools and methods
    • User needs vs. technical needs
    • An examination of methods
    • Process mapping methods
    • Transaction Table
    • Controls Table
    • CRUD Matrix
    • Swim-lane Diagrams
    • Documenting non-functional requirements using a Requirements Template
    • Creating the User Requirements Document (URD)
    • Principles of well-formed requirements
    • Word sensitivity, syntax and active voice
    • Well-formed vs. ill-formed requirements
    • Editing and rewriting requirements
    • Organizing requirements into a readable document
    • Validating Requirements
    • Achieving well-formed requirements through validation
    • Reviewing requirements with walkthroughs
    • Verifying requirements with inspections
    • Selecting the best validation methods
    • Writing test cases
    • Defining specific test objectives
    • Black box techniques
    • Assembling the test cases into test specifications
    • Ensuring traceability
    • Linking requirements to business needs and to test cases
    • Creating a traceability matrix
    • Management
    • Creating the plan
    • Creating the task list
    • The work breakdown structure
    • Creating task estimates
    • Matching resources to tasks
    • Assigning activities
    • Obtaining commitments for outside resources
    • Using a network diagram to denote task relationships and dependencies
    • Using a GANTT (bar) Chart to show schedule
    • Executing the plan what to do as things happen
    • Change management procedure the key to minimizing scope creep


      Onsite pricing is available. Please call us at 410-956-8805 or send an email to

    Register Now Without Obligation

  • spacer