The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
Raising the level of abstraction for software engineers to write applications is still an undergoing issue. So, models will most likely become the dominant artifact in the development of software. However, models are nothing without the framing of a methodology, like the software factories methodology, which includes the software product lines approach. In the context of software product lines, model-driven...
This paper describes our lessons learned and experiences gained from turning an analytical reverse engineering technology - architecture compliance checking - into a constructive quality engineering technique. Constructive compliance checking constantly monitors the modifications made by developers. When a structural violation is detected, the particular developer receives live feedback allowing prompt...
Seamless interoperability across system boundaries and optimally tailored solutions for customers are dominating concerns in the vision of future office infrastructures. This means to change the way how office systems are developed from todaypsilas ad-hoc integration of independent systems towards a collaborative approach for adequate systems of systems. In this paper, we propose a development method...
Service Orientation (SO) is a relevant promising candidate for accommodating rapidly changing user needs and expectations. Adopting SO in practice for real software and system development, however, has uncovered several challenging issues, such as how to identify services, determining configurations of services that are relevant to users' current context, and maintaining system integrity after configuration...
Product line organizations need to continuously invest into their product line infrastructure to minimize its degeneration and thus maximize its viability. Besides feedback on a strategic level to monitor changing customer requirements, technical feedback with respect to reusing product line components needs to be provided from application to family engineering. After successfully installing a product...
For installing product line engineering in practice, strategies are needed that are composed of smaller steps where, on the one hand, each of them represents a well-defined move towards the ultimate goal of a well-functioning product line organization but, on the other hand, does not bear unmanageable risks. Hence product line approaches like Fraunhofer PuLSETM must define such steps, as well as provide...
New ideas and concepts emerging from research have to be accepted by industrial stakeholders before they are used in product development. In this paper, we present our lessons learned and experiences gained from transferring a reverse engineering technology - architecture compliance checking - to Testo AG, one of the world's leading suppliers of portable measurement devices for industry and emission...
In this paper, we present an approach that supports efficient quality impact analyses in the context of iteratively constructed architectures. Since the number of established architectural strategies and the number of inter-related models heavily increase during iterative architecture construction, the impact analysis of newly introduced quality strategies during later stages becomes highly effort-intensive...
There's a growing gap between the state of the art and the state of the practice in software architecture. The state of the art revolves around advanced architecture description and modeling languages, while in practice, the software architect - if there is one - has neither the power nor the tools to create a sound software architecture that is truly useful throughout the entire software life cycle...
Over the last years scoping has been established as the initial activity for starting product line engineering. To be successful in defining the right scope for more than 5 years in industrial projects, we always had to customize our generic scoping process to the organizational context, projects constraints, available artifacts, and resources. In this paper, we present an update of the scoping process...
The decision of an organization to introduce product line engineering depends on a sound and careful analysis of risks and return on investment. The latter is computed by an economic model, which relies on high quality input and must reflect the envisioned migration strategy sufficiently. To facilitate risk analysis, this paper applies Monte-Carlo simulation to an existing product line economic model...
Product line practices are increasingly becoming popular in the domain of embedded software systems. This paper presents results of assessing success, consistency, and quality of Testo's product line of climate and flue gas measurement devices after its construction and the delivery of three commercial products. The results of the assessment showed that the incremental introduction of architecture-centric...
The software architecture is one of the most crucial artifacts within the lifecycle of a software system. Decisions made at the architectural level directly enable, facilitate, hamper, or interfere with the achievement of business goals, functional and quality requirements. Architecture evaluations play an important role in the development and evolution of software systems since they determine how...
Documentation is an integral part of a software system. It contains the information that is necessary to effectively and successfully develop, use, and maintain a system. In practice, however, the creation of appropriate documentation is largely neglected. This paper investigates the reasons for this neglect, presents view-based software documentation, our approach to improve the current situation,...
The software architecture is one of the most crucial artifacts within the lifecycle of a software system. Decisions made at the architectural level directly enable, facilitate, hamper, or interfere with the achievement of business goals as well as meeting functional and quality requirements. Software architectures are also essential for the success of product line engineering. In this work, we summarize...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.