You are on page 1of 30

2.

System Requirement Specification

1. Introduction to SRS 1.1 Purpose of SRS. This SRS document describes the software requirements for the Quality Assurance System built for Sirsyed University of Engineering and technology. 1.2 Scope. The SSUET is requesting proposals to build a Quality Assurance System (QAS) for their current system. This new QAS needs to be more perfect and accurate so that QAS can minimize the problems faced by the members of the SSUET. The system will be designed to provide a Web based version of the Quality assurance system in Sirsyed University. The system will have a user-friendly graphical interface and will be more cost effective compared to the current manual and less accurate Quality Assurance System. The objectives of this development effort are:

To improve the Quality Assurance System of SSUET To enhance the current Rating and quality assurance system of the SSUET An Automated Quality and Ranking system of faculty and Labs. To provide access to up to date ranking of each faculty member. To minimize the Human efforts.

1.3 References. http://www.wikipedia.com http://www.google.com http://www.cramster.com http://www.whatis.com 1.4 Overview. Chapter 2 is about SRS, the SRS is a brief description of the characteristics of the software to be built, its functions, its users, its constraints and its dependencies. Chapter 3 is about specific requirements, such as functional requirements, external interface requirements, performance requirements, and also design constraints and quality characteristics. Finally, chapter 4 includes all the supporting information, such as the Table of Contents, the Appendices, and the Index.

2. The General Description. This section describes the general factors that affect the product and its requirements. This section consists of five subsections that follow. This section does not state specific requirements. Each of the subsections makes those requirements easier to understand; it does not specify design or express specific requirements. Such detail is provided in section 3.

2.1 Product Perspective. The Quality Assurance System diagram showing the overview of the systems modules and the relationship of the system to external interfaces is presented in Figure 2.1. Figure Overview Diagram of QAS

2.1 the

the

2.2 Product Functions. This section provides a summary of the functions that software will perform. 2.2.1 Function Relationships Figure 2.2 to 2.6 depict the relationships among the functions to be implemented by the system.

Figure 2.2 QAS General Function Relationship Diagram

Figure 2.3 QAS Modify Category Diagram

Figure 2.4 QAS Manage Users Diagram

Figure 2.5 QAS Manage Labs Diagram

Figure 2.6 QAS stats and reports Diagram

2.2.2 Function Descriptions 2.2.2.1 Login Function Description: This function ensures that only authorized users gain access to the Reservation databases. An authorized user is a user who has an account on the system. Users include Teachers and students and SSUET Officials. The user must type a valid username and password to gain access. 2.2.2.2 Modify Categories Description: This function allows the Admin to show the information related to the Departments and also admin can add and delete a department and there is also an option of modification of the department 2.2.2.3 Manage Users Description: This function allows the Admin to manage and change the info and personal profile record of the user. Admin can List all the users and can add or delete a user and admin has the access to modify the user account. In modification admin can assign a department to teacher, make his public profile data and can assigned course etc. 2.2.2.4 Manage Labs Description: This function allows managing the labs. Through this function Labs can b added and added or deleted from database and can modify. In modification the admin can modify the lab type and lab department and make the profile data of the Lab. Also modify the lab staff data and his personal profile. 2.2.2.5 Manage Reports and Statistics Description: This function provides a complete and powerful function of the stats and rating. Ratings can be viewed, PDF format file can be generated through php and user receive in it email. This stats can be shown I graphical manner. Also users can comment and leave their feedback for the officials. 2.3 User Characteristics The Main users of the system will be students who rate teachers and view their up to date ratings, teachers to manage their profile and SSUET top management that access the reports, rating and graphs generated by the system as well as having veto power to administrate everything in the system. The User interface provides an easy way of using QAS to rate teachers and very interactive techniques to keep students up to date with current rating data. 2.4 General Constraints The overall rating is based upon the data submitted by student and it cannot be modified. The data of student is kept secret to make the system crystal clear and anonymous. The functional prototype should be available after 10 days of requirement gathering. Team is restricted to use third party tools to automate their modules; it may slow down the development speed.

The system will only be available on the local intranet of Sir Syed university, peoples outside university premises may not be able to use the system Current system of quality assurance is manual; QAS wants to discourage these practices.

2.5 Assumption & Dependencies Each member is rated out of 10 points, The rating by each student is limited to 1 time per teacher in a semester. The rating by each student is limited to 1 time per lab in a semester. Rating once submitted cannot be changed. Teachers are notified of their rating monthly via emails The following management reports will be available o Overall rating of department teachers o The ratio of positive & negative ratings o List of bad rating teachers per department o List of average rating teachers per department o List of good rating teachers per department Network connection may always be established SSUET will provide us with the faculty details 2.6 Dependencies The development may stop sometimes due sudden change in modules The development may stop sometimes due to need of a new software and its licensing SSUET will provide all the hardware and softwares required to run the system Our Teacher will help make arrangements with university top management, and serves as bridge between top management and us.

