Journal articles: 'UML diagram'

1

Oliveira, Rodrigo Diego de. "Análise do uso da cor no Diagrama de Classes da Linguagem Unificada de Modelagem (UML) | Analysis of the use of color in the Unified Modeling Language Class Diagram (UML)." InfoDesign - Revista Brasileira de Design da Informação 17, no. 1 (2020): 116–30. http://dx.doi.org/10.51358/id.v17i1.783.

Full text

Abstract:

O uso da cor em diagramas na Engenharia de Software não é novidade, em especial na Linguagem Unificada de Modelagem (UML), que consiste em um conjunto de quinze diagramas utilizados para documentar e especificar a complexidade de um software. Porém, a aplicação da cor muitas vezes é feita de forma aleatória ficando a cargo da subjetividade do projetista ou dos softwares utilizados para o desenho destes diagramas. O presente artigo aborda o uso das cores no diagrama de classes da UML segundo o modelo proposto por Coad, Lefebvre e De Luca (1999), que aplica a cor a partir de uma prática profissional utilizando post-its. O objetivo deste artigo é realizar uma análise descritiva da aplicação da cor para demonstrar a importância desta não só para melhorar a estética, mas também como símbolo, facilitando a leitura, compreensão e o estabelecimento de relações no diagrama de classes.*****The use of color in diagrams in Software Engineering is not new, especially in the Unified Modeling Language (UML), which consists of a set of fifteen diagrams used to document and specify the complexity of software. However, the application of color is often done in a random way, being in charge of the subjectivity of the designer or the software used to design these diagrams. This paper discusses the use of colors in the UML class diagram according to the model proposed by Coad, Lefebvre and De Luca (1999), who apply color from a professional practice using post-its. The purpose of this article is to perform a descriptive analysis of the application of color to demonstrate the importance of this not only to improve aesthetics but also as a symbol, facilitating reading, understanding and establishing relationships in the class diagram.

APA, Harvard, Vancouver, ISO, and other styles

2

Kambow, Lavleen. "Transformation of UML Class Diagram to UML Sequence Diagram." International Journal of Applied Information Systems 2, no. 9 (2012): 19–22. http://dx.doi.org/10.5120/ijais12-450413.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Kulkarni, Dr R. N., and C. K. Srinivasa. "Novel approach to transform UML Sequence diagram to Activity diagram." Journal of University of Shanghai for Science and Technology 23, no. 07 (2021): 1247–55. http://dx.doi.org/10.51201/jusst/21/07300.

Full text

Abstract:

Unified Modelling Language (UML) is currently accepted as a defacto standard language for modeling the software in the software industry. It will allow to implement object oriented concepts to model the software system. It provides a complete pictographic representation of software. Broadly these UML diagrams are classified into two groups viz. Structural diagrams and Behavioral diagrams. The sequence diagrams and Activity diagrams belongs to the second group i.e. behavioral diagrams. The sequence diagram represents the sequence of messages flowing from one object to another and activity diagram represents the flow of activities one after the other in a system. In this paper, we are proposing an automated tool which transforms the sequence diagram (which is represented in the table format) into activity diagram. The sequence diagram which is represented in the three column table called sequence table comprises various components of sequence diagram like objects, interactions, messages, alternations, iterations, loops, etc. The proposed tool reads the sequence table and converts the entire table components into the equivalent Activity table. Further the tool reads the activity table and then transforms to its equivalent activity diagram.

APA, Harvard, Vancouver, ISO, and other styles

4

Singh, Gurpreet, and Rasbir Singh. "Generation of test cases using UML models." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 13, no. 7 (2014): 4671–74. http://dx.doi.org/10.24297/ijct.v13i7.2511.

Full text

Abstract:

Software Testing plays an important role in Software development because it can minimize the development cost. UML is widely used in the software development, there consists of the designing and coding of the software. Designing phase is done with the help of the UML models, which consists of the sequence diagrams, activity diagrams, use case diagrams, state chart diagrams etc. After designing of the system, the next task is coding. Since the software development is time and human resource consuming, the reduction of consumption is done with the help of the code generation automatically. This work mainly focus on the UML sequence diagram and state chart diagram as the model. We Propose a Technique for Test Case Generation using UML Models. UML models give a lot of Â information that should not be ignored in testing. An innovative approach of generating test cases from the combination of UML design diagrams has been discussed in this paper. Present work used an approach where sequence diagram and state chart diagram has been used to generate test cases. The test cases thus generated are suitable for dynamic testing of system.

APA, Harvard, Vancouver, ISO, and other styles

5

Yusufu, Munina, Hai Jun Zhang, Gulina Yusufu, Zhan Dong Liu, Pen Cheng, and Dilidaer Dilisati. "Modeling and Analysis of Complex System with UML: A Case Study." Applied Mechanics and Materials 513-517 (February 2014): 1346–51. http://dx.doi.org/10.4028/www.scientific.net/amm.513-517.1346.

Full text

Abstract:

The Unified Modeling Language - UML - is the most used specification language, and the way the world models not only application structure, behavior, and architecture, but also business process and data structure. In this paper, we aim to demonstrate a system development methodology by generating the UML diagrams from the requirements of the Automatic Banking Machine (ABM) System and discuss their relationships, differences and suitability. The high-level requirements of the system are specified by using use-case diagram, activity diagram, state chart diagram, collaboration diagram, sequence diagram, and component diagram, and the low-level requirements of each component using class diagrams. We briefly introduce each diagram, their usage, their advantages and some limitations, and then we discuss the relationships and differences between two or more diagrams, and suitability for modeling the different parts of the system.

APA, Harvard, Vancouver, ISO, and other styles

6

Z, Sayf Hussain, and Suryaa V S. "AIRBNB SOFTWARE ARCHITECTURE MODELING USING UML EXTENSIONS." International Research Journal of Computer Science 8, no. 3 (2021): 53–61. http://dx.doi.org/10.26562/irjcs.2021.v0803.003.

Full text

Abstract:

Airbnb is a California based company that operates an online marketplace for lodging and homestays for vacation rentals, and tourism activities. Modeling a prototype of the application with all the integral features intact would help us understand the core working and success of the company. The Unified Modeling Language (UML) is a language for the specification, visualization and documentation of object-oriented software systems. In order to understand the features of the miniature Airbnb, we try to model the system using UML diagrams. In this study, the proposed extension to UML covers aspects of use case diagram, sequence diagram, activity diagram and class diagram of the miniature Airbnb model at various levels and perspectives.

APA, Harvard, Vancouver, ISO, and other styles

7

Modi, Salisu, Hanan Abdulrahman Taher, and Hoger Mahmud. "A Tool to Automate Student UML diagram Evaluation." Academic Journal of Nawroz University 10, no. 2 (2021): 189–98. http://dx.doi.org/10.25007/ajnu.v10n2a1035.

Full text

Abstract:

