Re: oclInState() constraint



Date view Thread view Subject view Author view

Jos Warmer (J.Warmer@klasse.nl)
Mon, 03 Jan 2000 16:25:42 +0100


Heloo Kedar, At 11:48 AM 28-12-99 -0500, you wrote: >Hello Everyone, > >I need a minor clarification on the oclInState constraint as defined in the >OCL specifications defined in UML 1.3. > >The documentation states that the operation oclInState(s : OclState) >returns in true if the object is in state s. The value of s are the names >of the states in the state machine(s) attached to the classifier of the >object. > >The type of the to this operation is OclState. > >However there are no given constraints or properties defined on OclState, >expect simply that a OclState is specified using the name of the state in >the statemachine. I belive this is incomplete since it provides no means to >evaluate the oclInState expression. Also i belive there should be some >constraints definitions to define a OCL state, since an object state at >that given time is mainly a combination the value of the class attributes >in a given range. > This is not entirely correct. The values of OclState are the States as they are defined in a UML statemachine for the Classifier. When using stacharts as a means to spcify the ligecycle of objects, these State values need not be a combination of attributes, nor can they always be derived from such a combination. When you make the transition to a design model (as opposed to a specification model) States usually end up being represented by one or more attributes or links. But this is one specific situation only. >With regards, > >Kedar A. Dongre >Graduate Student >Dept. of Computer Science >Clemson University. > Regards, Jos _____________________________________________________ Klasse Objecten tel : +31 (0)35 6037646 Chalonhof 153 fax : +31 (0)35 6037647 3762 CT Soest email : J.Warmer@klasse.nl The Netherlands internet: http://www.klasse.nl


Date view Thread view Subject view Author view