3. SPECIFIC REQUIREMENTS. This section of the SRS contains design requirements for the Quality Assurance system System. 3.1 Quality assurance System Functional Requirements. 3.1.1 Log In Function This function ensures that only authorized users gain access to the databases. An authorized user is a user who has an account on the system. Users include teachers and admin. The user must type a valid username and password to gain access. Logging into the system provides security and confidentiality to the system. It reduces the chance that someone can taper any individuals personal information and prevents unauthorized users Description Login: In the home page user login by using username and password. Verify Login: The user can enter the user name and password the user name and password is correct then got to main menu otherwise display message unauthorized user. The verification is done through database. Users Database: The user database consists of login records of the users who are authorized to login into backend. Main Menu: After successful login the main menu is appeared o Modify Categories: In modify categories the function allows the Admin to show the information related to the Departments and also admin can add and delete a department and there is also an option of modification of the department. o Manage Users: In manage users admin can List all the users and can add or delete a user and admin has the access to modify the user account. In modification admin can assign a department to teacher, make his public profile data and can assigned course etc. Following option is include in Modify Users. o Manage Labs: Through this function Labs can be added and added or deleted from database and can modify. In modification the admin can modify the lab type and lab department and make the profile data of the Lab.

Also modify the lab staff data and his personal profile. Following option is include in Modify Labs. o Statistics & Reports: Ratings can be viewed, PDF format file can be generated through php and user receive in it email. This stats can be shown in graphical manner. Specification Description Inputs Source Outputs Destination Precondition Post condition Side effects Data Flow Diagram Allow access to online QAS Username, password User inputs username & password Successful login, unsuccessful login None Authorized User No change to user accounts database Failures & successful logins are sent to database

3.1.2 Modify Categories This function allows the Admin to show the information related to the Departments and also admin can add and delete a department and there is also an option of modification of the department. Categories are used to organize the entire project. We can add one or more categories. Department, Courses & Designation are the parts of Category menu. Description List all department: It shows the List of all Departments which added in database and are currently present in the University. This function tells us the total registered departments in the University.

Add new department: For adding a new category or Department you just need to add a new entry to department table in database & new department will be created. This right is only for admin.

Delete department: If you want to delete any Department from university or you want to remove department from database so QAS provide function for this named as Delete Department.

Modify department: If we want some changes or edit some data we can select modify department menu. We can modify a department by making alteration in department name etc.

Specification Description Inputs Source Outputs Destination Precondition Post condition Side effects 3.1.3 Manage user: Allow User to Manage Data Add, Delete, Modify departments User selected department After categorized field show on output None Login and select the Menu New department admin None Modified/add/delete by

This function allows the Admin to manage and change the information and personal profile record of the user. Admin can List all the users and can add or delete a user and admin has the access to modify the user account. In modification admin can assign a department to teacher, make his public profile data and can assigned course etc. Description List all user: This function of list all users perform dynamically. After user login after that the user will be shown automatically the all members of selected category. The user is show with his primary key field.

A d d new user: This project (QAS) has the capability to add a user at any time. When we have to

create a user we just simply fill the signup form and add the user. QAS can easily add users at any instant without any storage limitations.

Delete user: If we dont need any user we can delete that user any anytime and remove it from the Database. Through this function we can delete user either by searching from the list or directly from the Users Id.

Modify a user: We can modify a user by making alteration on various fields like courses assign to a teacher, department from which user belong, change the user Designation in case of promotion and demotion and in last we can change his public profile which can b viewed by user that are students and other SSUET officials. o Assigned courses: User might assigned multiple number of courses belonging to several Different Departments and this Assigned Courses function may keep record that which course will be taught by which teacher. o Designation: QAS system's sub module named as Manage User has the powerful capability of changing the Designation of the User (teacher), in case of promotion or demotion teacher's designation must changes so our QAS is much flexible to accept these changes at any time. Only admin can change the current designation of the teacher with respect to his seniority and position in the faculty. o Department: This function can modify the user profile data and add or delete a department from the user profile. o Public profile data:

This function allows the user to display the following reports: This data is for public viewed by everyone and every student can access at any time. This public profile data plays vital role on the rating and ranking of the teacher.

