IT System Use: Actors, Use Cases, Classes, And Visual Representations

List the expected outcomes of your design/system in terms of the:

a. Business and 
b. Users.
Quantify them (give in numbers or  percentages)

Actors and Use Cases

It is assumed that this user can interact with the system directly. User can picture an actor as an IT system use, taken as an example, Mr. XYZ or Mrs. ABC from data input. On-screen actors communicate to segments that user interaction of the time they make use of the IT system, such as the section of a registration process. Distinct user or actor can be associated with more than one use case of the information technology system. It is imperative for the IT system within which segment of a individual is performing. In accordance with that, it is very important to sign on to huge amount of IT subsystems within a particular segment, taken as an example, as a distinctive user or as a supervisor. In terms of each situation, access to the appropriate functionalities or use cases are granted. Actors is not considered as the integral part of the IT system but they are the one who request processes implemented within the system. Last but not least, as representatives the actors can be considered to be a piece of the business framework.

The use cases used within the design are ticket generation, information input, make payment, fine and ticket expiry checking. Use cases represent the links that happens among IT systems and the actors with the processing of business processes. A use case addresses to a segment of the benefit of the IT system and authorizes the user (visualized as a performing actor) to obtain this benefit. Almost anything, which users may wish to do with IT system, should be marked as accessible as a use case (or a partial segment of a use case). Functions that presnt in the IT system, however the functions that are not obtained by procedures regarding use cases, are not marked as accessible in terms of the users. In spite of the fact that the idea behind use cases is to represent interactions and communications, which mostly does not include collaboration, can similarly be visualized as use cases. For example, creating registration measurements would be a clump use case.

The customer actor is connected to the use cases through the association relationship. An association is a relationship between a performer and a use case. An association demonstrates that an on-screen actor can do a use case. A few on-screen actors at single use case suggest that each of the on-screen actor can carry out the use case on her or his own. In addition to that, it is also a fact that not all actors do the use case jointly. Among all the use cases, only two of the use cases will be connected to the user as system. This decision is made on the basis of simplifying the user interactivity with the system. When the queue of cars will be long, it will be highly essential that the use can park cars within minimum time and for that minimum interactivity time with the system is necessary factor. Through the exclude option, it has been showed that the system only needs consumer data as input in specific times. The include relationship represents the operations that are essential to carryout out the connected task. 

Classes and Objects

It mainly three classes such as customer, ticket and payment. An object can be considered as the individual, occasion, thing, screen, idea, or report material to the the IT system. Objects are those parts that have idea about the things (they have traits) and the objects carry out the processes through the use of methods. A class is a representation of queries and the queries are extracted from several viewpoints. It is just a blueprint based on which the objects are drawn or created. Classes provide framework to the main generating segments of a remonstration situated application.

Likenesses regularly exist between various classes. All the time at least two classes will have similar actoristics or potentially similar techniques. Since designer would prefer not to need to compose a similar code more than once, designer need a system that exploits these similitudes. Legacy is that instrument. Legacy models "is an" and "resembles" connections, empowering designer to reuse existing information and code effectively. At the point when An acquires from B, we say An is the subclass of B and B is the superclass of A. Besides, we say we have "unadulterated legacy" when A acquire every one of the traits and techniques for B. The UML displaying documentation for legacy is a line with a shut sharpened stone indicating from the subclass the superclass.  Now, there is a change in the system that is noticeable in the is that the ticket class has been divided into two sections instead of customer class. The reason behind this activity is that the customer type is defined based on the ticket they buy. In addition to that, the customer can change type as soon as the ticket type will be changed. Therefore, based on that it can be firmly said that the tickets are truly two types. The ticket class has two parts such as Season Ticket and Ordinary Ticket which as two different operations to check ticket validation.

Classes are commonly represented as rectangles that has three parts:

1. The top part contains the name of the class
2. The center part is saved regarding the attributes of the class
3. The methods of the class are showed in the base part or bottom part

The fundamental classes of the system model can be differentiated in an indifferentiable process. In order to make the design simple and easily understandable various operations has been assumed to e within the visualized operations or methods of the classes. Taken as an example, the fine calculation is assumed to be within the TicketExpiryCheck method. The class is complete readable and dynamic in nature. 

