Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
for
Prepared by
Saurabh Singh 09BCE049 Instructor: Course: Lab Section: Date:
Akila Victor Software Engineering Lab L10-L11-L12 7th of February , 2012.
Contents
1 INTRODUCTION ............................................................................................................................................... 3 1.1 1.2 1.3 1.4 DOCUMENT PURPOSE ................................................................................................................................ 3 PRODUCT SCOPE ....................................................................................................................................... 3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW ................................................................................... 4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS ........................................................................................ 4
OVERALL DESCRIPTION .............................................................................................................................. 5 2.1 2.2 2.3 2.4 2.5 2.6 2.7 PRODUCT PERSPECTIVE ............................................................................................................................ 5 PRODUCT FUNCTIONALITY ......................................................................................................................... 6 USERS AND CHARACTERISTICS ................................................................................................................. 6 OPERATING ENVIRONMENT........................................................................................................................ 6 DESIGN AND IMPLEMENTATION CONSTRAINTS .......................................................................................... 6 USER DOCUMENTATION ............................................................................................................................. 7 ASSUMPTIONS AND DEPENDENCIES .......................................................................................................... 7
SPECIFIC REQUIREMENTS .......................................................................................................................... 7 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 EXTERNAL INTERFACE REQUIREMENTS .................................................................................................... 7 FUNCTIONAL REQUIREMENTS .................................................................................................................. 11 NON FUNCTIONAL REQUIREMENTS ......................................................................................................... 11 PERFORMANCE11 SUPPORTABILITY............12 DESIGN CONSTRAINTS.......12 LICENSING REQUIREMENTS....13 LEGAL, COPYRIGHT AND OTHER NOTICES.......13
OTHER INFORMATION...13
Page 2
1 Introduction
Which courses are good??? Which are the best colleges for that course?? How to get into those colleges? What is the exam pattern?? Students have a lot of confusion about the courses and what exams do they need to appear for getting into that course. Competitive Counselling System (CCS) is a web based application which guides the students and helps them overcome these situations. CCS is designed to aid students and inform them about various streams and different courses. The Competitive Counselling System (CCS) shall be used by students for getting information about various courses, the exam pattern and dates. CCS can also be used by students to clear their queries by posting questions which can be answered by fellow students and counselling experts. It shall also be used by authorized administrators who will be able to view the queries and student profile and also edit the content of the website. The purpose of this document is to analyze and elaborate on the high-level needs and features of the CCS. It focuses on the capabilities and facilities of the CCS. The details of what all are the needs of the CCS and if it fulfills these needs
The features that are described in this document are used in the future phases of the software development cycle. The features described here meet the needs of all the users. The success criteria of the system are based on the level up to which the features described in this document are implemented in the system.
The SRS will provide a detailed description of the Competitive Counselling System. This document will provide the outline of the requirements, overview of the characteristics and constraints of the system. Section 2: This section of the SRS will provide the general factors that affect the product and its requirements. It provides the background for those requirements. The items such as product perspective, product function, user characteristics, constraints, assumptions and dependencies and requirements subsets are described in this section. Section 3: This section of SRS contains all the software requirements mentioned in section 2 in detail sufficient enough to enable designers to design the system to satisfy the requirements and testers to test if the system satisfies those requirements
Page 4
2 Overall Description
2.1 Product Perspective
CCS aims at providing each and every minute detail of competitive examination and higher education to students. Students get all the information at a single source which is the objective of developing the system. The students may create an account or continue as guests. The system contains the data for each of the streams and their examination and the best colleges. The students can view the results and can also subscribe to our mail services. CCS provides the login facility to the administrators. After authentication the administrator can manage the content of the system. Administrator can also view the traffic statistics and can view the accounts of each of the students. The administrator can also mail the exam details and other notifications to the subscribed students. The product to be developed has interactions with the users: Students or Visitors, Administrator who manages the CCS. The complete overview of the system is as shown in the overview diagram below:
Users
Administrators
Server
figure 1: External Representation of the CCS
Page 5
Page 6
3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
The User interface will make use of the existing Web Browsers such as Mozilla Firefox or Google Chrome.The user-interface of the system shall be designed as shown in the user-interface prototypes. Main Page Prototype:
Page 7
Page 8
When the admin logins into CCS he gets a new screen where he could view the network traffic, manage content and view student profile. Admin Home Page Prototype:
Page 9
Page 10
3.4 Performance
3.4.4 Capacity The System capability depends on the capability or limit of the hosting server. 3.4.5 Resource Utilization The resources are modified according the input provided by the alumni and also according to the administrator in case he adds a new user.
3.5 Supportability
The system designers shall take in to considerations the following supportability and technical limitations. 3.5.1 Internet Protocols The system shall be comply with the TCP/IP protocol standards and shall be designed accordingly. 3.5.2 Information Security Requirement The system shall support the VIT information security requirements and use the same standard as the VIT information security requirements. 3.5.3 Maintenance The maintenance of the system shall be done as per the maintenance contract. 3.5.4 Standards The coding standards and naming conventions will be as per the IEEE standards.
Page 12
Page 13