2012
School Admission Process
Management System
Sy Bsc(IT);
Valia College of Bscit and BMS
2/21/2012
Valia College of Bsc IT and BMS
Subject – Software Engineering
Project- School admission Process Management
Group Number: 9
Proffessor In charge:
Prof. Megharani Shriram
Members:
Sabina Memon (15)
Zainab Khan (14)
Shital Katkar (72)
Swati Shedge (89)
2|Page
INDEX
1. Project Initiation and Scheduling:
1.1 Problem Definition
1.2 Purpose
1.3 Scope
1.4 Project Requirements
1.5 Software Requirements
1.6 Hardware Requirements
1.7Feasibility Study
1.8 Working of Present System
1.9 Disadvantages of Present System
1.10 Proposed System
1.11 Gantt chart
2. Diagram
2.1 Data Flow Diagram
2.2 Entity-Relationship Diagram
2.3 Sequential Diagram
2.4 use case Diagram
2.5 Activity diagram
3. Project Cost Estimation
4. Designing user interface
5. using of testing
5.1 White box Testing
5.2 black box testing
5.3 units testing
5.4 Integration testing
5.5 system testing
3|Page
1. PROJECT SCHEDULING AND INITIATION
Student Admission System
1.1 Problem Definition:
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.
It is required to Design of a Computerized Automated Student
Admission System, to speed up and make it easy to use system.
1.2 Purpose:
This document gives the detailed function and Non-functional
requirements for the School Admission Process Management
System.
The purpose of this document is that the requirements mentioned in
it should be utilized by software developer to implement the system.
The various activities carried out are:
1). Student Admission System Supports the student admission and
registration process, the maintenance of student personal, academic
and fee related data.
2). Database maintained by this system usually contains the
student’s personal, academic and its fee related information. It
focuses on storing and processing (insertion, updation) by using web
pages
3). Generates student information in formatted html tables,
generates the fees Invoice.
4). Generate Student’s Academic Detail Report.
5). Generate Student’s Personal Detail Report.
4|Page
6). Generate Student’s Fee Deposition Status Report.
7). Generate Student’s currently deposited their fees.
8). It Stores Merit list provided by University.
1.3 Scope:
The product will maintain the admission process of nursery students,
primary students, and higher standard students.
An application Software it will work for an institute conducting a
professional course like MCA/MBA under a governing university.
SAS Manages student (personal, academic, fees) Details.
Students are admitted according to the college allotted by university
according to their merit in examination and their choice of college.
Activities like Updation, Creations done in the system by the System
Operator will be maintained in the form of tables for auditing and
maintaining the integrity of the system.
1.4 Project requirements:
1. Functional requirements:
This section provides the over view of the product.
The project will require the PHP as a front end and at the back end
the database MYSQL will be running.
Various functional modules that can be implemented by the product
will be:
i.
ii.
Students registration / reference Id
Appointment (for interview) scheduling(check whether student
is eligible for the interview)
5|Page
iii.
iv.
v.
vi.
Interview selection(includes marks sheet, leaving certificate
,interview questions)
Create bio-data of student(who passed in interview)
Medical test
Payment / admission fees
2. Software Requirements:
Operating System: Microsoft Windows XP
Front End tools: HTML, ASP.NET
Back End tools: MS Access, SQL server
3. Hardware Requirements:
CPU: Pentium VI processor
RAM: 512 MB
HDD: 40 GB
Keyboard, Monitor, Mouse, Printer
1.7 Feasibility study:
It is to serve as a decision document. It has three questions to
answer.
Since, the present system is manual all the work is done in papers
and ink by hand so it is much costly and difficult to use and to
operate and it is also time consuming.
So our automated computerized student admission system is much
feasible, in cost, time, and efforts as compare to the previous manual
system.
It is economically feasible, it will only require a single operator to
operate the system, who
is responsible for entering the data into the database via a user
interface provided to him, who can also able to show all the data in
html tabular form so to provide information regarding the students
who are either taken admission or to take admission, since it
6|Page
requires only a single person to operate the whole system thus
reduces the cost to operate the system.
It is technically feasible, since the whole system is designed into the
latest technologies like ASP.NET and MS Access and SQL Server which
are the most recent technologies to develop web based systems and
design databases.
It uses the latest hardware technologies like P4 Systems so
It is Behavioral feasible, since the system is providing a attractive
user interface to the operator/end user, so he feel very easy to work
onto it. Response to operator/end user is very fast and very good.
Since, as we mentioned above that it requires much less amount of
cost, it uses computer work so it is very fast to operate and it is very
easy for user to work on it.
1.8 Working of present system:
In present, all work is done manually by hand in bulk of files which is
hard to operate and hard to maintain the reports of the student
presently, took admission in institute.
1. When the student comes in school.
2. First of all, he/she takes admission form from reception.
3. Fills it and submits it into office.
4. Filled form is first checked with documents like merit list and
details came from university and verified by an official person, if
there is any mistake then it is corrected
.
5. At the time of submission of it the fees is deposited by the
candidate.
6. At the time of submission of admission form enrollment no. is
assigned to the candidate by the institute.
7. Candidate gets the receipt of fees deposition.
7|Page
1.9 Disadvantages of Present System:1. Require much man power i.e. much efforts, much cost and hard to
operate and maintain.
2. Since, all the work is done in papers so it is very hard to locate a
particular student record when it is required.
1.10 Proposed System:1. It is automated computerized web based software system.
2. It uses latest technologies like ASP.NET and SQL Server.
3. It is easy to operate.
4. Attractive User Interface
8|Page
2. DIAGRAMS
2.1 Data Flow Diagram
Fig – Data Flow diagram of school admission management syste
9|Page
2.2 Entity-Relationship Diagram
Fig – ER diagram of school admission management system
10 | P a g e
2.3 Sequential Diagram
Fig – Sequential diagram of school admission management system
11 | P a g e
2.4 use case Diagram
Fig-school use case diagram
Fig-school database use case diagram
Fig-student use case diagram
12 | P a g e
2.5 Activity diagram
Fig – Activity diagram of school admission management system
13 | P a g e
3. PROJECT COST ESTIMATION
 The software cost estimation is the process of predicting