Unified modelling language (UML) is the accepted standard and modelling language for modeling in software development process. UML is widely used by most course tutors in teaching modules of software engineering and system analysis and design. Students taking such courses do submit assignments with UML diagrams such as use case, class, sequence, activity and so on. Different versions of such diagrams produced by the students for a given problem have to be assessed by the course tutor which is a challenging and time-consuming task. This paper presents a java-based tool which is developed based on a simple yet effective algorithm developed by the authors that will read student and tutors solution diagrams as inputs and evaluate and grade the diagrams automatically. The output of the tool is the score of the student diagram in respect of lecturer’s final solution. The output is presented in two feedback files, one containing students’ score for the lecturers and the other to be send to the student to note the areas that were incorrect. The tool has been tested and evaluated using a simple and assumed UML class diagram. The result shows that the tool functions effectively and can produce detail feedbacks for both students and tutors. The outcome of this paper contributes towards automating UML diagram evaluations.

APA, Harvard, Vancouver, ISO, and other styles

8

Mohamed, Sherif Magdy. "Enhanced UML Methodology with New Hybrid Diagrams: An ATM Application." Journal of Education and Vocational Research 4, no. 3 (2013): 60–68. http://dx.doi.org/10.22610/jevr.v4i3.101.

Full text

Abstract:

Object oriented proved to be the most important software engineering tools. The main reason behind the importance is that, Object Oriented covers the most powerful programming languages such as Java and C++. UML is a modeling language which is a part of object oriented and it was created to provide the software development industry with analysis and design techniques based on some diagrams. The most common UML diagrams in use are Class and Activity diagram. To implement any system using object oriented UML, the programmer needs at least two or three diagrams beside the Use Case diagram in order to understand a full picture of the system. There is no diagram which can show the full picture of the system. In this research, new methodology called â€œTouch and Goâ€ has been generated by the researchers to implement the system. In this methodology, analysis and design are merged in one stage called Touch. Implementation and testing stage are merged in one stage called Go. The Class and Activity diagram are merged to introduce new integrated diagram called Enhanced Class Activity (ECA) diagram and the normal Activity diagram will be modified and improved as Activity Remarked Class (ARC) diagram. Analytical analysis of the new methodology is implemented in ATM machine system which can be later implemented using Java language or any other Object Oriented language. A powerful system like ATM is chosen to apply the new technique and it has been shown clearly how the methodology is working perfectly with such system. This study helps to reduce the number of diagrams that are being used to implement the system, reducing total time of implementation and making the coding stage easier by using only few numbers of diagrams.

APA, Harvard, Vancouver, ISO, and other styles

9

ZHANG, PENGCHENG, HENRY MUCCINI, YUELONG ZHU, and BIXIN LI. "MODEL AND VERIFICATION OF WS-CDL BASED ON UML DIAGRAMS." International Journal of Software Engineering and Knowledge Engineering 20, no. 08 (2010): 1119–49. http://dx.doi.org/10.1142/s0218194010005092.

Full text

Abstract:

The Web Services Choreography Description Language (WS-CDL) is a specification developed by the W3C and can be viewed as a blueprint for the development of end-point services. Consequently, it is worth providing a systematic approach for its modeling, analysis and verification. The Unified Modeling Language (UML) is an industry standard for modeling. Applying UML to model WS-CDL is obviously a promising solution to bring together academics and practitioners through a unique standard language. In this paper, we propose to use different UML diagrams to model WS-CDL. UML Component Diagram is used to model the underlying structure of WS-CDL. UML Sequence Diagram is utilized to model the activities in WS-CDL. UML State Machine Diagram is utilized to model the behaviors of each role participating in a WS-CDL specification. We then enrich the UML State Machine Diagram with data by the use of UML Class Diagram. Given the UML specification of WS-CDL, we then provide a systematic way of formally analyzing and verifying WS-CDL against desired properties. Some experiments show that our approach can verify structural, behavioral and data properties in a middle-scale data-enriched WS-CDL specification.

APA, Harvard, Vancouver, ISO, and other styles

10

Sejans, Janis, and Oksana Nikiforova. "Problems and Perspectives of Code Generation from UML Class Diagram." Scientific Journal of Riga Technical University. Computer Sciences 44, no. 1 (2011): 75–84. http://dx.doi.org/10.2478/v10143-011-0024-3.

Full text

Abstract:

Problems and Perspectives of Code Generation from UML Class Diagram As a result of increasing technological diversity, more attention is being focused on model driven architecture (MDA), and its standard - Unified Modeling Language (UML). UML class diagrams require correct diagram notation mapping to target programming language syntax under the framework of MDA. Currently there are plenty of CASE tools which claim that they are able to generate the source code from UML models. Therefore by combining the knowledge of a programming language, syntax rules and UML class diagram notation semantic, an experimental model for stressing the code generator can be produced, thus allowing comparison of quality of the transformation result. This paper describes a creation of such experimental models.

APA, Harvard, Vancouver, ISO, and other styles

11

Galapov, Arthur, and Oksana Nikiforova. "UML Diagram Layouting: the State of the Art." Scientific Journal of Riga Technical University. Computer Sciences 44, no. 1 (2011): 101–8. http://dx.doi.org/10.2478/v10143-011-0027-0.

Full text

Abstract:

UML Diagram Layouting: the State of the ArtThe usual aim of the modern computer-aided system modelling is to improve a connection between software model and code components. Therefore, the task of a diagram import/export becomes very important during software development. Layouting of diagrams after importation from another tool and application plays the main role. Authors of this paper describe some concepts, which are currently being considered in the area of diagram layouting and indicate several problems and their potential solutions for use in the development of CASE tools.

APA, Harvard, Vancouver, ISO, and other styles

12

Mahmud, Umar. "UML based Model of a Context Aware System." International Journal of Advanced Pervasive and Ubiquitous Computing 7, no. 1 (2015): 1–16. http://dx.doi.org/10.4018/ijapuc.2015010101.

Full text

Abstract:

Context Awareness is the mechanism through which systems can adapt to the needs of a user by monitoring the context. Context includes environment, spatial, temporal, etc information that is used to infer the current activity. UML is used to design a context aware system. The context aware system is viewed as an Object Oriented software product. The UML model is generated through ArgoUML, a free UML modelling tool. The Use Case Diagram, the Sequence Diagrams and the Class Diagram are modelled using this tool. The Class Diagram is subjected to CK metrics to identify the strengths and weaknesses of the design. The measurements show that the proposed model is within the recommended range.

APA, Harvard, Vancouver, ISO, and other styles

13

Balaban, Mira, Azzam Maraee, and Arnon Sturm. "Management of Correctness Problems in UML Class Diagrams Towards a Pattern-Based Approach." International Journal of Information System Modeling and Design 1, no. 4 (2010): 24–47. http://dx.doi.org/10.4018/jismd.2010100102.

Full text

Abstract:

UML is now widely accepted as the standard modeling language for software construction. The Class Diagram is its core view, having well formed semantics and providing the backbone for any modeling effort. Class diagrams are widely used for purposes such as software specification, database and ontology engineering, meta-modeling, and model transformation. The central role played by class diagrams emphasizes the need for strengthening UML modeling tools with features such as recognition of erroneous models and the detection of errors’ sources. Correctness of UML class diagrams refers to the capability of a diagram to denote a finite but not empty reality. This is a natural, unquestionable requirement. Nevertheless, incorrect diagrams are often designed, due to the interaction of contradicting constraints and the limitations of current tools. In this paper, the authors clarify the notion of class diagram correctness, discuss various approaches for detecting correctness problems, and propose a pattern-based approach for identifying situations in which correctness problems occur, and for providing explanations and repair advices.

