and System Software Requirements Definition (SSRD)
Student Progress Web Application
Team 8
NAME Ashish Singh Ritesh Taunk Amarkanth Ranganamayna Ritesh Kothari Patrick Stevens Yue Chen Mike Oppenheim
ROLE Project Manager Developer V&V Developer V&V Mentor Client (Manual Arts High School)
EMAIL [e-mail] [e-mail] [e-mail] [e-mail] [e-mail] [e-mail] [e-mail]
SSRD_IOC_S07B_T08_v5.1
i
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
Version History
SSRD_IOC_S07_T8_v5.1
ii
Version Date: 03/31/07
System and Software Requirements Definition (SSRD) Date Author Amarkanth Ranganamay na Ritesh Taunk Versio n Changes made Rationale
Version 5.1
10/04/06
1.0
10/11/06
Amarkanth Ranganamay na Ritesh Taunk Amarkanth Ranganamay na
1.1
System and Software Using original template Requirements Definition from LeanMBASE v1.6 to for the "Student Progress apply with the Web Application" requirements for the project Development of the Added Sections 5, 6, 7 and complete SSRD document 8 to the SSRD document for LCO Draft. Added Missing information All changes are made based on the mistakes to section 1.1 pointed out by the IVV Removed the project members and the TA. requirement, PR-13 from section 2.5. Added missing terms in the Glossary as pointed out by the IVV members CR-7, CR-8 and CR-9 Capability requirements have been modified as mentioned by mentioned by the IVVers CR-10 Capability requirement's associated win-condition has been changed from W27 to W28. Removed Level of Service requirement, LOS-2 from Section 5 Added a new section called `Glossary' as section 8.1 Added the implicit course related development tools to section 2.2.1 Added missing operational states to section 6 All changes are made based on the mistakes pointed out by the IVV members and the Professors, TA's (during the LCO ARB Presentation)
10/16/06
2.0
10/23/06
Amarkanth Ranganamay na
2.1
SSRD_IOC_S07_T8_v5.1
iii
Version Date: 03/31/07
System and Software Requirements Definition (SSRD) Date Author Amarkanth Ranganamay na Versio n Changes made Rationale
Version 5.1
11/06/06
3.0
Made changes to the description of project requirement, PR-10 in Section 2.1. Missing Information has been added to System Requirement SR-3, section 4.1. Made changes to the Capability requirements All TBD's have been resolved. Corrections have been made to the operational modes of the system. Made changes to the Project Requirements. Removed all the design decisions that were mistakenly added as the project requirements Made necessary changes to section 1.1 and section 1.2 Made changes to Section 2.3, Section 3, Section 4 Made necessary changes to SSRD Section 1.1, Section 3 and Section 6
All Changes are made as suggested by the IVV members.
11/20/06
Amarkanth Ranganamay na
3.1
All changes are made as suggested by the TA
11/27/06
Amarkanth Ranganamay na
3.2
All changes are made as suggested by the oncampus developers and the IV & V members
02/02/07
Amarkanth Ranganamay na
5.0
LCA and final Semester Made changes suggested by VV. Made changes suggested by the TA and VV
03/31/07
Amarkanth Ranganamay na
5.1
SSRD_IOC_S07_T8_v5.1
iv
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
Table of Contents
SYSTEM AND SOFTWARE REQUIREMENTS DEFINITION (SSRD).............................I STUDENT PROGRESS WEB APPLICATION...................................................................I VERSION HISTORY..........................................................................................................II SYSTEM AND SOFTWARE REQUIREMENTS DEFINITION FOR THE "STUDENT PROGRESS WEB APPLICATION"..................................................................................III DEVELOPMENT OF THE COMPLETE SSRD DOCUMENT FOR LCO DRAFT............III ALL CHANGES ARE MADE BASED ON THE MISTAKES POINTED OUT BY THE IVV MEMBERS AND THE TA.................................................................................................III ALL CHANGES ARE MADE BASED ON THE MISTAKES POINTED OUT BY THE IVV MEMBERS AND THE PROFESSORS, TA'S (DURING THE LCO ARB PRESENTATION).............................................................................................................III ALL CHANGES ARE MADE AS SUGGESTED BY THE IVV MEMBERS......................IV ALL CHANGES ARE MADE AS SUGGESTED BY THE TA...........................................IV ALL CHANGES ARE MADE AS SUGGESTED BY THE ON-CAMPUS DEVELOPERS AND THE IV & V MEMBERS...........................................................................................IV LCA AND FINAL SEMESTER..........................................................................................IV MADE CHANGES SUGGESTED BY THE TA AND VV..................................................IV TABLE OF CONTENTS....................................................................................................V TABLE OF TABLES........................................................................................................VII A.1. SSRD Overview.......................................................................................................................1 A.1.1 Status of the SSRD..................................................................................................1 A.1.2 References................................................................................................................1 A.2. Project Requirements...............................................................................................................2 A.2.1 Budget and Schedule...............................................................................................2 A.2.2 Development Requirements.....................................................................................2 A.2.3 Deployment Requirements......................................................................................4 A.2.4 Transition Requirements..........................................................................................5 A.2.5 Support Environment Requirements .......................................................................5
SSRD_IOC_S07_T8_v5.1 v Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
A.3. Capability (Functional) Requirements.....................................................................................6 A.4. System Interface Requirements.............................................................................................12 A.4.1 User Interface Standards Requirements.................................................................12 A.4.2 Hardware Interface Requirements.........................................................................13 A.4.3 Communications Interface Requirements..............................................................14 A.4.4 Other Software Interface Requirements 14 A.5. Level of Service (L.O.S.) Requirements................................................................................14 6. Versions, States and Modes.....................................................................................................15 7. Evolutionary Requirements......................................................................................................15 7.1 Project Requirements.................................................................................................15 7.2 Capability Requirements...........................................................................................16 7.3 System Interface Requirements.................................................................................16 7.4 Level of Service Requirements..................................................................................16 8. Appendix..................................................................................................................................16 8.1 Gossary......................................................................................................................16
SSRD_IOC_S07_T8_v5.1
vi
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
Table of Tables
Table 1: PR-1 Budget at most 350,000 dollars Table 2: PR-2 24 Weeks Project Schedule Table 3: PR-3 Usage of Rational Software Architect Tool Table 4: PR-4 Tools specified by CS577B Course Table 5: PR-5 UML for Design and Analysis Table 6: PR-6 Minimum Hardware Requirements Table 7: PR-7 Operating System Requirement Table 8: PR-8 Browser Requirement Table 9: PR-9 Data Exchange through Internet Table 10: PR-10 COTS Products Installation 2 2 2 3 3 3 4 4 4 5
Table 11: PR-11 User Manual..............................................................................................................5 Table 12: PR-12 Training on System Installation and System Usage Table 13: CR-1 To Provide Secure Data Transfer Table 14: CR-2 To Provide Secure Log-on for the Users/Administrator(s)/Maintainer(s) 5 6 6
Table 15: CR-3 Admission Requirements for colleges/Universities after graduating from high school.............7 Table 16: CR-4 List of classes required for Graduation Table 17: CR-5 Single Log-on for Parents/Guardians to view their Children's Records Table 18: CR-6 Tracking Users and Data Table 19: CR-7 Backing-up and Restoring of Data and performing software updates Table 20: CR-8 Support for Error Logging Table 21: CR-9 Customized Error Pages Table 22: CR-10 Print Screen Option 8 8 9 10 10 11 11
Table 23: CR-11 Administrative Functionalities ............................................................................12
SSRD_IOC_S07_T8_v5.1
vii
Version Date: 03/31/07
System and Software Requirements Definition (SSRD) Table 24: SR-1 User Friendly BiLingual Web Interface Table 25: SR-2 Look and Feel Table 26: SR-3 Screen Font Size Table 27: SR-4 Feedback Information from the Users of the system
Version 3.2 13 13 14 14
Table 28: SR-5 Help Information..............................................................................................14 Table 29: SR-6 Hardware Interface For Printer(s)..................................................................................15 Table 30: SR-7 Network Interface Card......................................................................................15 Table 31: LOS-1 Correctness requirement....................................................................................16 Table 32: LOS-2 Availability requirement......................................................................................16 Table 33: ER-1 Interaction with LAUSD Servers......................................................................................17
SSRD_IOC_S07_T8_v5.1
viii
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
A.1.
SSRD Overview
A.1.1 Status of the SSRD
Currently this is the IOC Working Set1 version of our SSRD document. This version of the SSRD document summarizes the requirements gathered from our meetings with the client as well as the win-win negotiations between the Success Critical Stakeholders of our project which included the Developers, Client, a Representative of Parents and a Representative of Students. There are no significant differences between the content of SSRD version 4.0 and the Win-Win negotiated agreements. This version of the SSRD document is prepared in accordance with the Win-Win negotiated agreements present in the Win-Win Negotiation Report Version 2.1 There are no major requirements issues that have not been finalized. The current document is version 5.1 of the IOC Working Set1 milestone System and Software Requirements Definition for the desired system.
A.1.2 References
LeanMBASE Guidelines Version 1.7 http://greenbay.usc.edu/csci577/spring2007/site/guidelines/LeanMBASE_Guideline s_V1.7.pdf LeanMBASE Template - SSRD v1.6 http://greenbay.usc.edu/csci577/spring2007/site/guidelines/LeanMBASE Version 1.6 Templates for SSRD Team 8 Project Website http://greenbay.usc.edu/csci577/spring2007/projects/team8 Easy Win-Win Negotiation Report Version 2.1, Team 8 http://greenbay.usc.edu/csci577/fall2006/projects/team8/LCO/EWW_LCA_F06a_T 08_v2.1.doc Operational Concept Description (OCD) Version 5.1 http://greenbay.usc.edu/csci577/spring2007/projects/team8/IOC/OCD_IOC_S07b_ T08_v5.1.doc
SSRD_IOC_S07B_T08_v5.1
1
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
A.2.
Project Requirements
A.2.1 Budget and Schedule
Project Requirement: Description: Priority: Win-Win Agreement(s): PR-1: Budget at most 35,000 US Dollars The budget available for the development of the project is at most 35,000 US Dollars. Must have W10 Table 1: PR-1 Budget at most 350,000 US Dollars Project Requirement: Description: PR-2: 24 Weeks Project Schedule The duration of the project is 24 weeks. So, atleast the system architecture shall be finished at the end of 12 weeks during Fall 2006 and the system shall be finished within 12 weeks during Spring 2007. Must have W9 Table 2: PR-2 24 Weeks Project Schedule
Priority: Win-Win Agreement(s):
A.2.2 Development Requirements
.2.2.1 Tools Requirements
Project Requirement: Description: Priority: Win-Win Agreement(s): PR-3: Usage of Rational Software Architect Tool The Architect (i.e, SSAD) of the system shall be using Rational Software Architect Tool for developing the use-cases diagrams for the system Must have W13 Table 3: PR-3 Usage of Rational Software Architect Tool
SSRD_IOC_S07B_T08_v5.1 2 Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
Project Requirement: Description:
PR-4: Tools specified by CS577B Course DART tool shall be used for Risk Assessment Easy win win tool shall be used for identification and prioritizing of win conditions. COCOMO II tool shall be used for effort and schedule calculations MS Project tool shall be used for Life Cycle Planning
Priority: Win-Win Agreement(s):
Must have W40 Table 4: PR-4 Tools specified by CS577A Course
.2.2.2 Language Requirements
Project Requirement: Description: Priority: Win-Win Agreement(s): PR-5: UML for Design and Analysis All the diagrams used in documenting the analysis and design of the system shall be developed using UML. Must have W13 Table 5: PR-5 UML for Design and Analysis
.2.2.3 Computer Hardware Requirements
Project Requirement: Description: Priority: Win-Win Agreement(s): PR-6: Minimum Hardware Requirements The system shall run on a Pentium-IV computer or above having a main memory (i.e, RAM) of 1GB or more. Must have W50 Table 6: PR-6 Minimum Hardware Requirements
SSRD_IOC_S07B_T08_v5.1
3
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
.2.2.4 Computer Software Requirements
Project Requirement: Description: Priority: Win-Win Agreement(s): PR-7: Operating System Requirement The system shall use Windows 2003 Advanced Server as the Operating system (i.e, Server). Should have W14 Table 7: PR-7 Operating System Requirement
Project Requirement: Description: Priority: Win-Win Agreement(s):
PR-8: Browser Requirement The system shall be able to run on Internet Explorer (IE) version 5.0 and above, Mozilla Firefox version 1.2 and above Must have W2, W16, W17, W22 Table 8: PR-8 Browser Requirement
.2.2.5 Computer Communication Requirements
Project Requirement: Description: Priority: Win-Win Agreement(s): PR-9: Data Exchange through Internet Data exchange between the web application server and the client machines shall take place through the Internet via Http protocol. Must have W2,W14,W17 Table 9: PR-9 Data Exchange through Internet
A.2.3 Deployment Requirements
Project Requirement: Description: Priority: PR-10: COTS products Installation The development team shall install the COTS products on the client's server at the time of system delivery. Could have
4 Version Date: 03/31/07
SSRD_IOC_S07B_T08_v5.1
System and Software Requirements Definition (SSRD)
Version 5.1
Win-Win Agreement(s):
W12 Table 10: PR-10 COTS Products Installation
Project Requirement: Description: Priority: Win-Win Agreement(s):
PR-11: User Manual User Manual shall be provided to the client for reference. Must have W51 Table 11: PR-11 User Manual
A.2.4 Transition Requirements
Project Requirement: Description: PR-12: Training on System Installation and System Usage At the end of the project, the development team shall provide training to the client on how to acquire, install, integrate and configure COTS products used for developing the system. The development team shall also train the client on how to use the system. Want to Have W12
Priority: Win-Win Agreement(s): Table 12: PR-12 Training on System Installation and System Usage
A.2.5 Support Environment Requirements
There are no support environment requirements for the system.
SSRD_IOC_S07B_T08_v5.1
5
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
A.3.
Capability Requirement: Priority: Description: Input(s): Source(s): Output(s):
Capability (Functional) Requirements
CR-1: To Provide Secure Data Transfer Must have The system shall provide secure data transfer between the users and the web server. No Specific input No Specific Source Accurate Information requested by a User/Administrator/Maintainer Web Browser (i.e, Client) The Client and the Server agree on the Encryption technique to be used.. The users/Administrator(s)/Maintainer(s) can trust the data that is provided by the web server and vice-versa. W3 Table 13: CR-1 To Provide Secure Data Transfer
Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Capability Requirement: Priority: Description: Input(s): Source(s): Output(s): Destination(s): Precondition(s):
Post condition(s): Win-Win Agreement(s): Table 14: CR-2 Secure Log-on for the Users/Administrator(s)/Maintainer(s)
CR-2: To Provide Secure Log-on for the Users/Administrator(s)/ Maintainer(s) Must have The system shall provide Secure Logon functionality to the Users(i.e, Students, Parents, Guardians and Counselors), Administrators and Maintainers Username and Password Provided by a user/Administrator/Maintainer User/Administrator/Maintainer User/Administrator/Maintainer logged into the system and the homepage is displayed. Web Browser (Client) The User/Administrator/Maintainer has an account to log into the system. User/Administrator/Maintainer is logged into the system W3, W30, W329
SSRD_IOC_S07B_T08_v5.1
6
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
Capability Requirement: Priority: Description:
Input(s): Source(s): Output(s):
Destination(s): condition(s):
Win-Win Precondition(s):
Post Agreement(s): Table 15: CR-3 Provide Admission Requirements for colleges/Universities after graduating from high school
CR-3: Provide Admission Requirements for Colleges/Universities after graduating from high school Must have The system shall display comparison information between a student's current credit status and the admission requirements for colleges and universities specified in the System Capability Description. Request Admission Requirements by clicking on the "Get Admission Requirements" link. User/Administrator Comparision Information between a student's current credit status and admission requirements for a specific selected College/University is displayed to the User/Administrator in tabular format. Web Browser (Client) There is a database containing the admission requirements for the colleges and universities mentioned in the system capability description. User/Administrator logs into the system The user/Administrator knows exactly how many credits he/she has to complete to get into a specific college/University W5
SSRD_IOC_S07B_T08_v5.1
7
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
Capability Requirement: Priority: Description:
CR-4: List of classes required for Graduation Want to have If a student at particular grade level has not met requirements in English, Math, Science, foreign Languages etc. The system shall provide a list of classes that he/she needs to take to satisfy the requirements.. Request List of Classes by clicking on "List of Classes" link present on his/her homepage. User/Administrator List of classes the student has to take to satisfy the admission requirements for getting into different public colleges/universities present in Los Angeles. Web Browser (Client) There is a database which contains the admission requirements for the universities/colleges mentioned in the OCD. The admission requirements are present in the database in terms of what classes need to be taken by the student. User/Administrator logs into the system The user/Administrator knows what classes student has to take inorder to meet the admission requirements for a specific school/University W5
Input(s): Source(s): Output(s): Destination(s): Precondition(s):
Post condition(s): Win-Win Agreement(s):
Table 16: CR-4 List of Classes required for Graduation Capability Requirement: Priority: Description: CR-5: Single Log-on for Parents/Guardians to view their Children's records Must have The system shall allow parents/guardians to see the status of all their children in MAHS high school using their unique account. Input(s): Parent/Guardian provides a username and password to login to the Capability CR-6: Tracking Users and Data system Requirement: Source(s): Parent/Guardian Want to Have Priority: Output(s): Information corresponding shall use athe children of the which will keep Description: The system to all timestamp mechanism parent/Guardian track of who has accessed what kind of information using the Destination(s): Web Browser (Client) and stores that data in a log file system Precondition(s): Input(s): Parent/Guardian has an account in the system Username and password provided by the Post condition(s): The parent/Guardian can view their children's information User/Administrator/Maintainer to log into the system simultaneously. User/Administrator/Maintainer Source(s): Win-Win W8 Output(s): The information accessed by the User/Administrator/Maintainer Agreement(s): along with the time at which he/she has accessed the information Table 17: CR-5 Single Log-on for Trackingin the log file view their Children's Table 18: CR-6 Parents/Guardians to is stored Users and Data Records Destination(s): Log file Precondition(s): System making use of a timestamp mechanism SSRD_IOC_S07B_T08_v5.1 Post condition(s): The8 tracking information is Version Date: 03/31/07 log file of the now present in the system. Win-Win W330 Agreement(s):
System and Software Requirements Definition (SSRD)
Version 5.1
Capability Requirement: Priority: Description: Input(s):
Source(s): Output(s):
Destination(s): Precondition(s):
CR-7: Backing-up and Restoring of data and performing software updates Must have The system shall have provide Maintainer(s) with options to back up and restore data periodically and to perform software updates Maintainer(s) clicks on the Back-up data option provided on the user interface by the system. Maintainer(s) clicks on the Restore data option provided on the user interface by the system. Maintainer(s) clicks on the "Update System Softwares" option provided on the user interface to the Maintainer(s) of the system. Maintainer(s) Data is backed-up(i.e, written or copied) to external media Data is restored from the external device into the system Software updates have been successfully performed External Media ( Ex : Backup Tapes, DVD's etc..), System There are external media to which the data can be backed-up. The system can read the external media There are new updates available for the software present on the system. Maintainer(s) is logged into the system The system data is now available available on the external media to which the system data was backed-up. All the softwares present on the system are upto date. The data is restored from the backup(i.e, external device) into the system
Post condition(s):
Win-Win Agreement(s):
W328
Table 19: CR-7 Backing-up and Restoring of Data and performing software updates Capability Requirement: Priority: Description: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s): Table 20: CR-8for Error Logging Logging CR-8: Support Support for Error Must have If there is an error in the system such as automatic system shut down, the system shall provide error/exception logging Current state/error of the system Memory of the system. Information about the error/exception is saved to the Log file. Log file There is an error in the system. The current state/error of the system is stored in log file. W26
9 Version Date: 03/31/07
SSRD_IOC_S07B_T08_v5.1
System and Software Requirements Definition (SSRD)
Version 5.1
Capability Requirement: Priority: Description:
CR-9: Customized Error Pages Should have The System shall handle exceptions such as unavailable server by displaying an error page to the user e.g. if the server goes down suddenly then the system should not show a blank blue screen but give a message "could not contact the system. Please try again later" User/Administrator/Maintainer request for an unavailable page/resource OR User/Administrator/Maintainer perform an invalid operation on the system Web Server, Hardware and Infrastructure Appropriate Error page is displayed to the user Web Browser (Client) An exception has occured Based on the exception that occurred, an error page is displayed to the user. W27 Table 21: CR-9 Customized Error Pages
Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Capability Requirement: Priority: Description: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post condition(s): Win-Win Agreement(s):
Table Print Screen Option CR-10: 22: CR-10 Print Screen Option Must have The system's User interface shall provide an option for printing the current screen in a printable format. User/Administrator/Maintainer clicks on the print option to print the current screen. User/Administrator/Maintainer Printer prints the current screen that is submitted to it by the User/ Administrator/Maintainer. Printer There is a printer connected to the user's/Administrator's/Maintainer's system to take the printout The User/Administrator/Maintainer has the hard copy of the screen submitted by him/her to the printer W28
SSRD_IOC_S07B_T08_v5.1
10
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
Capability Requirement: Priority: Description:
CR-11: Administrative Functionalities Must have The system shall provide administrator(s) with the capability of importing data from the LAUSD servers, add users and delete users, delegation of administrative rights to maintainers and assigning maintainer(s) for the system. Request for performing administrative functionalites User/Maintainer(s) New User/Maintainer is added to the system, Certain selected existing User(s)/Maintainer(s) are removed from the system and the required data is imported from LAUSD servers to the MAHS internal servers. Certain maintainer(s) are given administrative rights by the administrator if required System and User/Maintainer Administrator is logged into the system and there is a need to perform data import. New user gets added to the system, certain users are deleted from the system and the data that is currently available on the LAUSD servers is now available on the internal servers of MAHS. Certain maintainers can now perform administrative functions. W328 Table 23: CR-11 Administrative Functionalities
Input(s): Source(s): Output(s):
Destination(s): Precondition(s): Post condition(s):
Win-Win Agreement(s):
SSRD_IOC_S07B_T08_v5.1
11
Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
A.4.
System Interface Requirements
A.4.1 User Interface Standards Requirements
.4.1.1 Graphical User Interface Requirements
System Interface SR-1: User Friendly Bilingual Web Interface Requirement: Description: The system shall provide a user friendly web interface and the web interface would be made available in 2 languages-English and Spanish. Also, the Users/Aministrator(s)/Maintainer(s) would be provided with an option to choose either English or Spanish language for display of the information. Priority: Must have Win-Win W2, W16, W17, W25 Agreement(s): Table 24: SR-1 User Friendly BiLingual Web Interface
System Interface SR-2: Stylistic Consistency Requirement: Description: The system shall make use of the same style guide that was used by the existing intranet system to achieve the similarity between the look and feel of the existing intranet system and the new system. Priority: Should have Win-Win W15 Agreement(s): Table 25: SR-2 Look and Feel
Table 26: System SR-3 Screen Font Size SR-3: Screen Font Size InterfaceRequirement: Description: The system shall allow the users to increase or decrease the screen font size. Priority: Should have Win-Win W21 Agreement(s):
SSRD_IOC_S07B_T08_v5.1 12 Version Date: 03/31/07
System and Software Requirements Definition (SSRD)
Version 5.1
System Interface SR-4: Feedback Information from the Users of the system Requirement: Description: The system shall allow the users to email the webmaster(i.e, Administrator) via the web based interface The system's web interface shall include an email link to school's counselor in case the students/parents/guardians want to ask a question to the counselor Priority: Should have Win-Win W19, W23, W24 Agreement(s): Table 27: SR-4 Feedback Information from the Users of the system
System Interface SR-5: Help Information Requirement: Description: The system shall provide context sensitive help for each item/elemen...