If you are in the business of developing distributed systems without the right tools to bridge the gaps between the different development phases and groups, you are losing money!
How much money?
A lot more than you think. Here’s why:
To start, you are doing about 5 times the work you should in most cases, as you have the following personnel defining the exact same interfaces data:
Defining interface data may not seem like much, but in systems that often have hundreds of messages and thousands of elements this is a lot of monotonous manual work. Typically there are a lot of changes made to the data throughout the lifetime of a project, each change has to be communicated to all the personnel, a daunting task within itself, and performed numerous times once again. This recurring process is annoying, boring, and highly prone to errors.
This brings us to our next point, bugs.
Various studies find that most bugs are introduced at Specification phase of software development, furthermore, transcription, communication and oversight are the major root causes of defects. In addition, there is wide acceptance in the industry of the theory, backed by some research that the cost of fixing a defect grows exponentially as development progresses over development phase.
This is where Adi’s Simple Case suite enters the picture, a set of tools that significantly reduces development time and inconsistencies, by employing a “Model Once Use Everywhere“ approach.
The ICD16 lets you model your system interfaces and generate code for your developed system in multiple available languages and formats.
The Failure Definition Manager (FDM) allows you to add logic for recognition of and reaction to fail conditions in distributed systems.
The Junction Tool is a form based extension of the ICD16 that allows you to define associations between data elements as well as dynamic behavior of messages.