APA, Harvard, Vancouver, ISO, and other styles

14

Shcherban, Sergei, Peng Liang, Zengyang Li, and Chen Yang. "Multiclass Classification of UML Diagrams from Images Using Deep Learning." International Journal of Software Engineering and Knowledge Engineering 31, no. 11n12 (2021): 1683–98. http://dx.doi.org/10.1142/s0218194021400179.

Full text

Abstract:

Unified Modeling Language (UML) diagrams are a recognized standard modeling language for representing design of software systems. For academic research, large cases containing UML diagrams are needed. One of the challenges in collecting such datasets is automatically determining whether an image is a UML diagram or not and what type of UML diagram an image contains. In this work, we collected UML diagrams from open datasets and manually labeled them into 10 types of UML diagrams (i.e. class diagrams, activity diagrams, use case diagrams, sequence diagrams, communication diagrams, component diagrams, deployment diagrams, object diagrams, package diagrams, and state machine diagrams) and non-UML images. We evaluated the performance of seven popular neural network architectures using transfer learning on the dataset of 4706 images, including 700 class diagrams, 454 activity diagrams, 651 use case diagrams, 706 sequence diagrams, 204 communication diagrams, 208 component diagrams, 287 deployment diagrams, 207 object diagrams, 246 package diagrams, 323 state machine diagrams, and 720 non-UML images, respectively. We also proposed our neural network architecture for multiclass classification of UML diagrams. The experiment results show that Xception achieved the best performance amongst the algorithms we evaluated with a precision of 93.03%, a recall of 92.44%, and an F1-score of 92.73%. Moreover, it is possible to develop small and almost the same efficient neural network architectures, that our proposed architecture has the least parameters (around 2.4 millions) and spends the least time per image (0.0135[Formula: see text]s per image using graphics processing unit) for classifying UML diagrams with a precision of 91.25%, a recall of 90.34%, and an F1-score of 90.79%.

APA, Harvard, Vancouver, ISO, and other styles

15

Kaliappan, Vasanthi, and Norhayati Mohd Ali. "Improving Consistency of UML Diagrams and Its Implementation Using Reverse Engineering Approach." Bulletin of Electrical Engineering and Informatics 7, no. 4 (2018): 665–72. http://dx.doi.org/10.11591/eei.v7i4.1358.

Full text

Abstract:

Software development deals with various changes and evolution that cannot be avoided due to the development processes which are vastly incremental and iterative. In Model Driven Engineering, inconsistency between model and its implementation has huge impact on the software development process in terms of added cost, time and effort. The later the inconsistencies are found, it could add more cost to the software project. Thus, this paper aims to describe the development of a tool that could improve the consistency between Unified Modeling Language (UML) design models and its C# implementation using reverse engineering approach. A list of consistency rules is defined to check vertical and horizontal consistencies between structural (class diagram) and behavioral (use case diagram and sequence diagram) UML diagrams against the implemented C# source code. The inconsistencies found between UML diagrams and source code are presented in a textual description and visualized in a tree view structure.

APA, Harvard, Vancouver, ISO, and other styles

16

Dobing, Brian, and Jeffrey Parsons. "Dimensions of UML Diagram Use." Journal of Database Management 19, no. 1 (2008): 1–18. http://dx.doi.org/10.4018/jdm.2008010101.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

XU, DIANXIANG, WEIFENG XU, and W. ERIC WONG. "TESTING ASPECT-ORIENTED PROGRAMS WITH UML DESIGN MODELS." International Journal of Software Engineering and Knowledge Engineering 18, no. 03 (2008): 413–37. http://dx.doi.org/10.1142/s0218194008003672.

Full text

Abstract:

The new constructs in aspect-oriented programming bring new types of programming faults with respect to crosscutting concerns, such as incorrect pointcuts and advice. This paper presents a UML-based approach to testing whether or not an aspect-oriented program conforms to its expected crosscutting behavior. We explore aspect-oriented UML design models to derive tests for exercising interactions between aspects and classes. Each aspect-oriented model consists of class diagrams, aspect diagrams, and sequence diagrams. For a method under test, we weave the sequence diagrams of the advice on the method into the method's sequence diagram. Based on the woven sequence diagram and class/aspect diagrams, we then generate an AOF (Aspect-Object Flow) tree by applying coverage criteria such as condition coverage, polymorphic coverage, and loop coverage to woven sequence diagrams. In the AOF tree, each path from the root to a leaf is an abstract message sequence, indicating a template of test cases. A concrete test case is obtained by creating objects that satisfy the collective constraints in the template. Our empirical study shows that the model-based testing approach is capable of revealing several types of aspect-specific faults, including incorrect advice type, incorrect (weaker or stronger) pointcut strengths, and incorrect aspect precedence.

APA, Harvard, Vancouver, ISO, and other styles

18

Koç, Hatice, Ali Mert Erdoğan, Yousef Barjakly, and Serhat Peker. "UML Diagrams in Software Engineering Research: A Systematic Literature Review." Proceedings 74, no. 1 (2021): 13. http://dx.doi.org/10.3390/proceedings2021074013.

Full text

Abstract:

Software engineering is a discipline utilizing Unified Modelling Language (UML) diagrams, which are accepted as a standard to depict object-oriented design models. UML diagrams make it easier to identify the requirements and scopes of systems and applications by providing visual models. In this manner, this study aims to systematically review the literature on UML diagram utilization in software engineering research. A comprehensive review was conducted over the last two decades, spanning from 2000 to 2019. Among several papers, 128 were selected and examined. The main findings showed that UML diagrams were mostly used for the purpose of design and modeling, and class diagrams were the most commonly used ones.

APA, Harvard, Vancouver, ISO, and other styles

19

Khaldi, Maha, and Mohamed Erradi. "Design and Development of an e-Learning Project Management System: Modelling and Prototyping." International Journal of Emerging Technologies in Learning (iJET) 15, no. 19 (2020): 95. http://dx.doi.org/10.3991/ijet.v15i19.14595.

Full text

Abstract:

In this work, based on the results obtained concerning the analysis and the needs of our project which concerns the design and development of an e-Learning project management system, we present the modeling stage with UML. Based on one hand, on two diagrams: class diagram and use case diagram, for static modeling and on the other hand, based on three diagrams: activity diagram, sequence diagram, diagram transition state for dynamic modeling. Finally, we offer examples of models for our project.

APA, Harvard, Vancouver, ISO, and other styles

20

Yasin, Verdi. "Tools Rekayasa Perangkat Lunak dalam Membuat Pemodelan Desain Menggunakan Unified Modeling Language (UML)." TRIDHARMADIMAS: Jurnal Pengabdian Kepada Masyarakat Jayakarta 1, no. 2 (2021): 139. http://dx.doi.org/10.52362/tridharmadimas.v1i2.666.

Full text

Abstract:

Pengembangan Rekayasa Perangkat Lunak berorientasi Objek, saat ini menggunakan tools pemodelan desain yang sesuai dengan model perancangan aplikasi sistem berorientasi objek. Dalam membangun suatu aplikasi sistem berorientasi objek atau berorientasi langsung dengan para pengguna (Users), maka tools yang tepat untuk di gunakan sebagai tools perancangan aplikasi sistem berorientasi objek yang dapat menggambarkan model proses (blueprint) dari suatu Rekayasa Perangkat Lunak Berorientasi Objek ialah Unified Modeling Language (UML). Unified Modelling Language (UML) adalah suatu metode dalam pemodelan secara visual yang digunakan sebagai sarana perancangan sistem berorientasi objek. Awal mulanya, UML diciptakan oleh Object Management Group dengan versi awal 1.0 pada bulan Januari 1997 [13]. Pada September 1997 lahirlah Unified Modeling Language (UML) versi 1.1 dengan 8 buah diagram, Pada tahun 1999 lahirlah Unified Modeling Language (UML) versi 1.3, menjadi 9 buah diagram, dengan penambahan “Business use case Diagram”, Pada bulan Mei 2001 lahirlah Unified Modeling Language (UML) versi 1.4, menjadi 10 buah diagram, dengan penambahan “Object Diagram”, Pada tahun 2002 lahirlah Unified Modeling Language (UML) versi 2.0, menjadi 13 buah diagram, dengan penambahan menjadi 13 buah diagram [1]-[3]. Model diagram proses yang dapat di kembangkan atau dibangun menggunakan Unified Modeling Language (UML) ialah Use Case Diagram, Business Use Case Diagram, Activity Diagram, Sequence Diagram, Object Diagram, Class Diagram, StateChart Diagram, Collaboration Diagram, Component Diagram, Deployment Diagram, Composite Structure Diagram, Interaction Overview Diagram, Package Diagram, Timing Diagram. Unified Modeling Language (UML) diharapkan mampu mempermudah pengembangan perangkat lunak serta memenuhi semua kebutuhan pengguna dengan efektif, lengkap, dan tepat. Hal itu termasuk faktor-faktor scalability, robustness, security. Adapun tujuan dan fungsi perlu adanya Unified Modeling Language (UML) yakni (1) Dapat memberikan bahasa pemodelan visual atau gambar kepada para pengguna dari berbagai macam pemrograman maupun proses umum rekayasa, (2) Menyatukan informasi-informasi terbaik yang ada dalam pemodelan, (3) Memberikan suatu gambaran model atau sebagai bahasa pemodelan visual yang ekspresif dalam pengembangan sistem, (4) Tidak hanya menggambarkan model sistem software saja, namun dapat memodelkan sistem berorientasi objek, (5) Mempermudah pengguna untuk membaca suatu sistem. Dan Unified Modeling Language (UML) berguna sebagai blueprint dalam perancangan berupa coding suatu program. Software yang dapat menggambarkan Unified Modeling Language (UML) ialah Aplikasi StarUML. Aplikasi StarUML dapat digunakan untuk membuat suatu alur atau proses dari suatu prosedur program yang ingin dibuat dengan cara menggambarkan model perangkatnya. Didalam StarUML terdapat beberapa bagian utama dari Unified Modeling Language (UML) yaitu view, diagram, model element, dan general mechanism.

APA, Harvard, Vancouver, ISO, and other styles

21

Afrianto, Yuggo, Novita Br Ginting, Suratun Suratun, and Yashintya Nelawati. "SISTEM INFORMASI INVENTORY P.O.S (POINT OF SALES) BERBASIS WEB PADA COUNTER CELLULAR." JURTEKSI (Jurnal Teknologi dan Sistem Informasi) 6, no. 2 (2020): 125–34. http://dx.doi.org/10.33330/jurteksi.v6i2.407.

Full text

Abstract:

Abstract: Data from the National Socio-Economic Survey of the National Central Bureau of Statistic (Susenas, BPS) 2016 shows that the average amount of national top up the balance spending per month in 2016 reaches Rp 22,182 per capita. It is becoming a business opportunity for top up the balance of retail entrepreneurs. However, in the process of managing the process of input, output and reporting of goods that are done manually (still using paper) are not monitored properly, often there are outgoing or incoming goods whose data is not recorded. This, in the long run, will cause large losses. The purpose of this study is to build applications that function to help provide information that makes it easy to control the process of entry and exit of goods. The system development methodology used is object-oriented system development using the Unified Modeling Language (UML). The results obtained from this research are the design and construction of Inventory Information System POS (Point of Sales) in the form of Context Diagrams and UML Diagrams (Use Case Diagrams, Activity Diagrams, Class Diagrams, and Sequence Diagrams), with the results of black box testing conducted already in operation properly according to the needs of the retail owner. Keywords: Point of Sales, Retail, UML Abstrak: Data Survei Sosial Ekonomi Nasional Badan Pusat Statistik (Susenas, BPS) 2016 menunjukkan, jumlah rata-rata pengeluaran pulsa secara nasional per bulan pada 2016 mencapai Rp 22.182 per kapita [1]. Tentu saja hal ini menjadi peluang usaha untuk para pengusaha retail counter. Namun, dalam proses pengelolaannya proses input, output dan pelaporan barang yang dilakukan secara manual (masih menggunakan kertas) tidak termonitoring dengan baik, seringkali terjadi adanya barang keluar ataupun barang masuk yang tidak tercatat datanya. Hal ini dalam jangka panjang akan menimbulkan kerugian yang besar. Tujuan penelitian ini adalah membangun aplikasi yang berfungsi dalam membantu memberikan informasi yang memudahkan dalam pengontrolan proses keluar masuknya barang. Metodologi pengembangan sistem yang digunakan adalah pengembangan sistem berorientasi objek menggunakan Unified Modeling Language (UML). Hasil yang didapat dari penelitian ini adalah perancangan dan pembangunan Sistem Informasi Inventory P.O.S (Point of Sales) berupa Diagram Konteks dan UML Diagram (Use Case Diagram, Activity Diagram, Class Diagram, dan Sequence Diagram), dengan hasil pengujian black box yang dilakukan telah beroperasi dengan baik sesuai kebutuhan owner retail. Kata kunci: Point of Sales, Retail, UML

APA, Harvard, Vancouver, ISO, and other styles

22

Ventayen, Timothy Joshua M., and Randy Joy M. Ventayen. "Systems Modeling Usage in Project Management among Junior and Senior Business System Developers." International Journal of Applied Science 1, no. 1 (2018): p1. http://dx.doi.org/10.30560/ijas.v1n1p1.

Full text

Abstract:

Unified Modeling Language (UML) is accepted as the standard for modeling software designs and is commonly used in software development Thus this paper investigated the practice of Junior and Senior Business System Developers in the use of UML and other Diagrams. Part of the study is the UML Systems modeling usage for Junior Developers by investigating the documentation used in development. This study used several methods in gathering data, interview, and questionnaire from junior and senior developers was used to come up with a result. It also investigates the possible usage of UML Diagrams in Business field which will be a basis for a future proposed content curriculum for both Business Administration and Information Technology. The result of the study shows that junior developers are not using UML Systems modeling, while senior developers increase as the experience increase in development. Most of the respondents used a diagram that is outside in the UML family. The study also shows that UML helps the managers and business people to build models and diagram that helps them to put things into perspective. It proposed that UML Diagrams should include in business Subject for both programs, the business and information technology program should unite to increase the UML usage.

