Requirement Products
Overview
Requirements surround us, whether implicit or verbal (e.g. instructions from your immediate manager) or formal written ones (e.g. user requirements, functional specification, interface requirements, contract, legal). They may often be presented or issued in many types of document which do not have 'requirement' or 'specification' in the name e.g. process, formal technical or management plan.
Identifying and understanding the correct set of requirements, expressing them in simple uanmbiguous and veriable ways and then assuring against them is essential to
- achieving the original 'design' intent
- producing feasible, verifiable repeatable products
- minimising technical debt (e.g. arising through not properly documenting the requirements being designed or worked-to)
- minimising the risk of failure.
Experience
Eclectica Systems Ltd. has worked with and producing requirements, including requirement tools and the production of requirements over 40 years in many areas and at many different levels.
- levels (business, customer, user, system, sub-system)
- domains (aerospace, defence, government, space, utilities, power and distribution)
- types of requirement document
- Acceptance Specification
- Business Process
- Capability Requirement (includes product and business capability)
- Commissioning Specification
- Data / Information Requirements
- Functional Specification
- Interface Control Document
- Interface Requirements
- System Requirement Document
- User Requirement Document
- Verification (Assurance) Requirements
- Trial Requirements
covering a wide variety of subjects from communication systems, software, radar, ground vehicle, aircraft, the odd part of a future space vehicle propulsion system, safety and protection to business capability and change requirements.
A requirement model can be the basis for an assurance/verification case and support creation of a Compliance Matrix (TRAK MV-04 Assurance View)
Typical Tasks
Tasks/ products might include:-
- assessment / setting up a requirement management capability
- integration with tools such as IBM DOORS (Classic and Next) or enterprise architecture tools such as Sparx Systems Enterprise Architect
- review / production of requirement management plan
- production of a requirement document or a model containing the requirements (user, product, system, process)
- review / improving the quality of an existing requirement document (including structure, suitability of boundaries and interfaces)
- support for a design review e.g. System Requirement Review (SRR), Test Readiness Review (TRR) or similar.
- mentoring / training of staff