Name University admission System

1.Introduction:PurposeThe University Admission System has been developed in order to automate the complete admission system starting from the notification to admission process. It also includes the Statistical reports on daily activities in the admission process. The system enables online admissions saving the time of the geographically scattered students. It enables reducing time in activities, centralized data handling and paperless admission with reduced manpower. It improves the operational efficiency and reduces the cost. It also provides consist view of data and integration with other institutions for verification of marks and details.

Document convention: Items that are intended to stay in as part of your document are in bold. Explanatory comments are in italic text. Plain text is used where you might insert wording about your project.

Intended audience and reading suggestion:This document is intended for, developers, project managers, users, testers, and documentation writers. Rest of the document describes the software in more detail. This document is divided into the following sections: the overall description section where, the perspective of the product, its features, user constraints, operating environment and design and implementation constraints are described. System features, where major system features are described.

External interface requirements including, user Interfaces, hardware interfaces, software interfaces and communication interfaces are described.

Product scope: Create different system users and assign different roles with related permissions. The Notification will be released through online and manually. Students can apply online or offline. Verification of marks/details done by interacting with different agencies like school boards or college management systems. Hall tickets will be issued for eligible candidates. Ranks will be generated depending upon the marks obtained for qualified candidates and call letters will be send to short listed candidates. Admissions will be done online, saving the time of students. Centralized data maintained. The seats management will be done by the convener online and availability of seats announced. Statistical reports on daily activities in the admission process will be generated.

 The system provides security through password authentication. The Administrative staff and system administrators have their own login ids and these ids help in maintain the integrity of the system.

Reference: IEEE Standard

Use case diagram

Overall description:Product perspective:The applications is designed to automate the existing paper based student admission system and the overall staff management system . This the first time an automate student, staff and program management system will be used . This is intended to minimize the delay in the paper process and also in the better management of student, staff and programs records.

Product function:The system will provide features to automate the students admission process into these programs. It will allow the students to fill various forms online and also allow faculty members and coordinators to make the decision online. The system will provide features to automate the process to create/update/delete various programs in the department. The system will provide a way to manage the staff and the decision committee in various programs offered by the department.

User class and characteristics:The Student should have the basic idea to operate (use) the system and he already has the experience to work in the internet (browser). Default Language is English. The various user classes that will be using this product are: Students:- this class of users will be using the system to fill various forms and place requests. Since the users will be applying for higher studies in the field relate to computers, they will have a basic knowledge and experience with various web based applications. Since filling the forms does not require much technical expertise it will be very easy for this class of users to use the system. System Coordinator:- The system administrator, which will be one of the department members, should be familiar with the department structure and functioning of the department. He/she must also be very well familiar with all the process in the department.

Operating Environment:The application can be run on desktop computers provided to the faculty and staff using internet explorer 5.0/higher or Netscape 5.0 or higher. The application run on the university tomcat server which a unix based environment. The application will be interacting with a backend database system, in this case an oracle server installed on the department computer system. The desktop computer from which the application is accessed should be running on windows 2000 or XP environment and the servers should be running on unix environment.

Design and Implementation Constraints:The system should be developed using oracle as a backend database. The faculty members and system administrators will be able to maintain the system efficiently as they are already experienced in it. Windows based environment should be used for documentation. Rational rose should be used to develop the design and analysis models for the system. After the system is deployed the department will be responsible for maintaining it. User Documentation:A
specific document should be prepared for the maintenance of the system. Online documentation facility is available for the students to assess them for the easy use. and should say the system in easiest way.

Assumptions and Dependencies :-

 Courses are already created and informations available for use. Roles and responsibilities are already established. Administrator is already created

External interface requirement:User Interfaces:The user interface for this system will have to be simple and clear. Most importantly, the ages must be easy to read, easy to understand and accessible. The color scheme should be appropriate to provide familiarity with the university and there should be no contrast issues.

Hardware interface:Software interface:Software will be developed on the windows 2000 and windows xp environment. Members of the project team have experience with J2EE based web technologies, Access/Oracle Database

System Features:Functional requirement: Selling of forms (through site and manual). Marks & details verifications of filled forms for eligibility checking.

 Sending call letters to eligible candidates for entrance exam. Online marks checking and merit list Sending offer letters for short listed candidates.
Counseling, Admission and hostel allotment

Other Non-functional Requirements: Performance Requirements:Security Requirements:Portability Requirements:Maintainability:Reliability:24x7 Availability:-