Solutions
Requirements and acceptance of an aviation IT system
Writing functional requirements with an acceptance check behind every item, or independent technical acceptance of a system a contractor is handing over.
What we do
These are two separate pieces of work joined by one method of verification.
Requirements. We develop the functional requirements for a system: subject area, roles, working processes, data model, computed part, interfaces and the boundaries of the system.
Every requirement receives an identifier and an acceptance check. A requirement that cannot be verified objectively does not enter the document.
Acceptance. We check the system being handed over against every requirement: whether the declared functions actually work, the completeness of the data, the quality of the build, access separation, and the behaviour when an external source is unavailable.
We record separately the questions that are a decision for the process owner rather than a defect of the system.
How we work
- Data
- Analysis
- Findings
- Recommendations
Form of the result
From you: for requirements — access to the specialists who run the process and to the current internal documents. For acceptance — access to the stand or the system, the contractor’s documentation and the contractual requirements.
Result: functional requirements with an acceptance table, or an acceptance report listing the findings and the status of each.
Acceptance of our work: on requirements — a working group on your side that has been through the document in full. On the report — a joint review of the findings, with the contractor taking part where they are willing.
What we do not do: we take no decision on accepting the system on the airline’s behalf and sign no acceptance certificate. Our report is the basis for your decision.
What the airline gets
On requirements: a document fit for procurement, development and the subsequent acceptance of a system.
On acceptance: an independent report listing the non-conformities found, the method by which each statement was verified, and a separation of the results into defects, deviations and open questions.