This preview shows pages 1–2. Sign up to view the full content.
This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: Behavior Capture and Test for Controlling the Quality of Component-Based Integrated Systems Leonardo Mariani Dipartimento di Informatica, Sistemistica e Comunicazione Universit`a degli Studi di Milano Bicocca via Bicocca degli Arcimboldi, 8 20126 Milano, Italy email@example.com Mauro Pezz`e Dipartimento di Informatica, Sistemistica e Comunicazione Universit`a degli Studi di Milano Bicocca via Bicocca degli Arcimboldi, 8 20126 Milano, Italy firstname.lastname@example.org 1. INTRODUCTION Complex software systems are seldom designed from scratch; rather they are often designed by assembling basic compo- nents. Software tools are not an exception: They are of- ten obtained by assembling simple tools that provide basic functionality. From the verification viewpoint, basic tools do not differ from components: in both cases they can be seen as black box elements that provide a set of services for the embedding system or tool. Complex systems and tools are often provided in many different versions and configu- rations that are obtained by adding and replacing various components. Let us consider for example a complex CASE tool that runs on several platforms and is distributed in var- ious versions for different user profiles. Many graphics and system components may be used for distinct platforms. For instance, the simple configurations distributed free-of-charge may include only a simple set of basic tools, while the ed- ucational and the professional editions may include a wider set of basic tools that provide extended functionality. Un- fortunately, behavioral differences among components may cause subtile failures difficult to reveal and remove. On of the main goals of verification is to check the completeness and compatibility of the services provided by the compo- nents to reveal possible conflicts, thus supporting efficient verification of different tool configurations and versions. The use of components in running systems produces a lot of useful information about the components behavior that could be used to check for the compatibility between differ- ent components and between components and embedding systems. Unfortunately this information is normally lost. This paper proposes a new technique, called Behavior Cap- ture and Test (BCT) , that takes advantage of this informa- tion. We first monitor the system execution and capture the essential characteristics of the behavior by means of au- tomatic probes. We then use the collected information to verify the compatibility of the components when used as part of other systems. In this way, we can automatically reveal incongruences of components that either replace ex- isting ones or are added to existing systems to extend their functionality....
View Full Document
- Spring '11