and System Software Requirements Definition (SSRD)
Version 3.8
System and Software Requirements Definition (SSRD)
Proctor and Test Site Tracking System
Team # 15
Name Mingoo Kim Heeseo Chae Soojin Kim Maged Boctor
Role Project Manager ([e-mail]) Operational Concept Engineer ([e-mail]) Prototype Manager ([e-mail]) IV&V ([e-mail])
SSRD_LCA_F08b_T15_V3.8.doc
i
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Version History Date 10/08/07 10/08/07 10/09/07 10/09/07 10/10/07 Author Lata Mantha Mingoo Kim Sudeep Red Mingoo Kim Sundeep Veguru Sudeep Reddy Soojin Kim Sudeep Reddy Mingoo Kim Sudeep Reddy Sudeep Reddy Heeseo Version 0.6 0.7 0.8 0.9 1.5 Changes made Original template for use with LeanMBASE v1.9 Corrected Errors Added sections 3&4 Reviewed and revised Final Review Rationale Initial draft for use with LeanMBASE v1.9 Update requirements in detail Added the Capability and LOS Requirements Pre final review Updated LOS requirements and made necessary corrections for the final draft Prepared for LCO Draft Review for LCO Draft Prepared for LCO Package
10/19/07 10/19/07 10/29/07
1.6 1.6 2.0
Revised Corrected errors and document format Updated the errors in the document incorporating the IV and V feedback Corrected Errors LCO package comments and IV &V Feedback incorporated Incorporated LCA Draft Feedback and LCA ARB Feedback Insert CR-18
11/05/07 11/27/07 12/10/07
2.1 3.0 3.2
Evaluation LCO Package Prepared for LCA Draft Prepared for LCA Package
02/08/08
3.8
RLCA
SSRD_LCA_F08b_T15_V3.8.doc
ii
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Table of Contents
SYSTEM AND SOFTWARE REQUIREMENTS DEFINITION (SSRD)......................................... I VERSION HISTORY ...................................................................................................................... II TABLE OF CONTENTS ................................................................................................................ III TABLE OF TABLES....................................................................................................................... V 1. SSRD Overview ................................................................................................................................... 1
1.1 Status of the SSRD ....................................................................................................... 1 1.2 References..................................................................................................................... 2
2. Project Requirements ....................................................................................................................... 3
2.1 2.2 2.3 2.4 2.5
Budget and Schedule................................................................................................. 3 Development Requirements...................................................................................... 4 Deployment Requirements........................................................................................ 8 Transition Requirements........................................................................................... 8 Support Environment Requirements......................................................................... 8
3. Capability (Functional) Requirements................................................................................................ 10 4. System Interface Requirements........................................................................................................... 19
4.1 User Interface Standards Requirements...................................................................... 19 4.2 Hardware Interface Requirements .............................................................................. 19 4.3 Communications Interface Requirements.................................................................. 19 4.4 Other Software Interface Requirements..................................................................... 19
SSRD_LCA_F08b_T15_V3.8.doc iii VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
5. Level of Service (L.O.S.) Requirements ............................................................................................ 22 6. Evolutionary Requirements ................................................................................................................ 24
6.1 Project Requirements .................................................................................................. 24 6.2 Capability Requirements............................................................................................. 24
7.Version, States & Modes ..................................................................................................................... 26 8.Glossary ............................................................................................................................................... 26
SSRD_LCA_F08b_T15_V3.8.doc
iv
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Table of Tables
Table 1: PR-1 Inception and Elaboration Phase to be completed in Fall 2007 semester........................................ 3 Table 2: PR-2: Construction and Transition Phase to be completed in Spring 2007 semester ............................... 3 Table 3: PR-3: Budget Constraint ......................................................................................................................... 3 Table 4: PR-4 Use of Web Designing Tools ........................................................................................................... 4 Table 5: PR-5 Wiki win-win tool............................................................................................................................ 4 Table 6: PR-6 Use of Uml modelling tools ............................................................................................................. 4 Table 7: PR-7 coldfusion Markup language .......................................................................................................... 5 Table 8: PR-8 querying language .......................................................................................................................... 5 Table 9: PR-9 Language for front end development .............................................................................................. 5 Table 10: PR-10 No ADDITIONAL Hardware IS Required .................................................................................. 6 Table 11: PR-11 Database Server .......................................................................................................................... 6 Table 12: PR-12 COLDFUSION MX Server ......................................................................................................... 6 Table 13: PR-13 MS-SQL Database ...................................................................................................................... 7 Table 14: PR-14 BROWSER Specification ............................................................................................................ 7 Table 15: PR-15 Internet protocol ......................................................................................................................... 7 Table 17: PR-16 Installation of the final product .................................................................................................. 8 Table 18: PR-17 user Training .............................................................................................................................. 8 Table 19: PR-18 User manual ............................................................................................................................... 8 Table 20: PR-19 Source Code documentation ....................................................................................................... 9 Table 21: PR-20 support After delivering the product............................................................................................ 9 Table 22: CR-1 Online Database Storage ............................................................................................................ 10
SSRD_LCA_F08b_T15_V3.8.doc
v
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Table 23: CR-2 ADD DATA OF TEST SITES AND PROCTORS....................................................................... 10 Table 24: CR-3 SITE TRACKING....................................................................................................................... 11 Table 25: CR-4 Proctor Selection List ................................................................................................................. 11 Table 26: CR-5 Cross Browser Compatibility ...................................................................................................... 12 Table 27: CR-6 Print Screen Option .................................................................................................................... 13 Table 28: CR-7 Proctor Schedule Online............................................................................................................. 13 Table 29: CR-8 Security ...................................................................................................................................... 14 Table 30: CR-9 User Authentication.................................................................................................................... 14 Table 31: CR-10 Proctor Change Schedule ......................................................................................................... 15 Table 32: CR-11 Restrict Change Schedule ......................................................................................................... 16 Table 33: CR-12 Manage Proctor Information.................................................................................................... 16 Table 34: CR-13 Email Notification .................................................................................................................... 17 Table 35: CR-14 Calendar Interface.................................................................................................................... 18 Table 36 : CR-15 Proctor Scheduling .................................................................................................................. 18 Table 37: CR-16 Manage Exam Schedule ........................................................................................................... 19 Table 38: CR-17: Application Recovery............................................................................................................... 19 Table 39: SR-1 calendar Interface....................................................................................................................... 19 Table 40: SR-2 Space for anouncements ............................................................................................................. 21 Table 41: SR-3 Help information ........................................................................................................................ 21 Table 42: SR-4 Hardware Interface for Printer(s) ............................................................................................... 21 Table 43: SR-5 ODBC CONNECTOR ................................................................................................................. 22 SSRD_LCA_F08b_T15_V3.8.doc vi VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Table 44: LOS-1: Reliability ................................................................................................................................ 22 Table 45: LOS-2 system scalability ...................................................................................................................... 23 Table 46: LOS-3 Response Time.......................................................................................................................... 23 Table 47: ER-1 Proctor Pay Estimate .................................................................................................................. 24 Table 48: ER-2 Proctor History ........................................................................................................................... 26
SSRD_LCA_F08b_T15_V3.8.doc
vii
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
1. SSRD Overview
1.1 Status of the SSRD
System and Software Requirements Definition, in short SSRD, is the LCA Draft version where all the requirements of a system are to be documented. The main purpose of SSRD is to describe the functional requirements of the Proctor & Test Site Tracking System (PTTS) for the City of LA. Basically, we summarize the behavior of the system and ensure that the win conditions of its stakeholders are well documented. The current SSRD report will give comprehensive details about the requirements gathered from the three meetings with the client, as well as the Win-Win negotiations carried out in two stages between the Success Critical Stakeholders of our project which included the Developers, Client and a Student Reviewer (IV&V). The WinWin negotiations helped us clearly define the requirements and the issues with any of the requirement have been absolved with mutual discussion carried on during the negotiations. Client feedback on the initial prototype design has also been taken into consideration and the further requirements suggested by the client have been incorporated in the current document. The current version also reflects the feedback given at the end of the inception phase. Few requirements have been removed after 2nd round of WinWin negotiations. The document has been made in sync with updated Operational Concept Description (OCD) document. . This version of the SSRD document is prepared in accordance with the Win-Win negotiated agreements present in the Updated Win-Win Negotiation Report. There are no major requirements issues that have not been finalized.
SSRD_LCA_F08b_T15_V3.8.doc 1 VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
1.2 References LeanMBASE Version 1.9 Templates for SSRD: http://greenbay.usc.edu/csci577/fall2007/site/guidelines/LeanMBASE_v1.9_template s_for_SSRD.doc Operational Concept Description: http://greenbay.usc.edu/csci577/fall2007/projects/team15/LCA/OCD_LCO_F07a_T1 5_v2.6.doc Wiki Win-Win Report: http://greenbay.usc.edu/csci577/fall2007/projects/team15/LCO/WikiWinWin_Report _F07_T15.doc Wiki Win-Win web site: http://pattaya.usc.edu/twiki/bin/view/CS577Project15/WebHome Initial Prototype: http://greenbay.usc.edu/csci577/fall2007/projects/team15/LCO/Prototype_LCO_F07_ t15.doc Client Meeting Notes: http://greenbay.usc.edu/csci577/fall2007/projects/team15/Team15a/CMN/index.html Team 15 Project Website
http://greenbay.usc.edu/csci577/fall2007/projects/team15
Team 15 New Project Website http://greenbay.usc.edu/csci577/spring2008/projects/team15/
SSRD_LCA_F08b_T15_V3.8.doc
2
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
2. Project Requirements 2.1
Budget and Schedule
Table 1: PR-1 Inception and Elaboration Phase to be completed in Fall 2007 semester Project PR-1: Inception and Elaboration Phase should be completed in Requirement: Fall 2007 semester. Description: Priority: Win-Win Agreement(s): The Inception and Elaboration Phase of the proposed system should be completed during Fall 2007 semester (12 weeks) M (Must have) WinC1.
Table 2: PR-2: Construction and Transition Phase to be completed in Spring 2007 semester Project PR-2: Construction and Transition Phase to be completed in Requirement: Spring 2008 semester (12 weeks) Description: Priority: Win-Win Agreement(s): The system should be implemented with all the requirements by the end of Spring 2007 semester M (Must have) WinC1.
Table 3: PR-3: Budget Constraint Project PR-3: Budget Constraint Requirement: Description: Priority: Win-Win Agreement(s): The initial cost of the system is zero as maximum development would be done open source platforms. Any cost incurred on the system will depend on any, if any, COTS software used. S (Should have) WinC38.
SSRD_LCA_F08b_T15_V3.8.doc
3
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
2.2
Development Requirements
2.2.1 Tools Requirements TABLE 4: PR-4 USE OF WEB DESIGNING TOOLS Project Requirement: Description: Priority: Win-Win Agreement(s): PR - 4: Use of Web Designing Tools Web Designing tools like Dreamweaver, Flash and Photoshop would be used for designing the Interface. C (Could have) WinC10.
TABLE 5: PR-5 WIKI WIN-WIN TOOL Project Requirement: Description: Priority: Win-Win Agreement(s): PR - 5: Wiki Win-Win tool Wiki Win-Win Tool must be used when negotiating win conditions, sorting out the issues, and finding options. M (Must have) WinC47.
TABLE 6: PR-6 USE OF UML MODELLING TOOLS Project Requirement: Description: Priority: Win-Win Agreement(s): PR-6 : UML modeling tools IBM Rational Software Modeler shall be used to draw UML Diagrams. M (Must have) WinC47
SSRD_LCA_F08b_T15_V3.8.doc
4
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
2.2.2 Language Requirements TABLE 7: PR-7 COLDFUSION MARKUP LANGUAGE Project Requirement: Description: Priority: Win-Win Agreement(s): PR-7: ColdFusion Markup Language ColdFusion Markup Language shall be used for server side scripting. M (Must have) WinC5, WinC4, WinC13.
TABLE 8: PR-8 QUERYING LANGUAGE Project Requirement: Description: Priority: Win-Win Agreement(s): PR-8: Querying Language SQL shall be used for querying the backend database from the frontend C (Could have) WinC4.
TABLE 9: PR-9 LANGUAGE FOR FRONT END DEVELOPMENT Project Requirement: Description: Priority: Win-Win Agreement(s): PR-9: Language for front end development HTML and JavaScript shall be used for front end development C (Could have) WinC10.
SSRD_LCA_F08b_T15_V3.8.doc
5
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
2.2.3 Computer Hardware Requirements TABLE 10: PR-10 NO ADDITIONAL HARDWARE IS REQUIRED Project Requirement: Description: Priority: Win-Win Agreement(s): PR-10: No Additional Hardware is Required The existing system must comfortably run the software and should not require any extra hardware. M (Must have) WinC39.
TABLE 11: PR-11 DATABASE SERVER Project Requirement: Description: Priority: Win-Win Agreement(s): PR-11: Database Server The system should have a database server to run the MS-SQL database M(Must have) WinC4, WinC9.
2.2.4 Computer Software Requirements TABLE 12: PR-12 COLDFUSION MX SERVER Project Requirement: Description: Priority: Win-Win Agreement(s): PR - 12: ColdFusion MX Server ColdFusion MX Server must be running on the web server. M (Must have) WinC5
SSRD_LCA_F08b_T15_V3.8.doc
6
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
TABLE 13: PR-13 MS-SQL DATABASE Project Requirement: Description: Priority: Win-Win Agreement(s): PR - 13: MS-SQL database MS-SQL database must be used for the proctor database M (Must have) WinC4.
TABLE 14: PR-14 BROWSER SPECIFICATION Project Requirement: Description: Priority: Win-Win Agreement(s): PR - 14: Browser Specification The system should be able to operate properly in either of the Browsers (Internet Explorer 6 and 7, or Firefox 2) . S(Should have) WinC6
2.2.5
Computer Communication Requirements
TABLE 15: PR-15 INTERNET PROTOCOL Project Requirement: Description: Priority: Win-Win Agreement(s): PR - 15: Internet Protocol The System being a web based application must use the internet protocol (e.g., HTTP protocol which is used by web browsers) M (Must have) WinC6.
SSRD_LCA_F08b_T15_V3.8.doc
7
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
2.3 Deployment Requirements TABLE 16: PR-16 INSTALLATION OF THE FINAL PRODUCT Project Requirement: Description: Priority: Win-Win Agreement(s):
PR 16: - Installation of the final product The CSCI 577 project team will install the new system on the clients hardware. M (Must have) WinC40.
2.4 TransitionRequirements TABLE 17: PR-17 USER TRAINING Project Requirement: PR - 17: User Training At the end of the project, the development team shall train the users of the system who are working at the City of LA Central Division. M (Must have) WinC41.
Description:
Priority: Win-Win Condition
2.5 Support Environment Requirements TABLE 18: PR-18 USER MANUAL Project Requirement: Description: Priority: Win-Win Agreement(s): PR - 18: User Manual A User Instructional Manual shall be provided M (Must have) WinC42.
SSRD_LCA_F08b_T15_V3.8.doc
8
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
TABLE 19: PR-19 SOURCE CODE DOCUMENTATION Project Requirement: Description: Priority: Win-Win Agreement(s): PR - 19: Source Code documentation The systems source code must be fully documented. It should be well structured and must have clear comments. M (Must have) WinC26.
TABLE 20: PR-20 SUPPORT AFTER DELIVERING THE PRODUCT Project Requirement: Description: Priority: Win-Win Agreement(s): PR 20: Support After Delivering the Product After the system is completely delivered, the system must be maintained by the City of LA IT Department. M (Must have) WinC48.
SSRD_LCA_F08b_T15_V3.8.doc
9
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
3. Capability (Functional) Requirements
TABLE 21: CR-1 ONLINE DATABASE STORAGE
Capability Requirement:
CR-1: ONLINE DATABASE STORAGE The system shall have a stable online database. Each time the schedule of the proctors changed, it should be updated in the database as well. M (Must have) Proctors Schedule Proctor or Proctor Manager Tables on Database with data MS-SQL database The Database fields shall be properly integrated with the forms Database shall maintain all data WinC4
Description:
Priority: Input(s) Source(s) Output(s) Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Table 22: CR-2 ADD DATA OF TEST SITES AND PROCTORS Capability Requirement:
CR-2: ADD DATA OF TEST SITES AND PROCTORS The System shall allow the Administrator to add data about the Test Sites and the Proctors. He should also be able to update and modify the data. The test sites information includes building address, room capacity, and etc. M (Must have) Test Sites and Proctors Data Proctor Manager Page conforming that all the data has been updated
Description: Priority: Input(s) Source(s) Output(s)
SSRD_LCA_F08b_T15_V3.8.doc
10
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Web Browser The administrator has to be logged in Database has to be online
WinC20.
Table 23: CR-3 SITE TRACKING Capability Requirement: CR-3: SITE TRACKING The system shall provide the capability to track sites. This allows the administrator to input the date and the number of students, and the system produces a list of test sites available on those dates S (Should Have) Test Sites and Proctors Data Proctor Manager Available test sites on a specific date Web Browser Complete site information must be provided None explicitly specified WinC21, WinC22.
Description:
Priority: Input(s) Source(s) Output(s) Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Table 24: CR-4 Proctor Selection List Capability Requirement: CR-4: PROCTOR SELECTION LIST The system shall provide the capability to get the list of proctors on a particular date, which allows users to check the available proctors on a specific date. S (Should Have)
Description:
Priority:
SSRD_LCA_F08b_T15_V3.8.doc
11
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Input(s) Source(s) Output(s) Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Date Proctor Manager Available List of Proctors Web Browser Entire information of the proctors must be available None explicitly specified WinC22.
Table 25: CR-5 Cross Browser Compatibility Capability Requirement: Description: CR-5: CROSS-BROWSER COMPATIBILITY
The System shall provide the capability to provide cross-browser compatibility in publishing and managing content on the website. CrossBrowser compatibility is available only between Internet Explorer 6, 7 and Mozilla FireFox 2. M(Must have) Text from User through keyboard. Users Correct Output in both browsers. User Interface Both browsers installed on users system NA WinC4
Priority: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
SSRD_LCA_F08b_T15_V3.8.doc
12
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Table 26: CR-6 Print Screen Option Capability Requirement: Priority: Description: CR-6: Print Screen Option
(M)Must have The systems User interface shall provide an option for printing the current screen in a printable format. Proctor/Proctor manager clicks on the print option to print the current screen. Proctor/Proctor Manager Printer prints the current screen that is submitted to it by the Proctor/Proctor Manager. Printer There is a printer connected to the Proctor/Proctor Manager system to take the printout The has the hard copy of the screen submitted by him/her to the printer WinC33
Input(s):
Source(s): Output(s):
Destination(s): Precondition(s):
Post condition(s): Win-Win Agreement(s):
Table 27: CR-7 Proctor Schedule Online Capability Requirement: CR-7: PROCTOR SCHEDULE ONLINE The system shall provide a capability to provide the proctors schedule online. The proctor must be able to access his schedule from anywhere using the Internet. M(Must Have) Proctors Username and Password Database The Proctors current Schedule Web Browser
Description:
Priority: Input(s) Source(s) Output(s) Destination(s):
SSRD_LCA_F08b_T15_V3.8.doc
13
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Precondition(s): Post condition(s): Win-Win Agreement(s):
The Proctor must be logged in The Proctors schedule is displayed WinC45.
Table 28: CR-8 Security
Capability Requirement: Priority:
CR -8: THE SYSTEM HAS TO BE SECURED M (Must Have) The System shall be secure; hence the Proctor information has to be secured since it provides personal information and critical information of the tests. Therefore, the requested information should be provided to the authenticated users only. The system must provide a secure login to verify the user authentication. The proctors will input their Email ID and password to login. Valid Email ID and password submitted during Registration 1) Display the Proctor information if the user is logged in
Description:
Input(s): Source(s):
Output(s): 2) Display the error message if the user is not authenticated Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s): Proctor Information page The system is properly initialized Redirected to the requested information page WinC14.
Table 29: CR-9 User Authentication Capability Requirement: Priority: CR-9: USER AUTHENTICATION M (Must Have)
SSRD_LCA_F08b_T15_V3.8.doc
14
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Description:
The system shall authenticate the User in the standalone login page. Once the user is authenticated the system must get their assigned respective privileges. System allows authorized personnel to access the system with different privileges as follows. Proctors can input their schedule and change their information. Proctor Managers can decide the exam schedules, input test sites information, proctor information, add and delete proctors, and assign proctors to specific exams. The user enter their authentication information submitted during Registration:
Input(s):
1) Email ID 2) Password
Source(s): Output(s):
The Users should have accessed to the user system interface If the supplied authentication information is valid then the user will gain access to the system The user gains access to the system, and will be directed to their respective page based on their assigned roles. The user should have already been registered The user should gain access to all the information that they are authorized to use. WinC14, WinC27.
Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Table 30: CR-10 Proctor Change Schedule Capability Requirement: Description: Priority: Input(s) Source(s) Output(s) CR-10: PROCTOR CHANGE SCHEDULE The system shall allow proctors to input their schedule online. They must be able to change and delete their schedule. M(Must have) Proctors Old schedule Database The Proctors current Schedule
SSRD_LCA_F08b_T15_V3.8.doc
15
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Web Browser The Proctor must be logged in The Proctors new schedule is updated in the database WinC45.
Table 31: CR-11 Restrict Change Schedule Capability Requirement: Description: Priority: Input(s) Source(s) Output(s) Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s): CR-11: RESTRICT CHANGE SCHEDULE The system shall provide a capability to restrict changing schedule of the proctors two weeks prior to their assigned exam date. M(Must have) Proctors schedule and the Date Database Changed schedule if possible Web Browser The Proctor must be logged in The Proctors new schedule is updated in the database WinC45.
Table 32: CR-12 Manage Proctor Information Capability Requirement: CR-12: MANAGE PROCTOR INFORMATION The System must provide a capability for an administrator to manage proctor information. He/She should be able to manually input the information of the proctors, and activate and deactivate proctors when necessary. He must also be able to assign different levels to the proctors based on the credentials.
Description:
SSRD_LCA_F08b_T15_V3.8.doc
16
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Priority: Input(s) Source(s) Output(s) Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
M(Must have) Proctors Details, which include Name, Phone, Email address, SSN, and Proctor Level Administrator Confirmation of Adding or Updating Data Web Browser Administrator must be logged in None WinC46.
Table 33: CR-13 Email Notification Capability Requirement: Description: Priority: Input(s) Source(s) Output(s) Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s): CR-13: EMAIL NOTIFICATION The System must notify the proctors who are assigned to specific exams by email. M(Must have) Proctors Schedule Database Email with Proctors Schedule Web Browser All proctors should have an email address. None WinC26.
SSRD_LCA_F08b_T15_V3.8.doc
17
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Table 34: CR-14 Calendar Interface Capability Requirement: CR-14: CALENDAR INTERFACE The System would provide a capability to provide a calendar interface for the proctors. The web interface would use a calendar component which the proctor can click and select the dates. W(Want to have) Proctors Schedule Database The Schedule on the selected date Web Browser Proctor must be logged in None WinC46.
Description:
Priority: Input(s) Source(s) Output(s) Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Table 35 : CR-15 Proctor Scheduling Capability Requirement: Description: CR-15: Proctor scheduling System should be able to facilitate scheduling of proctors based on exam schedule, proctors level, and proctors available time. M (Must Have) Exam Schedule , Proctors Available time and Proctors Level Database Matches between Proctors Schedule and Exam Timings Web Browser Schedules of exams and Proctors must exist prior the scheduling occurs Screen having names of the proctors with the schedules matched. WinC27.
Priority: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post conditions(s): Win-Win Agreement(s):
SSRD_LCA_F08b_T15_V3.8.doc
18
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Table 36: CR-16 Manage Exam Schedule Capability Requirement: CR-16: MANAGE EXAM SCHEDULE The system shall provide the capabilities like adding, deleting or updating the schedule information about an exam. The user shall have three fields to enter the exam schedule: (a) Exam Name, (b) Date and (c) Time M(Must have) Exam Timings and Schedule Administrator Confirmation that the exam schedule has been stored in the database Web Browser User must be logged in as the administrator None WinC39.
Description:
Priority: Input(s) Source(s) Output(s) Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Table 37: CR-17: Application Recovery Capability Requirement: Description: CR-18: APPLICATION RECOVERY The system should be able to handle errors and be able to recover from failure. M (Must have) Detected system failure Failure or Error Occurred during system operation Recovered system System Itself The system should detect the failures a. A log file indicated that the system has been restored with details of failure
19 VersionDate:02/08/08
Priority: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post conditions(s):
SSRD_LCA_F08b_T15_V3.8.doc
System and Software Requirements Definition (SSRD)
Version 3.8
Win-Win Agreement(s):
b. Recovered system WinC47.
Table 38: CR-18: Manager Proctor Capability Requirement: Description: Priority: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post conditions(s): Win-Win Agreement(s): CR-18: Manager Proctor Test Site and proctor are assigned M (Must have) Detected system failure Failure or Error Occurred during system operation Recovered system System Itself The system should detect the failures
4. System Interface Requirements
4.1 User Interface Standards Requirements TABLE 39: SR-1 CALENDAR INTERFACE System Interface Requirement: SR-1: Calendar Interface The system should have a calendar interface where the user can click on the dates in it. In this case, PTTS should give proctors schedule for that day. S (Should Have) WinC23.
Description:
Priority: Win-Win Agreement(s):
SSRD_LCA_F08b_T15_V3.8.doc
20
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
TABLE 40: SR-2 SPACE FOR ANOUNCEMENTS Capability Requirement: Description: SR-2: Space for Announcement
Appropriate space on the web pages should be provided to to pass out any messages to the proctors. W(Want To Have) WinC50.
Priority: Win-Win Agreement(s):
TABLE 41: SR-3 HELP INFORMATION
System Interface SR3:HelpInformation Requirement: Description: Thesystemshallprovidecontextsensitivehelpforeachitem/element in the User Interface. Also, the system shall show navigation help informationinthewebbrowsersstatusbar (M)Musthave WinC10,WinC2.
Priority: WinWin Agreement(s):
4.2 Hardware Interface Requirements TABLE 42: SR-4 HARDWARE INTERFACE FOR PRINTER(S) System Interface Requirement: Description: SR-4: Hardware Interface for Printer(s)
There shall be a hardware interface for connecting any printer to the system. This printer shall be used by the Administrator/Maintainer. (S)Should have WinC3
Priority: Win-Win Agreement(s):
SSRD_LCA_F08b_T15_V3.8.doc
21
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
4.3 Communications Interface Requirements There are no communications interface requirements as the tool we are building is web-based. 4.4 Other Software Interface Requirements TABLE 43: SR-5 ODBC CONNECTOR System Interface Requirement: Description: Priority: Win-Win Agreement(s): SR-5: ODBC CONNECTOR The System shall use ODBC interface to connect the ColdFusion application to the MS-SQL Database server S (Should Have) WinC4,WinC5.
5. Level of Service (L.O.S.) Requirements
TABLE 44: LOS-1: RELIABILITY Level of Service Requirement: Description: LOS-1:Reliability
The proposed system should be reliable 95% of the time for the Initial Operational phase. Its only downtime must be during the maintenance phase. M(Must have) The tool must be accessible for all day through the Internet except maintenance time. The proposed system should be reliable 95% of the time for the Initial Operational phase. The City of LA IT Department staff should be able to check and use the tool during their work hours
Priority: Desired Level:
Accepted Level:
Measurable:
SSRD_LCA_F08b_T15_V3.8.doc
22
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Achievable: Relevant: Specific: Win-Win Agreement(s):
By using a reliable broadband internet connection CR 2,CR 6 There are no specific requirements for the interface of the system. WinC36
TABLE 45: LOS-2 SYSTEM SCALABILITY Level of Service Requirement: Description: Priority: Desired Level: LOS-2 SYSTEM SCALABILITY
The system is able to handle at least 20 simultaneous users. M(Must have) The system can handle much more than 20 users working on the system. The system can handle 20 simultaneous users. 20 Proctors are able to login and work in the system at the same time.
Accepted Level: Measurable:
Achievable: Relevant: Specific: Win-Win Agreement(s): WinC26 There are no specific requirements for the interface of the system.
Table 46: LOS-3 Response Time LOS-3 RESPONSE TIME Level of Service Requirement: Description: The time elapsed between the user entering the input and the results being presented to the user in the form of HTML page. M(MAY have)
Priority:
SSRD_LCA_F08b_T15_V3.8.doc
23
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Desired Level: Accepted Level: Measurable: Achievable: Relevant: Specific: Win-Win Agreement(s):
The response time should be 2 seconds The response time can be 3 -5 seconds Time between entering input and results page.
There are no specific requirements for the interface of the system.
WinC46.
6. Evolutionary Requirements
6.1 Project Requirements There are no evolutionary Project Requirements. 6.2 Capability Requirements Table 47: ER-1 Proctor Pay Estimate
Evolutionary Requirement: Description: ER-1: PROCTOR PAY ESTIMATE
The System shall provide a capability to calculate the amount that the proctor has earned biweekly based on his hourly rate and the number of hours worked and can also keep a tab on the amount earned in an year. W(Want to have) Proctor Schedules ,Proctors Pay Details Administrator , Database
Priority: Input(s): Source(s):
SSRD_LCA_F08b_T15_V3.8.doc
24
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Output(s): Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Detailed Proctor Pay Estimate Web Browser Administrator must be logged in Any content must be saved in the database. WinC35.
SSRD_LCA_F08b_T15_V3.8.doc
25
VersionDate:02/08/08
System and Software Requirements Definition (SSRD)
Version 3.8
Table 48: ER-2 Proctor History
Evolutionary Requirement: Description: ER-2: PROCTOR HISTORY
The System shall provide a capability to track proctors. By clicking proctors on the list of all proctors, users can get a list of the exams that the proctor has administrated, and the list of exams scheduled. W(Want to have) Proctor Schedules Administrator , Database Detailed Proctor Info Web Browser Administrator must be logged in Any content must be saved in the database.
Priority: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post condition(s):
7. Version, States & Modes
Version This system has been developed since there are no earlier versions of the systems were made. States & Modes - The Proctor and Test Site tracking System (PTTS) Project has only one mode of operation. In this operational mode, there are two users: Proctors and Proctor Managers. Proctor Managers can add, modify, and delete information of the test sites, exams, buildings, and proctors. Also, time scheduled on a certain date and notifies it to the approved proctors.
SSRD_LCA_F08b_T15_V3.8.doc
26
VersionDate:02/08/08