Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
UML components: a simple process for specifying component-based software
UML components: a simple process for specifying component-based software
POPL '77 Proceedings of the 4th ACM SIGACT-SIGPLAN symposium on Principles of programming languages
On the Frame Problem in Procedure Specifications
IEEE Transactions on Software Engineering
Using OCL and UML to Specify System Behavior
Object Modeling with the OCL, The Rationale behind the Object Constraint Language
Data Flow Analysis of UML Action Semantics for Executable Models
ECMDA-FA '08 Proceedings of the 4th European conference on Model Driven Architecture: Foundations and Applications
Incremental integrity checking of UML/OCL conceptual schemas
Journal of Systems and Software
From declarative to imperative UML/OCL operation specifications
ER'07 Proceedings of the 26th international conference on Conceptual modeling
Specification of invariability in OCL
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
A library of OCL specification patterns for behavioral specification of software components
CAiSE'06 Proceedings of the 18th international conference on Advanced Information Systems Engineering
Component-Level dataflow analysis
CBSE'05 Proceedings of the 8th international conference on Component-Based Software Engineering
Hi-index | 0.00 |
Separation of concerns is an important aspect of component-based development (CBD), and managing data is a primary concern in enterprise systems. In CBD methods, such as Catalysis and UML components, this concern is addressed by business components. Although a business component is self-contained, having no direct dependency on any of the other components, the data propagation between components may lead to indirect data dependencies across the business components, and grasping such dependencies at design-time is crucial to maintaining data consistency. In this paper we propose a method for data-flow analysis (DFA) of the business component model, in which the operational behavior is described using the Object Constraint Language (OCL) pre-postconditions. Traditional DFA techniques are aimed at procedural descriptions, while OCL is a declarative language whose essential properties include nondeterminism and incompleteness. In order to extract a data-flow from the OCL descriptions taking account of their semantics, our proposed method applies the idea of abstract interpretation. We also analyze the safety of our abstract interpretation technique, and discuss the usefulness and scalability of the method from a practical viewpoint. The proposed method, when used in conjunction with the inter-procedural DFA techniques, would allow us to extract the propagation and dependency of data across the business components automatically.