Component diagram

From Wikipedia, the free encyclopedia

In the Unified Modeling Language, a component diagram depicts how a software system is split up into components and shows the dependencies among these components. Physical components include files, headers, link libraries, modules, executables, or packages. Component diagrams are prevalent in the field of software architecture but can be used to model and document any system’s architecture.

Note that components are types and only executable components may have instances.

[edit] External links

• Introduction to UML 2 Component Diagrams by Scott W. Ambler
• UML 2 Component Diagram Guidelines by Scott W. Ambler
• Component Diagrams in UML 2

Unified Modeling Language (UML) (category) ( view • talk • edit )
Background
Organizations: Object Management Group (OMG) • UML Partners Persons: Grady Booch • Ivar Jacobson • James Rumbaugh
Concepts
Object oriented: programming (OOP) • analysis and design (OOAD) Structure: Actor • Attribute • Class • Component • Interface • Object • Package  Behavior: Activity • Event • Message • Method • Operation • State • Use case  Relationships: Aggregation • Association • Composition • Dependency • Generalization (or Inheritance)  Extensibility: Profile • Constraint • Stereotype • Tagged values  Other concepts: Multiplicity • Role
Diagrams
Structure diagrams Class diagram • Component diagram • Composite structure diagram • Deployment diagram • Object diagram • Package diagram		Behavior diagrams Activity diagram • State Machine diagram • Use case diagram • Communication diagram • Interaction overview diagram • Sequence diagram • Timing diagram
Topics
Compared to relational database model (ERD) • Glossary of UML terms • Systems Modeling Language (SysML) • UML colors:
Role	Moment, Interval	Description	Party, place, thing
Tools(category) and Processes
List of UML tools • Rational Unified Process (RUP)