scholarly journals Requirements Association Extraction based on Use Cases Diagram

Author(s):  
Peter Gelu ◽  
Riyanarto Sarno ◽  
Daniel Siahaan

Requirements are the initial step in the software development process. It is very important to ensure the association (relationship) of requirements and high quality of specification as more than three-quarters failure of software derives from the software requirement process. Therefore, the analysis process is required to ensure the association between requirements and the requirements of other users. As a result, interdependency requirements association is essential. This research proposes an approach of software requirements association. These are based on the reference of interdependency in the user case, namely the result of collaboration of the association of the dependency of requirements based on Unified Modeling Language (UML) design in the Use cases diagram. In this research, the mapping between requirements and use cases and interdependencies between use cases are used to determine the interdependency between requirements. The analysis presented is the association of similar requirements, requires, or, temporal, elaborates dan generalises. The purpose of this research is to generate a requirements dependency graph that models the type of dependency between requirements within a software project.

Author(s):  
Dingding Lu ◽  
Robyn R. Lutz ◽  
Carl K. Chang

This chapter introduces an analysis process that combines the different perspectives of system decomposition with hazard analysis methods to identify the safety-related use cases and scenarios. It argues that the derived safety-related use cases and scenarios, which are the detailed instantiations of system safety requirements, serve as input to future software architectural evaluation. Furthermore, by modeling the derived safety-related use cases and scenarios into UML (Unified Modeling Language) diagrams, the authors hope that visualization of system safety requirements will not only help to enrich the knowledge of system behaviors but also provide a reusable asset to support system development and evolution.


2016 ◽  
Vol 9 (1) ◽  
Author(s):  
Andri Kulung ◽  
Steven Sentinuwo ◽  
Alicia Sinsuw

Bahasa Mandarin merupakan salah satu Bahasa yang terkenal di seluruh dunia. Ada sekitar 1.302 juta orang dengan berbagai kalangan umur telah menggunakan Bahasa mandarin, sehingga karena alasan tersebut banyak sekolah termasuk Sekolah Dasar (SD) Advent 1 Tikala Manado telah memasukkan Bahasa Mandarin sebagai salah satu mata pelajaran Bahasa asing. Namun siswa-siswa SD Advent 1 Tikala Manado merasa kesulitan dalam mempelajari Bahasa Mandarin dikarenakan tidak adanya media pembelajaran yang dapat membantu mereka dalam mempelajari Bahasa Mandarin di luar jam sekolah. Aplikasi pembelajaran Bahasa Mandarin Dasar merupakan solusi untuk membantu siswa SD Advent 1 Tikala Manado dalam mempelajari Bahasa Mandarin, baik dalam proses pembelajaran di sekolah maupun di luar sekolah. Unified Software Development Process (USDP) merupakan metode pengembangan perangkat lunak yang prosesnya dikendalikan oleh Use Case (use case driven) dan dikerjakan secara berulang (iterative) sehingga pada akhirnya menghasilkan perangkat lunak terintegrasi berukuran besar yang terbentuk secara bertahap (Incremental) dengan bantuan Unified Modeling Language (UML) sebagai alat bantu utama analisis dan perancangan sistem perangkat lunak. Aplikasi pembelajaran Bahasa Mandarin Dasar dibuat dengan fitur belajar dan bermain. Fitur belajar dilengkapi dengan materi pengajaran yang digolongkan ke dalam  beberapa kategori yaitu kategori kelas 1, kelas 2, dan kelas 3 serta sub fitur berupa suara dengan tujuan siswa bisa mengetahui cara pengucapan suatu kata. Dengan dibuatnya aplikasi ini diharapkan agar aplikasi ini bisa membantu siswa dalam mempelajari Bahasa Mandarin pada jam sekolah maupun diluar jam sekolah.


2021 ◽  
Vol 1 (1) ◽  
pp. 36-47
Author(s):  
Andrianjaka Miary Rapatsalahy ◽  
Hajarisena Razafimahatratra ◽  
Thomas Mahatody ◽  
Mihaela Ilie ◽  
Sorin Ilie ◽  
...  

