UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Session 25—Modeling the Static View: The Component Diagram 261 OrderProcessing::OrderInterface OrderEntryUI.exe OrderProcessing::Order OrderInterface OrderEntry.exe 1..1 1..* OrderProcessing::LineItem 0..1 1..1 Purchasing::Product Figure 25-10 The OrderEntry.exe is created from multiple source classes. Quite often, however, a component consists of a single class implemented as an executable, file, library, table, or document. In Figure 25-11, the order entry executable references a set of library components for the individual classes rather than compiling the classes into one component. The user interface application is broken into two html components. The result is a more modular design. index.html OrderEntry.exe OrderInterface orderentry.html dbinterface.dll order.dll product.dll Figure 25-11 One class equals one component. Finally, components can be organized into packages just like other diagrams and model elements. This can be very helpful when managing application distribution. The result is a directory containing all the software elements needed to implement the system or subsystem represented by the package.
262 Sunday Morning REVIEW The purpose of the Component diagram is to define software modules and their relationships to one another. Each component is a chunk of code that resides in memory on a piece of hardware. The UML groups components into three broad categories: Deployment components, which are required to run the system Work product components including models, source code, and data files used to create deployment components Execution components, which are components created while running the application The component icon is a rectangle with two small rectangles on the left edge. The interface to the component may be modeled two different ways: The lollipop notation represents the interface as a small circle connected to the component by a solid line and with the name of the interface near the circle. The second method uses a class with the stereotype with a realizes relationship drawn from the component to the interface class. A component may realize (implement) as many interfaces as it requires. QUIZ YOURSELF 1. What is a UML component (See “Explaining the Component Diagram.”) 2. What is the icon for a UML component (See “Defining the Notation for Components and Component Dependencies.”) 3. What notation shows that one component needs access to another component (See “Defining the Notation for Components and Component Dependencies.”) 4. What notation is used to show that a component implements an interface (See “Defining the Notation for Components and Component Dependencies.”) 5. True or False: Each component implements a class. (See “Mapping the Logical Design to the Physical Implementation.”)
- Page 234: Session 20—Modeling the Dynamic V
- Page 238 and 239: Part V — Sunday Morning Session 2
- Page 240 and 241: SESSION 21 Applying the Basic State
- Page 242 and 243: Session 21—Applying the Basic Sta
- Page 244 and 245: Session 21—Applying the Basic Sta
- Page 246 and 247: Session 21—Applying the Basic Sta
- Page 248: Session 21—Applying the Basic Sta
- Page 251 and 252: 228 Sunday Morning receivePmt(amt)[
- Page 253 and 254: 230 Sunday Morning Figure 22-4 repr
- Page 255 and 256: 232 Sunday Morning A substate is a
- Page 257 and 258: 234 Sunday Morning Monitor when tem
- Page 260 and 261: SESSION 23 Applying the Extended St
- Page 262 and 263: Session 23—Applying the Extended
- Page 264 and 265: Session 23—Applying the Extended
- Page 266 and 267: Session 23—Applying the Extended
- Page 268 and 269: SESSION 24 Modeling the Development
- Page 270 and 271: Session 24—Modeling the Developme
- Page 272 and 273: Session 24—Modeling the Developme
- Page 274 and 275: Session 24—Modeling the Developme
- Page 276 and 277: Session 24—Modeling the Developme
- Page 278 and 279: SESSION 25 Modeling the Static View
- Page 280 and 281: Session 25—Modeling the Static Vi
- Page 282 and 283: Session 25—Modeling the Static Vi
- Page 286 and 287: SESSION 26 Modeling the Static View
- Page 288 and 289: Session 26—Modeling the Static Vi
- Page 290 and 291: Session 26—Modeling the Static Vi
- Page 292 and 293: Session 26—Modeling the Static Vi
- Page 294 and 295: Session 26—Modeling the Static Vi
- Page 296 and 297: PART # V Sunday Morning Part Review
- Page 299 and 300: PART VI Sunday Afternoon Session 27
- Page 301 and 302: 278 Sunday Afternoon design, and mo
- Page 303 and 304: 280 Sunday Afternoon :User :Web Br
- Page 305 and 306: 282 Sunday Afternoon studied Java p
- Page 307 and 308: 284 Sunday Afternoon and time. A JS
- Page 310 and 311: SESSION 28 Analysis and Architectur
- Page 312 and 313: Session 28—Analysis and Architect
- Page 314 and 315: Session 28—Analysis and Architect
- Page 316 and 317: Session 28—Analysis and Architect
- Page 318 and 319: Session 28—Analysis and Architect
- Page 320 and 321: SESSION 29 Design of a Web Applicat
- Page 322 and 323: Session 29—Design of a Web Applic
- Page 324 and 325: Session 29—Design of a Web Applic
- Page 326 and 327: Session 29—Design of a Web Applic
- Page 328 and 329: Session 29—Design of a Web Applic
- Page 330 and 331: SESSION 30 UML Modeling Tools Sessi
- Page 332 and 333: Session 30—UML Modeling Tools 309
Session 25—Modeling the Static View: The Component Diagram 261<br />
<br />
OrderProcessing::OrderInterface<br />
<br />
OrderEntryUI.exe<br />
OrderProcessing::Order<br />
OrderInterface<br />
<br />
OrderEntry.exe<br />
<br />
<br />
<br />
1..1<br />
1..*<br />
OrderProcessing::LineItem<br />
0..1<br />
1..1<br />
Purchasing::Product<br />
Figure 25-10 The OrderEntry.exe is created from multiple source classes.<br />
Quite often, however, a component consists of a single class implemented as an executable,<br />
file, library, table, or document. In Figure 25-11, the order entry executable references<br />
a set of library components for the individual classes rather than compiling the<br />
classes into one component. The user interface application is broken into two html components.<br />
The result is a more modular design.<br />
index.html<br />
<br />
OrderEntry.exe<br />
OrderInterface<br />
orderentry.html<br />
<br />
dbinterface.dll<br />
<br />
order.dll<br />
<br />
product.dll<br />
Figure 25-11 One class equals one component.<br />
Finally, components can be organized into packages just like other diagrams and model<br />
elements. This can be very helpful when managing application distribution. The result is a<br />
directory containing all the software elements needed to implement the system or subsystem<br />
represented by the package.
Change language