use case models
Recently Published Documents


TOTAL DOCUMENTS

73
(FIVE YEARS 11)

H-INDEX

13
(FIVE YEARS 1)

2021 ◽  
Vol 11 (14) ◽  
pp. 6464
Author(s):  
Tomas Skersys ◽  
Paulius Danenas ◽  
Rimantas Butleris ◽  
Armantas Ostreika ◽  
Jonas Ceponis

In the domain of model-driven system engineering, model-to-model (M2M) transformations present a very relevant topic because they may provide much-needed automation capabilities to the whole CASE-supported system development life cycle. Nonetheless, it is observed that throughout the whole development process M2M transformations are spread unevenly; in this respect, the phases of Business Modeling and System Analysis are arguably the most underdeveloped ones. The main novelty and contributions of this paper are the presented set of model-based transformations for extracting well-structured SBVR business vocabularies from visual UML use case models, which utilizes M2M transformation technology based on the so-called drag-and-drop actions. The conducted experiments show that this new development provides the same transformation power while introducing more flexibility to the model development process as compared to our previously developed approach for (semi-)automatic extraction of SBVR business vocabularies from UML use case models.


Author(s):  
Nassima Yamouni-Khelifi ◽  
Kaddour Sadouni ◽  
Michał Śmiałek ◽  
Mahmoud Zennaki

Requirements definition is the first step in the life cycle of a software system. Requirements are formulated as paragraphs of text and appear ambiguous, so they cannot be translated directly into code. For this reason, they are treated as secondary artifacts for software developers. This paper presents a model-driven based approach where requirements are treated as first-class citizens, and can contribute to the final code. In this approach, requirements are formulated as use case models with their textual scenarios, using a precise requirements language called RSL, allowing an automatic transition to executable Java code. The structure of the generated code follows the Model-View-Presenter (MVP) architectural pattern. The work focuses on the Model layer code, which is responsible for the persistence and storage of data in a database system.


Author(s):  
Cristiana Pereira Bispo ◽  
Ana Patrícia Magalhães ◽  
Sergio Fernandes ◽  
Ivan Machado
Keyword(s):  
Use Case ◽  

2020 ◽  
Vol 10 (10) ◽  
pp. 2369-2377
Author(s):  
Waqar Mehmood ◽  
Hassan Jari ◽  
Ali Tahir ◽  
Waqar Aslam ◽  
Muhammad Kamran

Development of large-scale healthcare software projects essentially need the efficient management of the created software artifacts during software development process. In such projects different versions of an artifact are created at different times. Traditional software configuration management systems, such as Git, Subversion (SVN), etc., are designed for later phases of software development, which mainly handle the source code document. These systems are unable to perform difference detection and version management tasks on models such as unified modeling language diagrams. UML use case model is used for capturing functional requirements at analyses phase. Different versions of the use case model are created during analyses phase. This paper addresses the detection of differences between two versions of a use case model. In order to perform difference detection, we need to perform three main tasks, i. e., extract the contents of the model, comparison of models and difference representation. Most of the existing approaches in literature of model comparison deal with UML class diagrams. To the best of our knowledge, so far no appropriate approach addresses difference computation of use case model. Existing approaches are not applicable on use case model due to different semantics of use case model. In this research, the concept of model-based software configuration management (SCM) for use case difference detection is proposed. The use case models are created in an open source tool, starUML. The proposed difference algorithm is applied on intermediate tree structure representation of models. As a case study, different versions of a patient appointment healthcare system is used to evaluate different evaluation parameters, such as accuracy, domain independence, high conceptual level and tool independence.


2020 ◽  
Vol 10 (10) ◽  
pp. 2369-2377
Author(s):  
Waqar Mehmood ◽  
Hassan Jari ◽  
Ali Tahir ◽  
Waqar Aslam ◽  
Muhammad Kamran

Development of large-scale healthcare software projects essentially need the efficient management of the created software artifacts during software development process. In such projects different versions of an artifact are created at different times. Traditional software configuration management systems, such as Git, Subversion (SVN), etc., are designed for later phases of software development, which mainly handle the source code document. These systems are unable to perform difference detection and version management tasks on models such as unified modeling language diagrams. UML use case model is used for capturing functional requirements at analyses phase. Different versions of the use case model are created during analyses phase. This paper addresses the detection of differences between two versions of a use case model. In order to perform difference detection, we need to perform three main tasks, i. e., extract the contents of the model, comparison of models and difference representation. Most of the existing approaches in literature of model comparison deal with UML class diagrams. To the best of our knowledge, so far no appropriate approach addresses difference computation of use case model. Existing approaches are not applicable on use case model due to different semantics of use case model. In this research, the concept of model-based software configuration management (SCM) for use case difference detection is proposed. The use case models are created in an open source tool, starUML. The proposed difference algorithm is applied on intermediate tree structure representation of models. As a case study, different versions of a patient appointment healthcare system is used to evaluate different evaluation parameters, such as accuracy, domain independence, high conceptual level and tool independence.


2019 ◽  
Vol 24 (2) ◽  
pp. 215-228
Author(s):  
Aljia Bouzidi ◽  
Nahla Haddar ◽  
Kais Haddar
Keyword(s):  
Use Case ◽  

Sign in / Sign up

Export Citation Format

Share Document