Advantages of the USoft Approach

Previous Next

The USoft Approach has specific advantages when you want to create, adapt and maintain data-intensive business software.

Rapid prototyping with a wide audience

Specifications are so easy to read, navigate and test that you can have non-technical stakeholders validate them.

These non-technical stakeholders can also participate in the process of building working prototypes (implementations) that gradually evolve into the target software.

Separation of concerns

USoft models feature a clean separation between specifications and implementations and, in each of these columns, between architectural tiers, especially between the data, rules, service and interface tiers. This gives you a separation of concerns and a modular approach: whilst working in one area, teams know that other teams will remain functional or if their work directly impacts on another area, this impact is more likely to be traceable than in conventional coding environments.

Requirements, rules and implementations are traceable and cross-referenced

The different specifications and implementations needed to realise your system are described as much as possible as a model. This makes it much easier to make them traceable, to establish cross-references and navigation paths between them and to ensure single-point-of-definition of all the artefacts. In the long run, this gives you maintainability and reduced project and maintenance costs.


See Also

Introducing the USoft Approach

Principles of the USoft Approach