China
Africa
Explore chapters and articles related to this topic
FSM Library
Published in Miroslav Popovic, Communication Protocol Engineering, 2018
An object diagram, such as the one shown in Figure 6.18, helps us to better understand the structural relationships among objects. A collaboration diagram (Figure 6.2) shows the logical communication of automata instances over their virtual, peer-to-peer connections. On a more detailed level of abstraction, we see that the real communication is governed by the FSM system, which is the owner of the mailboxes (not shown in the figure) used for storing the messages, e.g., StandardMessage (shown in Figure 6.18). This particular message shown in one snapshot of object collaboration is the first message sent from instance_1 to instance_2. The message code is IDLE_MSG, and the value of the message sequence parameter is 1.
Design
Published in Miroslav Popovic, Communication Protocol Engineering, 2018
The means of defining the static structure of the system in UML are class diagrams and object diagrams. A class diagram shows the design classes and the static relations (dependencies, associations, and generalizations) among them without any respect to time. It shows important details about classes, such as their members, fields and functions, and furthermore their types, visibility, and so on. The object diagram is similar to the class diagram except that it shows the system frozen at a certain moment of time. Typically, the object diagram will show system objects (class instances) with the characteristic and important values of certain field members.
A Distributed and Safe Weighted Clustering Algorithm
Published in Amine Dahane, Nasr-Eddine Berrached, Mobile, Wireless and Sensor Networks, 2019
Amine Dahane, Nasr-Eddine Berrached
A view is composed of one or several diagrams. There are two types of views: Static viewsDynamic views – The use case diagram: It shows the structure of the necessary features for system users. It is normally used during the steps of capturing functional and technical requirements (see Fig. 5.11). – The class diagram: It is surely one of the most important diagrams in object-oriented development. On the functional side, this graph is intended to develop the structure of the entities manipulated by users. At designing side, the class diagram shows the structure of object-oriented code (see Fig. 5.12). – The sequence diagram: It represents the exchange of messages between objects, in the context of a particular operation of the system, (see Figs. 5.13, 5.14, and 5.15). – The activity diagram: It represents the rules of sequence of activities and actions in the system. It can be treated as an algorithm but schematically, it addresses the dynamic view of a system.– The object diagram: An object diagram shows a set of objects and their relationships. It represents static snapshots of instances of the things found in class diagrams. This diagram addresses the static design view of a system as do class diagrams 47 (see Fig. 5.16).
Sensitivity analysis of waste resin agitation and extraction in a mock-up test
Published in Journal of Nuclear Science and Technology, 2022
Naoyuki Ishida, Satoshi Yokoyama, Osamu Takamura
Figure 6 shows an analysis object diagram. The region for the analysis was the surface of the water. In order to reduce the calculation time by suppressing the number of analysis meshes, the structures of the eductor pipe and support fittings, etc. which have little effect on the flow in the tank were ignored, and only the suction pipe of the ejector and the body part of the eductors were placed in the tank as structures to be considered. Polyhedral meshes were used. Figure 7 shows an analysis mesh diagram. The fluid region was divided with a maximum mesh size of 30 mm and minimum size of 5 mm near the walls of the tank and the eductors. The total number of meshes was about 940,000. The pressure boundary was set at the water surface. The water surface level changed during the test, but the analysis set it to constant height of 2.5 m within the range observed in the test because the calculation time was enormous and not realistic when the change of the water level was treated. The water level was high enough that the resin was not released from the boundary.
Integrated product-process modelling for platform-based co-development
Published in International Journal of Production Research, 2020
Thomas Ditlev Brunoe, Ann-Louise Andersen, Daniel G.H. Sorensen, Kjeld Nielsen, Mads Bejlegaard
Based on this example, we can introduce a component type named ‘splined shaft’, illustrated in the object diagram in Figure 3. This diagram illustrates the objects that represent the generic component type ‘splined shaft’ in a company-specific ontology, along with the definitions of characteristics that are needed to describe the component type and determine the manufacturability in various processes. Note that the characteristic definitions describe only the name of the characteristics and the units to be used. Figure 4 also shows an object diagram, however, representing a company-specific ontology for processes, including four different process types; those needed for manufacturing the splined shaft. Again, the capabilities are defined stating only the name of the capability and the unit used to describe it. Hence, Figures 3 and 4 show the product domain and the process domain respectively.
On defining a model driven architecture for an enterprise e-health system
Published in Enterprise Information Systems, 2018
Blagoj Atanasovski, Milos Bogdanovic, Goran Velinov, Leonid Stoimenov, Aleksandar S. Dimovski, Bojana Koteska, Dragan Jankovic, Irena Skrceska, Margita Kon-Popovska, Boro Jakimovski
We give an example only on the part of the formal description of the ”Create Referral” process due to the verbosity required to fully describe the entire process. In the original workflow-diagram in Figure 3 after the ”Select Referral Type” step, based on the user selection, the process continues either to the ”Get available Appointment Times” step (if the user selected a Regular Referal type), or to the ”Populate Referral Details” step. This is modeled in the object diagram in Figure 7 with the transitions dictionary instance and the argumentMapping Table instance. The transitions contain an entry for the SelectReferralType key, an array of two OutgoingTransitions.