| Cart Total:
Menu
Training

Software Requirements Engineering

Course ID SRE
Format Classroom

Anyone involved in eliciting, analyzing, specifying, validating and/or managing requirements.


Software Requirements Engineering is a three-day course designed to provide a comprehensive knowledge base and practical skills for anyone interested in implementing or improving Software Requirements Development and Management techniques and practices in their organization. This course starts with an overview of software requirements basics, including definitions of terminology, a discussion of the importance of software requirements, an overview of software standards and models related to requirements and an introduction to the requirements engineering process. Course attendees will learn how to define the vision and scope of a software product and how to identify the product's stakeholders. The course will also discuss translating higher-level business and user requirements into software product requirements. This course includes an overview of the contents of various documents to specify requirements including a concept of operations document, software requirements specification and a data dictionary. Course attendees will learn to establish requirements baselines, perform requirements traceability and manage requirements change.This course is taught through lecture and interactive discussion. Actual examples from the software industry are utilized to make the information relevant. Throughout this course, learned skills are practiced using team exercises and case studies. For on-site courses, these exercises and case studies can be tailored to include actual examples from your organization in order to make the training even more relevant to your environment. The emphasis in this course is on techniques that allow the attendees to transition the skills learned in this course to their own work environments.

Course Data

  • CEU Hours: 2.1
  • Length: 21 Hours
  • ASQ RU: 2.1
  • Provider: ASQ - ILT
Course Overview

Learning Objectives:

  • Understand the basic concepts of software requirements engineering.
  • Select the appropriate requirements elicitation techniques to identify their requirements.
  • Effectively analyze their requirements.
  • Create a requirements specification to communicate their requirements.
  • Utilize various requirements validation techniques to critically evaluate their requirements to identify defects.
  • Manage change to their requirements.
Outline
  1. Software requirements — The basics
    1. What, why, when and who of requirements
      • What are requirements
      • Requirements defined
      • Levels of requirements information
      • Why are requirements important?
      • Why are requirements important?
      • Issue: Project failure
      • Issue: Incomplete requirements
      • Issue: Lack of user involvement
      • Issue: Requirements defects
      • Issue: Requirements churn
      • Issue: Wasted resources
      • Issue: Gold plating
      • Issue: Inaccurate estimates
      • Benefits of good requirements
      • When Requirements and the life cycle
      • When Requirements and the life cycle
      • Requirements engineering is iterative
      • Who Requirements stakeholders
      • “How to” of requirements engineering
    2. Standards and models related to requirements
      • SEI CMM® and CMMI SM
      • SEI CMM® and CMMI SM
      • Requirements management process area
      • Requirements development process area
      • Generic practices
      • IEEE software engineering standards
      • ISO 9000:2000 on requirements
    3. Requirements engineering process
      • Requirements engineering process
      • Incremental requirements development
      • Requirements engineering context
  2. Requirements elicitation
    1. Business level requirements
      • Purpose of business level requirements
      • The idea!
      • Vision statement
      • Vision statement Example
      • Vision statement Exercise
      • Defining business objectives
      • Business objectives Examples
      • Characteristics of “good” business objectives
      • Product scope and limitations
      • Product context diagram
      • Product context diagram Exercise
    2. Stakeholders
      • Stakeholder defined
      • Benefits of identifying stakeholders
      • Step 1: Identifying stakeholders
      • User types
      • Step 2: Prune the stakeholder list
      • Step 3: Participation strategy
      • Identify stakeholders Exercise
      • Stakeholder conflict management
      • Decision criteria alternatives
      • Customer’s bill of rights
      • Customer’s bill of responsibilities
    3. Requirements elicitation techniques
      • Direct-two-way communications
      • Before the interview
      • Open-ended questions
      • Context-free questions
      • During the interview
      • Listening actively
      • Interviewing tips
      • After the interview
      • Focus groups
      • Focus group meeting
      • Focus group Exercise
      • Facilitated requirements workshop
      • Benefits of facilitated requirements workshops
      • Facilitator do’s and don’ts
      • Documentation studies
      • Other requirements elicitation techniques
  3. Requirements analysis
    1. Requirements modeling
      • Requirements modeling
        • Benefits of models
        • Types of models
      • Object oriented models
        • Use cases
        • Step 1-3: Use case diagram
        • Step 4: Develop a use case for each interaction
        • Use case steps
        • Use case exercise
        • Other use case information
        • Class diagram
        • Sequence diagram
        • Sequence diagram Exercise
        • Activity network
      • Structured analysis models
        • Data flow diagram
        • Entity relationship diagram
        • State transition diagram
        • State transition table
      • Other models
        • Process flow diagram
        • Decision tree
        • Event/response table
        • Event/response table Exercise
    2. Identifying product requirements
      • Levels of requirements information
      • Use case -> Functional requirements
      • Use case -> Functional requirements Example
      • Data requirements
      • Data requirements CURDL
      • Use case -> Nonfunctional requirements
      • Quality attributes
      • Usability requirements Examples
      • Measurable nonfunctional requirements
      • Use case diagram -> External interface requirements
      • Product requirements Exercise
      • Class diagrams -> Product requirements
      • Data flow diagrams -> Product requirements
    3. Prototyping
      • Prototype
      • Prototyping suggestions
    4. Prioritizing requirements
      • Benefits of prioritizing requirements
      • Prioritization considerations
      • Prioritization First pass
      • Prioritization Second pass
  4. Requirements specification
    1. Concept of operations
      • Documenting user level requirements
      • Concept of operations document
    2. Software requirements specification
      • System requirements
      • System vs. software requirements
      • Software requirements specification
      • Writing "good" requirements
    3. Data dictionary
      • Data dictionary
      • Data dictionary notation
      • Data dictionary Example
  5. Requirements validation
    1. Requirements review
      • Reviews defined
      • Cost of rework
      • Hold many peer reviews
      • Inspection process
      • Inspection meeting
      • Who should inspect requirements
      • Requirements completeness
      • Requirements checklist
      • Requirements checklist Each requirement
      • Ambiguity
      • Peer review Exercise
    2. Requirements test planning
      • Testability
      • Writing test cases
      • Test matrix Example
  6. Requirements management
    1. Establishing and maintaining baselines
      • Baseline defined
      • Types of baselines
      • Requirements specification acquisition
      • Sign-off
    2. Traceability
      • Traceability defined
      • Bi- directional traceability
      • Benefits of requirements traceability
      • Traceability matrix
      • Traceability tagging
    3. Requirements change management
      • Configuration control procedures
      • Configuration control process
      • Approval authority process
      • Impact analysis
    4. Requirements metrics
      • Goal/question/metric
      • Requirements size
      • Requirements churn
      • Defect per requirements
      • Requirements defect backlog
      • Traceability
      • Requirements status
