China
Africa
Explore chapters and articles related to this topic
Object-Oriented Comodeling Methodology for Development of Domain Specific DEVS Models
Published in Gabriel A. Wainer, Pieter J. Mosterman, Discrete-Event Modeling and Simulation, 2018
The Unified Modeling Language (UML) is a standardized language for specifying, visualizing, and documenting the artifacts of an object-oriented system under development [9,10]. Note that UML is not a kind of modeling methodology, and it just provides a visual syntax that we can use to construct models. It simplifies the complex process of software design and presents the various views of a system as shown in Figure 7.5, making a blueprint for construction [11]. Objects contain information and may perform functions, and UML models have static structure and dynamic behavior. The former relates to the type of objects and relationship among them and the latter denotes functions of the systems. This section describes only three diagrams among the several diagrams of UML that are shown in Figure 7.5 and are used for modeling an object. The 4 + 1 view is a way of looking at the overall architecture of a system, and UML provides excellent support for each of the 4 + 1 views. The diagrams, which are used in this chapter, are the use case diagram, class diagram, and sequence diagram that is a subdiagram of interaction diagram.
Real-Time Grid Management
Published in Stuart Borlase, Smart Grids, 2018
Stuart Borlase, Jiyuan Fan, Xiaoming Feng, Jay Giri, Douglas Wilson, Gerald R. Gray, Zhenyu (Henry) Huang, Walter Sattinger, Bo Yang, Bo Zeng, Stuart Borlase, Jiyuan Fan, Jay Giri, Zhenyu (Henry) Huang, Rajat Majumder, Rui Menezes de Moraes, Thomas Morris, Reynaldo Nuqui, Manu Parashar, Walter Sattinger, Tim Taylor, Jean-Charles Tournier
Exploring the service-oriented architecture paradigm further, consider the messaging sequence diagram in Figure 5.37. A sequence diagram is a standard unified modeling language diagram that is read from left-to-right, and top-to-bottom. This diagram illustrates how the messages to support the creation of DER groups could be initiated by any other system, in this case, referred to generically as the “group forming entity.” The “group acknowledging entity” is most likely the DERMS. Optionally, at the top right of the diagram, this notation reflects that DER groups could be created locally. It is the loosely coupled nature of web services that supports the architectural paradigm that the DERMS could physically be deployed over a variety of locations and architectures.
Generation of Use Case UML Diagram from User Requirement Specifications
Published in Ibrahiem M. M. El Emary, Anna Brzozowska, Shaping the Future of ICT, 2017
Wahiba Ben Abdessalem, Eman H. Alkhammash
A use case diagram is a UML diagram used to capture functional requirements and model the dynamic aspects of the system. Use cases play important roles in the early stages of the development of the system. A use case diagram represents an abstract view of the systems and isolates details to better understand the portion of the system of concern (OMG, 2016b). UML use case diagrams consist of four main elements, which are system, actors, use cases, and relations. The actors, depicted by stickman icon, represent system/people that interact with the modeled system. The use cases, depicted by named ellipses, represent main functionalities provided by the system). The relations (association, dependency, and generalization) are used to indicate interactions between components. An association relationship is used between actors and uses cases. Generalization can be used between actors when they have the same roles. The common relationships used between use cases are generalization and dependencies. Generalization is used to show a parent–child relationship between use cases; thus it is used when two or more use cases have similar behaviors. Generalization is shown as a directed arrow with a triangle arrowhead. The child use case is connected at the base of the arrow, as shown in Figure 16.4. The two use cases PIN and Fingerprint are a “child” of the Customer Authentication use case.
An Enhanced Entity Model for Converting Relational to Non-Relational Documents in Hospital Management System Based on Cloud Computing
Published in IETE Technical Review, 2022
A. Samydurai, K. Revathi, L. Karthikeyan, B. Vanathi, K. Devi
This section provides the entire details of the HMS that are designed by means of a Mongo DB 5. Figure 2 depicts the class diagram of HMS in MongoDB 5. MongoDB has always supported ACID (atomicity, consistency, independence, and durability) transactions in a single document, and when leveraging the document model appropriately, many applications don’t need ACID guarantees across multiple documents. The class diagram refers to a unified modeling language (UML) which clearly depicts the system structure by revealing the system contents, their relationship among the objects, as well as the attributes. In addition to this, the class diagram is employed in describing the databases. For maintaining the recent data, the RAM is used by MongoDB. Therefore, on every occasion, the query generates the index and the data collections that fit in the RAM and the queries are made to run. The classes signify the collections and class names in the top part of each class. Each collection constitutes the primary field represented by (#). The foreign keys from another collection and the fields without any sign are FK. The line among the two collections is (*). The normal fields are denoted by (+). The detailed description regarding the information page of the HMS using Mongo DB is summarized in the following section.
Modeling, analysis and verification of real-time resource access control protocols: a formal approach
Published in International Journal of Computers and Applications, 2018
Rumpa Hazra, Shouvik Dey, Jayashree Singha
RTS are specially designed to relate to the concurrent behavior of the real world. Concurrency may lead to resource contention and blocking, which are also important issues to be handled in an RTS. Proper scheduling of the tasks sharing common physical and logical resources is essential to maintain perfect synchronization among tasks. Thus, use of an appropriate modeling language for RTS has become important. Finite-state machines, Petri Nets, and Timed CSP are among the many techniques that have been used to specify and design RTS for years. Unified Modeling Language (UML) is a latest industry-standard graphical modeling language. Its semi-formal notations can be easily used to model and design software systems. Different behavioral aspects of RTS can be expressed properly using the automated tools of UML. For example, scheduling of real-time tasks with strict deadlines can be suitably expressed using UML.
A novel approach to measuring enterprise procurement decision process: an information distance perspective
Published in Enterprise Information Systems, 2020
Xiong Li, Xiaodong Zhao, Wei Pu
UML is mainly used in conceptual modelling by its corresponding diagrams to describe the physical structure of a system, entity and multi-entity behaviours (Li, Pu, and Zhao 2019). In UML, activity diagram is one of important behavioural types (Bashir et al. 2016). UML activity diagram is a semi-formal language with the following basic graphical notations: initial node and activity final node, activity, flow/edge, fork and join, decision and merge, partition/swim lane. This diagram is more expressive for modelling data flows inside information system (Hassen, Turki, and Gargouri 2016). Rodríguez et al. (2011) presented an extension of UML 2.0 activity diagrams which allowed security requirements to be specified in business processes.