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

Sergiu Dascalu, Eric Fritzinger, Kendra Cooper, Narayan Debnath

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.

References

  1. Alexander, I., 2003. Misuse cases: use cases with hostile
  2. intent. In IEEE Software 20(5): 58-66.
  3. Arlow J. and Neustadt, I., 2002. UML and the Unified Process: Practical Object-Oriented Analysis and Design. Addison-Wesley.
  4. Dascalu, S., Fritzinger, E., Debnath, N., and Akinwale, O., 2006. STORM: Software Tool for the Organization of Requirements Modeling, in Procs. of the 6th IEEE Intl. Conf. on Electro/Information Technology (EIT2006), IEEE Computer Society Press, pp. 250-255.
  5. Dascalu, S., Varol, Y., Harris, F., and Westphal, B., 2005. Computer Science capstone course Senior Projects: From project idea to prototype implementation, Procs. of the IEEE FIE-2005 Frontiers in Education Conference, pp. S3J/1-6.
  6. Fritzinger, E., 2006. STORM: Software Tool for the Organization of Requirements Modeling, Master thesis, University of Nevada, Reno, USA.
  7. Booch, G., Rumbaugh, J., and Jacobson, I., 2002. The Unified Modeling Language: User Manual, AddisonWesley, 2nd edition.
  8. DOORS, 2007. Telelogic's DOORS. Requirements management traceability solutions. Available online as of March 31, 2007 at http://www.telelogic.com/ products/doorsers/index.cfm
  9. Endres, A., Rombach, D., 2003. A Handbook of Software and Systems Engineering, Addison-Wesley.
  10. EventStudio, 2006. EventHelix, EventStudio System Designer 2.5 - sequence diagram based system design. Available online as of July 5, 2006 at http://www eventhelix.com/EventStudio/.
  11. IBM Rational Rose, 2007. Available online as of April 11, 2007 at http://www-306.ibm.com/software/rational/
  12. Lauesen, S., 2002. Software Requirements: Styles and Techniques, Addison-Wesley.
  13. Liu, D., Subramaniam, K., Far, B.H., and Eberlein, A., 2003. Automating transition from use cases to class model. In Procs. of the 2003 Canadian Conference on Electrical and Computer Engineering, pp. 831-834.
  14. Metamill Software, 2007, Metamill - The UML CASE tool, model UML diagrams, and engineer Java, C, C++, and C# code,” Available online as of April 1, 2007 at http://www.metamill.com/
  15. Microsoft Visio, 2003. Microsoft Office Online: Visio 2003 Home Page. Available online as of June 1, 2006 at http://www.visio.com/
  16. OMG UML, 2007. Object Management Group - UML, Available online as of April 11, 2007 at www.omg.org
  17. OSRMT, 2006. Requirements Management Tool. News. Available online as of July 1, 2006 at http://www.osrmt.com/
  18. Pressman, R.S., Software Engineering: A Practitioner's Approach, McGraw-Hill, 6th edition.
  19. RUT, 2007. Requirements Use Case Tool. NASA. Assurance tools and techniques. Available online as of February 19, 2007 at http://satc.gsfc.nasa.gov/
  20. Scenario Plus, 2007. Scenario Plus - templates & tools for scenario-based requirements engineering. Available online as of March 20, 2007 at http://www.scenarioplus. org.uk/index.html
  21. Sommerville, I. 2006. Software Engineering, AddisonWesley, 8th edition.
  22. SourceForge, 2006. SourceForge.net: Use Case Editor. Available online as of July 1, 2006 at: http://sourceforge.net/projects/uced
  23. Stahl, T., Voelter, M., Czarnecki, K., 2006. Model-Driven Software Development: Technology, Engineering, Management, Wiley & Sons.
Download


Paper Citation


in Harvard Style

Dascalu S., Fritzinger E., Cooper K. and Debnath N. (2007). A SOFTWARE TOOL FOR REQUIREMENTS SPECIFICATION - On using the STORM Environment to Create SRS Documents . In Proceedings of the Second International Conference on Software and Data Technologies - Volume 2: ICSOFT, ISBN 978-989-8111-06-7, pages 319-326. DOI: 10.5220/0001345303190326


in Bibtex Style

@conference{icsoft07,
author={Sergiu Dascalu and Eric Fritzinger and Kendra Cooper and Narayan Debnath},
title={A SOFTWARE TOOL FOR REQUIREMENTS SPECIFICATION - On using the STORM Environment to Create SRS Documents},
booktitle={Proceedings of the Second International Conference on Software and Data Technologies - Volume 2: ICSOFT,},
year={2007},
pages={319-326},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0001345303190326},
isbn={978-989-8111-06-7},
}


in EndNote Style

TY - CONF
JO - Proceedings of the Second International Conference on Software and Data Technologies - Volume 2: ICSOFT,
TI - A SOFTWARE TOOL FOR REQUIREMENTS SPECIFICATION - On using the STORM Environment to Create SRS Documents
SN - 978-989-8111-06-7
AU - Dascalu S.
AU - Fritzinger E.
AU - Cooper K.
AU - Debnath N.
PY - 2007
SP - 319
EP - 326
DO - 10.5220/0001345303190326