the differences between component diagram and package diagram

Question

What is the differences between component diagram and package diagram?

I use Papyrus for system modeling

Solution 1

Component diagram typically employed to illustrate interfaces. So a component might be a class or it might be a collection of classes.

A package diagram is a mechanism for you to group together related UML items, think of it as acting like (file system) directory/folder for UML.

Solution 2

I reference Michael Feathers the author of "Working Effectively with Legacy Code" (Prentice Hall 2005)

In UML, components are groups of classes that are deployed together and packages are a general grouping device for model elements. Packages can group any model elements, even things like use cases, but in practice they usually group classes, so components and packages tend to be synonymous.

From a forum posting

Solution 3

Component diagram shows an encapsulated class and its interfaces, ports and internal structure consisting of nested components and connectors. It addresses the static design implementation view of a system.

Package diagram shows the decomposition of model itself into organizational units and their dependencies.

from UML 2 User Guide

Packages are grouping things. Components are replaceable parts of system. Usually packages are identified in the analysis model and components in design model. Component diagrams are used in component based development

Comments

[Carlos]

thank you @guycole for clarification .in the case of component diagram does this mean that the interface represent the operation of class if we consider the component as a class?

[guycole]

Yes, an interface could be single class or collection of classes. Whatever you need to make a clear point.

[Carlos]

thank you Mr. @guycole you can say an interface could be a single abstract class or collection of abstract classes?