Asee peer logo

A Light Weight Tool For Teaching The Development And Evaluation Of Requirements Documents

Download Paper |

Conference

2006 Annual Conference & Exposition

Location

Chicago, Illinois

Publication Date

June 18, 2006

Start Date

June 18, 2006

End Date

June 21, 2006

ISSN

2153-5965

Conference Session

Tools and Support for Software Education

Tagged Division

Software Engineering Constituent Committee

Page Count

12

Page Numbers

11.61.1 - 11.61.12

DOI

10.18260/1-2--138

Permanent URL

https://peer.asee.org/138

Download Count

157

Request a correction

Paper Authors

biography

Ben Garbers University of Wisconsin-La Crosse

visit author page

Ben Garbers has been working with IBM, Rochester, MN for 6 years where he had experience with software requirements gathering, design, development and testing. His technological expertise includes Java applications, dynamic web applications and artificial intelligent
applications. Ben is a graduate student in the Master of Software Engineering program at the University of Wisconsin La Crosse. Currently he is a first line manager of an internal build tools department at IBM.

visit author page

biography

Kasi Periyasamy University of Wisconsin-La Crosse

visit author page

Kasi Periyasamy is a Professor in the Computer Science Department and the Program Director of the Master of Software Engineering (MSE) program at University of Wisconsin-La Crosse. His research interests are in Software Specifications, Requirements Engineering, Software Testing and Verification. He has published a lot of papers in Software Engineering area, and is the co-author of the book "Specification of Software Systems" published by Springer-Verlag, 1998. He is a member of the Association of the Computing Machinery (ACM).

visit author page

Download Paper |

Abstract
NOTE: The first page of text has been automatically extracted and included below in lieu of an abstract

A Light Weight Tool for Teaching the Development and Evaluation of Requirements Documents Abstract

Writing correct and consistent software requirements specification (SRS) is one of the most important goals of a requirements engineering process. The SRS serves as the basis for subsequent design, testing and maintenance of the software product. The more errors and inconsistencies contained in an SRS, the more time and efforts are required to correct them at a later stage in the development process. Most SRS documents are manually typed using a word processor and hence the writer is responsible for ensuring the correctness and consistency of the document. Without adequate tool support, the manual construction and analysis of SRS documents is a tedious process and is error-prone. This paper describes an interactive tool developed at the University of Wisconsin-La Crosse that assists students preparing an SRS document based on the IEEE standard 83019981. The tool provides an easy-to-use interface and the ability to create, edit, load and save SRS documents. In addition, it evaluates the requirements document based on criteria published by the Software Metrics program at the Software Assurance Technology Center, NASA2. A function-point metrics analyzer is also built into the tool so that the efforts required to complete the project specified in the document can be evaluated.

Introduction

A project-oriented course in Software Engineering generally requires the students to analyze the requirements for the problem and then write the software requirements specification (SRS) document. Since the SRS serves as the basis for design, testing and maintenance of the software product, the students are expected to follow some standard such as IEEE 830-19981 while developing the SRS. A sample functional requirement in IEEE standard format is shown in Figure 1.

Index: ATM.2 Name: Deposit Purpose: To deposit an amount into an account Priority: High Input parameters: account number, amount Output parameter: None Action: Ensure that account number exists. Ensure that amount is greater than zero. Retrieve the account with account number. Update the balance in the account by adding amount to it. Exceptions: account number does not exist. amount is less than or equal to zero. Remarks: None Figure 1: An IEEE 830 compliant functional requirement in an ATM system

Garbers, B., & Periyasamy, K. (2006, June), A Light Weight Tool For Teaching The Development And Evaluation Of Requirements Documents Paper presented at 2006 Annual Conference & Exposition, Chicago, Illinois. 10.18260/1-2--138

ASEE holds the copyright on this document. It may be read by the public free of charge. Authors may archive their work on personal websites or in institutional repositories with the following citation: © 2006 American Society for Engineering Education. Other scholars may excerpt or quote from these materials with the same citation. When excerpting or quoting from Conference Proceedings, authors should, in addition to noting the ASEE copyright, list all the original authors and their institutions and name the host city of the conference. - Last updated April 1, 2015