Inventory System
The Student Communication and Tracking System
Software Requirements Specification
Marco Aviso
Jason Derenick
Michael Panzarella
Andrew Perhac
March 21, 2002
Submitted in partial fulfillment
Of the requirements of
CMPS 374-Fundamentals of Software Engineering
Table of Contents
1. Introduction 1
1.1. Purpose 1
1.2. Scope of Project 1
1.2. Glossary 2
1.3. References 4
1.4. Overview of Document 4
2. Overall Description 6
2.1. System Environment 6
2.2. Functional Requirements Definition 11
2.3. User Interface Specification 27
2.4. Non-Functional Requirements 28
2.5. System Evolution 30
3. Requirements Specification 31
3.1. External Interface Requirements 31
3.2. Functional Requirements 32
3.3. Detailed Non-Functional Requirements 44
Index 45
1. Introduction
1.1. Purpose
The purpose of this document is too provide a concise overall description of the functionality and anticipated constraints of The Student Communication and Tracking System, developed for the University of Scranton in Pennsylvania. This document will discuss the scope of the project at hand and will further specify the chosen system environment as well as the anticipated user interfaces for the system. Additionally, special considerations regarding the potential evolution of the system as well as both functional and non-functional requirements will be identified and discussed. The expected audience of this document will be the University of Scranton’s administration, faculty members, classroom instructors and Department of Public Safety officials. It is expected that this document will also serve as a viable reference for the software engineers and computer system specialists that are implementing The Student Communication and Tracking System at the University of Scranton in Pennsylvania.
1.2. Scope of Project
The scope of the project can be defined in terms of the documentation and development of a student communicator and
Software Requirements Specification
Marco Aviso
Jason Derenick
Michael Panzarella
Andrew Perhac
March 21, 2002
Submitted in partial fulfillment
Of the requirements of
CMPS 374-Fundamentals of Software Engineering
Table of Contents
1. Introduction 1
1.1. Purpose 1
1.2. Scope of Project 1
1.2. Glossary 2
1.3. References 4
1.4. Overview of Document 4
2. Overall Description 6
2.1. System Environment 6
2.2. Functional Requirements Definition 11
2.3. User Interface Specification 27
2.4. Non-Functional Requirements 28
2.5. System Evolution 30
3. Requirements Specification 31
3.1. External Interface Requirements 31
3.2. Functional Requirements 32
3.3. Detailed Non-Functional Requirements 44
Index 45
1. Introduction
1.1. Purpose
The purpose of this document is too provide a concise overall description of the functionality and anticipated constraints of The Student Communication and Tracking System, developed for the University of Scranton in Pennsylvania. This document will discuss the scope of the project at hand and will further specify the chosen system environment as well as the anticipated user interfaces for the system. Additionally, special considerations regarding the potential evolution of the system as well as both functional and non-functional requirements will be identified and discussed. The expected audience of this document will be the University of Scranton’s administration, faculty members, classroom instructors and Department of Public Safety officials. It is expected that this document will also serve as a viable reference for the software engineers and computer system specialists that are implementing The Student Communication and Tracking System at the University of Scranton in Pennsylvania.
1.2. Scope of Project
The scope of the project can be defined in terms of the documentation and development of a student communicator and
References: Martin, Dennis S. “Software Requirements Specification: Fall 2001 Edition." Computing Sciences, University of Scranton, March 17, 2002. . Martin, Dennis S. "General Format for Reports: Fall 2001 Edition." Computing Sciences, University of Scranton, March 17, 2002. Systran