Introduction
The Unified Modelling Language (UML) is a language which represents best engineering practices that are used to specify, visualize, construct, and document the elements of software, business modeling, and even non-software systems. The UML was developed in 1997 by the Object Management Group (OMG) ( Larman, 2012).
UML
UML provides designers with a framework that they could use to construct systems. The UML can be used by designers to specify what is needed of a system and how the system should be implemented. The UML also helps designers to visualize systems before implementing them. This is because UML is graphical in nature and this allows designers to see systems from a graphical point of view and therefore adjust them before implementing them. However, what UML does not provide is the methodology for designing systems ( Larman, 2012).
Delegate your assignment to our experts and they will do the rest.
The main reason why the UML was developed was to provide an architectural framework that could be used for modeling object-oriented applications and systems. OMG developed UML so that designers can have a basic structure or industry standard on which they base their designs or object modeling. If the UML had been developed, there would not have been an industry standard that could be used as a basis for object modeling. This implies that object modeling for different objects and systems would have different since there would have different methodologies and notations with regard to object modeling ( Larman, 2012).
UML diagrams
There are various groups of UML diagrams. They include UML use case diagram, UML sequence diagram, UML component diagram, UML class diagram, UML activity diagram, UML collaboration diagram, UML deployment diagram, UML state diagram, and UML Package diagram. The UML use case diagram depicts relationships between actors, use cases, and systems; the UML sequence diagram depicts how operations are carried out; the UML activity diagram models how activities are coordinated; the UML collaboration models system functionality; UML class diagram depicts object and information structures and communication with users; UML component diagram models the implementation of functionality; UML deployment diagram models physical hardware elements; UML state diagram models the dynamic nature of systems; and UML package diagram depicts the organization of a project. The use-case modeling identifies system functionality. it indicates how external devices or people interact with the system under design ( Larman, 2012).
The three major tasks in conducting object-oriented analysis are defining, analyzing, and grouping. Conducting object-oriented analysis involves defining the requirements which are necessary for the successful operation of a system under design. This ensures that the right requirements are provided in designing a system. Analysis involves assessing the requirements to determine whether they are suitable for the system. Object-oriented analysis is normally carried out on requirements to ensure that they are suitable for the system. The last task is grouping. Grouping putting items which interact by data, behavior, or class so that a model which accurately represents the purpose it was intended for is created ( Larman, 2012).
Business requirements use-case models are refined and changed into analysis use-case models through mapping. The activities in the requirements are mapped into the RUP of the analysis use-case models. The reason for the refinement and mapping is to allow for elaboration, inception, and construction of the system. The refinement and change thereby allows for the requirements to be involved in the construction of the system through mapping ( Larman, 2012).
Reference
Larman, C. (2012). Applying UML and Patterns: An Introduction to Object Oriented Analysis and Design and Interative Development . Pearson Education India.
