ABSE Increases Quality of Code

Using a model-driven, reuse-based and generative approach like ABSE helps you reduce the amount of custom code in the application, resulting in an overall increase in quality.

Your Atom Templates will mature with their usage, and every time you apply a mature Template on your project, you're saving time now and in the future, because its "untrusted code footprint" decreases.

If you don't reuse your mature code, you may end up repeating the same mistakes over and over again.

Mature, tried-and-tested code means less bugs and shorter time-to-market.

Reusing models and their generated code will ensure that your development practices can continuously improve, even after changes occur in your team.

Architecture Quality

Software Quality measures how well software is designed and how well the software conforms to that design. It is known that more time is spent testing and debugging code than actually writing it. ABSE's constraint system enforces a clean, controllable, reliable architecture definition. Your team expert can design a reliable architecture that can be successfully applied by other less skilled developers. This practice also insulates the project from problems derived by a constantly changing development team.

Reliability

Software reliability is an important facet of software quality. While software quality is subjective criteria, reliability is objective and measurable. The high complexity of software is the major contributing factor of software reliability problems. Because ABSE can split large problems into smaller ones, and because architecture quality is enforced, reliability is within reach for large, complex systems.

Because ABSE can only generate the code you tell it to, you, like any other human, can still make mistakes in code using ABSE models (1).

However, as soon as you correct a mistake on an Atom Template, all its Instances are updated. Result: The problem will be automatically corrected in the whole application (2).

Because with Atom Templates you reuse your accumulated code and knowledge, corrected bugs will disappear in the present and all future applications. You'll never make that same mistake again (3).