Case 1
Customer requirement: coaching to improve specification for a call to tender.
Situation: the formulation of requirements is not state of the art compliant, with potential risks for not getting quality requirements (ambiguous requirements, non verifiable requirements…). It is also difficult to ascertain the completeness and consistency of requirements. Better structuring of the specification is necessary.
ADN approach: in addition to the specification process, go through a stage of modeling in SysML to consolidate business needs.
Case 2
Customer requirement: develop a consistent and comprehensive technical specification for a user function on the basis of 3 entry documents (ISO, existing RFQ, Partner’s technical specification).
Situation: input formats vary, some requirements are duplicated, the terminology is not unified; requirements Human Machine Interface (HMI) cover several product variants.
ADN approach: conduct a functional analysis from the three input documents, represent variants as a model, develop generic requirements of the function in DOORS, from these two elements, ensuring traceability with input documents.
Case 3
Customer requirement: in a design phase, create specifications for a large number of design subsets with consistent requirements.
Situation: Many requirements are shared by a number of design subsets. Some design subsets have strong interactions with each other.
ADN approach: Conduct a functional analysis and establish functional chain for allocating functional requirements to different subsets.
Case 4
Customer requirement: Conduct a review of a technical specification
Situation: the requirements are generally well formed but there are a large number of complex requirements. Given this large number of requirements, a “classical” design review is time consuming with the risk of missing some ambiguous or incomplete requirements
ADN approach: parse requirements with the LEXIOR tool using the lexical rules incorporated into the tool and complete the review with manual analysis by an expert.
Case 5
Customer requirement: Conduct a review of technical specifications to allow the definition and the organization of testing campaigns in Quality Center tool.
Situation: the requirements of technical specifications in Word. They are traced to needs in a Tender through references to IDs of these needs. The analysis in Word of this traceability is complex because of multiple links.
ADN approach: review of requirements of the technical specification requires knowing the needs to which they relate. Traceability matrices are formed using Reqtify. Traceability and content of requirements are reviewed under Reqtify. Once requirements and traceability are validated, they are integrated and versioned in Quality Center via the use of Reqtify and development of scripts.
