Overwhelming evidence shows the most severe project problems, defects, delays, cost overruns, and failures are directly related to poor requirements. PMI’s 2017 Pulse of the Profession® sites 39% of projects’ primary cause of failure is due to poor requirements-gathering/management. It is our failure to understand the user and their perspective that results in the lack of proper requirements. It is critical we understand our user, their needs, and the vital skills essential to capture and communicate in an unambiguous manner product requirements adequately. Advance Requirements Writing for Engineers is a skills-based critical writing course that will help you understand the principles of the human-centric user by applying human factors and ergonomics using a variety of techniques. This course will instruct how to gather and develop user evidence and the technical writing techniques required for writing clear and unambiguous requirements.
Requirements training focuses on the human-centered design (HCD) approach for interactive product development. The human-centered design aims to make systems usable and useful by focusing on the user and their needs by applying human ergonomics and the user’s knowledge.
This one-day course will give you an understanding of the latest techniques for capturing better user requirements and writing clearer requirements that are less likely to be misunderstood and require fewer reviews and change cycles. This course, with practical exercises, will provide a pragmatic capability leading to improved project outcomes and product quality.
This seminar is intended for Control Engineers, Safety Development, or Risk Analysts that are persuing safety-releaded electronic systems applicable to the original safety standard, IEC 61508.
Part 1: The Human-Centered Design.
We start by teaching the principles, context of use, and strategies of The Human-Centered Design approach, according to ISO 9241-210.
Part 2: Writing Exceptionally Clear Requirements.
Writing clear statements for requirements or specifications has a technical point of view. In this training section, understanding the technical techniques and language will give you the skills to create understandable and complete requirements.
Part 3: Automotive Perspective.
Hardware and Software Development per ISO 26262 will show requirements and recommendations from the automotive perspective. This part provides a clear understanding of the requirements process and documentation for one of the most mature industries and standards.
Part 4: Structured Specifications.
Systems and software engineering per ISO/IEC/IEEE 29148 covers requirement’s characteristics, activities, and task and their documentation along with managing structured outlines for various types of specifications.
Part 5: Supporting Requirements Development.
It is essential that one manages documents during the requirements development process for changes, versions, revisions, and releases. In Part 5, we discuss the general requirements for Configuration Management and Change Management and provide practical reasoning for their performance.