Search

Behavioral diagrams in Unified Modeling Language reflect the interaction between system components and give a comprehensive description and visualization of the system during the design phase. One of the most important behavioral diagrams is the sequence diagram which describes the chronological sequence of events between the components of the system. The process of extracting information and metrics from a sequence diagram is time-consuming so creating a special tool to help developers obtain information from the sequence diagram has become necessary because of the great advantages and ease it provides. This paper aims to build a tool that extracts information from the sequence diagram, creates a table that includes this information, and then calculates three categories of metrics related to the sequence diagram which are size, complexity, and level of detail. These categories include 15 metrics to give quantitative values that indicate software quality which is used to estimate the schedule, cost, effort, and other resources in the software development process. As a case study, the hotel reservation system is adopted and constructed as two versions of sequence diagrams for comparison purposes. The results showed a quantitative measurement of small and unnoticeable differences between the two diagrams.

Current railroad customs clearance systems are problematic in that the movement of trains is occasionally restricted for extended periods during inspections to verify cargo integrity at customs clearance. Consequently, significant human and material resources are consumed to obtain customs clearance to the destination, considering different processes exist for cross-border trade. Therefore, we developed a cross-border blockchain-based non-stop customs clearance (NSCC) system to address these delays and reduce resource consumption for cross-border trains. The integrity, stability, and traceability of blockchain technology are used to construct a stable and reliable customs clearance system to address these problems. The proposed method connects diverse trade and customs clearance agreements in a single blockchain network, which ensures integrity and minimal resource consumption, and includes railroads, freight vehicles, and transit stations in addition to the current customs clearance system. The integrity and confidentiality of customs clearance data are protected using sequence diagrams and the blockchain to strengthen the resilience of the NSCC process against attacks; the blockchain-based NSCC system structurally verifies the attack resilience based on matching sequences. The results confirm that the blockchain-based NSCC system is time- and cost-efficient compared with the current customs clearance system and offers improved attack resilience.

Software architecture is one of the most fundamental products in the process of software development in the areas of behavioral or non- behavioral features like availability or transformability change. There are different ways to evaluate software architecture one of which is the creation of application model. An executable model of software architecture is an official description of architecture which if used prior to the running of architecture, its final behavior and function will be observed and as a result possible problems could be elevated and promoted. In this study we aimed at availability evaluation in object- oriented style. To ensure the applicability of the style the UML diagrams, especially the sequence diagram, were used to exhibit the architectural behavior. In the later stages, as the UML diagram is inapplicable, the following operations were done. First, metric annotation is used to tag clichés. Then, the studied style diagram was transformed into an applicable one. Afterwards and following the design of petri, using CpnTools, the applicable model based on color petri net was evaluated. In this research the availability evaluation on an ATM for the N=5 users was tested and the results of evaluation showed that the higher the rate of availability (approximately %100) the higher is the rate of usability of the system when needed.

Abstract. The model of e-learning environment built on the basis of cyclic principles, consistency and innovation is being discussed. Its main components are the leadership, normative framework, educational, informational, technological, and physical space components. Each component in itself comprises a complex subsystem with a specific content, participants, objectives, and actions. Non-directional nature of the sequence diagram that represents the model reflects the possibility of formation of e-learning at university in any workflow. The presented e-learning environment model is universal. On the one hand, it gives the opportunity to create an educational institution e-learning environment for hybrid, distant or mobile types of e-learning. On the other hand, the model meets the needs of any educational institution and can be viewed upon as a basis for the implementation strategy of e-learning technologies.

The purpose of this research is to apply the application of reverse engineering to determine interaction patterns of the Sequence diagram that can be used by system analysts as a template for designing UML sequence diagrams. Sample applications from android are used as dataset for reverse engineering and pattern identification. The first step is collecting application datasets. The next stage is identifying the features and applications activity, reverse engineering to obtain a sequence diagram model, and then synthesize all of the models into an interaction pattern of sequence diagram. The final step is to test the patterns by implementing it in an application development case stud. The evaluation results concludes that interaction patterns of sequence diagram designs obtained in reverse engineering steps is able to be implemented in software development that contained similar features with the obtained features in this research.

This ability in fuzzy UML, practically leaves the customers and market’s need without response in this important and vital area. Here, the available sequence diagrams in fuzzy UML will map into fuzzy Petri net. However, the formal models ability will be added to the Semi-formal fuzzy UML. This formalization will add the automatic processing ability to the Semi-formal fuzzy UML. Further more, the other advantages of this mapping is: access to non-functional parameters such as reliability automatically to the considering systems, study the verification of the designed plan and also decrease the expenses because of satiety to make lab sample before its implementation. Using the fuzzy UML mapping into fuzzy Petri net in control, critical and real-time systems will be more applicable.

The basic requirements are formulated and the basic settlement dependences by calculation of a mode of loading for realization of process of dynamic stabilization are given. Results of use of the executed calculations are resulted at introduction of process of dynamic stabilization for manufacturing frictional disks. Recommendations for further use of dynamic stabilization are given at manufacturing details of mechanical engineering.