Specification Description Inputs Source Outputs Destination Precondition Post condition Side effects Allow User to manage Data Add, Del, Modify, Data Manage Data & customize it After customizing give successful output None Authorized User after Login Edit, Delete or Modify Changes to Users database

3.1.4 Manage Labs This function allows managing the labs. Through this function Labs can b added and added or deleted from database and can modify. In modification the admin can modify the lab type and lab department and make the profile data of the Lab. Also modify the lab staff data and his personal profile. Description List all Labs

We can view all the records of the Labs currently present in SSUET, their up to date profile and their information

Add New Lab

We can also add the Lab record. This function is for future purpose if incase any New Lab will be developed in SSUET so there is an option for add the Record of that Lab in our Database and allow rating for that Lab

Delete a Lab

We can also delete a record of the lab present in the SSUET. We also can remove the Lab from any particular Department.

Modify a Lab

We can also modify a lab by changing various fields in records and add or delete the information of the Lab. These modifications consist many phases like: We can Modify lab Department, Modify the Lab type. We also can alter the record of the Lab staff and also change the public profile of any specific Lab of any department.

Specification Description Inputs Source Outputs Destination Precondition Post condition Side effects To manage and Modify the labs Lab name, lab ID, Dept Lab type Verification from Database and Success messages and updated Labs profile None Admin Login and manage Labs Insertion Deletion & Modification of Lab records None

3.1.5

Reports and Statistics:

This function provides a complete and powerful function of the stats and rating. Ratings can be viewed, PDF format file can be generated through PHP and user receive in it email. These stats can be shown in graphical manner. Also users can comment and leave their feedback for the officials. Description Statistics and graph We can generate a graph and can show the overall statistics of the rating by graphs (bar graph, line graph etc). We can show the overall statistics of a particular Department, selected member and there is also an option for show the stats and result graph for any particular period of time.

G e n e Create PDF report

An overall report and stats of any particular member or any department will generate and user can Download and view in PDF format.

Ratings

User can Rate by using various fields and can play a vital role in the report generation. User can rate teachers Lab and overall performance. This rating plays vital role and through this rating ranking process occurs.

Comments of Students

User (students) can comment after the viewing the rating graphs and stats of any particular teacher or department. Student can comment and can give their feedbacks to higher authorities regarding the specific teacher and department which will b under consideration.

This module also creates a sort of interaction between students & top management. Students can easily convey their messages regarding to any particular teacher through comments. Some particular words are filtered in this module to stop vulgarism and hate imposed stuffs from students side. Specification

Description Inputs Source Outputs Destination Precondition Post condition Side effects

View Rating graph Member id, time period User selected member & time frame Generate Graph, invalid input data None Member must be selected None None

3.2. External Interface Requirements 3.2.1 User Interfaces. The user interfaces are divided into few major components. One part includes the user accessing the system. The other portion involves the diagrams and explanations below demonstrate the major transition from one user interface to another. This is a brief description. However, a more detailed demonstration is done in the prototype. The purpose of this interaction is to illustrate the overall view of the QAS. The diagram below illustrates the major functionalities. These functionalities will be displayed depending on the user. This diagram displays the illustration of how the member profile viewed in QAS. In this profile showing option the Basic and updated information will be displayed having his Name, subjects field and many more. Anyone can view the limited profile of the teacher or other official. The view of how users profile will display is shown in the figure below:

The function of the QAS is to show the stats and report of the teacher. Through this students and other users can easily view the rating and statistics graph of any teacher. Basically this Graph will be generated on PHP that gather data from the survey and feedback form filled by the students and calculate and draw the graph. This Graphical data also shows the stats of the Teacher according to time frame. The reports and stats with Graph can be shown as in next Figure:

The useful and very positive tool of the QAS is the comments section. Here students and the other users can view the stats and report and rating of the teacher and after viewing the current rating and record of the teacher, student can comment various posts and can pass comment on the teachers ranking and rating. This is very useful and highly considerable comments section where the higher authorities and other officials of the SSUET observe these comments and will take action and appreciation according to the feedback. The comments section will look like as:

The member signup in the QAS is very easy and accurate by filling the sign up Form. This right is limited to the Admin only. Only Admin can sign up the new teacher and fill the form by using his/her details from the university record. This data also stores in database and updated eventually. When the new member signs up, student and other users are able to comment and rate that teacher. The new member signup form is shown in the figure below:

The QAS also have the option to add a new department in the University. In future if the new department will be form so QAS has ability to keep the record of that Department. Through this record the already signed up users or new comers also have the option to serve for that department. The department signup form/page will look like as shown in the next figure:

