loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Fifth Asia-Pacific Software Engineering Conference (APSEC'98)
Interpreting the Object Constraint Language
Taipei, Taiwan
December 02-December 04
ISBN: 0-8186-9183-2
ASCII Text
x 
 
Ali Hamie, John Howse, Stuart Kent, "Interpreting the Object Constraint Language," Asia-Pacific Software Engineering Conference, pp. 288, Fifth Asia-Pacific Software Engineering Conference (APSEC'98), 1998.
 
 
BibTex
x
 
@article{ 10.1109/APSEC.1998.733731,
author = {Ali Hamie and John Howse and Stuart Kent},
title = {Interpreting the Object Constraint Language},
journal ={Asia-Pacific Software Engineering Conference},
volume = {0},
year = {1998},
isbn = {0-8186-9183-2},
pages = {288},
doi = {http://doi.ieeecomputersociety.org/10.1109/APSEC.1998.733731},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Asia-Pacific Software Engineering Conference
TI - Interpreting the Object Constraint Language
SN - 0-8186-9183-2
SP
EP
A1 - Ali Hamie,
A1 - John Howse,
A1 - Stuart Kent,
PY - 1998
VL - 0
JA - Asia-Pacific Software Engineering Conference
ER -
 
Ali Hamie, University of Brighton,
John Howse, University of Brighton,
Stuart Kent, University of Brighton,
The Object Constraint Language (OCL), which forms part of the UML 1.1. set of modelling notations is a precise, textual language for expressing constraints that cannot be shown in the standard diagrammatic notation used in UML. A semantics for OCL lays the foundation for building CASE tools that support integrity checking of whole UML models, not just the component expressed using OCL. This paper provides a semantics for OCL, at the same time providing a semantics for classes, associations, attributes and states.
Citation:
Ali Hamie, John Howse, Stuart Kent, "Interpreting the Object Constraint Language," apsec, pp.288, Fifth Asia-Pacific Software Engineering Conference (APSEC'98), 1998
Usage of this product signifies your acceptance of the Terms of Use.