Change-Driven Consistency for Component Code, Architectural Models, and Contracts

During the development of component-based software systems, it is often impractical or even impossible to include all development information into the source code. Instead, specialized languages are used to describe components and on different levels of abstraction or from different viewpoints: Component-based architecture models and contracts, for example, can be used to describe the system on a high level of abstraction, and to formally specify component constraints. Because models, contracts, and code contain redundant information, inconsistencies can occur if they are modified independently. Keeping this information consistent manually can require considerable effort, and can lead to costly errors, for example, when security-relevant components are verified against inconsistent contracts. In this paper, we present an approach for keeping componentbased architecture models and contracts specified in the Java Modeling Language (JML) consistent with Java source code. We use cha...

• Type: Journal
• Year: 2015
• Where: CBSE
• Authors: Max E. Kramer, Michael Langhammer, Dominik Messinger, Stephan Seifermann, Erik Burger
• Keywords: CBSE 2015, Software Engineering