NOTE! This site uses cookies and similar technologies.

You can change your browser settings to disable them

I understand

FMEA

As part of System Engineering we perform in-depth, methodical failure mode effect analysis.

  • Boundary Diagram and Interface Analysis engaging all stakeholders
  • P-Diagram(s) to capture Inputs, Outputs, Noise Factors and Control Factors
  • Analysis of potential failures providing solutions for Prevention and Detection
  • Planning and Tracking of open actions
  • Final Sign-Off report

Requirements Engineering

Every project starts with one idea. The road from idea to final product is never easy, but becomes easier if it has a good start. Our vast experience with various Automotive ECUs can help you in making the first step right. Depending on scale of the project,  we can act independently or we can moderate Requirements Engineering Workshops with parties involved in development of the product. In each situation, we can cover all necessary steps:

Read more: Requirements Engineering

System Architecture to Software Design

Do we have requirements ? Excellent, we can start design. We have experience with Rhapsody (Telelogic/IBM) but we can use any UML capable tool (e.g. Microsoft Visio, PlantUML, etc) .

We will take into consideration

Read more: System Architecture to Software Design

Code construction

When we deliver SW Units, we don't just write code. We always make sure the code does what's intended to do. For this we follow closely the design and the verification strategy. 

    At unit level:
  • consistency and bilateral traceability are established between software detailed design and software units
  • each sw unit is analyzed for testability and correctness
  • cyclomatic complexity of each function is 10 or less
  • we apply static check with PC-lint - MISRA rules
  • we perform code review
  • we perform unit testing
    At project level:
  • sw units are prioritized based on their analysis

Software & System Testing

Our Test Strategy ensures left-shifting, optimising costs by identifying flaws very early but at the same time keeping under tight control the dependencies - to allow flexibility on change and proper regression testing.

When System/Software Requirements are identified and reviewed we start to write System/Software Validation Specification
When Architecture reaches a mature level we can start defining Integration Test Specification.
While Module Design is in process, we already think about Module Test Specification. This ensure our module is easy testable. Because we write test cases as soon as the design is ready, the module can be tested while it is being developed, reaching 100% coverage by automated tests soon after implementation is done.

You are here: Home Engineering