Working in a system engineering environment means that you always have to define interfaces. This fact applies to mechanical, hydraulic, electric as well as electronic systems.
When you start defining electronic interfaces you usually develop respective Interface Control Documents (ICDs).
No matter if you create simple systems with few interacting units or complex airliner avionics with hundreds of units you must be aware what every ICD must contain to be complete.
Interface Control Documents are always composed of:
- Logical interconnection data:
- What information is to be transferred
- Who is source and who is destination
- The way logical data is represented in e.g. a serial protocol or an analog signal
- Hardware channel ports and buses that are used to transmit and receive data
- Wiring interconnection data that transfers everything listed above
Being aware of the need for a complete ICD description is half the battle. Having good tooling to manage smooth development activities is the victory!
dBricks gains your ICD development activities with the following approach:
- You define your complete data model according the ICD composition needs
- While you are populating the database dBricks validates your inputs in time to avoid trivial errors. Scale up your customized consistency checks to more complex quality when you feel ready for it.
- Export your data in your needed format like: either human-readable (ICD in MS Word, data exchange files in MS Excel, Wiring schematics etc.) or machine-readable format (e.g. VHTNG type file, rig I/O configuration files etc.).
Is smooth ICD development interesting for you?
Find more product information here, ask question by mail email@example.com or request tool demo via form.