Software Architecture

Good software architecture is the foundation of successful software. When planning a system, software architects and developers work out an architectural blueprint tailored to the business logic. Development teams often deviate from the blueprint already during implementation due to unforeseeable details and under time pressure, thus building up initial technical debt. The result: maintenance becomes more complex, tougher and more expensive from year to year.

Microservices are very popular in software architecture. The hope: large, cumbersome monoliths can be broken down into smaller, more manageable microservices. Sounds good, but it involves many pitfalls: a conversion to microservices is time-consuming and - if done incorrectly - can lead to a worse result than in the previous state. The right approach is crucial.

If you make provisions in good time, you will be spared technical debt.

Good architecture planning and timely analyses protect against technical debt and expensive, major refactorings. Ensure long-term maintainability in good time when planning and implementing the software architecture. Avoid future technical debt and rising development costs. Bring your systems back into the corridor of low technical debt and optimised maintainability.

How do we do this? With an experienced architecture team with over 15 years of expertise in analysing the architectures of more than 300 systems.

The experienced WPS team of architects led by Dr Carola Lilienthal and Johannes Rost has been analysing software architectures since 2004. Since then, we have successfully analysed and optimised over 300 systems from 30,000 to 15 million LOC in Java, C++, C#, ABAP and PHP. With our support, you can bring your system back into the corridor of good architecture. Your system will once again be cost-effective to maintain and can be extended quickly and to a high standard.

Analysing the existing technical debt
Development of a future-proof target architecture
Refactoring proposals and advice on architecture improvements
Prioritisation of refactorings and improvement measures
Development of a roadmap for the implementation of the measures
Support in following the roadmap

Indicator of successful Software Architecture: the Modularity Maturity Index (MMI)

The figure above shows a selection of 22 software systems in Java, C#, C++, ABAP and PHP that have been analysed over the last six years. For each system, the Modularity Maturity Index (MMI) developed by the WPS is given on a scale from 0 to 10 (Y-axis) with the corresponding Lines of Code.

The quality of the systems is colour-coded for easy understanding: From green ("Everything OK") to red ("Attention"). The individual systems are marked alphabetically on the X-axis.

The MMI provides management and the development team with a tool that shows the status quo of the system and lets them document the degree of improvement.

Where is your system at? Let's find out together.

Diese Webseite verwendet Cookies

[#IABV2_TITLE#]

Software Architecture

Durable software architectures

Dr Carola Lilienthal

Domain-Driven Transformation

Dr Carola Lilienthal & Henning Schwentner

Architectural assessment in concrete terms

iSAQB Module ARCEVAL

If you make provisions in good time, you will be spared technical debt.

Software architecture - evaluation of existing software systems

Podcast Computing Time

Software Architecture Metrics

Dr Carola Lilienthal

Dealing with technical debt

Durable software architectures

Indicator of successful Software Architecture: the Modularity Maturity Index (MMI)

Our offer

Get out of Technical Debt

Your Contact Persons

Contact

Johannes Rost

Software Architect

Dr Carola Lilienthal

Managing Director