Presentation tier

The presentation tier for the College Admission System is HTML. Web Forms with Master Pages. The presentation tier

takes care of user interaction and the visual part of the application. The various Web from used by clients are listed below:

HTML Web Forms Definition

[Link] This is default page, called first time when user access the
application. Having login form .user must provide credential
for access the functioning of the system

Welcome .html This web page is blank dashboard

Session .html This page contains the list of all session created & show the
start -end date, active & completion detail.

Program_ [Link] This web page shows the details of programme group i.e.
Diploma, or PG

[Link] This web page is use to functioning link of CRUD, & shows
the list of programs offer by university.

Program _ intake .html This web page use to assign seats to colleges for a particular
course in the active session.

Manage _student .html This web from is use to enter enrolled student detail.

Institute _ [Link] This web form is use to create user for the system, user are
the colleges who will access the student form for enter their
detail.

User _right.html This web page is use to assign the rights to access the module
of the system.

Static_report.html This web page is used for display the static data of the
student, college wise i.e. admission statics, boys-girls ration
etc.

Graphical_report.html This is report is same as static report but show the data in
graphical from in pic & bar chart.

Admission_report.html This report is used for show the detail of information of the
student in college wise program wise & combine.
 ABSTRACT
Abstraction is an indispensable part of the design process and is essential for problem partitioning. Partitioning essentially is the

exercise in determining the system components a not isolated from each other but interacts with other components. Abstraction is

used for exit components as well as components that are being designed. using this abstraction behavior of the entire system can

be understood.

ABSTRACT STRUCTURE:

Admin User

College User

Login

Master Manage User SIS Management SIS Reports

User Rights Admission Form

Session Program Group Programs Assign Programs Program Intake

Admission Graphical Static Report

Report Report

Fig. 1 System Structure

 ACKNOWLEDEMENT

At the outset, we offer our sincere thanks and deep gratitude to Mr. Sandeep Deora I had the

privilege to receive great inspiration and guidance from him, which helped us to the objectives of this

study and complete the report. I am fortunate to have constant encouragement and practical guidance in

all aspect of our study. his experience in this line has been a boon to us in this respect.
 TABLE OF CONTENTS

CHAPTER1: INTRODUCTION Page

1.1 Background 7
1.2 Objective 7

1.3 Purpose, Scope and Applicability 8

1.3.1 Purpose 9
1.3.2 Scope 9

1.4 Achievements 9

1.5 Organization of Report 9

CHAPTER 2: SERVEY OF TECHNOLOGY 10

CHAPTER 3: REQUIREMENT AND ANALYSIS 10

3.1 Problem Definition 10

3.2 Requirement Specification 11
3.3 Planning and Scheduling 13
3.4 Software and Hardware requirements 18

3.4.1 Hardware Requirements 18

3.4.2 Software Requirements 18

CHAPTER 4: SYSEM DESIGN 19

4.1 Data Flow Diagram 20

4.2 Data Dictionary & Data Model 22

4.2.1 Schema Design 23

4.2.2 Data Model 27
 4.3 Analysis & Designing 27

4.3.1 System Analysis 27

4.3.2 System Designing 28

4.4 User Interface Design 28

4.5 Three tier Architecture 30

Chapter 1 INTRODUCTION

1.1 Introduction

Today, computerized processing of transaction data is an activity of almost any organization. In this generation, everybody’s life

becomes in computerized. They go ahead with the computer. The areas of computer applications are literally too numerous to

mention. Computers have become an integral part of man’s every-day. They dominate every sphere of life be it entertainment,

education, banking, insurance, medicine, design or manufacturing. Actually this generation is the era of rapid growth of

Information Technology. IT has change the working process in all fields of human being. So they continue grow and the open

new horizons of discovery and application. One of the primary reasons for the immense popularly of computers is the speed with

which they can accomplish specific tasks. However computer applications are not always easy to use.

It is a simple small system illustrated by using the most common features of Visual Basic. This project includes student admission

and record management in the Colleges & Universities. With this project it is tried to manage this things easily and with less time

fo the organization “Tumkur University”. The problem while managing data in traditional method i.e. in excel & paperwork, they

lost some of information of newly enrolled students, sometime it happen that colleges give admission more than available seats

which become issue in the time of examination. University wants to restrict & allow colleges to fill the admission within the

allotted seat in particular that session.

