Component Diagram example essay topic

UML (Unified Modeling Language) The Unified Modeling Language is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems. The key is to organize the design process in a way that clients, analysts, programmers and other involved in system development can understand and agree on. The UML provides the organization. The UML was released in 1997 as a method to diagram software design, by some of the best minds in object oriented analysis and design. It is by far the most exciting thin to happen to the software industry in recent years.

Every other engineering discipline has a standard method of documentation. Electronic engineers have schematic diagrams; architects and mechanical engineers have blueprints and mechanical diagrams. The software industry now has UML. There are different types of UML diagrams. Each UML diagram is designed to let developers and customers view a software system from a different perspective and in varying degrees of abstraction. UML diagrams commonly created in visual modeling tools include: use case diagram which displays the relationship among actors and use cases.

Class case diagram models class structure and contents using design elements such as classes, packages and objects. It also displays relationships such as containment, inheritance, associations and others. Sequence diagram displays the time sequence of the objects participation in the interaction. This consists of the vertical dimension (time) and horizontal dimension (different objects). Collaboration diagram displays an interaction organized around the objects and their links to one another. Numbers are used to show the sequence of messages.

State diagram displays the sequences of states that an object of an interaction goes through during its life response to received stimuli, together with its response and actions. Activity diagram displays a special state diagram where most of the states are action states and most of the transitions are triggered by completion of the actions in the source states. This diagram focuses on flows driven by internal processing. Component diagram displays the high level packaged structure of the code itself.

Dependencies among components are shown, including source code components, binary code components, and executable components. Some components exist at compile time, at link time, at run times well as at more than one time. Deployment diagram displays the configuration of run time processing elements and the software components, processes, and object that live on them. Software component instances represent run time manifestation of code units.