 |
Register Now |
 |
Buy online lessons |
|
Fall 2010 Blended Learning Schedule
Blended Learning Online |
|
Register for public classes |
|
|
Fall 2010 Public Class Schedule
Philadelphia metro
New York City metro
Washington, D. C. metro |
|
Request a quote for on-site training |
Writing Well-formed Requirements
Students will apply tried-and-true techniques for writing and organizing requirements, communicating them to business and technical audiences, and converting them from raw to well-formed requirements.
Course SpecificationsCourse identifier: WWReq.
Course duration: 8.0 hours / 8.0 PDUs.
Delivery schedule: One day.
Course DescriptionIEEE Std. 1233 states that a well-formed requirement is a "statement of system functionality (a capability) that can be validated, and that must be met or possessed by a system to solve a customer problem or to achieve a customer objective, and is qualified by measurable conditions and bounded by constraints." Requirements begin their lives as raw requirements, meaning that the everyday language of the source of that requirement has been used to describe system functionality. Rarely is such initial language free of ambiguity, misclassification, assumption, and implication. This course immerses the student in exercise after exercise concerned with identifying raw requirements and converting them into well-formed requirements. The final deliverable is a requirements repository containing well-formed requirements which can be validated and presented to a customer.
Course Objective: Students will learn the key definitions and properties of a system requirements specification. Students also will apply tried-and-true techniques for organizing requirements, communicating them to business and technical audiences, and converting them from raw to well-formed requirements.
Target Student: This course is designed for business analysts and systems analysts who are responsible for documenting requirements.
Prerequisites: A professional command of the English language is required. To get the most out of this course, we strongly recommend that you take at least one of the following courses, first:
Systems Analysis Using Structured Techniques
Systems Analysis Using the UML
Delivery Method: Instructor led, group-paced, classroom-delivery learning model with structured hands-on activities.
Performance-Based ObjectivesUpon successful completion of this course, students will be able to:
build and use a system or software requirements specification template;
construct a requirements repository;
apply the nine properties of quality to the requirements repository to ensure system scope stability and viability;
distinguish among functional, qualitative, and derived requirements;
convert raw requirements to well-formed requirements using the laws of factual writing;
apply the four properties of quality to individual requirements;
support the analysis of requirements by applying the seven categories of requirements analysis best practice;
define and implement the system requirement specification process;
validate well-formed requirements through requirements traceability;
present requirements to a customer.
Lesson 1: Introduction
Topic 1A: Objectives
Topic 1B: Logistics and materials
Lesson 2: System Scope: The Bedrock of Requirements
Topic 2A: Perspectives on "Scope"
Topic 2B: Definition of Terms
Topic 2C: The Visual Abstraction of System Scope Using Graphical Modeling Techniques
Topic 2D: Scope Communication Problems and Their Solutions
Topic 2E: Requirements Document Analysis
Topic 2F: Requirements Elicitation
Topic 2G: Requirements Facilitation
Topic 2H: Alternative Scoping Techniques
Topic 2I: Achieving System Scope Stability
Topic 2J: Case Study: Problem
Topic 2K: Case Study: Solution
Lesson 3: Requirements Specification Templates
Topic 3A: System Requirements Specification Standard
Topic 3B: Software Requirements Specification Standard
Lesson 4: The Requirements Repository
Topic 4A: The Central Importance of the Requirements Repository
Topic 4B: Repository Design
Topic 4C: Repository Implementation Alternatives
Topic 4D: Requirements Validation
Topic 4E: The Nine Properties of Requirements Repository Quality
Topic 4F: Case Study: Problem
Topic 4G: Case Study: Solution
Lesson 5: Requirement Categories
Topic 5A: Functional Requirements
Topic 5B: Qualitative Requirements
Topic 5C: Derived Requirements
Topic 5D: Case Study: Problem
Topic 5E: Case Study: Solution
Lesson 6: Requirements and the System Development Life Cycle
Topic 6A: Raw Requirements
Topic 6B: The Four Properties of Quality for Well-formed Requirements
Topic 6C: Partitioning Requirements Into Dynamic and Static Model Classes
Topic 6D: Converting Raw to Well-formed Requirements
Topic 6E: Case Study: Problem
Topic 6F: Case Study: Solution
Lesson 7: Requirements Analysis
Topic 7A: The Seven Categories of Requirements Analysis Best Practice
Topic 7B: Avoiding the Pitfalls of Requirements Analysis
Topic 7C: The System Requirement Specification Process
Topic 7D: Requirements Documentation and the Laws of Factual Writing
Topic 7E: Case Study: Problem
Topic 7F: Case Study: Solution
Lesson 8: Testing
Topic 8A: Requirements Traceability
Topic 8B: Verification and Validation (V&V) Techniques
Topic 8C: Integrating the SDLC with the Project Life Cycle
Topic 8D: System Test Specification
Topic 8E: Acceptance Test Specification
Topic 8F: Case Study: Problem
Topic 8G: Case Study: Solution
Lesson 9: Case Study Completion
Topic 9A: Team-based Work
Topic 9B: Formal Presentation
Topic 9C: Best-practice Review and Lessons Learned
Lesson 10: Conclusion