This ability in fuzzy UML, practically leaves the customers and market’s need without response in this important and vital area. Here, the available sequence diagrams in fuzzy UML will map into fuzzy Petri net. However, the formal models ability will be added to the Semi-formal fuzzy UML. This formalization will add the automatic processing ability to the Semi-formal fuzzy UML. Further more, the other advantages of this mapping is: access to non-functional parameters such as reliability automatically to the considering systems, study the verification of the designed plan and also decrease the expenses because of satiety to make lab sample before its implementation. Using the fuzzy UML mapping into fuzzy Petri net in control, critical and real-time systems will be more applicable.

El diagrama de secuencias es un esquema conceptual que permite representar el comportamiento de un sistema, para lo cual emplea la especificación de los objetos que se encuentran en un escenario y la secuencia de mensajes intercambiados entre ellos, con el fin de llevar a cabo una transacción del sistema. Existen diferentes enfoques que buscan la generación automática de modelos conceptuales, como el diagrama de secuencias. Algunos trabajos parten del lenguaje natural, pero generan diagramas diferentes al de secuencias o, si lo hacen igual, dejan de lado elementos como los fragmentos combinados, que describen ciertas condiciones lógicas en el sistema. Otros trabajos parten del código fuente, el cual se suele ubicar en una fase más avanzada del ciclo de vida del software. En este artículo se define un método, basado en reglas heurísticas, que permite identificar los elementos del diagrama de secuencias, incluyendo los fragmentos combinados, tomando como punto de partida los esquemas preconceptuales. Se realiza la implementación de las reglas en la herramienta AToM³ aplicándolas a un caso de estudio.Sequence diagram is a conceptual schema for representing behavior of a system. For performing such a task, it employs the object spec from a scenario and the sequence of messages exchanged among the objects. These elements describe a transaction of the system. Several approaches try the automated generation of conceptual models (like sequence diagram). Some of them use natural language as a starting point, but they are focused on other diagrams. Some others are focused on sequence diagram, but they do not obtain elements like combined fragments describing several logical constraints of the system. Other approaches use source code as a starting point, but source code can be related to an advanced phase of the software development life cycle. In this paper we define a method based on heuristic rules for obtaining automatically the elements of the sequence diagram (including combined fragments) from pre-conceptual schemas. These heuristic rules are implemented in the AToM³ tool and applied in a case study.

La Ingeniería inversa de software aparece como un proceso que ayuda al aseguramiento de la calidad y documentación de aplicaciones con deficiencias en los modelos de análisis y diseño. Además, ayuda en la disminución de costos y tiempos de mantenimiento. En la actualidad existen herramientas CASE y algunas propuestas de investigación que realizan el proceso de ingeniería inversa a diagramas UML, en especial a los diagramas de clases y secuencias. Algunas se encuentran en fases experimentales; otras se enfocan mucho más en el diagrama de clases que en el de secuencias. Un tercer grupo obtiene algunos elementos del diagrama de secuencias, pero no posee muchos de los elementos que hacen parte de la especificación de UML 2.0. En este artículo se propone un método que automatiza la conversión de código JAVA en diagrama de secuencias de UML 2.0, por medio de la aplicación de reglas de transformación que convierten los elementos del código en elementos del diagrama. Se presenta también un ejemplo de aplicación del método con un prototipo que lo emplea, el UNC-Inversor.Software reverse engineering seems to be the process for helping software quality assurance and documentation in applications with low-quality analysis and design models. It also helps for decreasing maintenance cost and time. Currently, some CASE tools and research proposals assist analysts to develop reverse engineering process with UML diagrams as a result (especially class and sequence diagram). Some of them have reached experimental phases. Some others are focused more on class diagram and less on sequence diagram. A third group of CASE tools and proposals obtains sequence diagram, but the resulting diagram lacks some of the elements of the UML 2.0 specification. In this paper, we propose a method for automating the conversion of JAVA code into UML 2.0 sequence diagram, by means of the application of transformation rules for converting code elements to the diagram elements. We also present an example of the method application through a prototype named UNC-Inversor.

When modeling systems and using UML concepts, a real system can be viewed in several ways. The RUP (Rational Unified Process) defines the "4 + 1 view": 1. Logical view (class diagram (CD), object diagram (OD), sequence diagram (SD), collaboration diagram (COD), state chart diagram (SCD), activity diagram (AD)), 2.Process view (use case diagram, CD, OD, SD, COD, SCD, AD), 3. Development view (package diagram, component diagram), 4. Physical view (deployment diagram), and 5. Use case view (use case diagram, OD, SD, COD, SCD, AD) which combines the four mentioned above. With sequence diagram constructs we are describing object behavior in scope of one use case and their interaction. Each object in system goes through a so called lifecycle (create, supplement object with data, use object, decommission object). The concept of the object lifecycle is used to understand and formalize the behavior of objects from creation to deletion. With help of sequence diagram concepts our paper will describe the way of interaction modeling between objects through lifeline of each of them, and their importance in software development.