The basic web language used in this project is Php and the database of the whole project is created used MYSQL Server. The

front end is designed in HTML jQuery & CSS and the back end is mysql database. By using the front-end user can access data

from database as well as store data in the database. By using the Menu system user can use the other functioning of the

application.
1.2 Objective

Tumkur University having about 80 affiliated college & 3 constituent colleges. Which are offer main stream UG & PG courses as

well as some professional courses like BCA, MCA & MBA. Each academic session, University accept new admission from the

affiliated & constituent colleges as per seat allocation. In the manual / current system these colleges provide the original

documents, the list of students & the soft copy excel sheet which has the entire information of the student after the ending of

admission season & a representative of these college app_____ itself to deliver all these data.

University want to receive all these data on real time & want to apply a uniform method to get the information from all

the colleges for verification.

The student admission process is managed in all the academic institutes i.e. school & colleges, mostly in a manual

procedure. But in the manual procedure there may be so many drawbacks. In the manual procedure it is quite lengthy to keep all

the records. Sometimes information may be recorded incorrectly. The major objective of the proposed computerized system is to

overcome the drawback of the existing manual system to provide a paperless office environment. The other objective of this

system includes providing an information sources, increasing efficiency, productivity and build greater user satisfaction and

eliminating duplication of records. So we have found the required information quickly to improve the various data processing.

The proposed system is important for the store of data with minimum redundancy. It is also important for further use. This will

maintain the data integrity. During the designing of the software my main objective will be make it a user friendly one.

Primary Objectives can be notified as listed below:

o Develop a model of the enterprise from an information viewpoint in order to improve communications, both within and

outside the organization.

o Monitoring student data, document and reports that create, process, store, and disseminate information.

o Utilization of information resources effectively to achieve the overall goals and mission of the organization.

1.3 Purpose and Scope

1.3.1 Purpose

College Admission System would have the following goals.

 Provide a user interface to add, view modify & delete records in different courses.
 Provide a user interface to register student.
  Provide a user interface to change user settings like password and view profile.

 Provide a user interface for administrator to mange the user & students record & module accessibility rights.

 Provide a master data functioning to add dynamic list of different kind of data _____ session master, program course
master etc.

 System is developed in aspect to enhance the functioning area from admission module to Student information System
where user can manage student’s information, their promotion in the next level, attendance & marks.

1.3.2 Scope

The main scope and deliverables of the project would be to:

 Understand and prepare detailed requirement and specifications.

 Prepare high level and detailed design specifications of the system.

 Prepare Test Plan and Test cases.

 Develop the system and coding

 Perform unit testing integration and system testing

 Demonstrate a bug free application after suitable modification if needed.

1.4 Achievements

By successfully implementing College Admission System, a substantial knowledge has been acquired on the implementation of a

server-based database system. this knowledge will be useful in the future in creating any type of application or database system.

The objective of College Admission System was the creation of a useful application for the colleges which has been fulfilled.

This system can be easily modified to serve the needs of nay reminder.

1.5 Organization of Report

This report is organized in seven chapters. As indicated in the Table of Contents. These chapters deal with the important aspects

of the Systems Development Cycle. Each of the chapters is divided into Headings and Sub-Headings. Chapter I introduces the

project, its background and purpose. The technologies used in the project and the reason thereof are explained in Chapter 2.

Chapter 3 broadly deals with the requirements. Analysis and planning of the project. All the design aspects have been death with

in Chapter 4 including schema design. interface design.

Security and test cases. The actual implementation has been discussed in Chapter 5, which includes coding and testing of the

working of the system. Chapter 6 discusses the test reports and project documentation and finally the conclusions have been

drawn in Chapter 7. At the end of the report, the reference made and the glossary has been included.
Chapter 2. SURVEY OF TECHNOLOGY

In a web-based application like FEDENA, Edu Craft, there is a scope for a large number of platforms, Languages., web servers

and frameworks to choose from. Before selecting from this large array of technologies, the following aspects, which are

characteristic to web-based application like this one, have been kept in mind:

 Dynamic page generation

 Data validation

 . Performance

 . Reliability

 . Scalability

 . Security

 . Portability

 . Performance

 . Time constraint

 . Cost constraint

Chapter 3. REQUIREMENTS AND ANALYSIS

3.1. Problem Definition

The first step to the system analysis process involves the identification of need. The intent is to understand the software objective

