Requirements Association Extraction based on Use Cases Diagram
Peter Jr Gelu2018, Lontar Komputer : Jurnal Ilmiah Teknologi Informasi
Sign up for access to the world's latest research
checkGet notified about relevant papers
checkSave papers to use in your research
checkJoin the discussion with peers
checkTrack your impact
Abstract
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 simi...
Related papers
Identifying Requirements Association Based on Class Diagram Using Semantic Similarity
2019
Requirements association depicts inter-relation between two or more requirements within a software project. It provides necessary information for developers during decision-making processes, such as change management, development milestones, bug prediction, cost estimation, and work breakdown structure generation. Modeling association between requirements became a focus of software requirements researchers. Previous studies indicate that requirements association was pre-defined by requirements engineer based on their expert judgments. The judgments require knowledge on requirements and their class realizations. This paper introduces a method to generate a mapping between a set of requirement statements and a set of classes of a given project that realized the respected requirements. The method also generates associations among requirements based on information on associations between classes and the class-requirement mapping. The method utilizes element of relational information res...
Relationship analysis in requirements engineering
Requirements Engineering, 2004
Execution of a requirement model in software development
2004
Latest research results have shown that requirements errors have a prolonged impact on software development and that they are more expensive to fix during later stages than early stages in software development. Use case diagrams in UML are used to give requirements for a software system, but all descriptions for each use case are written in informal language. In this paper, we propose a new language HCL (High-Level Constraint Language) to which any requirement model given by use case diagrams can be mapped. Not only is the language HCL based on a formal language but also the requirement model written in HCL can be executed. Many errors occurring during requirements analysis and design can be detected by means of execution.
A Relational Model for Formal Object-Oriented Requirement Analysis in UML
This paper is towards the development of a methodology for object-oriented software development. The in tention is to support effective use of a formal model for specifying and reasoning during the requirements analysis and design of a software development process. The overall purpose is to enhance the application of the Unified Modelling Language (UML) with a formal semantics in the Rational Unified Software Develop- ment Process (RUP). The semantic framework defines the meaning of some UML submodels. It identifies both the static and dynamic relationships among these submodels. Thus, the focus of this paper is the de- velopment of a semantic model to consistently combine a use-case model and a conceptual class diagram to form a system specification. Keywords: Object-orientation, UML, use-cases, conceptual models, requirement specification
Formal and use-case driven requirement analysis in UML
2001
UNU/IIST is jointly funded by the Governor of Macau and the governments of the People's Republic of China and Portugal through a contribution to the UNU Endownment Fund. As well as providing twothirds of the endownment fund, the Macau authorities also supply UNU/IIST with its office premises and furniture and subsidise fellow accommodation.
Enhancing requirements reusability through semantic modeling and data mining techniques
Enterprise Information Systems
Enhancing the requirements elicitation process has always been of added value to software engineers, since it expedites the software lifecycle and reduces errors in the conceptualization phase of software products. The challenge posed to the research community is to construct formal models that are capable of storing requirements from multimodal formats (text and UML diagrams) and promote easy requirements reuse, while at the same time being traceable to allow full control of the system design, as well as comprehensible to software engineers and end users. In this work, we present an approach that enhances requirements reuse while capturing the static (functional requirements, use case diagrams) and dynamic (activity diagrams) view of software projects. Our ontology-based approach allows for reasoning over the stored requirements, while the mining methodologies employed detect incomplete or missing software requirements, this way reducing the effort required for requirements elicitation at an early stage of the project lifecycle.
Digging into Use Case Relationships
Lecture Notes in Computer Science, 2002
Use case diagrams are one of the key concepts in the Unified Modeling Language, but their semantics and notation have some gaps that lead to frequent misunderstandings among practitioners, even about very basic questions. In this paper we address some issues regarding the relationships in which use cases may take part. The Include and Extend relationships between two use cases have presently an inconsistent definition, since they are represented as stereotyped dependencies, but they are not true dependencies in the metamodel. Besides, the direction of the dependency arrow in the Extend relationship can be misleading, unnatural and difficult to understand for the common practitioner. Finally, we show also some conceptual problems regarding the included or extending use cases, which in our opinion are not true use cases.
Structural and Semantic Similarity Measurement of UML Use Case Diagram
Lontar Komputer : Jurnal Ilmiah Teknologi Informasi, 2020
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 ex...
An Effective Approach for Transforming Use Cases Specifications into Class Diagram
The transition from object-oriented software requirements to design is a crucial activity in the software process. Being the most important diagram of the design phase, class diagram combines the presentation of the components that will provide the solution and their relationships. Class diagram requires much focus and effort to be developed. In order to read the use cases specifications written in natural languages and design the class diagram will provide the intended solution, several software researches made great effort in this matter. This paper suggests the use of natural language processing techniques in order to extract information from the use case specifications and translate these information into a class diagram. The approach will identify the classes, how they are related and will provide information about the internal structure of each class.
An empirical study of requirements model understanding
Proceedings of the 2010 ACM Symposium on Applied Computing - SAC '10, 2010
Visual modelling languages are commonly used to support software requirements analysis and documentation. A variety of languages are available, based on different conceptual paradigms. They can be roughly divided into two main groups: goal-oriented approaches and scenario-based approaches. In the last ten years, numerous works developed case studies that illustrate the effectiveness and limitations of goal-oriented and scenario-based approaches. A few works even suggest coupling these approaches in order to capture requirements from different perspectives. However, experimental comparisons of these approaches have been rarely addressed. This paper presents the design and preliminary results of an empirical study that compares two state of the art requirements modelling methods: Use Cases, which is a scenario-based approach, and Tropos, which is a goaloriented approach. The objective is to evaluate different levels of comprehension of requirements models expressed in both methods, as well as to estimate the time required to perform simple analysis tasks using both methods. Preliminary results show that Tropos models seem to be more comprehensible, although more time consuming, than Use Case models to novice requirements analysts.
Related topics
Related papers
On the decomposition of use case diagrams for the refinement of requirements
in 14th International Conference on Computational Science and Its Applications (ICCSA), pp 237-240, 2014
"Requirements elicitation is a complex and usually longstanding but crucial activity to the software development. UML use case models are one of the most popular techniques to describe the functional requirements of a system. Use cases can be written with a high-abstraction level or with a lowabstraction level. In fact, when one needs to see the system as a whole, the high-abstraction level use cases are useful. But when the system’s details need to be known, low-abstraction level use cases are a lot more useful. This paper describes an iterative and incremental approach to support the construction of UML use case diagrams as a first documentation effort of the requirements elicitation activities. The approach adopts a refinement mechanism to detail use cases, in a controlled way, as a mean to obtain a functional requirements model of the system. This allows relating an abstract use case with the corresponding more concrete use cases."
An approach to determine software requirement construction sequences based on use cases
2008 International Conference on Advanced Software Engineering & Its Applications, 2008
The majority of software development projects utilize the use cases technique to define software requirements, which are necessary to determine not only the scope of the software itself, but also the sequence in which this software will be constructed. Currently, there are several proposals to define the construction sequence of software requirements, but most of these proposals lack of ease of use from the developer's perspective.
Modelling Requirements With UML: a Rigorous Approach (Doing Requirements Well With UML)
Citeseer
The tutorial addresses the problems connected with requirements modelling in a UML-based development process. UML supports requirements modelling by means of use cases. This practice suffers from several limitations, especially as use cases are quite informal descriptions ...
Process of Requirement Analysis Link to Software Development
This paper is giving an overview of the process of requirement analysis for software development. Here I have discussed about key parts in requirement analysing, gathering relevant materials, functional analysis and allocations, how to improve and make a quality process and also document development as well and many more which relates to requirement analysis process. The scope of this study is not a generalized approach but rather discuss through specific cases such as like Dutch flower case. It describes the main areas of requirement process in practice, and highlights. I hope that readers will find this paper useful in guiding them toward the knowledge and resources they needed.
The Role of Interdependencies in Software Requirements Analysis Estimation
International Journal of Computer Applications, 2013
Requirement analysis is sophisticated process to understand the exact requirement in which some are singular and some may depend on other requirements. This Paper presents identification of requirements interdependencies in the software development process. Requirements elicitation is the gathering of relevant knowledge to find out the solution for a problem domain. There are various requirement elicitation techniques available such as: Interviewing and questionnaires, requirements workshops, brainstorming and idea reduction, storyboards, use cases, role playing, prototyping. This paper provides a significant work done on selecting an appropriate technique among them to address the number of unresolved issues concerning the identification and mapping of interdependencies.
Efficient Requirement Engineering for Small Scale Project by Using UM
—Today, web based applications have transform into problematical, famous and vital in each organization which needs high consistency and high quality of web based application. Effective development involving software system based on to the quality of any requirement engineering process. This research focus on in what way to elicit and specify the necessities of software to be developed. These events (activities) are supported with in the field called requirement engineering. The study present now aims at refining a specific practice in requirement engineering called UML modelling. In this research we proposed a module based integrated model. This model is further demonstrated with the help of UML modelling. By this technique we achieve the efficient requirement engineering for small scale project. This research investigate the role connected with use case diagram and sequence diagram modelling and also class diagram throughout requirement engineering process. The outcome obtained in this research offer more help for in what way to effectively put on requirement engineering with UML modelling as an essential basis for software development.
Formalization, Testing and Execution of a Use Case Diagram
Lecture Notes in Computer Science, 2003
Errors in a requirements model have prolonged detrimental effects on reliability, cost, and safety of a software system. It is very costly to fix these errors in later phases of software development if they cannot be corrected during requirements analysis and design. A Use Case diagram, as a requirements model, plays an important role in giving requirements for a software system. It provides a communication tool between software requirements developers and prospective users to understand what requirements of a software system are. However most descriptions of a use case diagram are written in some informal language, leading to possible misunderstanding between developers and users. In this paper, we propose a new rigorous review technique which can be applied to software requirements models. Using this new technique before a software system is fully designed will help us find some potential errors in a requirements model, resulting in reduced time, labor and expenditure in software development.
On the Decomposition of Use Cases for the Refinement of Software Requirements
2014 14th International Conference on Computational Science and Its Applications, 2014
Requirements elicitation is a complex and usually longstanding but crucial activity to the software development. UML use case models are one of the most popular techniques to describe the functional requirements of a system. Use cases can be written with a high-abstraction level or with a lowabstraction level. In fact, when one needs to see the system as a whole, the high-abstraction level use cases are useful. But when the system's details need to be known, low-abstraction level use cases are a lot more useful. This paper describes an iterative and incremental approach to support the construction of UML use case diagrams as a first documentation effort of the requirements elicitation activities. The approach adopts a refinement mechanism to detail use cases, in a controlled way, as a mean to obtain a functional requirements model of the system. This allows relating an abstract use case with the corresponding more concrete use cases.
An empirical study of requirements model understanding: Use Case vs. Tropos models
2010
Abstract Visual modelling languages are commonly used to support software requirements analysis and documentation. A variety of languages are available, based on different conceptual paradigms. They can be roughly divided into two main groups: goal-oriented approaches and scenario-based approaches. In the last ten years, numerous works developed case studies that illustrate the effectiveness and limitations of goal-oriented and scenario-based approaches.
JGOOSE: A REQUIREMENTS ENGINEERING TOOL TO INTEGRATE I* ORGANIZATIONAL MODELING WITH USE CASES IN UML
2009
En los días actuales los sistemas computacionales se caracterizan por su complejidad, dinamismo y gran importancia estratégica. En este complejo escenario de especificación de software, generar documentación de alta calidad es una difícil tarea. En general los clientes no saben exactamente lo que desean y muchas veces los requisitos del software no reflejan las reales necesidades de los clientes y del ambiente organizacional. Es bastante común encontrar requisitos inconsistentes e incompletos. En este contexto, uno de los grandes desafíos está en la necesidad de integrar los requisitos organizacionales y funcionales del sistema computacional que será desarrollado. En este trabajo se presenta la herramienta computacional JGOOSE (Java Goal Into Object Oriented Standard Extension) que permite integrar diagramas de casos de uso en UML con requisitos organizacionales representados utilizando la técnica i*. Se presenta la utilización de la herramienta en el caso de estudio de un Sistema de Gestión de Evento Científico.
Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.