APA, Harvard, Vancouver, ISO, and other styles

23

Shaikh, Asadullah, Uffe Kock Wiil, and Nasrullah Memon. "Evaluation of Tools and Slicing Techniques for Efficient Verification of UML/OCL Class Diagrams." Advances in Software Engineering 2011 (September 27, 2011): 1–18. http://dx.doi.org/10.1155/2011/370198.

Full text

Abstract:

UML/OCL class diagrams provide high-level descriptions of software systems. Currently, UML/OCL class diagrams are highly used for code generation through several transformations in order to save time and effort of software developers. Therefore, verification of these class diagrams is essential in order to generate accurate transformations. Verification of UML/OCL class diagrams is a quite challenging task when the input is large (i.e., a complex UML/OCL class diagram). In this paper, we present (1) a benchmark for UML/OCL verification and validation tools, (2) an evaluation and analysis of tools available for verification and validation of UML/OCL class diagrams including the range of UML support for each tool, (3) the problems with efficiency of the verification process for UML/OCL class diagrams, and (4) solution for efficient verification of complex class diagrams.

APA, Harvard, Vancouver, ISO, and other styles

24

Muhamad, Zainab Hassan, Dhafer AbdulAmeer Abdulmonim, and Bashar Alathari. "An integration of uml use case diagram and activity diagram with Z language for formalization of library management system." International Journal of Electrical and Computer Engineering (IJECE) 9, no. 4 (2019): 3069. http://dx.doi.org/10.11591/ijece.v9i4.pp3069-3076.

Full text

Abstract:

Unified Modeling Language (UML) is the effective standard for modeling object-oriented software systems. However, the ambiguity of semantics and the absence of consistency among UML diagrams lead to lack of precisely defining the requirements of a system. On the other hand, formal methods are techniques and tools use the mathematical notations, and they involve the precise syntax and semantics of the unambiguous software requirements specification. It applied in early stages of Software Development Life Cycle (SDLC). Therefore, an integrated between UML specification and formal specification is required to reduce the requirements' ambiguity and error, and to improve the quality and security of software systems. This paper proposes an approach involves the combining UML use-case diagram and activity diagrams with Z language for formalization of Library Management System (LMS). The focus of this paper is on consistency between the UML diagrams to Z Schema, and then verified by using the Z / EVEs tool.

APA, Harvard, Vancouver, ISO, and other styles

25

Arifin, Mohammad Nazir, and Daniel Siahaan. "Structural and Semantic Similarity Measurement of UML Use Case Diagram." Lontar Komputer : Jurnal Ilmiah Teknologi Informasi 11, no. 2 (2020): 88. http://dx.doi.org/10.24843/lkjiti.2020.v11.i02.p03.

Full text

Abstract:

Reusing software has several benefits ranging from reducing cost and risk, accelerating development, and its primary purposes are improving software quality. In the early stage of software development, reusing existing software artifacts may increase the benefit of reusing software because it uses mature artifacts from previous artifacts. One of software artifacts is diagram, and in order to assist the reusing diagram is to find the level of similarity of diagrams. This paper proposes a method for measuring the similarity of the use case diagram using structural and semantic aspects. For structural similarity measurement, Graph Edit Distance is used by transforming each factor and use case into a graph, while for semantic similarity measurement, WordNet, WuPalmer,and Levenshtein were used. The experimentation was conducted on ten datasets from variousprojects. The results of the method were compared with the results of assessments from experts.The measurement of agreement between experts and method was done by using Gwet’s AC1 andPearson correlation coefficient. Measurement results with Gwet’s AC1 diagram similarity are 0,60,which were categorized as “moderate" agreement and the result of measurement with Pearsonis 0.506 which means there is a significant correlation between experts and methods. The resultshowed that the proposed method can be used to find the similarity of the diagram, so finding andreuse of the diagram as a software component can be optimized.

APA, Harvard, Vancouver, ISO, and other styles

26

Filipova, Olga, and Oksana Nikiforova. "Definition of the Criteria for Layout of the UML Use Case Diagrams." Applied Computer Systems 24, no. 1 (2019): 75–81. http://dx.doi.org/10.2478/acss-2019-0010.

Full text

Abstract:

Abstract Nowadays, the topicality and applicability of model-driven development in the object-oriented development approach has increased, so it is important that created models and diagrams display not only the content, but also visually reflect information. Transparent diagram placement that influences work productivity is important for displaying information. Manual layout of diagrams is a time-consuming activity, which can also be ineffective, so in this paper the application of UML use case automatic layout is reviewed. The paper also examines the requirements of use case diagrams and placement criteria, which will serve as a basis for the creation of an automatic use case diagram layout algorithm.

APA, Harvard, Vancouver, ISO, and other styles

27

Wang, Yu Hua, Gui Sheng Yin, and Hai Tao Zhang. "Research on Conversion Method of Ontology Based Formal Requirements Model to UML Requirements Document." Advanced Materials Research 268-270 (July 2011): 1086–91. http://dx.doi.org/10.4028/www.scientific.net/amr.268-270.1086.

Full text

Abstract:

In the process of requirements modeling based on ontology, the obtained model description is based on application ontology; which is not easy for designer to understand and cannot be converted into requirements specification documents for design. UML is actual standard for object-oriented modeling. For this issue, this paper creates the UML meta-model, and establishes mapping rules description language for application ontology to UML meta-element, which implements the generation of UML class diagrams based on rule, use case diagrams, state transition diagram models and requirements specification documents based on UML.

APA, Harvard, Vancouver, ISO, and other styles

28

Podyachev. "UML diagram based TTCN tests implementing." SPIIRAS Proceedings, no. 4 (March 17, 2014): 155. http://dx.doi.org/10.15622/sp.4.10.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Wang, Xi, Fang Wei, and Chuan Cheng. "Slicing Objects Using UML State Diagram." Advanced Materials Research 605-607 (December 2012): 2538–42. http://dx.doi.org/10.4028/www.scientific.net/amr.605-607.2538.

Full text

Abstract:

System modeling reduces ambiguity, misunderstanding, and misinterpretation of system specifications. Modern systems tend to be very large and complex and they are hard to understand, difficult to modify and test. There is a need to analyze a particular functionality, such as a requirement of interest or a transition, a particular system feature. In this paper, we present a slice approach to generate the slices based on the UML state diagram. The slice algorithm and slice criteria are proposed in the paper. The UML state diagram slices can be applied in the fields of the software testing such as regression test, debugging and maintenance.

APA, Harvard, Vancouver, ISO, and other styles

30

Gedam, Madhuri, and Bandu B. Meshram. "Proposed Secure 3-Use Case Diagram." International Journal of Systems and Software Security and Protection 13, no. 1 (2022): 1–18. http://dx.doi.org/10.4018/ijsssp.293237.

