June 2003
Intermediate to advanced
984 pages
25h 13m
English
Content preview from UML™ Bible
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
CHAPTER 15
Modeling Software Using the Component Diagram
In This Chapter
- Defining the Component diagram for UML 1.4 and 2.0
- Defining and modeling component types
- Defining and modeling component containment
- Defining and modeling dependencies
- Defining and modeling «reside» and «implement» dependencies
- Defining and modeling interfaces and ports
- Defining and modeling connectors
Once the logical design is completed using the Use Case, Class, and Interaction diagrams, the next step is to define the physical implementation of your design. The physical implementation must address three issues:
- The physical description of the software. The Component diagram models the physical implementation of the software specified by the logical requirements in Class diagram.
- The layout of the hardware. The Deployment diagram (discussed in Chapter 16) models the physical architecture of the hardware.
- The integration of the software and the hardware. The combined Deployment and Component diagrams (covered in Chapter 17) model the integration and distribution of the software across the hardware.
Classes describe the logical organization and intent of your software design. Components describe the physical implementations of your software design.
The purpose of the Component diagram is to define physical ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.