Requirements Engineering Training Workshop

Requirements Engineering Training Workshop

Requirements Engineering Training Workshop Course Description

Requirements Engineering training workshop provides a strong grounding in a range of techniques for revealing, analyzing and documenting business and system requirements.

Requirements engineering training workshop covers fundamental principles and concepts of requirements engineering and the techniques used to capture, validate, and gain a complete understanding of requirements.

Requirements engineering training workshop discusses measures of effectiveness (MOEs), goals, and related value relationships. The course concentrates on the structure of requirements features, based on principles and without reference to specific languages.

The Requirements engineering training workshop course assesses a range of elicitation techniques and how to document user requirements for an information system. The main areas will be discussed by this hands-on workshop include, but not limited to, prioritizing requirements, resolving conflicting requirements, and connecting project objectives and requirements to the business case. You also will develop the skills required to work with stakeholders’ specifications to make sure that requirements fulfill all the point of views and that disagreements are negotiated to a position of agreement. You will learn to collaborate with stakeholders to certify the requirements are thorough, clear, feasible and testable.

Learn About

• Elicitation techniques
• Requirements analysis
• Requirements categorization, prioritization and documentation
• Quality characteristics of requirements
• Traceability and management of changes to requirements
• Verification, validation, and approval of requirements

Audience

Requirements engineering training workshop is a 2-day course designed for:

• Project managers, project engineers, and project analysts
• Product owners, subject matter experts (SMEs), business change managers, senior users, project stakeholders
• IT systems architects, software developers, testers, support and trainers
• Practicing business analysts
• Product managers
• Engineering managers
• Requirements managers/engineers
• Specification writers
• Software systems engineers
• Software engineers
• Design engineers
• Hardware engineers

Training Objectives

Upon the completion of requirements engineering training workshop, attendees are able to:

• Understand the concepts of requirements engineering
• Comprehend the importance of requirements analysis in accomplishing successful project results
• Understand the concept of requirements quality.
• Measure the quality of a requirements characteristics
• Comprehend the fundamental types of requirements (functional, performance, external interface, environmental, resource, etc), and the significance of these distinctions.
• Distinguish various requirements from each other
• Apply the tools that establish an efficient method for performing requirements analysis
• Adjust the application of the techniques of requirements analysis to different scenarios
• Understand the role of specification writing in accomplishing successful project results
• Recognize the principles of good specification structure, for specification of systems, software and services
• Understand a broad range of public domain standards for different types of requirements specifications
• Determine the nature of the requirements and the type of information to which they belong
• Document and prioritize requirements, distinguish, and help resolve conflicting requirements
• Connect project objectives/requirements to the business case
• Explain the responsibilities of key stakeholders in the requirements engineering process
• Present the usage of various requirements elicitation techniques
• Discuss the application of requirements elicitation approaches and their relevance to certain situations
• Record and prioritize user requirements for an information system
• Determine issues with requirements and explain how requirements documentation may be improved
• Develop a process/function model of requirements for an information system
• Understand a model of the data requirements for an information system
• Describe the role of project objectives and requirements
• Explain the concepts of requirements management and explain the importance of managing requirements
• Describe the principles of Requirements Validation and define an approach to validating requirements

Course Outline

Overview

• Requirements engineering definition
• Issues and terminology
• Lessons from real projects
• Background and evolution of requirements engineering
• The origin of requirements
• Concept of the system boundary
• The modeling boundary
• The systems engineering process
• Development of system architecture and detail design
• Requirements traceability
• Baselines and their use
• The waterfall life cycle paradigm
• Incremental development
• Evolutionary development
• The spiral model

What are Requirements?

• Definitions and views
• Relationship to design
• Relationship to baselines

Requirements Classification

• Categorizing requirements by type
• Eight basic types
• Differences between requirements for hardware, software, services
• Non-requirements
• Other categories – design drivers, critical, global, priority, importance, stability

Requirements Engineering Process

• Lifecycle for business change
• Business plans and objectives
• Problems with requirements
• The stakeholders involved in RE
• RE process overview

Requirements and the Business Context

• Hierarchy of requirements
• TOR/PID
• Functional requirements
• Non-Functional requirements
• General/Technical requirements
• Service level requirements

Eliciting and Documenting Requirements

• Issues of elicitation
• Different stakeholders expectations
• Elicitation techniques
• Prioritization of requirements
• The structure and contents of a requirement

How to Interview for Requirements

• Interviewing for RE
• The interviewing lifecycle
• Planning, preparing, conducting and following up the interview
• Questioning strategies

How to Negotiate Requirements

• Iterating requirements
• Correspondence with business objectives
• Evaluating requirements in regards to:
  • Classification
  • Priority
  • Ambiguity
  • Testability
  • Risk
  • Granularity
  • Omissions
  • Conflicts
  • Overlaps
  • Achievability
• Resolving conflicts

Techniques to Evaluate the Quality of Requirements

• Correctness
• Completeness
• Consistency
• Clarity
• Non-ambiguity
• Traceability
• Testability
• Singularity
• Feasibility
• Freedom from product/process mix

Requirements Analysis Techniques

• Primary, secondary, tertiary stakeholders
• Initial analysis and planning
• Calculating requirements quality
• Requirements dialogue methods
• Context analysis
• Rest of scenario analysis

Facing the Real World

• How to handle the user who “doesn’t know”
• How to react to “moving goalposts”
• How to avoid the communication gap

Tools to Support Requirements

• Tools supporting requirements analysis
• Tools supporting requirements management
• Some examples of available tools
• Common drawbacks in using tools

Requirements Verification

• Requirements reviews
• Use of metrics

Requirements Validation

• Requirements validation
• Requirements reviews
• Validation checklist
• Validation by prototyping

Management of Requirements Analysis

• Management issues
• Using and managing “TBDs”
• Designing a requirements codification scheme
• Managing resolution of requirements issues

Developing Requirements Specifications

• What is a requirements specification?
• Relationship between requirements specifications and requirements
• Relationship between requirements specifications and configuration baselines
• Using a requirements database

Requirements Flow down into Requirements Specifications

• The specification tree
• Special considerations for interface requirements

Requirements Formats

• Basic types of requirements specification
• Using DIDs and templates
• IEEE specification
• US Military and other national and international specification standards

Developing Your Specification

• Solicitation or agreement documents
• Constructing a statement of work
• Constructing a system specification
• Constructing a software requirements specification
• Constructing an interface requirements specification
• Introduction and Scope
• Dealing with variants
• Listing applicable and other referenced documents
• Definitions, acronyms and abbreviations
• Requirements section
• Identification of required external interfaces
• Dealing with states and modes
• Functional, functional and performance, functionally oriented, versus design -oriented requirements specifications

Requirements Engineering Training Workshop