Guide to Customer Requirements EngineeringAn in-depth guide for developing quality requirements that lead to products, solutions and services that delight customersRequirements are the what, design is the how.”“ ProverbObjectives of this Expert Toolkit Guide1.Understand what requirements engineering is, how to use it to build high quality customer requirements2.Learn specific, important principles and best practices related to the application of requirements engineering, including:–Traceability, Release Management, Change Management3.Learn how to use key tools and methods involved in developing quality customer requirements:•Voice of the Customer•House of Quality•Kano AnalysisCustomer Requirements Engineering v1.0© 2017 EXPERT TOOLKIT | ALL RIGHTS RESERVED | USAGE PERMITTED ASPER USER AGREEMENTPage 3Introduction to requirements engineeringCustomer Requirements Engineering is the discipline of Requirements Engineering when the Customer is the primary stakeholder.Requirements EngineeringRequirements engineering is a method, approach, technique for understanding and determining stakeholder (such as customer) requirements and capturing them in a concise form so as they can be incorporated into product, service or system design. Requirements that have been engineered effectively lead to solutions that best meet the needs of stakeholders. Requirements ManagementRequirements management is the administration and control of requirements over the course of the design-through-delivery cycle. It incorporates documentation, control, tracking / traceability, change management, version control and release management.Customer Requirements Engineering v1.0© 2017 EXPERT TOOLKIT | ALL RIGHTS RESERVED | USAGE PERMITTED ASPER USER AGREEMENTPage 4How is Requirements Engineering Different to Requirements Management?Requirements engineering is an element of a five part process1. Requirements Planning2. Requirements Engineering3. Requirements Selection & Application4. Requirements Validation5. Requirements Management•Determine requirements structure•Roles and responsibilities•Agree processes and tools for requirements•Naming and numbering conventions•Identify stakeholders•Capture requirements•Structure requirements•Assign requirements to design components•Determine dependencies•Determine criticality•Prioritize requirements•Compare with competing or similar products / solutions•Approve requirements•Assign requirements to releases / versions•Validate fulfillment of requirements in the development phase•Conduct product / prototype testing•Conduct unit, system, integration testing•Conduct acceptance testing•Documentation of requirements and dependencies•Version and approval management•Change management for requirements•Classification of requirements•Integration managementThe Full Requirements LifecycleCustomer Requirements Engineering v1.0© 2017 EXPERT TOOLKIT | ALL RIGHTS RESERVED | USAGE PERMITTED ASPER USER AGREEMENTPage 5The following material relates to aspects essential to the discipline of requirements engineering.Why is requirements engineering important?•Complexityis Increasing: This complexity, across products, systems and processes drives the need for precision and clarity in the “what” (requirements) an item must do.•Interdependencyis Increasing: The level of integration and interrelationships between components is increasing. Discrete components need to work with other components and exactly how this must happen is spelt out by clear requirements. •Varietyis Increasing: The number of product models, versions, varieties is increasing making it critically important to be clear on “what” will be included in each variant. •Globalizationis Increasing: Products and systems are increasingly used in multiple jurisdictions which impose their own constraints or requirements. These constraints need to be engineered into the solution.•LegalRequirements are Increasing: Increasing regulations and legal requirements need to be identified and engineered appropriately into the design.•Innovationis Increasing: The level of product innovation and experimentation is growing at a faster rate than ever. Requirements engineering aides in identifying and capturing these innovations effectively.Robust and Effective Requirements Engineering is Important for Many ReasonsCustomer Requirements Engineering v1.0© 2017 EXPERT TOOLKIT | ALL RIGHTS RESERVED | USAGE PERMITTED ASPER USER AGREEMENTPage 6Typical requirements engineering challengesStakeholdersIdentifying the key stakeholders. What are their needs?LanguageUsing the right language so requirements are clear and concise.StructureStructuring, grouping, segmenting requirements into various component parts.QualificationQualifying, approving and prioritizing the requirements.Customer Requirements Engineering v1.0© 2017 EXPERT TOOLKIT | ALL RIGHTS RESERVED | USAGE PERMITTED ASPER USER AGREEMENTPage 7Common Challenges Experienced in Requirements EngineeringManaging and controlling changes in the requirements.ChangeOrganizeOrganizing requirements by level, type, association and other criteria.There are a range of challenges and obstacles experienced with the engineering of high quality requirements. It is important to consider these challenges and incorporate appropriate strategies and measures for dealing with them during the requirements engineering process.The two types of requirementsFunctional RequirementsNon-Functional Requirements•Functional requirements specify specific behavior or features of a product or system•This behavior may be expressed as services, tasks or functions that are required to be performed•It is useful to distinguish between the baseline functionality and enhanced functionality•Baseline functionality is that which is necessary to be a viable option for customer use•Enhanced functionality or features provide differentiation from competing options•Non-functional requirements describe technical elements of the product and how it operates, rather than specific behaviors.•Non-functional requirements include–Speed–Reliability–Security–Standards–Dimensions–Performance–Documentation–PriceGenerally Speaking, There Are Two Types of RequirementsCustomer Requirements Engineering v1.0© 2017 EXPERT TOOLKIT | ALL RIGHTS RESERVED | USAGE PERMITTED ASPER USER AGREEMENTPage 8Best Practices in Requirements EngineeringNext >