Full text

Abstract:

The global use of UML diagrams serving as a baseline for the development of software leads to the mandatory consideration of non-functional requirements providing a secure and robust application. Secure SRS model with CIA-AAA provides the consideration of non-functional requirements and quality attributes before authorizing the users for accessing use cases. The extensive literature survey for UML Use case diagram is done. The UML use case diagrams do not provide notations, stereotypes, constraint for mis-use case and defense mechanism. This paper describes various notations, the new stereotypes such as Authentication, Buffer Overflow, SQL Injection, Encryption, Session Expiration and Connection Flooding with mathematical modelling for mitigating the attacks on the various transactions or use cases handle by the actors for providing the security.

APA, Harvard, Vancouver, ISO, and other styles

31

Ņikiforova, Oksana, Sergii Putintsev, and Dace Ahiļčenoka. "Analysis of Sequence Diagram Layout in Advanced UML Modelling Tools." Applied Computer Systems 19, no. 1 (2016): 37–43. http://dx.doi.org/10.1515/acss-2016-0005.

Full text

Abstract:

Abstract System modelling using Unified Modelling Language (UML) is the task that should be solved for software development. The more complex software becomes the higher requirements are stated to demonstrate the system to be developed, especially in its dynamic aspect, which in UML is offered by a sequence diagram. To solve this task, the main attention is devoted to the graphical presentation of the system, where diagram layout plays the central role in information perception. The UML sequence diagram due to its specific structure is selected for a deeper analysis on the elements’ layout. The authors research represents the abilities of modern UML modelling tools to offer automatic layout of the UML sequence diagram and analyse them according to criteria required for the diagram perception.

APA, Harvard, Vancouver, ISO, and other styles

32

Kezai, Mourad, and Abdallah Khababa. "Generating Maude Specifications from M-UML Statechart Diagrams." Journal of Advanced Computational Intelligence and Intelligent Informatics 26, no. 1 (2022): 8–16. http://dx.doi.org/10.20965/jaciii.2022.p0008.

Full text

Abstract:

The unified modeling language (UML) is used for the specification, visualization, and documentation of object-oriented software systems. Mobile UML (M-UML) is an extension of UML that considers mobility aspects, and a mobile statechart is an extension of the standard UML diagram that deals with the requirements for modeling, specifying, and visualizing mobile agent-based systems. However, mobile statecharts inherit UML’s lack of formal notation for analysis and verification purposes. The rewriting logic language Maude is a formal method that deals with mobile computations. In this paper, we propose a formalization of M-UML statechart diagrams using Maude to provide formal semantics for such diagrams. The generated Maude specifications are then used to analyze and check the systems using Maude analytical tools. This approach is illustrated through an example.

APA, Harvard, Vancouver, ISO, and other styles

33

Żyła, Kamil, Adam Ulidowski, Jan Wrzos, Bartłomiej Włodarczyk, Krzysztof Krocz, and Patryk Drozd. "UML – a survey on technical university students in Lublin." Journal of Computer Sciences Institute 13 (December 30, 2019): 279–82. http://dx.doi.org/10.35784/jcsi.825.

Full text

Abstract:

Unified Modeling Language (UML) is a commonly known OMG (Object Management Group) standard for designing software systems. However, practice shows that the usage of UML varies depending on the specificity of a software system and company. The authors decided to explore the perspective of students with experience in using UML by conducting a survey with them. Analysis of the data gathered revealed that they use UML diagrams as an additional help when developing software. The main risk turned out to be different diagram interpretations.

APA, Harvard, Vancouver, ISO, and other styles

34

Ansari, Rudy, and Nahdi Subairi. "IMPLEMENTASI UML PADA SISTEM PENJADWALAN MATA KULIAH." Jurnal Teknologi Informasi Universitas Lambung Mangkurat (JTIULM) 5, no. 1 (2020): 1–10. http://dx.doi.org/10.20527/jtiulm.v5i1.47.

Full text

Abstract:

Dalam penjadwalan mata kuliah memerlukan sistem otomatis agar penjadwalan dapat efektif dan efesien. Agar sistem efektif dan efesien maka diperlukan penerapan algoritma yang cukup handal. Dengan perancangan sistem menggunakan Unified Modeling Language (UML) bertujuan untuk memahami kompleksitas desain dari sistem, kami memodelkan pendekatan menggunakan usecase dan squence diagram. Usecase dan Squence diagram adalah diagram UML paling penting yang digunakan untuk pengembangan aplikasi perangkat lunak. Ada banyak properti yang harus dipertimbangkan saat menggambar usecase dan squence diagram. Kedua diagram ini mewakili berbagai aspek aplikasi perangkat lunak. Hasil dari model yang diusulkan telah ditemukan bermanfaat ketika diimplementasikan.

APA, Harvard, Vancouver, ISO, and other styles

35

El Miloudi, Khadija, and Aziz Ettouhami. "A Multiview Formal Model of Use Case Diagrams Using Z Notation: Towards Improving Functional Requirements Quality." Journal of Engineering 2018 (December 2, 2018): 1–9. http://dx.doi.org/10.1155/2018/6854920.

Full text

Abstract:

We propose a new formal model of UML use case diagram using Z notation to address some of its shortcomings. UML use case diagram has therefore become commonly used to structure functional requirements and the greatest challenge facing the software developer nowadays is to deliver a high quality product meeting customers’ requirements. However, the major disadvantage of UML models is their imprecision. In addition, they are basically in a form of semiformal modelling representations and associated natural language requirements and lack any mechanism to rigorously check consistency which results in its models being subject to ambiguity. This paper reports on the first formal modelling approach of use case diagrams in a multiview context. The approach is divided into two steps. In the first step, a formal model of UML use case diagram is proposed using Z notation. Then, a multiview consistency checking is presented. This approach guarantees software consistency, improving requirements quality.

APA, Harvard, Vancouver, ISO, and other styles

36

SALDHANA, JOHN ANIL, SOL M. SHATZ, and ZHAOXIA HU. "FORMALIZATION OF OBJECT BEHAVIOR AND INTERACTIONS FROM UML MODELS." International Journal of Software Engineering and Knowledge Engineering 11, no. 06 (2001): 643–73. http://dx.doi.org/10.1142/s021819400100075x.

Full text

Abstract:

UML, being the industry standard as a common OO modeling language, needs a well-defined semantic base for its notation. Formalization of the graphical notation enables automated processing and analysis tasks. This paper describes a methodology for synthesis of a Petri net model from UML diagrams. The approach is based on deriving Object Net Models from UML statechart diagrams and connecting these object models based on UML collaboration diagram information. The resulting system-level Petri net model can be used as a foundation for formal Petri net analysis and simulation techniques. The methodology is illustrated on some small examples and a larger case study. The case study reveals some unexpected invalid system-state situations.

APA, Harvard, Vancouver, ISO, and other styles

37

Wang, Yong Ming, and Shao Peng Wang. "UML Modeling of Diagram Document Online Approval Process." Advanced Materials Research 684 (April 2013): 563–66. http://dx.doi.org/10.4028/www.scientific.net/amr.684.563.

Full text

