Towards implementing a framework for modeling software requirements in magicdraw uml
TL;DR: This paper presents a framework for modeling software requirements consistently using multiple UML diagrams and discusses how such a framework could be implemented in one of the most popular UML tools, MagicDraw UML, by using its powerful features for customizing the modeling environment.
read more
Abstract: UML is considered to be de facto standard for software modeling. However, in software requirements analysis it is quite common to apply only use case and activity diagrams and focus on the textual requirements specification with some non-standard graphical illustrations. In this paper we present a framework for modeling software requirements consistently using multiple UML diagrams. We illustrate the application of this framework with the examples of different requirements artifacts based on a case study system MagicTest. We discuss how such a framework could be implemented in one of the most popular UML tools, MagicDraw UML, by using its powerful features for customizing the modeling environment, defining methodology wizards, specifying validation rules, analyzing model element relationships, and generating documentation based on user-defined templates. We recognize that our approach provides the foundation, which could and should be refined and extended for special cases of requirements analysis. Our work should be considered as a starting point for practitioners trying to adopt UML for requirements analysis and for scientists working on creating more detailed requirements analysis methods based on UML.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
An approach for the metamodel of the framework for a partial agile method adaptation
Gytenis Mikulėnas,Rimantas Butleris,Lina Nemuraitė +2 more
- 01 Mar 2011
TL;DR: The main aim of this paper is to present a metamodel of the framework for a partial agile method adaptation and extend some of the earlier and more fragmented findings that have been described in the previous work.
Enterprise knowledge based software requirements elicitation
Aurelijus Morkevicius,Saulius Gudas +1 more
- 12 Sep 2011
TL;DR: The paper presents an approach for the enterprise knowledge based software requirements elicitation based on the Unified profile for Ministry of Defence Architecture Framework, System Modeling Language (SysML) requirements model, and a Semantics of Business Vocabulary and Business Rules (SBVR) standard as a formal background for elicited software requirements.
An Approach for Prioritizing Agile Practices for Adaptation
Gytenis Mikulenas,Kestutis Kapocius +1 more
- 01 Jan 2011
TL;DR: This chapter proposes an approach for prioritization of available practices in accordance to the particular circumstances and combines ideas from Analytic Hierarchy Process (AHP) decision-making technique, cost-value analysis, and Rule-Description-Practice (RDP) technique.
12
Consistency Checking of UML Business Model
TL;DR: In this paper, the authors present approach in ensuring UML model consistency and several examples of consistency rules are included to illustrate how approach is working in a domain of enterprise manufacturing windows and doors.
Integrating Safety into MBSE Processes with Formal Methods
Alexander Ahlbrecht,Umut Durak +1 more
- 03 Oct 2021
TL;DR: In this paper, a use-case that analyzes a simplified Collision Avoidance System architecture is presented, and the presented approach is able to improve the development by automating and validating error-prone tasks of the safety assessment.
11
References
•Book
The entity-relationship model: toward a unified view of data
Peter P. Chen
- 17 Oct 2013
TL;DR: A data model, called the entity-relationship model, is proposed that incorporates some of the important semantic information about the real world and can be used as a basis for unification of different views of data: the network model, the relational model, and the entity set model.
Goal-oriented requirements engineering: a guided tour
TL;DR: The paper compares the main approaches to goal modeling, goal specification and goal-based reasoning in the many activities of the requirements engineering process and suggests what a goal-oriented requirements engineering method may look like.
•Book
Software Requirements
Karl Eugene Wiegers
- 01 Jan 1999
TL;DR: This updated edition of Software Requirements, Second Edition features new case examples, anecdotes culled from the author's extensive consulting career, and specific Next Steps for putting the book's process-improvement principles into practice.
1K
Software Requirements
Rick Lutowski
- 01 Apr 2005
TL;DR: The activities of elicitation, analysis, specification, validation, and requirements management are discussed and recommended practices in each of those areas are highlighted.
497