Development of Component and Service-Oriented Software Architectures with UML and UML-RT - Sequence Diagrams and Statecharts | CSE 218, Study notes of Software Engineering

Download Development of Component and Service-Oriented Software Architectures with UML and UML-RT - Sequence Diagrams and Statecharts | CSE 218 and more Study notes Software Engineering in PDF only on Docsity! California Institute for Telecommunications and Information Technologies La Jolla, CA 92093-0405, USA Department of Computer Science & Engineering University of California, San Diego La Jolla, CA 92093-0114, USA Development of Component- and Service-Oriented Software Architectures with UML and UML-RT — Components and Services — Ingolf H. Krueger ikrueger@ucsd.edu © Ingolf H. Krueger 2February 4, 2003 CSE/CAL·(IT)2 Overview • What’s in a Component? • Systematic Component Development • Component Diagrams © Ingolf H. Krueger 5February 4, 2003 CSE/CAL·(IT)2 What‘s in a Component? „component (in code): A coherent package of software implementation that (a) has explicit and well- specified interfaces for the services it provides; (b) has explicit and well-specified interfaces it expects from others; and (c) can be composed with other components, perhaps customizing some of their properties, without modifying the components themselves. As a consequence of these properties, a component can be independently developed, delivered, and deployed as a unit.“ [DW98] © Ingolf H. Krueger 6February 4, 2003 CSE/CAL·(IT)2 What‘s in a Component? UML: „A physical, replaceable part of a system that packages implementation and conforms to and provides the realization of a set of interfaces.“ [RJB99] ⇒ Very technical, implementation-oriented ⇒ Covers: ⇒ Source code (header-files, ...) ⇒ Binary code (link-files, ...) ⇒ Executables (.exe-, .dll-files, ...) © Ingolf H. Krueger 7February 4, 2003 CSE/CAL·(IT)2 What‘s in a Component? More general: Component is unit of – Function – Composition – Development – Implementation – Execution – Reuse – ... © Ingolf H. Krueger 10February 4, 2003 CSE/CAL·(IT)2 Components: Basics Component A Component B Encapsulation of structure, state, behavior Interface offered by “A” Interface required by “A” © Ingolf H. Krueger 11February 4, 2003 CSE/CAL·(IT)2 Components: Basics Component A Component B Encapsulation of structure, state, behavior Interface offered by “A” Interface required by “A” A1 A2 A3 IF- Handler1 IF- Ha dler2 IF- Handler3 Hierarchy/Composition © Ingolf H. Krueger 12February 4, 2003 CSE/CAL·(IT)2 Component-Oriented Developement: • Identify reusable entities • Focus on – Composition instead of on inheritance – Hierarchy – Decoupling – Distribution/Concurrency © Ingolf H. Krueger 15February 4, 2003 CSE/CAL·(IT)2 Systematic Component Development CLS – Domain Model reset close open Command *«ordered» Command Source * 1 Lock 1 * controls Target SensorKey Button Trunk Right Door Left Door ... 1 1 CLS KDoors KTrunk KAll Collision © Ingolf H. Krueger 16February 4, 2003 CSE/CAL·(IT)2 Systematic Component Development CLS - Use Cases • Handle Command – Commands consist of action identifier („open“, „close“, „reset“, ...) and a target lock – Translate arriving messages into signals for corresponding target • Register Lock – Register lock with CLS – Only after registering the lock with CLS will signals be forwarded to the lock • Register Source – Register signal source with CLS • Self Test – Continual self test – ... • ... © Ingolf H. Krueger 17February 4, 2003 CSE/CAL·(IT)2 Systematic Component Development Command Interpreter ICLSCommand OutSignal Converter Opener Closer Resetter LockReg Interpreter Target Table IRegLock Target Handler SourceReg Interpreter Source Table IRegSource Source Handler Test Plan Tester Interface Classes Control Classes Domain Classes © Ingolf H. Krueger 20February 4, 2003 CSE/CAL·(IT)2 Component Diagrams Interface offered by A Interface required by A Component A Component B IXY Interface name Component symbol © Ingolf H. Krueger 21February 4, 2003 CSE/CAL·(IT)2 Component Diagrams Stereotype «interface»: Class without implementation for operations Component A IXY IW IZ «interface» IXY operation1() operation2() operationN() ... © Ingolf H. Krueger 22February 4, 2003 CSE/CAL·(IT)2 Component Diagrams Interface Definition “Simplicity” of component diagrams requires disciplined augmentation by means of – use case diagrams – Interaction diagrams – statecharts to describe behavior at interface