STORM: Software Tool for the Organization of Requirements Modeling

Dascalu, Sergiu M.; Fritzinger, Eric; Debnath, Narayan C.; Akinwale, Olusegun

doi:10.1109/eit.2006.252151

Cited by 1 publication

(3 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our work on STORM has been initially materialized in a 2005 version of the tool (Dascalu, 2006). Further work has been done continuously since then on improving STORM and a second, 2006 version has been developed as part of a Master thesis in Computer Science successfully defended in June 2006 by one of this paper's authors .…”

Section: Background and Motivationmentioning

confidence: 99%

“…The goal of the STORM project was to create a CASE tool for the specific purpose of supporting the requirements and specification phases of software engineering (Dascalu, 2006). It has been designed as a tool to be used in an academic setting, in particular for supporting the way specification is done at the University of Nevada, Reno, USA.…”

Section: Future Work and Conclusionmentioning

confidence: 99%

“…STORM has been introduced in a 2006 paper (Dascalu, 2006) that described its main concepts and provided excerpts from its software model and prototype in action. Since then, STORM has undergone further development and has evolved in terms of new features, operational capabilities, and reliability.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A SOFTWARE TOOL FOR REQUIREMENTS SPECIFICATION - On using the STORM Environment to Create SRS Documents

Dascalu

Fritzinger

Cooper³

et al. 2007

Proceedings of the Second International Conference on Software and Data Technologies

View full text Add to dashboard Cite

Abstract:STORM, presented in this paper, is a UML-based software engineering tool designed for the purpose of automating as much of the requirements specification phase as possible. The main idea of the STORM approach is to combine adequate requirements writing with robust use case modelling in order to expedite the process leading up to the actual design of the software. This paper presents a description of our approach to software requirements specification as well as an overview of STORM's design concepts, organizing principles, and modes of operation. Also included are examples of the tool's use, a comparison between STORM and similar CASE tools, and a discussion of needed features for software environments that support text aspects of requirements and use case modelling.

show abstract

Section: Background and Motivationmentioning

confidence: 99%

Section: Future Work and Conclusionmentioning

confidence: 99%