The communication between the objects of the classes demonstrated. It visualizes the flow of reason within the system framework in terms of a visual process, empowering designer both to report and make approval to the system rationale. In addition to that, the system system segments  are constantly made use of regarding both arrangement purposes and analysis. Sequence s are one of the the most conventional UML objects regarding dynamic visualizations that focuses on identifying the characteristics within system. Other dynamic visualizing mechanisms include correspondence outlining, association appraisal graphing, process ming, and scheduling. Use case s, simultaneously with class s and objective information s are most necessary plan level regarding present day Business Application enhancement.

Legacy and Subclasses

As the class and use case suggested,has been completed with only one actor. An Actor models a kind of pretended by a substance that communicates with the subject, however which is outside to the subject. On-screen actors may speak to parts played by human clients, outside equipment, or different subjects. Take note of that a performing actor does not really speak to a particular physical element but rather just a specific aspect of some substance that is significant to the determination of its related use cases.

Through this  operation is perfectly displayed. The sequence shows that the user will generate ticket that requires payment. After the payment is done the system provides the ticket. This method works for both the cases. Ticket price will be stored in the database as default value. The system will collect that and charge the price. The payment verification process will ensure that the payment is complete.

A convention scenario can be considered as a possible mechanism in which the system is made use of. The rationale of a sequence scenario may be a segment of a use case or maybe a alternate route. It might likewise be one whole go through a usage scenario. Taken as an example, the customer pays for the ticket and immediately the system starts accepting the customer as the reisted user and provide best services possible. The reason of a sequence scenario may similarly be a experience the reasons held within some of the use cases. Taken as an instance, a student get admission in the college, and after that quickly enlists in three classes. Sequence s can be utilized to analyze the reason of a highly method, capacity, or mechanism. One approach to consider sequence s, especially very point by point graphs, is as visual question code. An administration is adequately an abnormal state strategy, regularly one that can be summoned by a wide assortment of customers. This incorporates web-benefits and business exchanges actualized by an assortment of advancements.

The sequence s show that at the end of all the processes, the system shows the message that says ticket confirm. This message may vary between processes. In terms of etry to the park, after the ticket verification is successful, the system will show park the car in “this” section.  This sequence has been generated for showing the complete system flow but to show the working nature of the system and its working efficiency. 

Visual Representations

The visual representation of the activities carried out in whole system or a part of the system. The ticket generation processes has been showed. The activity has been completed using four components such as activity, edge, decision node and plane. Activity Edge is a dynamic class for the coordinated associations along which tokens or information objects stream between activity hubs. It incorporates control edges and question stream edges. The source and focus of an edge must be in an indistinguishable activity from the edge. Activity edge can have a protect - particular assessed at runtime to decide whether the edge can be navigated. The project must assess to valid for each token that is offered to go along the edge. The customer interacts with the system directly, Therefore, only two planes has been used such as customer and system. The activity shows how the customer response is handled by the system and how the customer provide input while systems asks for.

The first big black dot that can be seen is the initial node. The initial node is the beginning stage of an activity. An activity can have more than one introductory hub; for this situation a few streams begin toward the start of an activity. It is additionally conceivable that a activity has no underlying hub, yet is started by an occasion.

Every activity of the customer lead to another process until the system generate the ticket. The ‘make successful payment’ activity has been shown in short. It is actually an activity and a decision node testing whether the payment is successful or not. However, for the sake of simplicity and less complex design, use of two decisions nodes has been avoided.

An activity outwardly exhibits a progression of activities or stream of control in a framework like a flow or an information stream graph. Activity outlines are frequently utilized as a part of business process displaying. They can likewise depict the means in an use case graph. Exercises displayed can be consecutive and simultaneous. In both cases a activity outline will have a start and an end.

Al-alshuhai, A., & Siewe, F. (2015). An extension of the use case to model context-aware applications. In SAI Intelligent Systems Conference (IntelliSys), 2015 (pp. 884-888). IEEE.

Caniato, M., Vaccari, M., Visvanathan, C., & Zurbrugg, C. (2014). Using social network and stakeholder analysis to help evaluate infectious waste management: A step towards a holistic assessment. Waste Management, 34(5), 938-951.

Kumar, B. S., & Krishnamurthi, I. (2016). Improving User Participation in Requirement Elicitation and Analysis by Applying Gamification Using Architect’s Use Case . In Proceedings of the 3rd International Symposium on Big Data and Cloud Computing Challenges (ISBCC–16’) (pp. 471-482). Springer International Publishing.

Yue, T., Briand, L. C., & Labiche, Y. (2015). atoucan: An automated framework to derive UML analysis models from use case models. ACM Transactions on Software Engineering and Methodology (TOSEM), 24(3), 13.