Table of Contents

1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations 4
1.4 References 5

2. Positioning 5
2.1 Business Opportunity 5
2.2 Problem Statement 5
2.3 Product Position Statement 5

3. Stakeholder and User Descriptions 6

3.1 Stakeholder Summary 6
3.2 User Summary 6
3.3 Stakeholder Profiles 6
3.5.1 Supervisor 6
3.5.1 Student
3.7 Key Stakeholder or User Needs 7

4. Other Product Requirements 8

4.1 System Requirements 8
5.
 1. Introduction

The main idea for the development of online admission system (OAS) is
to solve different issues regarding admission process. The system will
help in solving problems related to student admission . OAS will also
help in managing the record of the student in there own database
system which will help them for future use. This system will also help
student to submit there admission form online. OAS is a desktop
based, highly functional, flexible, fast, reliable and easy to learn
system.

1.1 Purpose
In this document we state what we hope to accomplish an online
admission system for students which will be fast and user friendly. In
previous system, there was no online system for the student. All the
forms were submitted manually which made certain problems. But by
this online admission system, student will submit his form online and
this will help in solving different problems of a student. This document
also tells that how others stake holders can use this system.

1.2 Scope
AS is an online admission system that allows managing in submission
of the form online. The scope of this document is the admission
system. This document also covers the working of administration and
other stake holders with the system

1.3 Definitions, Acronyms, and Abbreviations

Term/
Description
Abbreviation
IIUI International Islamic University Islamabad
AS Admission System

DBA Database Administrator

SE Software Engineering

S/W Software

1.4 Refrences

1.5 Overview
 Coming sections of this vision document explains how OAS will be positioned in the
current organization and will create its need for the business. Moreover, the vision
document has the description of the problem statement, the stakeholders and users
from the business, and then an overview relating some aspects of the OAS system.

2. Positioning
2.1 Business Opportunity

Online Admission System (OAS) has very high business opportunities

as most of the student would able to submit there form and apply in
the university. The current system has many drawbacks like student
have to go through tough process for admission curremt has lot of
manual work that takes lot of time to complete the admission due to
this istudent have to wait for the conformation of the admission.
2.2 Problem Statement

The problem of The current system is not an online system, so

because of this number of student cant able to apply
for the admssion, its all manual system . It’s not
efficient. It’s is hard to manage. It can not be
accessed anytime anywhere. Difficult to maintain the
transactional data. Hard to maintain and manage
information.

Affects Students and management staff are the main

stakeholders who are affected by above mentioned
problem.
the impact of which is Due to current system less number of students apply
for admission and because of this less revenue is
generated from this business process.Managment
staff has to work alot , sometimes all the night to
accomplish thier tasks.
a successful solution Proposed system is completely online system so it will
would be help istudent and managment staff in a less
time,form will be submitted online and less manual
work will be required.
 2.3 Product Position Statement

For Student and admission department staff.

Who For the student who wants to apply for online admission to
save their time and for the admission department staff to
avoid excessive manual work that lots of time.

The (product name) OAS (Online Admission System)

That System will be efficent fast and time saving.

Unlike

Our product

3. Stakeholder and User Descriptions

3.1 Market Demographics

Our system is helpful to the admission staff so it can be usefull to other educational
insitutions and other insitution can buy it.
3.2 Stakeholder Summary

President Incharge of the university Approves the final list of

students
Course Offering Department Incharge of the courses Approves the courses that
offered in the university are able to be taught in
university..

HOD Head of the department Ensures that the number

of students entering the
program is with in the
limits and monitors
different section as well.

IT managers Incharge of IT department Checks the entry test

papers and generates the
result.

New paper Agencies Incharge of the news Gives the ad in newspaper

papers regarding about the admission the
university admission courses which the
process university is offering and
schedule date for the test.

Bank Department Incharge of the bank Assist the student those

 regarding admission who are applying for the
forms. university admission
manually.

3.3 User Summary

ACTOR RESPONSIBILITIES GOALS

Student Applies for the university Selects the interested field.
admission.
Submit his full data required in the
admission form.

Program Coordinator Coordinates with Coordinates work.

admission department
Prints the reports regarding number of
officers and HOD.
student applying in the concernd
course.
HOD Incharge of the Approves the number of student under
department the limit.
Administration har Performs the task on Manage the student data those how
banda asakta hy OAS as an authorized have applied.Generates roll number as
person. well.
Admission Fee Incharge of the fee Manages the admission fee of
department department regarding students.
admission fee.
Stake holder

3.4 User Environment

• Number of people involved in completing the task is

varying from task to task. This might be 1 in some cases
and more than 1 in other cases.
• OAS will be accessed only within the premises of the
department on some specific terminals.
 • No other applications are in use but OAS may need to
communicate with applications that are external to the
system. Like an application in use by the Bank & News
papers department regarding admission forms.
3.5 Stakeholder Profiles

President

Representative Dr. Anwar Hussain Siddique

Description In charge of the University.

Type Highly Qualified personnel.

Responsibilitie Ensures that required student are approved and

s merit list is fair..

Success Less staff required.

Criteria
Involvement Approves final merit list

Deliverables

HOD

Representativ Dr. Muhammad Sher

e
Description In charge of the department who manages and heads the department.

Type Professional in the field of Computer Science and Software Engineering.

Responsibiliti Monitors the system working.

es
Success The task cycle has shortened.
Criteria
Involvement He will review the requirements and give possible suggestions.

Deliverables Hard copies relating List of student involving in the field under the limit
Course offering department
Representativ Muhammad Aftab Hassan
e
Description Incharge of the admission department

Type Professional in field of computer science

Responsibiliti Monitors the admission process

es
Success Automated system, less human error
Criteria
Involvement

Deliverables Forms of student weather it is on the net or manually filled by the student

IT Managers

Representati
ve
Description Incharge of the IT department

Type Professional in the field of web and internet applications.

Responsibilit Conducts the entry test.

ies
Success Auto generated computer work.
Criteria
Involvement Final results of entry test are complied and sent back to the admission cell.

Deliverables

News Paper agencies

 Representat
ive
Description Incharge of University admission Ads.

Type Related to ads category in the news papers.

Responsibili Ads in news paper Description of offered courses by the university.

ties
Success People using news papers for admission information.
Criteria
Involvement Given ads in the newspaper can help the student to choose their field.

Deliverables Admission cell updates about the courses, entry test dates and fee as well.

Bank Department

Representativ
e
Description Incharge of the admission form for the students.

Type

Responsibiliti Guides student about admission forms.

es
Success
Criteria
Involvement Form submission.

Deliverables Admission cell updates about the courses and fee.

3.6 Users Profile

Student

Representativ
e
Description Applying in the university

Type Casual user

Responsibiliti
es
Success Gets him selves registered and get the roll number earlier as compare to old system.
Criteria
Involvement

Deliverables

Comments / If he/she does not the required marks in the entry test he/she is not selected for the
Issues choosen field

Program Coordinator

Representativ
e
Description Professional in the field of administration work.

Type Casual User.

Responsibiliti Coordinates work and print reports.

es
Success Reports printed successfully.
Criteria
Involvement HOD asks for the merit list.”””

Deliverables Admission cell updates about the number of students being enrolled in the field.

Comments / Very helpful and caring.

Issues

HOD

Representativ Dr. Muhammad Sher

e
Description In charge of the department who manages and heads the department.

Type Professional in the field of Computer Science and Software Engineering.

Responsibiliti Checks that the student enrolled in the field are under limit.
es
Success The task cycle has shortened.
Criteria
Involvement He will review the requirements and give possible suggestions.

Deliverables Hard copies relating List of student involving in the field under the limit

Comments /
Issues
Administration

Representativ Admission cell team.

e
Description Performs tasks on the OAS as an authorized person.

Type

Responsibiliti Performs admission process and manage database of the student those who have
es applied.

Success Student successfully registered and applicable for entry test and futher process.
Criteria
Involvement Student applies for the admission.

Deliverables Students form.

Comments /
Issues

Admission fee Department

Representativ
e
Description Performs tasks on the OAS as an authorized person.

Type Professional in accounts managing and fee issues.

Responsibiliti Checks the admission fee.

es
Success Admission fee is obtained.
Criteria
Involvement Form submission.

Deliverables Admission cell updates about the fee.

Comments /
Issues

3.7 Key Stakeholder or User Needs

Need Priority Concerns Current Solution Proposed Solutions

Entering the data medim Students Automation Easy to use online
manually. forms.
high Admission Automation
Less Vulnerability of departme
high Automation
human errors. nt
More student facilitation. IT
departme
 nt

3.8 Alternatives and Competition

OAS does not have any alternatives now. The
only alternative that student have is he/she can apply by manual form.

4. Other Product Requirements

4.1 PLATFORM
The system must use windows XP/Vista/7.
4.2 .Net Framework
Visual Studio.Net 2008 used to develop the Project.
4.3 DBMS
MS SQL Server 2008
5. Quality Ranges:
Our OAS is quiet easy to use. Its very ser friendly and easy to understand as
well. There are certain characteristics that support the user friendly
environment.
• Help menus are available

• Balloon Tips are available

• High Graphical interface

• Self Explanatory

• If any fault occurs system will back up the data which can be covered up
later.

6. Precedence & Priority:

Features Priority

Application Submission High

Merit list generation ? Medium
Admission Approval ? High
Program Offering x High
 I.D card regeneration? Medium
Roll number allotment Medium
Help High

7. Other product requirement

7.1 Applicable Standards
OAS is made in C# and it would be compatible and reliable as well it
use Microsoft platform and also uses the tool provided by Microsoft.OAS also
compile on communications protocols standards like (TCP/IP,ISDN).
7.2 Performance Requirements
The OAS will have many users using it at a time, thus it requires
scalability reliable and when there is a more load like at the time of
admission the system should be reliable or act reliably, less crash of system
will occurs.

7.3 System Requirements

o Windows XP SP2 (or Higher) or Windows Vista or Windows 7.
o 512 MB Ram, but better to have more – 1 or 2 GB.
o 1 GHz CPU, the faster the better, System process will be better.
o Shader Model 1.1 Admission system card or better Shader Model
2.0.

7.4 Environmental Requirements:

The purpose of user manual is that it will be helpful to novice user who
does not have training of OAS.

8. Documentation Requirements:
Documentation aspect of a system is very important for the successful
processing of the system.OAS has some important point relating
documentation requirements which as follow:
8.1 User Manual
The font in the manual should not be less than 10 and the
recommended font for writing is New Times Roman. The manual page
printing should be A 4 . The user manual will provide help in tutorial
format so step by step details would be given for each task.
8.2 Online Help:
Online help system of our OAS can be considered as another separate
module and thus is planned to be done in future variance, thus online
 help will be not available in current version.
8.3 Installation Guide
Installation guide will let the user to help the user in install the
admission system, the configuration setting will be provided with the
installation Cd or OAS in a read me file, the read me file will also
contain a section “What new with this release”.