Affordable Access

Análise da compatibilidade de componentes especificados em UML

Authors
Publication Date
Source
Repositório Institucional da UFSC
Keywords
License
Unknown
External links

Abstract

In the component-based software development, an application is produced by connecting two or more components. Increasing predictability of the result of combination of a component with others components is still an issue for research. The compatibility analysis of components is performed from the interface#s description of the interconnected components. Most proposals for compatibility analysis are limited to verify the compatibility between only two components and does not consider the whole component set of an application. And when they do it, they only detect deadlock in the system. This study proposes a strategy to achieve automated behavioral analysis of components from an approach described in the literature, in which the interface of components is described entirely in UML.The structural description uses the component, class and deployment diagrams, and behavior description, the state machine diagram diagram. The proposed strategy provides a way of converting the state machine of the individual components and of the application in Petri nets, transparently to the user, and sets criteria for behavioral analysis. Behavioral problems are identified from the interpretation of the Petri nets properties in the context of the components. This solution considers the behavior of the system as a whole and allows the identification, in addition to deadlock, of potential behavioral problems, and treats then as warnings that must be analyzed by the user, such as: unavailable services, temporarily available services, or component available services become temporarily available or unavailable in the application. The proposed solution allows a more predictable result of the combination of components. This solution has been automated in the SEA environment, using automated tools included in it, where reports are issued with the found problems. The case studies produced to evaluate the proposal are presented.

Statistics

Seen <100 times