Modeling Software Architectures in the Unified Modeling Language

More documents

Recommendations

Info

Modeling Software Architectures in UML • 33--3-- An “action” transition consists of a null event and a single action-- (Figure 14b).self.WSMtransitionType = action implies(self.event->isEmpty and self.action->size = 1)Stereotype WrightState for instances of meta class State--1-- All Transitions in a composite WrightState must be WSMTransitionsself.oclIsKindOf(CompositeState) impliesself.transition->forAll(t | t.stereotype = WSMTransition)--2-- WrightState applies recursively to its nested statesself.oclIsKindOf(CompositeState) implies(self.oclAsType(CompositeState).state->forAll(s |s.stereotype = WrightState))Stereotype WrightStateMachine for instances of meta class StateMachine--1-- A WrightStateMachine consists of one of the composite states discussed-- above, and partially depicted in Table 2. This constraint is elided in the-- interest of space.--2-- All WrightStateMachine transitions must be WSMTransitions.self.top.oclIsKindOf(CompositeState) impliesself.top.transition->forAll(t | t.stereotype = WSMTransition)--3-- The nested states of the top state of a WrightStateMachine must be-- WrightStatesself.top.oclIsKindOf(CompositeState) implies(self.top.oclAsType(CompositeState).state->forAll(s |s.stereotype = WrightState))The stereotypes above use the operation oclAsType to coerce the associatedmodel element to the specified class of the meta model, thereby providing accessto the other meta model elements accessible from the specified meta class. Theyalso illustrate the basic pattern we use to constrain state machines, namely,expressing constraints in terms of model elements reachable from the single,top-level state of a state machine (i.e., its attribute top).5.2.2 Wright Component and Connector Interfaces in UML. Each Wrightinterface (a port in a component or a role in a connector) has one or moreoperations. In Wright, these operations are modeled implicitly, as part ofa port or role’s CSP protocol. We choose to model the operations explicitlyin UML. The CSP protocols associated with a port or role are modeled asWrightStateMachines.Stereotype WrightOperation for instances of meta class Operation--1-- WrightOperations do not have parameters; parameters are implicit in the-- CSP specification associated with each operation.ACM Transactions on Software Engineering and Methodology, Vol. 11, No. 1, January 2002.
34 • N. Medvidovic et al.self.parameter->isEmptyStereotype WrightInterface for instances of meta class Interface--1-- WrightInterfaces are tagged as either ports or roles.WrightInterfaceType : enum { port, role }--2-- All operations in a WrightInterface are WrightOperations.self.operation->forAll(o | o.stereotype = WrightOperation)--3-- Exactly one WrightStateMachine is associated with each WrightInterface.self.stateMachine->size = 1 andself.stateMachine->forAll(sm | sm.stereotype = WrightStateMachine)--4-- The WrightStateMachine of a WrightInterface is expressed only in terms-- of that interface’s operations, all of which must be operations associated-- with the call events on the transitions of the state machine.self.stateMachine.transition->forAll(t |(t.event.oclIsKindOf(CallEvent)) impliesself.operation->exists(o | o = t.event.operation))5.2.3 Wright Connectors in UML. A connector type in Wright is describedas a set of roles, which describe the expected behavior of the interacting components,and a glue, which defines the connector’s behavior by specifying howits roles interact.We will model Wright connectors with the UML meta class Class. Wrightconnectors provide multiple interfaces (roles) and participate in associationswith other classes (Wright components). Wright connector types are assumedto have no state other than the state of their internal parts, and thus may haveno direct attributes.Stereotype WrightGlue for instances of meta class Operation--1-- WrightGlue contains a single WrightStateMachine.self.stateMachine->size = 1 andself.stateMachine->forAll(sm | sm.stereotype = WrightStateMachine)Stereotype WrightConnector for instances of meta class Class--1-- WrightConnectors must implement at least one WrightInterface, which-- must be a role.self.interface->size >= 1 andself.interface->forAll(i |i.stereotype = WrightInterface andi.WrightInterfaceType = role)--2-- A WrightConnector contains a single glue.self.operation->size = 1 andself.operation->forAll(o | o.stereotype = WrightGlue)ACM Transactions on Software Engineering and Methodology, Vol. 11, No. 1, January 2002.
Page 1 and 2: Modeling Software Architectures in
Page 3 and 4: 4 • N. Medvidovic et al.Table I.
Page 5 and 6: 6 • N. Medvidovic et al.architect
Page 7 and 8: 8 • N. Medvidovic et al.Fig. 3.An
Page 9 and 10: 10 • N. Medvidovic et al.Fig. 4.
Page 11: 12 • N. Medvidovic et al.Fig. 5.T
Page 24: Modeling Software Architectures in
Page 27 and 28: 28 • N. Medvidovic et al.with the
Page 31: 32 • N. Medvidovic et al.Table II
Page 35 and 36: 36 • N. Medvidovic et al.placehol
Page 39 and 40: 40 • N. Medvidovic et al.(?A : Na
Page 43 and 44: 44 • N. Medvidovic et al.Rule2. U
Page 45 and 46: 46 • N. Medvidovic et al.componen
Page 47 and 48: 48 • N. Medvidovic et al.6.2 Arch
Page 49 and 50: 50 • N. Medvidovic et al.the “a
Page 51 and 52: 52 • N. Medvidovic et al.7.1.4 Ar
Page 53 and 54: 54 • N. Medvidovic et al.completi
Page 55 and 56: 56 • N. Medvidovic et al.MEDVIDOV

Modeling Software Architectures in the Unified Modeling Language

Create successful ePaper yourself

Delete template?

Save as template?