Product Perspective........................................................................................................................2 Product Features.............................................................................................................................2 User Classes and Characteristics....................................................................................................3 Operating Environment..................................................................................................................3 Design and Implementation Constraints.........................................................................................3 User Documentation.......................................................................................................................3 Assumptions and Dependencies.....................................................................................................3
User Interfaces................................................................................................................................3 Hardware Interfaces........................................................................................................................3 Software Interfaces.........................................................................................................................4 Communications Interfaces............................................................................................................4
4. System Features.......................................................................................................................4 4.1 System Feature...............................................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4 5.1 5.2 5.3 5.4
6. Project Plan..............................................................................................................................5 6.1 Team Members...............................................................................................................................5
Software Requirements Specification for College Website
1.
Introduction
1.1
Purpose
Page 1
The software described in this document is the http://www.sdbct.ac.in/ website and associated support pages. This document seeks to provide the Software Requirements Specifications for the College Website. The purpose of this document is to record the requirements for the design and development of College Website. Rev1 of the website was created on or about summer of 2006. This document describes requirements for Rev2, summer of 2010. There may be a need for future updates of the website. The document reflects the current requirements of the project as understood by the project team. This document presents an initial description of the various functionalities and services provided by the software. The document will also serve the basis for acceptance testing by the user. The scope of the website is not only limited to attracting and encouraging high school students to take coursework at Sushila Devi Bansal College of Technology. But it also aims to provide information about institute keeping in mind that the person visiting this website wants a full knowledge of the college.
1.2
Document Conventions
There are no standard document requirements for this document.
1.3
Intended Audience and Reading Suggestions
Primary readers of this document are the web designers contributing to and testing of the college website. Contributors to this document are members of the Computer Science Branch of SDBCT. The remaining sections of this SRS describe the functional requirements for college site.
1.4
Project Scope
The scope of the website is to provide a high school teen friendly set of web pages that are easy to navigate and at the same time provides sufficient depth and information about college. Two potential groups of viewers exist: 1. Students interested in BE, MBA or MCA seeking more in-depth information about a College. 2. Students that are in that college but are seeking for some information. The goal of website is to encourage more students to choose college, eventually increasing the number of BE, MBA and MCA graduates from respective college. Maintaining a teen friendly site is deemed of highest importance in order to hold student attention and guide the viewer to information that will lead to a decision to pursue a career in BE, MBA or MCA
Software Requirements Specification for College Website
Page 2
Benefits for using the site should include: • Personal and Career information from a broad spectrum of BE, MBA and MCA professionals • BE, MBA and MCA course and other information from college • Timely and up to date information that encourages readers to return to the site • Call to action, and plans for students to follow to prepare for a BE, MBA and MCA career
1.5
References
NONE
2.
Overall Description
2.1
Product Perspective
This product is an update of the existing website version 1. The new site will be version 2. A future version 3 may be needed to incorporate ideas learned from version 2. Website is aimed toward students who have completed their higher studies or graduation and are looking for a college for further studies. Website should be user-friendly, ‘quick to learn’ for the above purpose.
2.2
Product Features
Major features of the website include the following pages/subsections: • Downloads o Syllabus of each semester for students of the college o Time Table of all departments and there classes for students o Time Table of all exams conducted by college, including the Time Table of final exam as declared by RGTU o Bus route for students to make them sure which bus will come to their respective stop, similarly this will help students to choose correct bus to reach their destination o Assignments and notes provided by college faculties o Fee structure of each year •
News and events o Any notice that is to be displayed by college o Announcement or information college want to provide
•
Jobs o o o
•
Our sister institutions o Information about other institutes of Bansal Group
Placement Scenario Placed students Companies visited
Software Requirements Specification for College Website
2.3
Page 3
•
About Us/Mission o It specifies the aim of college
•
About Us/Our Uniqueness o It specifies the qualities and uniqueness of college, including the details and pros that why one should opt this college and not any other
User Classes and Characteristics
There are mainly two types of user: 1. Typical college students that are interested in MBA or MCA seeking more in-depth information about a college. 2. Students that are in that college but are seeking for some information. Changes to version 2 should include design changes to all existing pages to shorten up paragraphs and add bullets and charts where possible to accommodate faster page reading and shorter reader attention span keeping in mind most of the users are high school teen-agers
2.4
Operating Environment
The site runs on college servers
2.5
Design and Implementation Constraints
There are no Design and Implementation Constraints
2.6
User Documentation
There are no user documents.
2.7
Assumptions and Dependencies
There are no development assumptions or dependencies.
3.
External Interface Requirements
3.1
User Interfaces
The website should work and be tested against IE, Firefox, Google Chrome and Netscape.
3.2
Hardware Interfaces
There are no special hardware interface requirements
Software Requirements Specification for College Website
3.3
Page 4
Software Interfaces
Software requirements of the system are very nominal and no other special requirement is there hence it is economically feasible. Also Java is open source and thus easily available free of cost.
3.4
Communications Interfaces
There are no special communication interface requirements
4.
System Features
4.1
System Feature 4.1.1
Description and Priority Maintaining a teen friendly site is deemed of highest priority in order to hold student attention and guide the viewer to information that will lead to a decision to pursue a career in BE.
4.1.2
Stimulus/Response Sequences Maintaining a feedback column will help website to frequently change according to user need.
4.1.3
Functional Requirements There are no special functional requirements Very obvious: internet connection
5.
Other Nonfunctional Requirements
5.1
Performance Requirements
The website should be hosted on a server that can provide adequate response time. High school students tend to have short attentions spans, so a slow server would not be satisfactory for this application. The current college (www.sdbct.ac.in) site is a good example of rapid response time.
Thank you for interesting in our services. We are a non-profit group that run this website to share documents. We need your help to maintenance this website.