[UOM Web Accessible Database System]
ID No : 0700165
========================================================================
Software Requirements Specification
Version 1.0
UOM Web Accessible Database
Arshad
========================================================================Table of Contents
1.0. Purpose
1.1. Introduction
1.2. Scope
1.3. Glossary
1.4. References
1.5. Document overview
2.0. Overall description
2.1. System environment
2.2. Functional requirements definitions
2.3. Use cases
2.3.1. Use Case: Access UOM Home Page
2.4. Non-functional requirements
3.0. Requirement specifications
3.1. External interface specifications
3.2. Functional Requirements
3.2.1. Access UOM Home Page
3.2.2. Survey
3.3. Detailed non-functional requirements
3.4. System Evolution
4.0. Index
1.0. Introduction
1.1 Purpose.
This Software Requirements Specification provides a complete description of all the functions and specifications of the University of Mauritius (UOM) Web Accessible Database. The expected audience of this document is the Faculty of Engineering, including the department of Computer Science who will use this system and the developer. It will also serve as a reference for other students.
1.2. Scope
The University of Mauritius (UOM) Web Accessible Database [UOMWAD] is designed to run on the departmental server (CSE server) and to allow UOM students to fill out a survey form. The data will be held in an Access database on the departmental server.
1.3. Glossary
Term | Definition |
UOM student | |
BDE | Borland Database Engine |
CI | Configuration Item |
CSE | Computer Science & Engineering |
Html | Hyper text markup language |
IEEE | Institute of Electrical and Electronic Engineers |
SCMP | Software Configuration Management Plan |
SDD | Software Design Document |
SEI | Software Engineering Institute |
SQAP | Software Quality Assurance Plan |
SRS | Software Requirements Specification |
Survey | Form filled out and submitted by an UOM student. |
Web Site | A place on the world wide web |
1.4. References
[IEEE] The applicable IEEE standards are published in “IEEE Standards Collection,” 2001 edition.
[Bruade] The principal source of textbook material is “Software Engineering: An Object- Oriented Perspective” by Eric J. Bruade (Wiley 2001).
1.5. Document overview
The remainder of this document is two chapters, the first providing a full description of the project for the owners of CSE department. It lists all the functions performed by the system. The final chapter concerns details of each of the system functions and actions in full for the software developers’ assistance. These two sections are cross-referenced by topic; to increase understanding by both groups involved.
The UOMWAD encompasses numerous files and information from the UOM Database, as well as files on the department server system. This system will be completely web-based, linking to UOMWAD and the remote web server from a standard web browser. An Internet connection is necessary to access the system.
2.1. System environment
The UOMWAD web site will be operated from the departmental server (CSE server). When an UOM student connects to the University Web Server, the University Web Server will pass the UOM student to the Departmental Server. The Departmental Server will then interact with the UOM Database through BDE, which allows the "Windows-type" program to transfer data to and from a database
2.2. Functional requirements definitions
Functional Requirements are those that refer to the functionality of the system, i.e, allow UOM students to fill out a survey form.
2.3. Use cases
The system will consist of CSE/UOM Home page.
It is used is to fill out a survey. The questions on the survey will be created by a designated faculty member. The survey will ask the UOM student questions concerning their degree, job experience, how well their education prepared them for their job, and what can the CSE department do to improve itself. This information will be retained on the CSE departmental server and an e-mail will be sent to the designated faculty member.
All pages will return the student to the UOM Home Page.
2.3.1. Use Case: Access CSE Home Page
Brief Description:
The Departmental Web Server is waiting on an UOM student to connect.
Initial step-by-step description:
For this use case to be initiated, the UOM student must be connected to the Internet and connected to the University Web Server.
1. The student connects to the University Web Server.
2. The student selects the CSE link on the UOM home page.
3. The University Web Server passes the student to the CSE Home Page.
[Reference SRS 3.2.1]
2.3.2. Use Case: UOM student Chooses Survey
Brief Description:
The UOM student chooses to fill out a survey.
Initial step-by-step description: For this use case to be initiated the UOM student must be connected to the Internet and is on the CSE Home Page.
1. The UOM student selects the “Fill out a survey” link.
2. The CSE Departmental Server provides the survey form.
3. The UOM student fills in the form.
4. The UOM student clicks submit.
5. The CSE Departmental Server retains information in the database & designated faculty member will be notified.
6. The CSE Departmental Server returns the student to the UOM Home Page.
[Reference SRS 3.2.2]
2.4. Non-functional requirements
There are requirements that are not functional in nature. Specifically, these are the constraints the system must work within.
The web site must be compatible with Netscape, Mozilla and Internet Explorer web browsers. This system will use the same type of Internet security presently being used by University of Mauritius.
3.0. Requirement specifications
3.1. External interface specifications
None
3.2. Functional Requirements
3.2.1. Access CSE Home Page
Use Case Name: | Access UOM Home Page |
Priority | Essential |
Trigger | Menu selection |
Precondition | UOM student is connected to the Internet and is on the University Web Server (UOM Home page) |
Basic Path | 1. University Web Server sends the UOM student to the CSE Departmental Server. 2. The CSE Departmental Server presents the student with the CSE Home Page. |
Alternate Path | N/A |
Postcondition | The student is on the CSE Home Page |
Exception Path | If there is a connection failure the CSE Departmental Server returns to the wait state |
Other | |
Reference | SRS 2.3.1 |
3.2.2. Survey
Use Case Name: | Survey |
Priority | Essential |
Trigger | Selects |
Precondition | The student is connected to the Internet and on the CSE Home Page |
Basic Path | 1. The CSE Departmental Server presents the student with a survey form. 2. The UOM student fills in the form and click submit 3. The CSE Departmental Server checks to see if all required fields are not empty. 4. If the required fields are not empty, the Departmental Server creates a new record in then Survey Table of the UOM Database. 5. If any of the required fields are empty, the CSE Departmental Server returns a message and returns the student back to the Survey form. 6. The CSE Departmental Server returns the student to the UOM Home Page at the end. |
Alternate Path | N/A |
Postcondition | The survey record is created in the Survey Table of the UOM Database. |
Exception Path | 1. If the connection is terminated before the form is submitted, the fields are all cleared and the CSE Departmental Server is returned to the wait state. |
Other | |
Reference: | SRS 2.3.2 |
3.3. Detailed Non-Functional Requirements
Attribute Name | Attribute Type | Attribute Size |
LastName*# | String | 30 |
FirstName*# | String | 30 |
MaidenName*# | String | 30 |
Address1*# | String | 50 |
Address2# | String | 50 |
City*# | String | 30 |
State*# | String | 2 |
Zip*# | Int | 6 |
Year*# | Int | 4 |
AdditionalDegrees# | String | 50 |
Spouse# | String | 30 |
Children# | String | 50 |
CurrentEmployment# | String | 50 |
EmailAddress# | String | 20 |
ReceiveEmails#^ | Boolean | 1 |
Password*#^ | String | 10 |
EntireRecordVisible*^ | Boolean | 1 |
Fields marked with a ‘#’ can be visible or not visible and is determined by the UOM student. Fields marked with a ‘^’ are never visible to anyone other than the UOM student.
The questions that are used on the survey form will be initially created by a designated faculty member.
The questions will be stored in the Question Record of the Survey Table of the UOM Database. The answers to these questions will be stored in a record in an Answers record in the Survey Table of the UOM Database.
Hardware:
CSE Departmental Server & UOM Web Server
Operation System:
Window 98 or above
Internet Connection:
Existing telephone lines / LAN
Code Standard:
The web pages will be coded in html by using Front Page. The forms will be done in Active Server Pages (ASP 3.0).
The connection to the UOM Database will be done with Windows BDE.
Each page of the web site will be fully documented.
Performance:
The system should generate the records in the appropriate table of the
UOM Database 100% of the time
3.4. System Evolution
In the future this system will be updated to allow students from the Humanities Department to join the survey. A report generated by the system concerning the responses to the survey could be another addition to the UOMWAD in the future.
No comments:
Post a Comment