and to define the goals required to meet the objectives.

The existing system

Description of the existing system is explained below-

(a) Form Received From Students: University & college accept the form from the students, thus they manage the data into

files & excel sheet with the each of information that students has provided. In other case Colleges send these excel
4. Security should be high such that no intruder can tamper with data.

5. The access of the system should be traceable to identify whow are the users of the system and when they last logged in to the
system.

Feasibility Study

Feasibility Study is one of the fundamental aspects in design of system.

The key-points are as follows:-

1) Form a project team and appoint a project leader.

2) Prepare system flow chart.
3) Enumerate potential candidate systems.
4) Describe and identify characteristics of candidate systems.
5) Determine and evaluate performance and cost effectiveness of each candidate system.
6) Weight system performance and cost data.
7) Select the best candidate system.
8) Prepare and report final project directive to management.

Three key considerations are involved in the feasibility analysis:

i. Technical
ii. Operatuibak
iii. Economical

Technical Feasibility:

It specifies whether the proposed solution in the project is possible to be implemented using available hardware and
software.

Operational Feasibility:

Operational feasibility considers the factors that how the software will satisfy the need of the users, how it could be
changed for future requirements and the operational factors of the computer.

Economical Feasibility:

This defines the measuement cost effectiveness of the project. It further consists of two parts:

a. Direct cost.
b. Indirect cost.

Economincal Feasibility of the Proejct:

a) Initial cost for development is not high since a machine with required configuration was available in the company.
b) Necessary software for back-end and front-end use were also available there.
3.3 Planning and Scheduling

[Link]

The purpose of Project Plan is to define all the techniques, procedures, and methodologies that will be used in the project to
assure timely delivery of the software that meets specified requirements within project resources. This will be reviewing and
auditing the software products and activities to verify that they comply with the applicable procedures and standards and
providing the software project and other appropriate managers with the results of these reviews and audits.

Giant Chart for College Admission System

Process Name Week Week Week Week Week Week Week Week Week
1 2 3 4 5 6 7 8 9
Collect system Requirement
Prepare SRS Report
Module development
Module Testing
Test Case Resolutions
Implementation
User Training
Software Handover

Fig 5 : Giant Chart for College Admission System

The table below show the Project Phases in terms of data dureing the project development

Phases Shart Date End Date

Inception Feb 15th 2016 Feb 22nd 2016

Implementation Feb 23rd 2016 Apr 30th 2016

Elaboration May 1st 2016 May 10th 2016

Table : 1 Project Phase Schedule

The Table below shows the break-down of time spent in each phase for Research, Design, Coding, Testing and Documentation.

Inception(Hours) Implementation Elaboration (Hours) Time

(Hours)
Research 20 25 5

Design 17 20 5 42

Coding 0 210 34 247

Testing 0 15 30 45

Documentation 20 28 20 68

Total 57 298 97 452

Table: 2 Phase Breakdown

The Pie chart in Fig.1 shows the hour break down for each phase.
The pie chart in Fig 2 shows the Time allocated for various tasks during the Project Implementation.

UML and Software Lifecycle

As software student though I have good knowledge in UML and Software LIFE cycle I never had any good practical experience

regarding them. Through this procjet I have learnt how to develop a project followiing the various stages in Software Life Cycle.

Documentation
I always had a feeling that I am not good at documentation. But through this project and suggestions from my committee

members I believe that I have improved my Documentation skills.

2. Management
2.1 Organization and Responsibilities
The organization consists of supervisory committee, major professor, developer and formal technical inspectors. The committee

will be responsible for attending the presentation and Sheet to university to manage record & to get enrolment no for the

students each offered courses.

(b) University’s expect from all colleges to provide all mandatory information verified student’s documents and information

which is most important for further student reports i.e. Marks-sheet / Reports Card, Migration certificate & Degree.

Drawbacks of the existing system:-

The main drawbacks of the existing system are:

 Maintenance of paper is very tedious process.

 Take extra time & may cause of delay in providing data from the college if they don’t prepare it in time.

 Data inconsistency can occur due to the duplication of information.

 The data processing speed of the manual process is very slow.

 Redundant and repetitive works had to be done manually.

 Difficult to find out the information of single or as per required search criteria

 Searching process is very problematic since data are stored in files.

 Data may be lost.

 Reports are generated manually. There is also a chance of missing of the reports when they are generated manually.

 Number of Admitted student can exceed if there is no restriction in the system & can cause of illegal issues.

 No, seats can be changed as per UGC rule, should be maintain.

3.2 Requirement Specification

Requirements Specification involves the basic requirements that the system to be developed should possess. These
can be broadly classified into two types.

1. Performance Requirements.
2. Functional Requirements.

Understanding the requirements specificatin is critical for the project’s success otherwise the system does not get developed
according to the suctomer’s wishes.

Performance Requirements:
1. The system should be bilt in a way such that it is independent of the type of database use (MYSQL, SQL Server etc.)

2. Response should be fast.

3. High throughput.
reviews at the end of each phase. After each presentation, the committee will provide feedback and suggestions regarding the
project.

Project Manager
The project manage will be responsible for supervising and evaluating the work and progress done by the developer on a weekly
basis.

Developer
The developer should submit all the deliverable and complete the project functionalities on time. He should keep updating his
weekly progress to the Major Professor.

Formal Technical Inspectors

The formal technical inspector will be responsible for a technical review of the architecture design artifacts and the formal
requirements specifications and will also be required to submit a formal report base on their findings.

Formal Technical Inspection Checklist

Item to be Inspected Pass/Fail/Partial Comments

All the symbols used in the class diagrams are according

to the UML standards.
All the classes in the class diagram are clear as to what
they represent in the architecture design document.
The symbols used in the sequence diagram correspond
to UML standards.
Sequence diagram matches class diagram.
All the classes in the USE model are represented in the
class diagram
The multiplicities in the USE model have been
Depicted in the class diagram.

All the requirements in the Software Requirements

Specification have been covered in the Architecture
Design Document.

2.2 Tasks
All tasks to be performed are mentioned in the Project Plan 1.0 After the first phase if any changes are quired the Major

Professor will discuss with the developer.

4. Documentation
The documentation will consist of all the deliverables. They are vision document, project plan, sotware quality assurance plan,

formal requiremets specification, architecture design test plan, formal technical inspection, prototype, user manual, component

design, source code, assessment evaluation, project evaluation, references, and formal technical inspection letters. The

committee memers will review all documentation for final approval.

All documentation will be posted on the developer’s website.

5. Reviews and Audits

All the deliverables produced in each phase of project development are reviewed by the major professor and supervising

committee. These are evaluated by the committee, at the end of each phase and provide comments on the software prototype

as well as suggestions for any changes or addition to the requiremtns specification. The two formal technical inspectors will

assess the architecture design artefacts and submit a formal report based on their findings.

6. Tesh and Problem Reporting

All the testing procedures used for the project would be mentioned in the test plan document at the end of second phase. The

results would be reviewed and all the unresolved problems will be reported toe the committee members.

7. Tools, Techniques and Methodologies

The following tools, techniques and methods would be used for the project for the specified purpose:

 Coding:- CSS, HTML, PHP, Dreamweaver IDE, MySQL server & SQLyog

 Testing:- Manual & Automation testing QTP

 Documentation: - MS Word, Rational Rose, MS Project, OCL

[Link] collection, Maintenance, and Retention

Three sets of design documentation would be produced and distributed to the University Library, Major Professor and

developer. The source code, documentation and web pages are submitted to the Major Professor in the form of a CD.
9. Deliverables
The deliverables for all the three phases are listed below:

Phase I
 Vision Documet 1.0
 Project Plan 1.0
 Software Quality Assurance Plan

Phase II
 Action Items- identified during phase I
 Vision Document 2.0
 Project Plan 2.0
 Formal Requirements Specification
 Architecture Design
 Test Plan
 Formal Technical Inspection
 Executable Architecture Prototype

Phase III
 Action Items- identified during phase I
 User Manual
 Component Design
 Source Code
 Assessment Evaluation
 Project Evaluation
 References
 Formal Technical Inspection

3.4 Software and Hardware Requirements

3.4.1 Software Requirement

This software is design for access over the network, so that every user can access this from any remote
place. For this purpose it will be require to upload the software to a web host apache server like godaddy & bigrocks. The
software quire for this software ate

1. Apache 2.0 web server with ssl secure certificate

2. Php 5.4x version
3. Mysql database version 5.3x
3.4.2 Hardware Requirement