resources required for the development of the project.
 Fundamental questions that are asked to judge the estimation
are 1. How much effort is required to complete the project?
 2. How much calendar time is needed to complete the project?
 3. What is the total cost computed for an activity
 Various cost components are1. Hardware and software cost.
2. Travel and software or technology training cost.
3. Effort costs(this is most essential factor in many
projects).It may involve Salaries of employees involved in the project.
 Social and insurance cost.
4. Cost of building, heating and lighting.
5. Costs of networking and communications.
6. Costs of shared facilities such as library, staff.
 Once the project is in progress the project manager should
regularly update their cost and schedule estimate. This helps in
effective utilization of the resources.
 Software price to the customer is equal to cost of the software
project plus profit.
14 | P a g e
1.11 GANTT CHART
15 | P a g e
4. DESIGNING USER INTERFACE
16 | P a g e
5. USING OF TESTING
1. White box testing:
 It is also called as STRUCTURAL TESTING or GLASS BOX
TESTING.
 Testers use the knowledge of internal logic of the system.
 Mostly verification techniques are used.
 It does not ensure that the user requirement had been met.
 The test may not mimic the real world situations.
 Cost is very high since expert testers are required.
 Example: feasibility review, designer review, code inspection
and code walk through.
2. Black box testing:
 It is also called as FUNCTIONAL TESTING. These tests are
conducted at interface.
 Testers do not have information about the internal
functionality of the system.
 Mostly validation techniques are used.
 It stimulates the actual system usage.
 They have potential of not detecting the logical errors.
 The possibility that efforts are duplicated is high.
 Example: unit testing, integration testing, system testing, and
acceptance testing.
3. Unit testing:
 In unit testing the individual component are tested
independently to ensure their quality.
 The focus is to uncover the errors in design and
implementation.
17 | P a g e
 The various test that are conducted during the unit test are
described below:
i. Module interfaces are tested for proper information flow in
and out of the program.
ii. Local data are examined to ensure that integrity is maintained.
iii. Boundary conditions are tested to ensure that the module
operates properly at boundaries established to limit or restrict
processing
iv. All the basis (independent) paths are tested for ensuring that all
statements in the module have been executed only once.
v. All errors handling paths should be tested.
4. Integration testing:
 A group of dependent components are tested together to
ensure their quality of their integration unit.
 The objective is to take unit tested components and build a
program structure that has been dictated by software design
 The focus of integration testing is to uncover errors in:
 Design and construction of software architecture.
 Integrated functions or operations at subsystem level
 Interface and interaction between them.
 Resources interaction and / or environment integration.
 The integration testing can be carried out using two
approaches.
i. The non incremental integration.
ii. Incremental integration
18 | P a g e
5. System testing:
The system test is a series of tests conducted to fully the computer
based system.
Various types of system tests are:
I.
II.
III.
IV.
Recovery testing.
Security testing.
Stress testing.
Performance testing.
The main focus of such testing is to test







I.



II.

System functions and performance.
System reliability and recoverability(recovery test).
System installation (installation test).
System behavior in special condition (stress test).
System user operations (acceptance test).
Hardware and software integration and collaboration.
Integration of external software and the system.
Recovery testing:
Recovery testing is intended to check the system’s ability to
recover from failures
In this type of testing the software is forced to fail and then it is
verified whether the system recovers properly or not.
For automated recovery then reinitialization , check point
mechanisms , data recovery and restart are verified
Security testing:
Security testing verifies that system protection mechanism
prevent improper penetration of data alteration.
19 | P a g e
 It also verifies that protection mechanism built into the system
prevent intrusion such as unauthorized internal or external
access or willful damage.
 System design goal is to make the penetration attempt more
costly than the value of information that will be obtained in it .
III. Stress testing:
 Determines breakpoint of a system to establish maximum
service level.
 In stress testing the system is executed in manner that
demands resources in abnormal quality, frequency or volume.
 A variation of stress testing is a technique called sensitivity
testing.
 A variation of stress testing is a technique called sensitivity
testing.
 The sensitivity testing is a testing in which it is tried to uncover
data from a large class of valid data that may cause instability
or improper processing.
IV. Performance testing:
 Performance testing evaluates the run time performance of the
software especially real time software.
 In performance testing resources utilization such as CPU load ,
throughput ,response time, memory usage can be measured.
 For big system (e.g. banking system) involving many users
connecting to servers (e.g. using internet) performance testing
is very difficult.
20 | P a g e