Using QAS, the Admin can also add a new lab into the record. No matter the Lab concerns with any department. Only admin can add a new Lab data using QAS. When adding a new lab into record of the SSUET a form have to be filled by the admin regarding the complete information of the lab to be added. The department and specification of the Lab according to the PEC also mentioned while sign up a new Lab. The New lab entry will look like:

3.2.2 Hardware Interfaces. The QAS includes major hardware component: regular PC's. It involves the regular PCs, which communicate with the server. The server then communicates with the database. The protocol involved between the PC's and the server is the HTTP protocol, which allows communication between the PC's and the Server. The remote PC's, such as someone accessing the QAS from home using the Internet, are able access the information. The requests come in through the HTTP protocol, and using an ODBC the database results are returned and processed using Perl to give an HTML web page. The format of the output is displayed as web pages. 3.2.3 Software Interfaces. MySql database will be used to manage and store all the data of the whole system. Data redundancy is very important thats why daily backup of database is necessary. The Apache server between the client and the database will handle all communication, and the server will run on a Linux operating system. Furthermore, the HTML pages must be implemented such that they can be displayed on all major web browsers i.e. Internet Explorer, Mozilla Firefox, Google Chrome, Opera, Safari etc. Information about the products used for the QAS: (1) Name: MySql (2) Mnemonic: MySql (3) Version Number: 5 (4) Source: MySql.Com (1) Name: Windows XP (2) Mnemonic: XP (3) Version Number: Sp1, Sp2, Sp3 (4) Source: Microsoft (1) Name: Red Hat (2) Mnemonic: Red Hat Linux (4) Source: Microsoft (1) Name: Internet Explorer (2) Mnemonic: IE (3) Version Number: 7.0, 8.0, 9.0 (4) Source: Microsoft (1) Name: Google Chrome (2) Mnemonic: Chrome (3) Version Number: 6.0

(1) Name: Mozilla Firefox (2) Mnemonic: Firefox (3) Version Number: 3.2 (4) Source: Mozilla (1) Name: Apache (2) Mnemonic: Apache (3) Version Number: 2.2.14 (4) Source: Apache Software Foundation (1) Name: Macromedia Dreamweaver 3 (2) Version Number: 3 (1) Name: Adobe Dreamweaver (2) Version Number: CS-3

3.3 Performance Requirements. The following sections list the performance requirements for the system. 3.3.1 User Requirements User Requirements Description of Environment Requirement For Design

Location(s) and Number(s) SSUET of Users Expected Growth Number of Users After 1 year After 2 year User Expectation in 20% TBD

Interactivity

User expects that it provides a very easy to use graphical user interface just like desktop applications, and complying newest technology standards. For some applications, reliability must be 100% during the application session Database and server must be adapted as per user load and data. Security algorithms should be implemented to avoid MySql injection and other vulnerabilities. Less than 2,000 Rs

Reliability Adaptability

Security Cost / Funding

3.4.1 Standards Compliance. There are no design constraints that can be imposed by other standards limitations. 3.4.2 Software Limitations. must be able to run on most popular web browsers to access the system. must have Java Script enabled device to access the system to avail full GUI features.

3.5 Quality Characteristics. There are a number of quality characteristics that apply to the QAS software system. 3.5.1 Portability The QAS is web based system which can be accessed from anywhere in the world through any internet enabled device i.e. Computer, PDA, etc. The system will be tested on major hardware before being released to ensure that is it compliant with this requirement. 3.5.2 Reliability The system should be capable of processing ratings and ranking. During the development of the prototype for the 5 departments having more than 50 teachers, the system will be tested in its actual environment to ensure that it can handle the load of various ratings that occur during a regular workday. 3.5.3 Usability The QAS system will be developed so that it is an easy to use system that requires the least amount of user input possible. Every input will be validated. The user should only have general computer use knowledge. Error messages will be displayed if the user enters an invalid value or tries to access a function without the required permissions. An easy and well-structured user manual will be provided to the SSUET and the system will include descriptive help for all operations allowed. 3.5.4 Correctness The QAS system will be considered correct when the official of the SSUET approves the prototype presented and agrees that all the functions they require are implemented as stated in the Software Requirements Specification. 3.5.5 Flexibility The QAS system should be developed in such a way that it is easily customizable. If new functions are required by SSUET, there will be little effort required to update the system to support new users or new Departments. 3.5.6 Security The QAS system should not compromise the teacher private information at any time. The user information will never be sold to other and will be kept secure at all times. Users will be authenticated to ensure that no unauthorized users gain access to private information.

3.5.7 Maintainability The QAS source code will be kept well structure and documented so that it is easier to maintain and extend the system. All changes to the system shall be documented. 4. Supporting Information. There is no supporting information required for this project.