22-07-2014, 04:44 PM
Software Requirements Specification
Software Requirements.doc (Size: 48 KB / Downloads: 327)
Introduction
This software is being developed to for customer Xuan Gu, an employee for the CISE Department at the University of Florida. TA1 is part of a four-part project consisting of a Faculty, Admin, TA1 and TA2. The TA1 interface will allow the user to edit the number of TA slots for a particular course as well as assign/update TA applicant categories. There will also be a secure login before any of these interfaces are accessible.
Project Scope
The scope of this project includes our group of developers assisted by our customer, Xuan. The scope thus far has been the completion of the basic interfaces that will be used to build the system. The database used, has been set up and given the necessary permissions. The constraints felt thus far by the group have only been our weekly story cards, the end-to-end side of the interface, and our first release, scheduled for February 11, 2004
Overall Description
Product Perspective
The TA1 Project is a new product that is part of a larger, more complete product for our customer. It will provide the faculty a way of viewing all of the TA’s information that is necessary in order to make a decision on every TA’s status.
Product Features
This project has three pages that are part of TA1, which is part of the larger product. The first page is a login interface that will only allow access from the proper users. The second page displays the available classes based on a certain semester and the course enrollment for a particular class. The third and final page displays information about TA’s, their status, and any special notes that might’ve been posted about them
System Features
Secure Login to interface
3.1.1 Description and Priority
This feature will give the user a secure and simple login screen. It is based on professor Cubert’s exclusionary principle. This means rather than creating try catches for a handful of error types, it just has only a handful of available and possible inputs, to prevent any improper logging in, which might cause unexpected errors, and therefore limiting the system’s capabilities.
3.1.2 Stimulus/Responses Sequences
It will consist of two basic fields, Username and Password. There are two buttons: Login and Lost or Forgot Password. Login will submit the entered data for approval followed by access, and the forgot password will direct the user to access his/her password which has been forgotten.
3.1.3 Functional Requirements
The most important function is to only grant access to users that are listed in the database. The customer will provide the information on who will be allowed access. To implement the security, the web page must check the database to see if the Username and Password are valid. If they are not, the user will receive an “Invalid
Web-based interface for editing TA slots
3.2.1 Description and Priority
This feature will allow the user to edit the number of TA slots for a specific course. The user will be given a list of course numbers and names for a given semester. They will also be provided with the number of students enrolled in each specific class.
3.2.2 Stimulus/Responses Sequences
This interface will consist of basic fields for the user to enter information. Also, information about each person in the database that is listed will be shown if the mouse is highlighting a name for one second. This helps alleviate some time when the user is searching for data because it lessens the usage of the submit button because the data has already been found.
Additionally, once logged in, upon hitting the back button and reentering the site will not call for another log in screen. It will therefore take you to the following page of options.
3.2.3 Functional Requirements
To use this interface there will be many functional requirements. The main function will use PHP to pull the course information off of the database
Web-based interface to assign/update TA info
3.2.1 Description and Priority
This feature will not only provide the user with the general information on all the applicants, but also allow them to assign and update the TA categories. The user will be given a list of names and UFID’s of all the applicants to their courses. They will also be given the ability to sort the applicants in order of UFID or alphabetically by their last names.
3.2.2 Stimulus/Responses Sequences
The user will be able to change the status of the applicants as needed.
3.2.3 Functional Requirements
This interface will depend mostly on retrieving information from the database. PHP will be integrated into the HTML and will retrieve needed information for the interface.
The site will be xhtml1.1 and css compliant