Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Evolving algebras 1993: Lipari guide
Specification and validation methods
Design pattern modelling and instantiation using DPML
CRPIT '02 Proceedings of the Fortieth International Conference on Tools Pacific: Objects for internet, mobile and embedded applications
A UML-Based Pattern Specification Technique
IEEE Transactions on Software Engineering
Precise Modeling of Design Patterns in UML
Proceedings of the 26th International Conference on Software Engineering
Using the Metamodel Mechanism to Support Class Refinement
ICECCS '05 Proceedings of the 10th IEEE International Conference on Engineering of Complex Computer Systems
| Hi-index | 0.00 |
Detecting errors in an early phase of software development can help to reduce the cost of software systems. Many research attempts presented a fixed set of rules to help finding errors in a model. However, flexibility is one of the characteristics during software development. The correctness of a model usually depends on many factors such as development environments. The predefined rules usually fail to provide such flexibility. This paper will apply the idea from YACC/BISON to allow software engineers to define the validity of their application models in a profile. Central to the profile mechanism is the instance-of relation, which is established between an application model and a profile. As a result, engineers can first define the validity of an application in a profile and thus find errors in a model when the model is not a valid instance of the profile. Based on the profile mechanism, we build a tool, called ICER, which can automatically help developers to check the instance-of relation between a profile and an application model. As an example, we apply the reification of the Factory Method pattern to illustrate how the ICER tool helps to support error detection.