Our References in Architecture-Centric Engineering
Fraunhofer Institute for Experimental Software Engineering IESE
- Reference Projects
- Empirical Results
One of the primary goals of the Fraunhofer-Gesellschaft is the long-term entrenchment of scientific research results in industrial application.
Overview of Architecture Projects
In recent years, IESE has conducted more than 50 architecture projects with customers from industry in the areas of embedded systems and information systems.
The motivations of our customers were quite diverse, but the projects can be classified according to their criticality for the customer:
Projects with a focus on evaluation activities
- Risk management: Situation is under control, but risks should be identified.
- Emergency: Situation is not under control anymore. Reasons and countermeasures have to be identified.
- Clash: Situation between different organizations is critical with regard to a product (e.g., customer / supplier relationship for a software system). Reasons and countermeasures have to be identified.
Projects with a focus on constructive activities
- Quality management: Long-term quality improvement for systems that are still in good shape.
- Evolution or revolution: Long-term quality improvement for systems that are already in a critical state.
• In more than 40 cases, an architecture evaluation done by IESE allowed identifying and rating risks early. Based on the results, business-critical decisions were facilitated.
• More than 90% of the recommendations resulting from an architecture evaluation were accepted by a customer and their realization was ordered within two weeks.
• In more than 80% of the cases, no up-to-date or sufficient architecture documentation exists, which could serve as a basis for making critical decisions. The architecture reconstruction offered by IESE supports goal-oriented and efficient reconstruction in order to achieve a sound basis for decision making.
• In architecture coaching with customers we could observe that during architecture construction, far more than 50% of the architects’ time had to be spent on requirements clarification, reconstruction of existing system ideas, and on other communication and organization tasks.
Performance & Effectiveness
• With Fraunhofer SAVE, many systems with several million lines of code were checked for compliance to the intended architecture. In particular systems, more than 50,000 violations of the architecture were discovered and recommendations for improvement were derived.
• Optimization of the visualization of software architectures in Fraunhofer SAVE allowed reducing the processing time of analysis tasks by more than 60%.
• A recurring check of the architecture compliance of a product family’s implementation with Fraunhofer SAVE allowed increasing conformance sustainably up to 98%.
• Developers getting real-time feedback about architecture violations through SAVE LiFE cause up to 60% less architecture compliance violations.
• With goal-oriented analysis and consequent re-design of the architecture, the response time of user interactions in an architecture visualization tool was reduced by a factor of more than 10 for very large systems being visualized.