Abstract:

Network-based diagram document online approval management is imperative. Focusing on the development of an enterprise diagram document online management system, this paper defined the task node of diagram documentation approval process, and analyzed the corresponding diagram document approval process. According to the change demand, the diagram document change approval process was subdivided into three sub process: problem report approval, change request approval and change approval, and each main node task of the three sub process has been designed. On this basis, the UML activity diagram model of the document change and approval process was established, which is useful to develop the diagram document online approval management system.

APA, Harvard, Vancouver, ISO, and other styles

38

Zhang, Chong Ming, Zu Hua Fang, Chun Mei Wang, and Ji Feng Ni. "Using UML as Front-End for PLC Program Design." Advanced Materials Research 267 (June 2011): 521–24. http://dx.doi.org/10.4028/www.scientific.net/amr.267.521.

Full text

Abstract:

To minimize the influence of experiential factor and guarantee the software quality from the design phase, with the aid of unified modeling language (UML), an object-oriented design method for PLC program is presented. With UML as design tool, class diagram and state machine diagram are chosen respectively to describe the static structure and dynamic behavior of the PLC based control system, and PLC ladder diagram is acquired from state machine diagram subsequently. With the combination of object-oriented technology, UML and classic PLC design technology, the software reliability of PLC based control system is promoted, and the application area of object-oriented technology and UML is extended.

APA, Harvard, Vancouver, ISO, and other styles

39

Kurniawan, Tri Astoto, Lam-Son Lê, and Bayu Priyambadha. "Challenges in Developing Sequence Diagrams (UML)." Journal of Information Technology and Computer Science 5, no. 2 (2020): 221. http://dx.doi.org/10.25126/jitecs.202052216.

Full text

Abstract:

During the object-oriented software design phase, the designers have to describe the dynamic aspect of the system under development through the most common interaction diagram variant in UML 2.0, i.e. sequence diagrams. Some novice designers, including undergraduate and postgraduate students, suffer from making inappropriate models due to insufficiently detailed guidance required to develop such sequence diagrams. This paper classifies some potential mistakes which are likely performed by such novice designers, and discusses the corresponding corrections. We summarized such mistakes based on our long experiences in teaching software modeling classes as well as software analysis and design classes. There were classified twenty-one potential mistakes with respect to the syntactical and semantical correctness of the developed models. It is concluded that novice designers have to be aware and take into account the identified mistakes in such a way they can produce correct sequence diagrams.

APA, Harvard, Vancouver, ISO, and other styles

40

Yang, Feng Yu, Ying Chen, Zheng Hu, Wei Zheng, and Xi Long Duan. "Design and Implement of a Flexible Workflow Model Based on UML Modeling Technology." Applied Mechanics and Materials 738-739 (March 2015): 304–10. http://dx.doi.org/10.4028/www.scientific.net/amm.738-739.304.

Full text

Abstract:

As the rapid development of modern society, it's hard for traditional workflow technologies to meet the variant requirements inside an enterprise. The research focus of workflow technology has been moved to flexibly adjustable workflow models that can easily and fast adapt to business change. In terms of this point, a flexible workflow model is put forward based on the UML technology. Several UML diagrams, such as class diagram, activity diagram and sequence diagram, are introduced to illustrate both model elements and detailed working mechanism of the workflow model. In addition, the strategy of flexible adaption is proposed to deal with changes. Based on this model, a general-purpose system of project application and review is designed and implemented, which is able to adapt flexibly to the business flow changes of project applying after putting into use.

APA, Harvard, Vancouver, ISO, and other styles

41

Plavsic, Vera, and Emil Secerov. "Modeling of login procedure for wireless application with interaction overview diagrams." Computer Science and Information Systems 5, no. 1 (2008): 87–108. http://dx.doi.org/10.2298/csis0801087p.

Full text

Abstract:

In this paper we describe in details UML modeling of login procedure, which is a part of UserBarCodeReader application, developed for large stores and intended for use as a customer support during the shopping session. Login procedure is realized within access control system, in this case over a wireless network. Paper gives the whole modeling and implementation cycle of login procedure, from Use Case diagrams to the Java source code. Login procedure is modeled using interaction overview diagram, new in UML 2.0 which gives concise representation and divides complex sequence diagram into several smaller. The link between these diagrams is modeled with OCL postcondition and precondition expressions.

APA, Harvard, Vancouver, ISO, and other styles

42

Trisno, Indra Budi, and Yulius Hari. "Desain dan Analisa Sistem Magang di Prodi Teknik Informasi Universitas Widya Kartika Menggunakan UML." Jurnal Nasional Komputasi dan Teknologi Informasi (JNKTI) 4, no. 6 (2021): 490–500. http://dx.doi.org/10.32672/jnkti.v4i6.3682.

Full text

Abstract:

Abstrak— Prodi Teknik Informatika merupakan salah satu prodi yang terdapat pada Universitas Widya Kartika Surabaya. Mahasiswa yang mengambil jurusan ini, diharuskan untuk melakukan magang selama kurang lebih 200 jam di perusahaan. Saat ini dokumentasi magang masih dilakukan secara manual. Penulis menggunakan metode UML untuk membuat analisa sistem magang ini. Tool-tool UML yang digunakan adalah Class Diagram, Sequence Diagram serta Activity Diagram. Pembuatan analisa dan desain sistem ini akan memudahkan penulis untuk melakukan implementasi analisa menjadi program, karena banyak Bahasa pemrograman sudah mendukung konsep Object Oriented Programming.Kata kunci: Sistem Magang, Universitas Widya Kartika, UML. Abstract— Informatic Engineering is one of available study program at Widya Kartika University, Surabaya. Each student that takes this study program has to take internship as long as minimum 200 hours at any company. The process from registering until submitting internship grade has been done manually. The author applied UML in order to develop a blueprint of the internship system. UML Diagram tools will be used are Class Diagram, Sequence Diagram and Activity Diagram. Applying UML will make development of the system will be easy, because a lot of programming languages nowadays support Object Oriented Programming.Kata kunci: Internship system, Universitas Widya Kartika, UML.

APA, Harvard, Vancouver, ISO, and other styles

43

CHO, YONGSUN, WOOJIN LEE, and KIWON CHONG. "THE TECHNIQUE OF BUSINESS MODEL DRIVEN ANALYSIS AND TEST DESIGN FOR DEVELOPMENT OF WEB APPLICATIONS." International Journal of Software Engineering and Knowledge Engineering 15, no. 04 (2005): 587–605. http://dx.doi.org/10.1142/s0218194005002452.

Full text

Abstract:

A technique for creating analysis models of a web application from a business model is proposed for easy and effective development. Moreover, a technique for generating test cases from the sequence diagrams for a web application is proposed. The use case diagram and web page list are generated from the business model which is depicted using the notations of the UML (Unified Modeling Language) activity diagram. The page diagram and logical/physical database models are created based on the web page list and extracted data fields. Test cases for the web application are generated from call messages (including self-call messages) of the UML sequence diagram. The effectiveness of these techniques is shown using a practical case study which is a development project of a web application for RMS (Research material Management System).

APA, Harvard, Vancouver, ISO, and other styles

