Requirements Specification

If your primary approach to capturing requirements is the written word, your development process must anticipate: misinterpretation, language translation, poor communication and limited automation. On the other hand, attempting to record a requirement directly into a behavioral model is too imposing for a task that should only take a few seconds to complete!

With Mx-VDev™ we focus on describing a required behavior by showing the relation between inputs and outputs (along with a few words)

• Timing diagrams, truth tables, state transition tables, …

This more formal ‘Use Case’ representation of requirements dramatically improves communication and the possibility for automation, while allowing system designers to quickly and graphically capture the information.

Since no information about implementation is captured, the approach works as well for modeled systems, (UML, Simulink, …), C code, or defining requirements for electronic circuits.