top of page
Process 04_edited.jpg

Our Process

  • We follow the established engineering V-model

  • Established industry foundations ISO/IEC, INCOSE, NASA

  • We do not stop until Technology Mastery has been achieved

    • Understand, control and measure excatly what the technology is intented to do

    • Capture the design in controlled and intuitive way (document, model or hybrid)

    • Proof compliance through traceablity

Methodology

  • Step 1: Define Outputs

  • Step 2: Breakdown into logical work packages & process

  • Step 3: Link deliverables to outputs and work packages

  • Step 4: Breakdown deliverables into work items

  • Step 5: Create traceability between work times, deliverables, work packages and outputs

Step1_edited.png

01

Stakeholder Needs and Requirements Definition Process

  • Process Breakdown

    • Define stakeholders

    • Define required capabilities in the life cycle stages

    • Define stakeholder constraints

    • Prioritize and transform into stakeholder requirements

  • Outputs

    • Stakeholders identified

    • Required characteristics and context of use of capabilities in the life cycle stages, including operational concepts, are defined

    • Constraints identified

    • Stakeholder needs are defined

    • Stakeholder needs are prioritized and transformed into clearly defined stakeholder requirements

    • Critical performance measures are defined

    • Stakeholder agreement that their needs and expectations are reflected adequately in the requirements is achieved

    • Any enabling systems or services needed for stakeholders needs and requirements are available

    • Traceability or stakeholder requirements to stakeholder and their needs is established

02

Product/Plant/Facility Requirements Process

  • Process Breakdown

    • Define high-level product description, external interfaces and functions

    • Defined highest-level product/plant/facility requirements and constraints

 

  • Outputs

    • The product/plant/facility description, including interfaces, functions and boundaries, for the product solution is defined

    • Product requirements (functions, performance, process, non-functional, interface, etc.) and design constraints

    • Critical performance measures are defined

    • The product/plant/facility requirement are analyzed

    • Any enabling systems or services needed for product/plant/facility requirements definition are available

    • Traceability of product/plant/facility requirements to stakeholder is developed

03

Architecture Definition Process

  • Process Breakdown

    • Establish architecture & interfaces

    • Integrate architecture, physical and process

    • Assess architecture selections to available technology

    • Assess architecture for processes throughout life cycles

    • Verify architecture to product design requirements

 

  • Outputs

    • Identified stakeholder concerns addressed by architecture

    • Architecture viewpoints are developed

    • Context, boundaries, and external

    • Architecture views and models of the system are developed

    • Concept, properties, characteristics, behaviours, functions, or constraints that are significant to architecture decisions of the system are allocated to architectural entities

    • Product elements and their interfaces are identified

    • Architecture candidates are assessed

    • An architectural basis for processes throughout the life cycle is achieved

    • Alignment of the architecture with requirement and design characteristics is achieved

    • Any enabling systems or services needed for architecture definition are available

    • Traceability of architecture element to stakeholder anad system requirements is developed

04

Design Definition Process

  • Process Breakdown

    • Define system characteristics & requirements

    • Define system interfaces & interface requirements

    • Assess system alternatives

    • Define product physical, electrical and system layout

    • Define product life cycle manuals

    • Certify Design

 

  • Outputs

    • Design characteristics of each system element are defined

    • Product requirements are allocated to systems elements

    • Design enablers necessary for design definition are selected or defined

    • Interfaces between system elements composing the system are defined or refined

    • Design alternative for system elements are assessed

    • Design artifacts are developed

    • Any enabling systems or services needed for design definition are available

    • Traceability of the design characteristics to the architectural entities of the system architecture

Step5_edited.jpg

05

Product/Plant/Facility Analysis Process

  • Process Breakdown

    • Identify product level analysis

    • Complete analysis, use results to inform the design and validate the assumptions

    • Establish and maintain traceability of analysis to product architecture

 

  • Outputs

    • Product analyses needed are identified

    • System analysis assumptions and results are validated

    • System analysis results are provided for decisions

    • Any enabling systems or services needed for systems for system analysis are available

    • Traceability of the system analysis results is established

bottom of page