44

Sukamto, Sukamto, Roni Salambue, Elfizar Elfizar, and Anna Kaswari. "Pembuatan Aplikasi Portal Akademik Berbasis Mobile (Studi Kasus: D3 Manajemen Informatika FMIPA Universitas Riau)." Digital Zone: Jurnal Teknologi Informasi dan Komunikasi 8, no. 2 (2017): 147–59. http://dx.doi.org/10.31849/digitalzone.v8i2.640.

Full text

Abstract:

Abstrak- Penelitian ini membahas tentang aplikasi portal akademik berbasis mobile, studi kasus pada D3 Manajemen Informatika Fakultas Matematika dan Ilmu Pengetahuan Alam Universitas Riau. Aplikasi ini dapat mempermudah mahasiswa khususnya mahasiswa D3 Manajemen Informatika dalam melakukan pengisian Kartu Rencana Studi dengan menggunakan Smartphone Android. Pembuatan Aplikasi mobile ini menggunakan bahasa pemograman Java dan MySQL sebagai database. Sedangkan dalam perancangan aplikasi menggunakan Unified Modeling Language (UML) yaitu Use Case Diagram, Class Diagram, Activity Diagram, dan Sequence Diagram. Kata kunci: Aplikasi Portal Akademik, Mobile, Kartu Rencana Studi, Smartphone Android. Abstract- This research discusses about Portal Academic Application based Android Mobile with case at Diploma of Information Management the Faculty of Mathematics and Natural Sciences, University of Riau. This application can facilitate in particular the Student Information Management Diploma in charging Card Study Plan that has been using smartphones based on Android. Making mobile applications using the programming language Java, and PHP, and then MySQL as database. While the design of the application using the Unified Modeling Language (UML), Use Case Diagrams, Class Diagrams, Activity Diagrams, and Sequence. Keywords: Portal Academic Application, Android Mobile, Study Plan Card, Android Smatrphone

APA, Harvard, Vancouver, ISO, and other styles

45

Sahoo, Pulak, and J. R. Mohanty. "Early Test Effort Prediction using UML Diagrams." Indonesian Journal of Electrical Engineering and Computer Science 5, no. 1 (2017): 220. http://dx.doi.org/10.11591/ijeecs.v5.i1.pp220-228.

Full text

Abstract:

<p>Software Testing is essential for delivering quality software products. Accurate test effort estimation is an important part of project planning. Prediction of test effort at early phases of Software Developmen Life Cycle enables managers to plan ahead for the testing phase. This increases the chances of the project meeting its timeline while achieving required quality. Unified Modeling Language is a widely-used standard for representing Object Oriented Systems. Use Case and Class Diagrams are two of the most important models of the system created during early phases of software development. This work proposed that the initial test effort is predicted early using Use Case Diagram during the requirement stage and is refined during design stage when Class Diagrams are available. The predicted test efforts in both stages are functions of parameters derived from Use Case and Class Diagrams. Estimations can be revised when rest of the UML diagrams are created.</p>

APA, Harvard, Vancouver, ISO, and other styles

46

Abdulkareem, Soran Mahmood, Norhayati Mohd Ali, Novia Admodisastro, and Abu Bakar Md Sultan. "Class Diagram Critic: A Design Critic Tool for UML Class Diagram." Advanced Science Letters 23, no. 11 (2017): 11567–71. http://dx.doi.org/10.1166/asl.2017.10330.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Grigorjevs, Jurijs. "Model-Driven Testing Approach Based on UML Sequence Diagram." Scientific Journal of Riga Technical University. Computer Sciences 44, no. 1 (2011): 85–90. http://dx.doi.org/10.2478/v10143-011-0025-2.

Full text

Abstract:

Model-Driven Testing Approach Based on UML Sequence Diagram This paper is devoted to model-driven testing technique of testing model generation from UML sequence diagram to UML Testing profile. The article discusses principles of model transformation and shows practical approach to specific model generation from another one. The idea of such transformation is to generate test cases from sequence diagram of the system. Described transformation rules are focused on timing aspect verification and the goal of generated test cases is to cover successful as well as unsuccessful system behaviour. Presented example of model transformation is based on a sequence diagram XMI representation, which firstly is pre-processed and moved into data base structures, and then transformation rules applied to generate testing model from data describing sequence diagram.

APA, Harvard, Vancouver, ISO, and other styles

48

Masya, Fajar, and Elvina Elvina. "PENGEMBANGAN APLIKASI PERMAINAN SCRABBLE DUA BAHASA MENGGUNAKAN JAVA." CommIT (Communication and Information Technology) Journal 4, no. 2 (2010): 133. http://dx.doi.org/10.21512/commit.v4i2.547.

Full text

Abstract:

Game applications are favored by many computer users. The population of Indonesia, especially common people do not like playing games in a foreign language. Yet such games can be a fun learning media for foreign languages , especially English. Hence, we developed a game application using the concept of the game Scrabble. The design of this application uses a waterfall methodology, with application design modeling with UML diagrams (Unified Modelling Language) including Use Case Diagram, Activity Diagram, Statechart Diagram, Class Diagram and Sequence Diagram. In the implementation phase, Blue J software used to build the interface using the Java Development Kit (JDK) version jdk1.6.0_02 as the executor, as well as using the command prompt to call the results of execution. Tests on gaming applications are performed using the Black Box and White Box method. The product of this development is a single player game application, which uses two language options.Keywords: game applications, Scrabble, waterfall software engineering methodologies, UML (Unified Modeling Language), Java Programming.

APA, Harvard, Vancouver, ISO, and other styles

49

Deryugina, Olga. "UML class diagram object-oriented metrics: algorithms of calculation." ITM Web of Conferences 18 (2018): 03001. http://dx.doi.org/10.1051/itmconf/20181803001.

Full text

Abstract:

The paper proposes algorithms of the object oriented UML class diagram metrics calculation. Metrics include Average CBO, Average DIT, Average NOC, Average DAC, Average NLM, Average NOM, DAC2, SIZE2, and DSC. The proposed algorithms have become a part of the UML Refactoring tool providing UML class diagram analysis and transformation.

APA, Harvard, Vancouver, ISO, and other styles

50

He, Tao, Hua Zhong Li, Tang Ren Dan, De Fen Zhang, Jun Qiang Liu, and Guo Rong Qin. "Design and Analysis of Test Model under Heterogeneous and Internet-Ware." Applied Mechanics and Materials 687-691 (November 2014): 2635–39. http://dx.doi.org/10.4028/www.scientific.net/amm.687-691.2635.

Full text

Abstract:

Studying a method based on UML model software architecture performance prediction: this method chosen software architecture design in UML, use case diagram, activity diagram and component diagram, and pull stereotypes and tagged values in it, and enlarge them to be UML SPT model, and then turn UML SPT model into queuing network model through conversion algorithm, this algorithm can deal with UML model activity diagram which included branch node and confluent nodes. Finally, using frequency domain analysis theory to get queuing network model, to know performance parameters and performance bottlenecks and also introduce the design plan of UML software architecture performance automation tools, and give a example of performance prediction software architecture.

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'UML diagram'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles