<Management of admission system> Requirements Specification Document

UNIVERSITY OF EDUCATION

MANAGEMENT OF ADMISSION SYSTEM

University of education College road Township campus Lahore

September 15, 2011

.

<Management of admission system> Requirements Specification Document

Prepared by:

Group Members:
No. Roll Number Name Email Signatures

1.

MscIT-F10-A06

Kousar Ramzan

amna.amna81@yahoo.com

2.

MscIT-F10-A48

Saira Kanwal

shaina_48@yahoo.com

3.

MscIT-F10-A49

Sundus Ahsan

sundus_libra@hotmail.com

4.

MscIT-F10-A50

Sameea Mahmood (Leader)

smkhan005@gmail.com

Accepted by: Mr.Sohaib Shahid Management of admission system University of education September15, 2011

<Management of admission system> Requirements Specification Document

REVISION HISTORY

Revision no. 1

Date of Issue Aug17, 2011

Author(s)

Brief Description of Change

<Management of admission system> Requirements Specification Document

Table of content
1- Admission system proposal ------------------------- 5 2- Introduction-------------------------------------------- 6 2.1 System Overview ---------------------------------- 6 2.2 Customers ------------------------------------------- 6 2.3 Reference Documents ----------------------------- 6 2.4 Assumptions ---------------------------------------- 6 3- System Requirements -------------------------------- 7 3.1 Functional Requirements-------------------------- 8 3.2- Similarly defined other requirements ---------- 9 4 Requirements Testing Criteria-------------------- 10 5- Glossary ---------------------------------------------- 11 6- Use-case diagram ----------------------------------- 12 7- Use-case description ------------------------------- 13 8-Data flow diagram ----------------------------------- 17

<Management of admission system> Requirements Specification Document

1- Admission system proposal

Term:

M.Sc I.T (Afternoon) 2010-2012

Project Title: Project Description:

Development of admission system

Student Admission System Supports the student admission and registration process, the maintenance of student personal, academic and fee related data. Today all the work at the time of admission of the students is done manually by ink and paper, which is very slow and consuming much efforts and time. Duplication of data & no security Lose of data Updating data Old mechanism Time consuming Difficult to store data Computerized automated student admission system Trained and skillful people Easy to modified data Efficient retrieval Enhance security through password Attractive user interface Provide accuracy of data Time saving

<Management of admission system> Requirements Specification Document

2- Introduction
2.1 System Overview
Apply for admission: For the admission, student selects the standard university and also keeps in mind about different courses for which he/she is going to apply. Submit the form with whole documents and courses their wish to take. Wait for merit list: After submit the form, student wait for merit list. Accept /reject form: Administrator submitted the form, verifies that each courses selected is still open by referencing the course file. Subsequently, the administrator determines which of students selection can be accepted or rejected. Display merit list: Administrator makes the merit list according to rule and displayed it on notice board for confirmation the course for which student registered.

2.2 Customers
Students target is to get admission by submitted the form.

2.3 Reference Documents

Degree Metric F.A/FSc B.A/BSc

Year 2006 2008 2010

Grade A+ A A

Name of Institute Punjab school Punjab college Punjab university

2.4 Assumptions
Student admission system should be computerized. People should be trained and skillful for system. Data should be easy to modified and efficient retrieval. System security should be enhancing through password. It proves its self as attractive user interface and system provide accuracy of data.

<Management of admission system> Requirements Specification Document

3- System Requirements

Windows
Internet connection Operating system Computer processor

Minimum Requirements
Cable or DSL XP, Vista, or Window 7 CPU with SSE2 support, including Intel Pentium 4, Pentium M, Core or Atom.

Recommended
Cable or DSL XP, Vista, or Window 7 1.5 GHz(XP), 2-GHz(Vista) 32bit(x86) or better

Computer memory Screen resolution

512 MB or more 1024 x768 pixels

1 GB or more 1024 x768 pixels or higher

Mac OS X
Internet connection Operating system Computer processor

Minimum Requirements
Cable or DSL Mac OS X 10.5 or better 1.5 GHz Intel based Mac

Recommended
Cable or DSL Mac OS X 10.5.4 or better 2 GHz Intel Core 2 duo or above

Computer memory Screen resolution

512 MB or more 1024 x768 pixels

1 GB or more 1024 x768 pixels or higher

<Management of admission system> Requirements Specification Document

3.1 Functional Requirements

Data will not be duplicated in admission system. There should be no chances of lost of data. System updates data without creating any problem such as old system. It store data by using latest technology.

Req. #

Requirement

Description

Resolution of a display device should be clear.

Display resolution of a screen, gives the image is actually formed.

Software application needs special peripherals for high performance.

Such peripherals include CD-ROM drives, keyboards, pointing devices, network devices, etc.

<Management of admission system> Requirements Specification Document

3.2- Similarly defined other requirements

Hardware Requirements

CPU: Pentium VI processor RAM: 512 MB HDD: 40 GB Keyboard, Monitor, Mouse, Printer

Software Requirements

Operating System: Microsoft Windows XP Front End tools: HTML, ASP.NET Back End tools: MS Access, SQL Server

Operational Requirement

Operating System: Microsoft Windows XP

Backup Requirements

Operating System: Microsoft Windows XP Back End tools: MS Access, SQL Server, Data Backup software

<Management of admission system> Requirements Specification Document

4 Requirements Testing Criteria

