What the first project usually looks like.
Prospects rarely arrive with a specification. They arrive with a date, a standard and a gap. These are the shapes that engagement usually takes.
NEAT / TECHNICAL ENGINEERING
ENGAGEMENT MODELS
Six ways to work together.
They differ in who owns the deliverable and who carries the safety argument. Most programmes start with one and move to another.
Turnkey developmentWe own the deliverable end to end, against your requirements, with the evidence package included. You review and accept; we answer to the assessor.
Design authorityWe own the architecture and the safety argument, your team builds under it. Suited to customers with capacity but without a safety track record in this domain.
Co-developmentJoint teams, shared configuration management, one lifecycle. It works when both sides already run a comparable process, and it fails when they do not.
Staff augmentationNamed engineers into your programme, working to your process and your tools. The fastest to start and the one that transfers the least know-how.
Certification supportWe arrive when the technical work is done and the dossier is not. Common, and more expensive than involving us earlier.
Feasibility and conceptShort, early, and often the thing that saves the programme: a few weeks spent deciding whether the architecture can be approved at all.
METHOD
How we work.
- A defined lifecycle model, applied rather than referenced
- Requirements management with traceability maintained, not reconstructed
- Coding standards, static analysis, unit and integration testing
- Configuration management from the first commit
- Documentation deliverables agreed at the start, not negotiated at the end
- IP arrangements stated in the contract, including background IP
DELIVERABLES
What you get at the end.
The product, and the evidence that it is what we said it is. For safety-related work the evidence is not a by-product; it is half the deliverable, and it is priced as such from the first estimate.
Model driven where it helps
NEAT uses a model-driven approach as a standard for application development, with MATLAB, Simulink, Stateflow, Embedded Coder and ANSYS SCADE Suite. Where it does not help, we write C.
NEAT uses a model-driven approach as a standard for application development, with MATLAB, Simulink, Stateflow, Embedded Coder and ANSYS SCADE Suite. Where it does not help, we write C.