V. Mencl, F. Plasil, and J. Adamek (Czech Republic)
SoftwareMethodologies,UML,UseCases,FormalMethods
Designing components and composing them into an architecture inherently involves describing their behavior. The classical software engineering approach to specifying requirements for large-scale components is to start with use cases. However, employing use cases to component architectures triggers the need of(i) assembling the behavior specified by several use cases, (ii) composing the behavior ofcommunicatingentities,and (iii)reasoningonconsistency of the composed behavior. Applying a modeling language, such as UML, while dealing with these issues is desirable. Based on the composite structures framework, the emerging standard UML 2.0 defines a hierarchical component model; here, behavior of components may be specified with use cases. UML 2.0 provides four behavior specification mechanisms. The key goal of this paper is to evaluate whether and how these behavior specification mechanisms address the issues above. We show that only Interactions implicitly allow for addressing all of them.
Important Links:
Go Back