To access the software user need at least a computer system that have internet connectivity and have updated
browser. These are the following hardware requirement for the software:
1. Mozilla Firefox 17.0+, chrome browser, opera browser

2. Internet connection having minimum 512 kbps bandwidth

3. System requirement depends on browser basis

CHAPTER 4: SYSTEM DESIGN

4.1 Data flow diagram
A DFD is a graphical tool, which has the purpose of clarifying system requirement and identifying major transaction
that will become programs in the system design. It is also known as “Bubbles chart”, which has the purpose of defining
system requirement and in functionally decomposes of requiement specification down to the lowest level of detail. The
DFD consists of series of bubbles joined by a line. The bubles represent data transformation and the line represents the
flow of the data in the system. The DFD provides a mechanism for function modelling as well as information modelling. So,
it is the starting phase of the design phase. DFD symbols are: A process

The destination system data

The flow of inforamtion

The table in which inforamtion

Will be started
4.2 Data Dictionary & Data Model
In DFD, a data item that flows between processes is identified by unique names. Data Dictionary is repository of
various data flows defined in a DFD. It contains the details of the structure of data itmes and files used in DFD’s. A data
dictionary defines each term encountered dureing the analysis and design of a new system. Data elements can describe files,
data flows as usual processes.

The term may have one of several closely related meanings pertaining to databases and database management systems (DBMS):

 a document describing a database or collection of databases

 an integral component of a DBMS that is required to determine its structure

 a piece of middleware that extends or supplants the native data dictionary of a DBMS
4.2.1 Schema Design:
Database Design
Usually, a collection of interrelated data is referred to as database. The database contains information about one particular
enterprise. The management of database involves both definitions of structures of the stage of information. In addition, this
database system must
4.3 Analysis Design
4.3.1 System Analysis
System analysis is a study of various operation performed by a system and their relationship within and outside of the

system. It is a systematic technique that defines goals and objectives. The goal of system development is to deliver the system in

line with the user’s requirement and analysis is the heart of this process. Out of the main aspects of analysis it is defining the

boundaries of the system and determining whether or not a candidate system should consider other related system.

System study has been conducted witht eh following objectives in mind:

Identify the user’s needs.

 Evaluate the system concept for feasibility.

 Perform economica and technical analysis.

 Allocate functional to hardware, software, people, database and other system elements and

 Establish cost and schedule constraints.

Both hardware and software expertise is required to sucessfully attain the objectives listed above.
4.3.2 System Design
The most creative and challenging phase of the System Life Cycle is System Design. This refers to the technical

specifications that will be applied in implementing the candidate system. System design specifies how the system will achieve

the objective of the proposed system.

 Logical Design: Logical System Design involves developing gneral specification for how the basic information

system activities of input, processing, output, storage and control can meet end user requirements.

 Physical Design: Physical Design involves the detail design of user interface methods and procts, database

structures, processing and control procedures.

4.4 User Interface Design

The first step in System Design is the User Interface Design. The User Interface Design activity focuses on the

preparation of input and design of output reports in a form acceptable to the users.

User Interface Design consists of two steps- Input Design and Output design.

 Input Design: Input Design is the process of converting user originated inputs to a computer based format. The goal

is a make the data entry as easy, logical and free from errors as possible.

 Output Design: Computer output is the most important and direct source of information to the user. Efficient,

intelligible output design helps the user in decision making. Provide for safely information storage in the database,

system crash or unauthorized access

4.5 Three-tier Architecture
There-tier (layer) is a client-server architecture in which the user interface, business process (business rules) and data storage
and data access are developed and maintain as independent modules or most often on separate platforms.

The Architecture of College Admission Systemis based on three-tier architecture. The three logical tiers are

 Presentation tier-HTML & Javascript Web forms, m=Master Pages, Images

 Middle tier- PHP Script & library classes.
 Data tier-MYSQL Database
Fig4 below shows the model of 3-tier architecture for the College Admission System is as follows:

Flexibility:
 Management of data is independent from the physical storage support.
 Maintenance of the business logic is easier.
 Migration to new graphical environments is faster.
 If there is a minor change in the business logic, we don’t have to install the entire system in individual user’s PCs.

Reusability:
 Reusability of business logic is greater for the presentation layer. As this component is developed and tested, we can
use it in any other project and would be helpful for future use.

Security:
 More secured architecture since the client cannot access the database directly.