DEV475 Mastering Object-Oriented Analysis and Design with UML ...

More documents

Recommendations

Info

DEV475 Mastering Object-Oriented Analysis and Design with UMLWhat Is a Component?What Is a Component?• A non-trivial, nearly independent, andreplaceable part of a system that fulfillsa clear function in the context of a welldefinedarchitecture• A component may be• A source code componentSource FileName• A run time component• An executable componentComponentInterfaceExecutableNameComponentNameOO Principle: EncapsulationMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 34From the UML User’s Guide (Booch, 1999): A component is “a physical andreplaceable part of a system that conforms to and provides the realization of a set ofinterfaces.”Software components include:• Source code components (for example, .h, .cpp files, shell scripts, data files),• Binary code components. Examples include: Java Beans, ActiveX controls, COMobjects (DLL's and OCX's from VB), CORBA objects), and• Executable components (.exe’s).Stereotypes (with alternate icons) may be used to define these specific kinds ofcomponents.Component-based development is the creation and deployment of software-intensivesystems assembled from components. Component software development should notbe confused with object-oriented programming (OOP). OOP is a way to buildobject-based software components. Component-based development (CBD) is atechnology that allows you to combine object-based components. OOP is concernedwith creating objects, CBD is concerned with making objects work together.A component conforms to and provides the physical realization of a set of interfaces.Components are implementation things. They are the physical realization of anabstraction in your design. Interfaces were discussed earlier in this module.2 - 34
Module 2 - Concepts of Object OrientationSubsystems and ComponentsSubsystems and Components• Components are the physical realization ofan abstraction in the design• Subsystems can be used to represent thecomponent in the designDesign ModelImplementation ModelComponentInterfaceComponent NameComponentInterfaceComponentNameOO Principles: Encapsulation and ModularityMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 35A component conforms to and provides the physical realization of a set of interfaces.Components are implementation things. They are the physical realization of anabstraction in your design. A subsystem can be used to represent the component inthe design.A subsystem is the design representation of a component. They both encapsulate aset of replaceable behaviors behind one or more interfaces. Subsystems andinterfaces will be discussed later in the course.2 - 35
Page 2 and 3:
Rational UniversityDEV475 Mastering
Page 5 and 6:
AcknowledgmentsThe development of t
Page 7 and 8:
► ► ► Module 0About This Cour
Page 9 and 10:
Module 0 - About This CourseCourse
Page 11 and 12:
Module 0 - About This CourseIntende
Page 13 and 14:
Module 0 - About This CourseRationa
Page 15 and 16:
Module 0 - About This CourseRationa
Page 18 and 19:
DEV475 Mastering Object-Oriented An
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47: DEV475 Mastering Object-Oriented An
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276:
show all

DEV475 Mastering Object-Oriented Analysis and Design with UML ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?