Fluent Essays

An Analysis class diagram, communication diagram and a sequence diagram needed all constructed in enterprise architect software. The attached version are the diagrams that were required for this task. copy_2.docx Unformatted Attachment Preview 1 UML Modeling Name Institution Instructor Course Date Systems Analysis and Design 2 Table of Contents 1 2 3 4 Part 1 ................................................................................................................................ 3 1.1 Analysis class diagram ............................................................................................ 3 1.2 Decision made while drawing the Analysis class diagram ................................... 4 Part 2 ................................................................................................................................ 5 2.1 Communication Diagram ........................................................................................ 5 2.2 Communication diagram for the use case ............................................................. 6 2.3 Sequence Diagram ................................................................................................... 7 Part 3 ................................................................................................................................ 9 3.1 Evaluation................................................................................................................. 9 3.2 Unified Modeling Language and how it supports the designer ......................... 10 3.3 Benefits of UML ..................................................................................................... 11 Bibliography .................................................................................................................. 12 Systems Analysis and Design 3 1 1.1 Part 1 Analysis class diagram An Analysis class diagram is used to represent eloquent concepts in computational domains. It centers on the domain’s concepts rather than the software elements as would be in the class diagram. The analysis class diagram requires the existing use cases and actors; it may also be built at the same time as use cases. These diagrams are used in the illustration of things, ideas and concepts, they also illustrate the attributes of the concepts (Chren, Buhnova, Macak, Daubner and Rossi, 2019). The diagrams facilitate decomposition of the domain problems into comprehensible units and clarifying the terminologies. The concepts can be identified from physical objects, roles. Places, events, and records. Other sources of concepts can be from processes, specifications and rules (Lending and May, 2019). as opposed to the class diagram, the Analysis class diagram has associations such as Related –to, Owned-by, Far-from, Above, below. Communicates with, Uses, manages, or controls, description of contained in, Part-of. Systems Analysis and Design 4 Figure 1 1.2 Decision made while drawing the Analysis class diagram The most important element in the Diagram is the identifications of the associations and concepts that would map in the class diagram. The concepts could be driven from objects such as tour, real-world things such as tour leader and tour drivers. The types of association between these three can be identified in many forms, such as Tour driver often communicates with the tour leader. At the same time, the tour leader communicates with the driver. The tour leader is part of Tour while the clerks manage the tour and the tour leader as well. Another area that needed a decision is the cardinality of the objects, for example, a tour can have one or more tour drivers. Clerk manages many tours while a tour can have one or more drivers. The entities and the behaviors of each class Systems Analysis and Design 5 had to be decided upon, for example, the most important feature of the tour leader is its code and for the tour driver, it is the driver code. 2 2.1 Part 2 Communication Diagram The essence of communication diagrams is to illustrate the interaction of objects. It is an extension of object diagrams that serve the purpose of illustrating how messages are relayed across the objects. It also shows the messages that are sent to one another by various objects. The communication diagram, therefore, models the messages that pass between the objects or roles that deliver the functionalities of the use cases and the operations (Jagtap,Gawde, Pawar, Shendge and Avhad, 2016). It also captures the collaborations that indicate the history of messages between the objects and functions within the cooperation scenario. It also supports the identification of classes and objects and their attributes and the operations or messages that participates in the use cases (Bazydło and Adamski, 2016). Systems Analysis and Design 6 2.2 Communication diagram for the use case Figure 2 The communication diagram shows how communication happens between the two entities. The major entities in the scenario are the System and the clerk. The data, therefore, flows from the system to the clerk and vice versa. The first decision to be made was the sequence of the messages. The first messages first and the last messages going last in the system. Then the most difficult part is the identification of the communicating entities in the use case. There are only two, the system and the Clerk as shown previously. Clerk, therefore, adds tour, enters tour details into the system and selects both driver and the tour leader. On the other hand, the system gives the clerk tour details as entered by the clerk, it assigns the driver and authenticates the driver codes. The error codes are then sent to the clerk who identifies the source of the error. Systems Analysis and Design 7 2.3 Sequence Diagram Sequence diagrams are similar to communication diagram as they both depict the communication interaction between two objects. They gives the order of interactions among objects. The major function of a sequence diagram is illustrating the order of objects within the system function and is mostly utilized during the designing of the system (Karim, Liawatimena, Trisetyarso, Abbas and Suparta, 2017). The sequence diagram is therefore used to model the usage scenario: this shows how the system could be used, it gives the best way to work through the system logic for the System. The Sequence diagram also uses UML sequence to explore the logic of functions procedure and any complex process (Faria and Paiva, 2016). Another item in the sequence diagram is modeling service logic. Strategized services are high-level techniques used by many firms and the sequence diagram gives the best way to represent the business processes. Systems Analysis and Design 8 Figure 3 A sequence diagram shows how communication happens between the different entities within a system. The major entities in the scenario are the System and the clerk, Tour Driver, Tour and Tour Leader. The data, therefore, flows between these three entities. The first decision to be made was the sequence of the messages. The first messages first and the last messages going last in the system. Then the most difficult part is the identification of the communicating entities in the use case. There are only two, the system and the Clerk as shown previously. Clerk, therefore, adds tour, enters tour details into the system and selects both driver and the tour leader. On the other hand, the system gives the clerk tour details as entered by the clerk, it assigns the driver and authenticates the Systems Analysis and Design 9 driver codes. The system is designed to have communicated between all the entities and also shows the error codes as well. 3 3.1 Part 3 Evaluation CASE tools are the standard tools that are used in automated support for software engineering. The case tools, therefore, are any tool that is used in automating activities that are associated with software development which includes Web Development, e-commerce and any other form of software design. CASE is therefore used in the implementation of defect-free and high-quality software, which gives a disciplined methodology and help developers, testers and designers view the project tasks during the software development life cycle. In addition, CASE tools assist in many areas such as documentation of the design specifications which meet the reallife requirements. Also, the tools ensure that the customer remains a component of the process. In the project, the case tools have been used in the analysis, design, and testing of the system, the draw.io is the case tool that has been used to automate class diagrams, sequence diagram and communication diagrams. In a sequence diagram, for example, the case tool was useful in identifying the entities, and the messages that have been sent between the different scenarios. Case tools, therefore, improve productivity and the quality of the resulting system by assisting the developer during the design stage of the system. CASE tools can be categorized into planning, analysis and design case tools. Through the use of CASE Tools, the computer application of laborsaving and productivity enhancement is done, and the tools have been applied in different scenarios. The following are the reasons why Case tools were used during the project 1. It saves the resources that are required in software development 2. It helps in reducing errors during the design process Systems Analysis and Design 10 3. During the development stage, they enable easy detection and identification of bugs 4. Reduces the cost of maintaining the codes. 5. It improves cost savings during the project design 6. It gives high quality and consistent project documents and designs Therefore, for the project, CASE tools were applied in the development of the Sequence diagram, communication diagram and class diagram. In the project, CASE tools were used in the development of the following concepts 3.2 • Identifying classes and objects • Drawing the class diagram and Sequence diagrams • Drawing of the communication diagrams. Unified Modeling Language and how it supports the designer UML is a free specification language for the object modeling, it is used generally with a unified graphical interface that can be applied in the development of the abstract system. The UML is extendable and offers a profile for customization as well. It gives a way of visualizing a software program using diagrams and it has evolved to cover variety of software projects (de Marcos, Flores Morador and Javier, 2013). UML therefore improves the integration of the models such as structural models like class diagram and activity diagrams. Utilizing the UMLs help project managers to approve the compositional structure of the product (Siau and Cao, 2001). Most tools are non-proprietary and use general-purpose modeling language that applies standardized graphical notations that are applied in the creation of the abstract systems. The most prominent parts of a system that can be modeled include: Systems Analysis and Design 11 Functional Modeling: this showcases the how the system functions from the perspective of the user. This where Use Case modeling takes place. Object Modeling: This shows the substructure and structure of a system. This is where the attributes, operations, and associations of a system are defined. This point is where class diagrams are applied. Dynamic Models: dynamic modeling shows the internal behaviors of systems. The dynamic modeling includes communication diagrams and sequence diagrams. 3.3 Benefits of UML It helps in taking control of a system, it, therefore, guards the path to be taken next based on the criteria. UML also helps to improve business outcomes just the same way simulations help to improve communications and reduce complexity. Systems Analysis and Design 12 4 Bibliography Bazydło, G. and Adamski, M., 2016. Using UML behavior diagrams for graphical specification of programs for logic controllers. In Design of Reconfigurable Logic Controllers (pp. 131142). Springer, Cham. Chren, S., Buhnova, B., Macak, M., Daubner, L. and Rossi, B., 2019, May. Mistakes in UML diagrams: analysis of student projects in a software engineering course. In Proceedings of the 41st International Conference on Software Engineering: Software Engineering Education and Training (pp. 100-109). IEEE Press. de Marcos, L., Flores Morador, F. and Javier, J. (2013). Modeling with Plato: The Unified Modeling Language in a Cultural Context. SSRN Electronic Journal. Faria, J.P. and Paiva, A.C., 2016. A toolset for conformance testing against UML sequence diagrams based on event-driven colored Petri nets. International Journal on Software Tools for Technology Transfer, 18(3), pp.285-304. Jagtap, S., Gawde, V., Pawar, R., Shendge, S. and Avhad, P., 2016. Generate Test Cases From UML Use Case and State Chart Diagrams. International Research Journal of Engineering and Technology (IRJET), 3, pp.873-881. Karim, S., Liawatimena, S., Trisetyarso, A., Abbas, B.S. and Suparta, W., 2017, November. Automating functional and structural software size measurement based on XML structure of UML sequence diagram. In 2017 IEEE International Conference on Cybernetics and Computational Intelligence (CyberneticsCom) (pp. 24-28). IEEE. Lending, D. and May, J., 2019. Using activity diagrams to model systems analysis techniques: Teaching what we preach. Journal of Information Systems Education, 24(2), p.1. Siau, K. and Cao, Q. (2001). Unified Modeling Language. Journal of Database Management, 12(1), pp.26-34. ... Purchase answer to see full attachment