Course Number: 900
Length: 2 Days
Group of people on a business meeting late in the evening
The two-day Specification Development and Writing course addresses the techniques used to write requirements and technical design specification. The course teaches the attendees the techniques to capture, validate and gain a complete understanding of requirements communicated at all stages of the system life cycle and concert them into a specification.
Eliciting, collecting, and developing requirements workshop is an interactive course combined of several labs, group activities, practical exercises, real-world case studies, and hands-on seminars.
Training Objectives
Upon the completion of this training, the attendees are able to:
- Analyze the validity of project requirements
- Identify relevant stakeholders, validating their needs and write high-level requirement
- Create a framework for a requirements and specifications writing
- Choose appropriate tools for requirements and specification writing
- Elicit, analyze and write and trace requirements by applying different tools
- Apply best practices of specification and requirements writing and development
Audience
Requirements and Specification Writing Training is a 2-day course designed for:
- Business analysts
- Project managers
- Project engineers
- Software engineers
- Design team personnel
- All individuals who are involved in the processes of writing and developing specifications and requirements.
Course Outline
Basics of Systems Engineering
- Definition of Common Terms
- System Definition and Design
- Design Methodologies
- Process flow for system development
- Master Plan Scope
- Concept of Operations (ConOps)
- Preliminary Engineering Activities
- Requirements Development
- Stakeholder Management
- Final Engineering Activities
Requirements Analysis
- Introduction to Requirements
- The Quality of Requirements
- Description of Requirements Writing (within the larger context of system development)
- Overview of Requirements Development
- Requirements Elicitation
Communication Techniques for Eliciting Requirements
- Stakeholder involvement
- Defining valid and meaningful needs
- Technical reviews
- Stakeholder feedback on the needs being collected
- Prioritization of the needs
- ConOps to System Requirements Mapping (generic)
Requirements Collection and Development
- Purpose of Requirements
- Levels of Requirements
- Understanding the different levels of requirements
- Performance requirements
- Conditions [e.g. environmental, reliability, and availability]
- Environmental and Non-Functional requirements
- System
- Sub system
- Component / task
- Validation of Stakeholders Needs
Classification of the Requirements
- Eight basic types
- Differences between requirements for hardware, software, services
- Functional
- Non functional
- Performance
- Non-Requirements
Structure of a Well Formed Requirement
- Definition
- Capabilities
- Conditions
- Constraints
- Operational Policies & Constraints
- Technical and Policy Constraints
- Properties
- Interface
- Human
- Hardware
- Software
- Communications
- Functional analysis – needs analysis, operational analysis, use cases
- Design requirements analysis
- States & Modes analysis
- Workshop – States and modes analysis
- Requirements Verfiication
Requirements Development and Major Stakeholder Expectations
- Development of requirements
- Description of the current environment
- Stakeholders
- Feedback to Stakeholders
- Facilitation skills and techniques
- Transforming Requirements into Requirements Specifications
- How requirements specifications relate to requirements
- Requirements Flowdown in Specifications
- Specification Types and Formats
- Types of requirements specification
- Specification Writing
- Review of requirements quality
- Requirement structural template
Workshops/Exercise
- Workshop 1
- Examples of good and poor requirements (group project)
- Requirements constructs
- Group presentations and discussions
- Workshop 2- Classifying requirements as functional or design
- Workshop 3 – Writing a functionally oriented specification vs. a design oriented specification
- Analysis of Conops document
- Analysis of Requirements Development