Constraint checking in UML modeling

ABSTRACT

Modeling aims to represent a system in a given formalism. As representations based on high level modeling languages can be interpreted in many ways, constraints are introduced to restrict the field of the possible. On the other hand, language semantics is defined using constraints as well. Within the context of the UML, a classification is proposed to clarify the nature of the constraints that must be fulfilled to ensure model correctness. Constraint violations are only warnings while others are serious. Depending on the kind and the context of the violation, help and advice can be supplied, and improvements may be conditionally done. In the UML, constraints are assertions described in a side-effect free language (OCL), while actions are not supplied. To extend capabilities, the constraints are translated intowell-using modeling rules that form the knowledge base of an expert system in modeling. This modeling companion is briefly outlined.

REFERENCES

• 1: C. Balzer, T. Cheatham, C. Rich, "Report on a knowledge-based software assistant",A.I. and Software Engineering Morgan Kaufman publishers, 1986
• 2: Grady Booch , James Rumbaugh , Ivar Jacobson, The Unified Modeling Language user guide, Addison Wesley Longman Publishing Co., Inc., Redwood City, CA, 1999
• 3: G. Caplat, "Sherlock Environment", //servif5.insa-lyon.fr/chercheurs/gcaplat/
• 4: A. S. Evans, S. Kent, "Meta-modelling semantics of UML: the pUML approach", UML'99, LNCS 1723, 1999, 140-155
• 5: D. Harel , B. Rumpe, Modeling Languages: Syntax, Semantics and All That Stuff, Part I: The Basic Stuff, Weizmann Science Press of Israel, Jerusalem, Israel, 2000
• 6: Stuart Kent, Constraint diagrams: visualizing invariants in object-oriented models, Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications, p.327-341, October 05-09, 1997, Atlanta, Georgia, United States
• 7: S. Kent and Y. Gil, "Visualising action contracts in OO modelling",IEEE Software Engineering Journal, 1999.
• 8: Kevin Lano , A. Evans, Rigorous Development in UML, Proceedings of the Second Internationsl Conference on Fundamental Approaches to Software Engineering, p.129-144, March 22-28, 1999
• 9: Luis Mandel , María Victoria Cengarle, On the Expressive Power of OCL, Proceedings of the Wold Congress on Formal Methods in the Development of Computing Systems-Volume I, p.854-874, September 20-24, 1999
• 10: John Mylopoulos , Lawrence Chung , Brian Nixon, Representing and using nonfunctional requirements: a process-oriented approach, IEEE Transactions on Software Engineering, v.18 n.6, p.488-497, June 1992
• 11: I. Ober, "More meaningful UML Models",TOOLS - 37, IEEE Press, 2000, 146-157
• 12: www.omg.org/
• 13: OMG, "Schedulability, Performance and Time" Reply to the RFP of the OMG, ARTiSAN Software Tools, I-Logix, Rational Software Corp., Telelogic AB, TimeSys Corporation, Tri-Pacific Software, 2000
• 14: B. Peuschel, W. Schaefer, S. Wolf."A knowledge-based software development environment supporting cooperative work", I.J.S.E.K.E., Vol.2(1), 1992, 79-106
• 15: http://www.cs.york.ac.uk/puml/
• 16: Howard B. Reubenstein , Richard C. Waters, The Requirements Apprentice: Automated Assistance for Requirements Acquisition, IEEE Transactions on Software Engineering, v.17 n.3, p.226-240, March 1991 [doi>10.1109/32.75413]
• 17: M. Richters, M. Gogolla, "Validating UML Models and OCL Constraints", UML 2000, LNCS 1939, 2000, 265-277
• 18: Mark Richters , Martin Gogolla, OCL: Syntax, Semantics, and Tools, Object Modeling with the OCL, The Rationale behind the Object Constraint Language, p.42-68, January 2002
• 19: J. L. Sourrouille. "A Knowledge-based Framework for O-O software development environments",I.J.S.E.K.E., Vol.4(4), 1994, 451-479
• 20: J. L. Sourrouille, "UML Behavior: Inheritance and Implementation in Current Object-Oriented Languages", UML'99, LNCS 1723, 1999, 457-472
• 21: UML, "OMG Unified Modeling Language Specification (draft)", Version 1.3, March 1999
• 22: W3C (World Wide Web Consortium). Extensible Markup Language (XML), 1998

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques
          Subjects: Object-oriented design methods

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.6 Programming Environments

General Terms:
Design, Languages, Verification