Details

Method of Instruction


This course is taught through lecture and interactive discussion. Actual examples from the software industry are utilized to make the information relevant. Throughout this course, learned skills are practiced using team exercises and case studies. For on-site courses, these exercises and case studies can be tailored to include actual examples from your organization in order to make the training even more relevant to your environment. The emphasis in this course is on techniques that allow the attendees to transition the skills learned in this course to their own work environments.

Who Should Attend


Business analysts, system and software requirements analysts, project managers, functional managers, software developers, testers, software quality engineers and other software stakeholders who will be involved in eliciting, analyzing, specifying, validating and/or managing requirements.

Course Highlights

  • Understand the basic concepts of software requirements engineering.
  • Select the appropriate requirements elicitation techniques to identify their requirements.
  • Effectively analyze their requirements.
  • Create a requirements specification to communicate their requirements.
  • Utilize various requirements validation techniques to critically evaluate their requirements to identify defects.
  • Manage change to their requirements.
Cancellation Policy
ASQ reserves the right to cancel or re-schedule courses and to change instructors. Please be advised that in the event of a course cancellation, ASQ is not responsible for airfare penalties or other travel related expenses you may incur.
  • If you need to cancel, we will refund your paid registration fee as noted below.
    • Requests for cancellations/transfers received at least 5 business days before the start of the course receive a full refund/transfer.
    • Requests received within 5 business days of the course starting incur a $150 processing fee.
    • After the course starts, there are no refunds or transfers.
    • Registrants who fail to attend without advance notice are liable for the entire course fee.
    • If you cannot find a substitute, we can transfer your course fees to another ASQ course of your choice.
  • You must successfully complete the entire course or program before IACET CEUs and a Certificate of Completion can be awarded.
Instructors
Linda Westfall CSQE, CMQ/OE, CQA, CBA

Enrollment Details

Format: Classroom
Format: Classroom

An instructor-led traditional classroom experience. Classroom-based instruction involves the highest level of instructor/student interaction. We offer classroom style training in two formats. See public and on-site.

09/11/2017 - 09/13/2017 Denver 9894ILT CO US Linda Westfall CBA, CMQ/OE, CQA, CSQE English List: $1495 Member: $1295

GROUP TRAINING


ON-SITE TRAINING FOR YOUR ORGANIZATION.


ASQ’s customized on-site training programs are the cost-effective way for you to train employees on your schedule. Training on-site minimizes the cost-per-student, reduces travel expenses, and ensures that the content is specific to your exact needs.

5 Benefits of On-Site Training

  1. Expertise to your location: Saves time and travel expenses
  2. Convenient scheduling: Train groups of five or more
  3. Customizable courses: Training tailored to your groups’ needs
  4. Immediate results: Employees complete courses ready to apply what they’ve learned
  5. Value-add support: Instructors available to answer questions after session