Functional requirement Non-functional requirement The system shall be user friendly Change old mechanism into new technology & get efficient retrieval. Change all manual work into computerized system. Testing Requirement Demonstration Inspection

Analysis

10

<Management of admission system> Requirements Specification Document

5- Glossary
Term System requirements (SR) Definition To be used efficiently, all computer software needs certain hardware components or other software resources to be present on a computer. These pre-requisites are known as (computer) system requirements and are often used as a guideline as opposed to an absolute rule. Most software defines two sets of system requirements: minimum and recommended. In software engineering, a functional requirement defines a function of a software system or its component. A function is described as a set of inputs, the behavior, and outputs. Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish The most common set of requirements defined by any operating system or software application is the physical computer resources, also known as hardware, A hardware requirements list is often accompanied by a hardware compatibility list (HCL), especially in case of operating systems. Software requirements deal with defining software resource requirements and pre-requisites that need to be installed on a computer to provide optimal functioning of an application.
An Operational Requirement or (OR) was a UK Air Ministry document setting out the required characteristics for a future

Functional requirements (FR)

Hardware requirements (HWR)

Software requirements (SWR) Operational requirements (OR) Backup requirements (BR)

In information technology, a backup or the process of backing up is making copies of data which may be used to restore the original after a data loss event.

11

<Management of admission system> Requirements Specification Document

6- Use-case diagram

Admission system

Apply for admission

Accept /reject form

Wait merit list

Display merit list

Student

Administrator

12

<Management of admission system> Requirements Specification Document

7- Use-case description

UC-ID: UC-786 UC-Name Apply for admission Description: 1. Student admission system supports the student admission. 2. Registration process, the maintenance of student personal, academic and fee related data. 3. Through the computerize system modified data easily. 4. Efficient retrieval of data. Primary Actor: Student Pre-Conditions: Student visit for admission. Post-Conditions: Student applied for admission. Main 1. Student selects University for admission. Success Scenario: 2. Student selects the one or more courses for admission. 3. Student "Submit" the form.

Extensions: 2a. No courses are available for this student. --- 2a1. System displays error message saying no courses are available, and provides the reason & how to rectify if possible. 3a. Some necessary documents are not attached. --- 3a1. Some necessary documents should be attached with the student form

13

<Management of admission system> Requirements Specification Document

UC-ID: UC-787 UC-Name Wait for merit list Description: 1. The student asks the date of displaying merit list from administrator. 2. The administrator accommodates all the submitted forms. 3. He makes a list of Appling students carefully and rechecks it keenly. 4. He saves this list in the computer. Primary Actor: Student Pre-Conditions: The student submits the admission form. Post-Conditions: The student will Check the merit list. Main 1. Student submits the form. Success Scenario: 2. Wait for the date of display merit list desperately 3. Administrator arranges the first merit list of highly qualified or highest marks gaining students. 4. After displaying the merit list student check its name in it. Extensions: 2a. Sometimes the merit list according to the obtained marks of the student but he/she does not find his/her name in the selected students. --- 2a1. Administrator tells him that his/her documents were incomplete if he/she provide the complete documents you will be eligible for admission. 3a. If the students form is lost by the administrator then the name of the student will not display in the merit list. --- 3a1. If the marks of the student according to the displayed list then the administrator will be provided him another admission form for reconsideration.

14

<Management of admission system> Requirements Specification Document

UC-ID: UC-788 UC-Name Accept/ reject form Description: 1. Checking of required documents /absence of any document leads to rejection of form. 2. Checking of reference course keenly/absence of reference course can be the cause of rejection of form. 3. Enrollment of student after formal checking. 4. Submission of form to the related department. Primary Actor: Administrator. Pre-Conditions: The administrator checks the student form. Post-Conditions: The satisfactory checking by administrator leads to the acceptance of form otherwise he will reject the admission form.(he will accept/reject the form) Main 1. The administrator makes a list of accepted forms. Success Scenario: 2. He makes merit list on the basics of accepted forms. 3. He rechecks the merit list and number of applying students to avoid of any mistake. 4. He makes a list of students according to the marks and seats respectively. Extensions: 2a. Data can be lost by crushing the system. --- 2a1. The administrator should keep backup of the related data. 3a. The name of the student can be missed from the merit list due to the miss print. --- 3a1.The administrator should print the merit list very carefully.

15

<Management of admission system> Requirements Specification Document

UC-ID: UC-789

UC-Name Display merit list Description: 1. After checking the form, merit list will be displayed. 2. Students check the displayed merit list. Primary Actor: Administrator. Pre-Conditions: Students confirm their names on merit list. Post-Conditions: After confirming their names, student submitted the fee. Main Success Scenario: 1. Administrator makes a list of students according to the aggregate and seats respectively.

2. He displayed the merit list on notice board. Extensions: 1a. Student marks according to merit but not shown in merit list due to system failure. --- 1a1. Administrator should take back up of data.

16

<Management of admission system> Requirements Specification Document

8-Data flow diagram

Context level/ Level 0

Receive form

P-0

Administrator
Admission management system

Apply for admission

Accept/reject form

Student

17

<Management of admission system> Requirements Specification Document

Level 1:

P-1 Choose
Student Courses Course file

P-2 Student Registration

Registration file

P-3

Student

Display Merit List

Admission file

18

<Management of admission system> Requirements Specification Document

No

WorkProducts/Deliverables Name

Submission Date

On time? Remarks

19