Component+Diagrams

Mujtaba Mansoor Muhammad Usman Kamran Zubair Azmat [] [] [] [] [] [] ** SUMMARY: ** UML component diagrams describe system components and how they are dependent on each others. A component is an autonomous unit within a system. The components can be used to define software systems of relative size. The diagrams also enable to model the high-level software components, and the interfaces to those components. The c omponent and subsystems can be flexibly reused and replaced. There is a dependency between two elements a change in the attribute of one element may cause changes to the other. They are also referred to as “wiring diagrams”. There are two components in Componenet diagram Modular unit with well-defined interfaces that is replaceable within its environment and Autonomous which has one or more provided and required interfaces. Its internal are hidden and inaccessible. There are two fundamental strategies for developing a component model, either top down or bottom up. Top down approach helps in identifying the system software view for all team members, thus promoting over building of the system. Bottom up approach is used when we have to componentized the existing classes.
 * COMPONENT DIAGRAM **
 * GROUP MEMBERS: **
 * The Sources: **