Handling conceptual model validation by planning

Costal, Dolors; Teniente, Ernest; Urpí, Toni; Farré, Carles

doi:10.1007/3-540-61292-0_15

Cited by 9 publications

(7 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…With our method, analysts can (1) avoid a systematic definition of all operations and (2) ensure the quality of the behavior schema in terms of their completeness [31] and executability [14] properties. As far as we know, ours is the first approach to provide the automatic generation of a complete and executable basic behavior schema.…”

Section: Introductionmentioning

confidence: 99%

Automatic generation of basic behavior schemas from UML class diagrams

Albert

Cabot²,

Gómez³

et al. 2008

Softw Syst Model

View full text Add to dashboard Cite

The specification of a software system must include all relevant static and dynamic aspects of the domain. Dynamic aspects are usually specified by means of a behavioral schema consisting of a set of system operations that the user may execute to update the system state. To be useful, such a set must be complete (i.e. through these operations, users should be able to modify the population of all elements in the class diagram) and executable (i.e. for each operation, there must exist a system state over which the operation can be successfully applied). A manual specification of these operations is an error-prone and time-consuming activity. Therefore, the aim of this paper is to present a strategy for the automatic generation of a basic behavior schema. Operations in the schema are drawn from the static aspects of the domain as defined in the UML class diagram and take into account possible dependencies among them to ensure the completeness and executability of the operations.We believe our approach is especially useful in a Model-Driven Development setting, where the full implementation of the system is derived from its specification. In this context, our approach facilitates the definition of the behavioral specification and ensures its quality obtaining, as a result, an improved code generation phase.Peer ReviewedPostprint (published version

show abstract

Section: Introductionmentioning

confidence: 99%

Automatic generation of basic behavior schemas from UML class diagrams

Albert

Cabot²,

Gómez³

et al. 2008

Softw Syst Model

View full text Add to dashboard Cite

show abstract

“…In UML, the derivation rules are written in OCL. Derived types must be satisfiable too [6]. Satisfiability of a derived type means that its derivation rule may derive at least one instance of it at certain time.…”

Section: Derived Type Satisfiabilitymentioning

confidence: 99%

“…In a conceptual schema, a base type is unsatisfiable when the set of constraints defined in that schema can only be satisfied if the population of that type is empty or infinite [17]. In conceptual modeling, it is usually required that all base types be satisfiable [4,6,14]. Let T i be a base type (entity types, attributes and associations) defined in a conceptual schema.…”

Section: Base Type Satisfiabilitymentioning

confidence: 99%

“…Domain event type satisfiability comprises the properties of applicability and executability defined in [6,19]: A domain event type Dev i is applicable if there is a consistent IB state and one instance d of Dev i with a set of characteristics such that the event constraints are satisfied, and Dev i is executable if Dev i is applicable and the effects of d leave the IB in a state that is consistent and satisfies the event postconditions.…”

Section: Domain Event Type Satisfiabilitymentioning

confidence: 99%

See 1 more Smart Citation

Testing Conceptual Schema Satisfiability

Olivé

Tort

2010

Intentional Perspectives on Information Systems Engineering

View full text Add to dashboard Cite

Satisfiability is one of the properties that all conceptual schemas must have. Satisfiability applies to both the structural and the behavioral parts of a conceptual schema. Structurally, a conceptual schema is satisfiable if each base or derived entity and relationship type of the schema may have a non-empty population at certain time. Behaviorally, a conceptual schema is satisfiable if for each event type there is at least one consistent state of the information base and one event of that type with a set of characteristics such that the event constraints are satisfied, and the effects of the event leave the information base in a state that is consistent and satisfies the event postconditions. There has been a lot of work on automated reasoning procedures for checking satisfiability but it is well known that the problem of reasoning with integrity constraints and derivation rules in its full generality is undecidable. In this chapter, we explore an alternative approach to satisfiability checking, which can be used when conceptual schemas are developed in the context of an environment that allows their testing. The main contribution of this chapter is to show that when conceptual schemas can be tested then their satisfiability can be proved by testing.

show abstract

“…Behavioral schemas must be complete [14] and executable [7]. A behavioral schema bs is complete when, through the system operations in bs, a user can apply all kinds of structural events to any modifiable element of the class diagram (i.e.…”

Section: Introductionmentioning

confidence: 99%

Deriving Operation Contracts from UML Class Diagrams

Cabot¹,

Gómez²

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

Class diagrams must be complemented with a set of system operations that describes how users can modify and evolve the system state. To be useful, such a set must be complete (i.e. through these operations, users should be able to modify the population of all elements in the class diagram) and executable (i.e. for each operation, there must exist a system state over which the operation can be successfully applied). Manual specification of these operations is an error-prone and time-consuming activity. Therefore, the goal of this paper is to automatically provide a basic set of system operations that verify these two properties. Operations are drawn from the elements (classes, attributes, etc) of the class diagram and take into account the possible dependencies between the different change events (i.e. inserts/updates/deletes) that may be applied to them. Afterwards, the designer could reuse our proposal to build up more complex operations.

show abstract

Handling conceptual model validation by planning

Cited by 9 publications

References 20 publications

Automatic generation of basic behavior schemas from UML class diagrams

Automatic generation of basic behavior schemas from UML class diagrams

Testing Conceptual Schema Satisfiability

Deriving Operation Contracts from UML Class Diagrams

Contact Info

Product

Resources

About