The final executable code should no longer be considered as a central element in a software development process but rather a naturally important component that results from a model transformation. The objective of the MDA (Model Driven Architecture) approach is to lift the lock of software development automation from the CIM (Computation Independent Model) requirements until the code of an application is obtained. Therefore, we have proposed in the framework of MDA an approach that consists of automatically generating object-oriented code from the CIM model represented by ReLEL (Restructuring extended Lexical Elaborate Language). ReLEL is a natural language-oriented model that represents both the client requirements and the conceptual level of a system. However, the MDA framework does not recommend the type of UML model that corresponds to each business activity. Consequently, automating the software development process from the CIM model specified by ReLEL becomes a complex task. Our strategy in this paper includes the instantiation of the ReLEL model in the Praxeme methodology, which models each of the company's concerns, grouped in a homogeneous whole, using the UML (Unified Modeling Language) and which considers the articulation of these aspects by adopting the MDA principle. To do this, we propose to automate the articulation that covers the intentional, semantic, logical, and software aspects of Praxeme. To validate our approach, we measure the coupling and cohesion of the UML class diagram obtained from the Java code generated from this article using the slicing technique. The results show that the coupling is weak, and the cohesion is strong. It can be deduced that the method proposed in this paper can produce a more reliable and efficient system. 


2012 ◽  
Vol 546-547 ◽  
pp. 1556-1561 ◽  
Author(s):  
Ai Mei Dong

System analysis is the most important Part of the software life cycle. A successful software system is always based on good analysis. Modeling with UML has become a trend in object-oriented analysis and design. This paper firstly discusses object-oriented software development process based on UML (Unified Modeling Language), then describes in details object-oriented software design process, and lastly applies the design process into business personnel management system.


2014 ◽  
Vol 599-601 ◽  
pp. 530-533
Author(s):  
Hong Hao Wang ◽  
Hui Quan Wang ◽  
Zhong He Jin

Due to the complex timing sequence of NAND flash, a unified design process is urgently required to guarantee the reliability of storage system of nano-satellite. Unified Modeling Language (UML) is a widely used high level modeling language for object-oriented design. This paper adopts the UML as the design and modelling tool in the low level storage system design to elaborate the UML application in each phase of design in detail. The result shows taking UML as the modelling tool results in a clear and unambiguity design, which promotes the reliability and quality of software. At last, the feasibility of object-oriented implementation in C is presented.


2004 ◽  
Vol 1 (2) ◽  
pp. 173-194 ◽  
Author(s):  
Radoslav Rakovic

Successful management of a software project, besides a well-defined project development process, requires an early estimate of project complexity. In a prevailing practice, software development costs usually have been determined a posteriori i.e. after software project implementation. It is essential however, to know this estimate a priori, i.e., before commencement of works. This paper presents an attempt to construct a methodology that would enable an early estimate of software development cost and its refinements during subsequent development phases. The methodology assumes an object-oriented approach based on the Unified Modeling Language (UML) and Unified Software Development Process (USDP). It outlines an Use Case Driven Architecture-Centric, Iterative and Incremental estimate process that could significantly improve and simplify early cost estimates. The presented methodology is illustrated on example of the POST software development project.


2019 ◽  
Vol 21 (3) ◽  
pp. 223-233
Author(s):  
Gunadi Emanuel ◽  
R. Kristoforus J. Bendi ◽  
Arieffianto Arieffianto

Abstract :  Tic-Tac-Toe is one of the board games. It is played by filling the columns on the board with X or O in such a way as to form parallel lines vertically, horizontally and diagonally. This study aims to design Non-Player Characters (NPC) in the tic-tac-toe game with the minimax algorithm. The Tic-tac-toe game will be designed with two game modes: easy and minimum random modes. While in minimax NPC mode will determine the best step. The game development process of the tic-tac-toe application is based on a linear sequence process model. In the analysis phase, the NPC will be designed based on the concept of minimax. Software modeling was designed using Unified Modeling Language (UML), and coded with Visual Basic programming. Our tests show that NPCs with the Minimax algorithm can work well.


2015 ◽  
Author(s):  
Giuseppe Destefanis ◽  
Marco Ortu ◽  
Steve Counsell ◽  
Michele Marchesi ◽  
Roberto Tonelli

A successful software project is the result of a complex process involving, above all, people. Developers are the key factors for the success of a software development process, not merely as executors of tasks, but as protagonists and core of the whole development process. This paper investigates social aspects among developers working on software projects developed with the support of Agile tools. We studied 22 open source software projects developed using the Agile board of the JIRA repository. All comments committed by developers involved in the projects were analyzed and we explored whether the politeness of comments affected the number of developers involved and the time required to fix any given issue. Our results showed that the level of politeness in the communication process among developers does have an effect on the time required to fix issues and, in the majority of the analysed projects, it had a positive correlation with attractiveness of the project to both active and potential developers. The more polite developers were, the less time it took to fix an issue. In the majority of the analysed cases, the more developers wanted to be part of a project, the more they were willing to continue working on the project over time.


Sign in / Sign up

Export Citation Format

Share Document