Chapter 1: Introduction To Project

Online Student Administration System
CHAPTER 1: INTRODUCTION TO PROJECT
1.1 PROJECT BACKGROUND
1.2 LITERATURE SURVEY
1.3 PROBLEM DEFINATION
1.4 SOFTWARE REQ UIREMENT SPECIFICATION
1.5 REQUIREMENT AND CONSTRAINTS
`1 | P a g e CO-6 G, G.V.Acharya Polytechnic

1 .INTRODUCTION TO PROJECT
1.1 PROJECT BACKGROUND
Student Online admissions are a vital part of any university’s running because students are what keep a
University alive. The Student admission is one of the most important activities within a university as one cannot
survive without students. A poor admissions system can mean fever students being admitted into a university
because of mistakes or an overly slow response time.
Online Student Admission System is the software which is helpful for students as well as the department In this
project, the student is facilitated by the online system for registering students admission form Our Student
Management System deals with the various activities related to the students.
`In the Software we can register as a user and user has of two types,. “ Student & Administrator”
Administrator has the power to add new user and delete a user. Through this online system we overcome many
Problems.
 Time and Money is saved.
 Nothing is done manually.
 Long lines in the department for these issues.
1.2 LITERATURE SURVEY

A HRMS refers to the systems and processes at the intersection between human resource management
(HRM) and information technology. It merges HRM as a discipline and in particular it’s basic HR activities and
processes with the information technology field whereas the programming of data processing systems evolved
into standardized routines and packages of enterprise resource planning (ERP) software.
An organization or company with a very large number of employees manages a greater volume of data.
This activity can be daunting without a more sophisticated tool to store and retrieve data. The various levels of
sophistication can be examined by looking at the evolutionary aspects of HR technology. These aspects can be
characterized into four stages of development: Paper-based systems, early personal computer (PC) technology,
electronic databases, and Web-based technology.
The technology of the future will be about speedy access to accurate current information, and reliability
to access
this information via multiple systems will give organizations a strategic edge. HR is expected to relinquish its
role as sole owner of HR information, so that managers and employees can use this information to solve their
own problems using Web-based systems.
This new system will not necessarily mean reduction in HR staff. The new system will enable HR
professionals to focus on transforming information into knowledge that can be used by the organization for
decision making; it will be about HR and IT working together to leverage this technology.
The two most popular Web-based HR applications used today are self-service for employees and self-
service for managers. These applications have enabled companies to shift responsibility for viewing and updating
records onto individual employees and have fundamentally changed the manner in which employees acquire
information and relate to their HR departments.
1.3 PROBLEM STATEMENT

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.
Recently, most major universities have moved from phone-based registration systems to web-
based systems that allow students to search and register for courses. As more universities follow this trend and
begin to only offer online registration, it will become increasingly important for these systems to be considered
usable by all students. In addition to the system being usable, it must also provide the student with convenient
access to information that will ease the course scheduling process.
The idea for the project was mostly motivated by the online admission system. It seems
unacceptable that such a large colleges would have a system that offers such a low level of flexibility and lacks
functionality to make the process easier for the students. Combining our knowledge of other course registration
systems, we came up with a list of features that are important to an online course registration system.
Between the two of us we had experiences with a number of course registration systems, each
of them had their strengths, but none of them encompassed all the necessary functionality in a reasonable way.
The following examples a demonstrate some of the most common weaknesses. Most of the systems did not
include enough information about the courses. For example, system did not allow the user to see the course
description, the user would have to navigate another area of the colleges website to access this information. When
registering, it would be helpful to have all of this information in the same place. Some systems did not allow for
flexible searches. This includes the systems that only allowed searches based on one field, such as department.
With some systems it was inconvenient to view the classes a student was already registered for. it only showed a
list of the courses ordered by department.
Using the weaknesses from existing systems, we decided a useful system would have the
following characteristics. Searching for a course should be as flexible as possible to allow the student to either
find a specific course or a group of possible courses to consider. All information about the courses should be
available from the search results page. The student should be able to view their registered courses from anywhere
in the course registration system, and the courses should be displayed in a way that provides the student with all
useful information.

1.4 SOFTWARE REQUIREMENT SPECIFICATION
1.4.1 Purpose
The purpose of this OSA document is to specify software requirements of the Online Admission
for the university. It is intended to be a complete specification of what functionality the admission provides. The
main purpose of the system is to automate the task carried out by different peoples in the organization to perform
the student admission. Specific design and implementation details will be specified in a future document.
1.4.2 Project Scope
This project’s aim is to automate the system, pre-checking the inclusion of all required material and
automatically ranking each student’s application based on a number of criteria. These criteria include the ranking
of their university, their grade at said university and their language grade Certificate. The data used by the system
is stored in a database that will be the centre of all information held about students and the base for the remainder
of the process after the initial application has been made. This enables things to be simplified and considerably
quickened, making the jobs of the people involved easier.
1.5 . REQUIREMENT AND CONSTRAINTS

1.5.1 Functional Requirements:
 Authentication
Login Module: Login module will help in authentication of studennt accounts. Those student who have
valid login id and password can only login into respective accounts.
Update/Delete Module: Suppose there are hundreds of students and from this we have to update/search a
particular student and we know the name of the student , in manual system it is a tedious task though we know
the name of the student, but using this module we can easily update/delete student by specifying the name of
the student in the search criteria .
User Management: This module will help the administrator in enabling /disabling a user account and
updating user information as required.
 Authorization
User role check- After logging in, the administrator will be checked from the database and the user
interface will be displayed according to their role.

 Process Data
Display - Student with defined roles can display the content of the database. Being more specific,
student can only view his/her personal information. Admin can display all student information.
Edit - A user with student role can edit his/her specific personal information. Admin can only edit
Student’ personal information that is under his/her coverage except user role type. Admin can edit all
information related to all student including their user role type.
Search- User with Admin role can search the content of database for the student who are under his/her
coverage. Admin roles can search all the student information in the database. Search feature works on
specific keywords showing student’s characteristics, skills, features, and etc.
Update authentication - This feature can be used only by admin role type. Admin can update the role
type of a specific student.
 Leave Application/Approval
Leave application- The student can be able to fill in leave application form in the appropriate fields.
Leave approval- The admin can be able to approve leave applications based on the reasons stated,
length of leave as well as available on a department.
 Recruitment
Add new student- Admin role type is able to add a new student id to the database. The new student will
have all the valid required personal information related to him/her. The new created student will have
an id.
 Report generation
Report generation- Admin shall be able to generate a report for each employee based on the
information in the database.
1.5.2 Functional Requirements:

 Performance requirements
Automate manual paper work done at the time of student’s admission in the institute.
Eliminate paper work.
Efficiently manage the student (academic, personal) details..

 Hardware requirements
Minimum 2GB RAM
Processor-Intel Core 2 Duo and Higher

Hard disk- 25GB of Hard Disk Space
Others: Mouse, keyboard, and monitor.
 Software requirements
Microsoft Visual Studio 2015
SQL Server 2014
Operating System: Windows 8 and 10
Web Browsers Supported-
1. Microsoft Internet Explorer version 8,9,10,11
2. Microsoft Edge
3. Google Chrome
4. Mozilla Firefox
LANGUAGE USED BY SYSTEM

 ASP.net
 Visual Basic
 SQL

CHAPTER 2: AIM AND OBJECTIVE OF THE

PROJECT
2.1 AIM OF THE PROJECT
2.2 OBJECTIVE OF THE PROJECT
2.3 NEED OF THE PROJECT

2. AIM AND OBJECTIVES OF THE PROJECT
2.1 AIM OF THE PROJECT

The Aim of the project is to automate the system, pre-checking the inclusion of all required material
and automatically ranking each student’s application based on a number of criteria
Our Online Admission System helps our Students to avoid standing at long queues and the process is
simplified
With our Online Admission System students can fill the Admission form online at their convenience sitting
at home or anywhere
The data can be used by Management to keep record of students admitted in college
Students can fill Admission form anytime and anywhere.
Every student get the admission as per there rules and allotted seats
2.2 OBJECTIVE OF THE PROJECT
The objective of the online admission system is to address the limitations of the current
system. To Provide facility for students to fill admission form online at their convenience.The
requirements for the system have been gathered from the defects recorded in the past and also based on
the feedback from users of previous metrics tools. Following are the objectives of the admission
system:
 One of the important objectives of the admission system is communicate with all the students
scattered geographically.
 Reducing time in activities. Reduce the time taken process the applications of students, admitting a
student, verify student marks, and send call letters to selected students.
 Centralized data handling. Transfer the data smoothly to all the departments involved and handle the
data centralized way.
 Paperless admission with reduced manpower. Reduce the manpower needed to perform all the
admission and administration task by reducing the paper works needed.
 Cost cutting. Reduce the cost involved in the admission process.

 Operational efficiency. Improve the operational efficiency by improving the quality of the process. .
2.3 NEED OF THE PROJECT

 The online admission system is totally computerized system.
 The system should be flexible.
 It provide security and authorization. It save time and cost.
 It is user friendly.
 In online admission system , use less man power than manual system.
 In this process the data require less space to store than the manual system.
 Students can easily get information about organization and easily apply for admission.

CHAPTER 3: PROJECT PLANNING AND
MANAGEMENT
3.1 PROJECT DEVELOPMENT LIFECYCLE
3.2 TASKS AND MILESTONES

3. PROJECT PLANNNING AND MANAGENMENT

3.1 PROJECT DEVELOPMENT LIFECYCLE
2.1.1 Initiation:
We got the sponsorship for this project so we are select the “Employee Data Storage System” .
2.1.2 System Concept Development:

In Employee Data Storage System, we define online three sections which are for Admin , HR and for
Employee as per the customer requirements.
2.1.3 Planning:
By the communication with sponsor we understood what the requirements he wants are. Then we plan
according to that.
2.1.4 Requirement Analysis:

Here we gather all the requirement of end user which is required to develop in system. Also we gathered
raw material (software tools and hardware) which are required to develop the system. Then we create
final requirement document list.
2.1.5 Design:
We transform the detail requirement into complete system, design documents, and focuses on how to
delivers the required functionality. We design final UML diagrams of each for our system.
2.1.6 Development:
We prepare test case, procedure, coding, compiling, refining a program then performing test readiness
review.
2.1.7 Integration and Test:

We demonstrates that developed system confirms to requirement as specified in the functional
requirement document conducted by quality assurance, end user (manual), automated testing, and
analysis.

2.1.8 Implementation:
We implement the system into production environment, resolution problem identity in the integration and
test phase.
2.1.9 Operations and Maintenance:

We describe the task to operate and maintain information system in product.
2.1.10 Disposition:
Here we describe how system works and create user manual for end user. Here importance is given to
proper preparation of data.
3.2 TASKS AND MILESTONES
Sr. No Test Case Step Expected Cases Status Build Test
1 Database Connectivity successful Connectivity done Yes

connectivity Do successfullys Successful
2 Admin Login Admin should be Admin Log In Yes

successful Log In. Successful
3 Users Registration System must be able to New user is successfully Yes

register new user register.
4 GUI Design GUI should look fine GUI looking fine Yes
5 Add Employee Employee should be Employee is added Yes

added Successfully
6 Update Employee Employee Details Employee Details Yes
Details should should
Be updated Be updated Successfully
7 Edit/delete Employee should be Employee Yes
Employee changed/deleted changed/deleted
successfully

8 Assign Task to Task should be assign to Task should be assign to Yes
Employee an employee an employee
successfully
9 Login to Employee should login Employee should login Yes
Employee panel to his account to his account
successfully
10 Emplyee can view Employee should view Employee should view Yes
his/her details his/her details his/her details
Successful
11 Generate Report Employee should be Employee can generate Yes
able to generate reports repost successfully
12 Employee can Employee should be Employee should be Yes
view project able to view project able to view project
details details details successfully
13 HR can assign HR should be able to HR should be able to Yes
role to new user assign role to user assign role to user
Successfully
14 Logout User getting logged out User was logged out Yes
Table 3.2 Tasks and Milestones

CHAPTER 4: PROJECT ANALYSIS
4.1 USE CASE MODEL WITH SCENARIO
4.2 ACTIVITY DIAGRAMS

4. PROJECT ANALYSIS
4.1 USE-CASE MODEL WITH SCENARIOS
A use case defines a goal-oriented set of interactions between external users and the system under
consideration or development. Thus a Use Case Scenario is a description that illustrates, step by step, how a user
is intending to use a system, essentially capturing the system behavior from the user's point of view.
In order to create relevant use cases for the system, the following actors for the system have been identified:
Employee
Head Of Department (HOD)
Human Resource (HR)
Admin
Figure 4.1.1 Employee Use Case

Figure 4.1.2 HOD Use Case

Figure 4.1.3 HR Use Case

Figure 4.1.4 Admin Use Case

4.2 ACTIVITY DAIGRAM

UML includes another kind of diagram that between activities as we move from an initial starting point
to desired goal.
They are similar to flowchart or petri nets, traditionally used to model program flow or human activity.The
figure shows the Activity diagram which necessary action in action state in rounded rectangle and transaction
between activity states. It also includes fork for concurrent activity and also fork join.
Figure 4.2.1 Admin Activity Diagram

Figure 4.2.2 HR Activity Diagram

CHAPTER 5: PROJECT DESIGN
5.1 ALGORITHMS IMPLEMENTED
5.2 ARCHITECTURE/BLOCK DIAGRAM
5.3 DETAILED WORKING OF PROJECT
5.4 DATA FLOW DIAGRAM
5.5 E-R DIAGRAM
5.6 CLASS DIAGRAM
5.7 SEQUENCE DIAGRAM
5.8 COLLABORATION DIAGRAM

5. PROJECT DESIGN
5.1 ALGORITHMS IMPLEMENTED
1. Start
2. Displaying the home page with various fields like Contacts us, Gallery, Notifications etc.
3. Show the login option for the Admin, HR , Employee
4. Select the required option by user.
Admin Login :
1. Click on Admin login

2. Enter username and password
3. If Login successfully
4. Go to step 6
5. Else re-enter the username and password
6. Showing the next page
7. Admin check the number of Employees and add new users .
8.Exit
HR Login :
1. Click on HR login
4. Go to step 6
6. Showing the next page
7. HR check the number of Employees and add new users .
8.Perform the required operation
Add Employee
Assign task to Employee
Generate Reports
Create Project Team
9.Logout

Employee Login :
1. Click on Employee login

4. Go to step 6
6. Showing the next page .
8.Perform the required operation
View and Update his/her personal details
View task assign to Employee
Generate progress Reports
View Project details
9.Logout
5.2 ARCHITECTURE/BLOCK DIAGRAM
Figure 5.2.1 System Block Diagram

5.3 DETAILED WORKING OF PROJECT

The system will have three entries for Employee and Admin or HR. In the Admin section he will have the
registration to view employee personl details. He also can add employee by or new user by providing him new
user-id and password , so that employee can login to the system using that user-id and password. He can view his
personl details, he can also edit or update his details ,also he/she can view his/her task assign by HR .
The HR also having login section so he can also do the same task like admin in additional task he can
assign task to particular employee ,he can also make project team and he can also generate report of employee
salary.
The Employee also having a login section . he can login his/her account using user-id and password
which is provided by admin. So he/she can perform required operations which are mentioned above. Also he can
apply for leave request to the admin or hr and then admin or hr check his/her leave status and as per the leave he
approved or disapproved his request.
Software design is a process of problem solving and planning for a software solution. After the purpose
and specifications of software are determined, we develop a plan for a solution. It includes low-level component
and algorithm implementation issues as well as the architectural view. It includes many architectural diagram by
using UML tool like Enterprise architecture,UML2.0 etc. Structural diagrams and Behavioral diagram are the
types of design diagram.
5.4 DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information
system. A data flow diagram can also be used for the visualization of data processing (structured design). It is
common practice for a designer to draw a context-level DFD first which shows the interaction between the system
and outside entities. This context-level DFD is then "exploded" to show more detail of the system being modeled.
.

Figure 5.4.1 Authorization & Authentication Level 0 DFD
Figure 5.4.2 Admin Level 1 DFD

5.5 E-R DIAGRAM
An Entity-relationship model is an abstract conceptual representation of structured data. Entity-
relationship modeling is a relational schema database modeling method, used in software engineering to produce
a type of conceptual data model (or semantic data model) of a system, often a relational database, and its
requirements in a top-down fashion. Diagrams created using this process are called entity-relationship diagrams,
or ER diagrams for short. The first stage of information system design uses these models during the requirements
analysis to describe information needs or the type of information that is to be stored in a database.
Figure 5.5.1 Entity Relationship Diagram

5.6 CLASS DIAGRAM
A class diagramshows which classes exist in the business (during analysis) or in the system itself (during
subsystem design). Figure shows an Employee Data Storage system Class diagram, with each class represented
as a labeled box. Class diagrams (static artifacts) are introduced. As well as the classes themselves, a class diagram
shows how objects of these classes can be connected together.
In the class diagram below, the Employee and Admin classes inherit from the User class. The employee
class is also parent class to Human Resource class, Head of Department class and Ordinary employee class .
Figure 5.6.1 System Class Daigram

5.7 SEQUENCE DIAGRAM
A sequence diagramshows interactions between objects. Communication diagrams also show interactions
between objects, but in a way that emphasizes links rather than sequence. In this sequence diagrams are used
during subsystem design, but they’re equally applicable to dynamic modeling during analysis, system design and
even requirements capture. The above diagram specifies how the customers\ interact with system. Messages are
shown as arrows flowing between vertical bars that represent objects (each object is named at the top of its bar).
Time flows down the page on a sequence diagram.
Figure 5.7.1 Employee Sequence Diagram

Figure 5.7.2 HR Sequence Diagram

Figure 5.7.3 Admin Sequence Diagram

5.8 COLLABORATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration
of the relationships and interactions among software objects in the Unified Modeling Language (UML).
Figure 5.8.1 Employee Collaboration Diagram

Figure 5.8.2 HR Collaboration Diagram

Figure 5.8.3 Admin Collaboration Diagram

CHAPTER 6: PROJECT IMPLEMENTATION

AND CODING
6.1 DATABASE IMPLEMENTATION
6.2 GUI IMPLEMENTATION
6.3 CODE DETAILS

6. PROJECT IMPLEMENTATION AND CODING

6.1 DATABASE IMPLEMENTATION
6.1.1 Data Dictionary:
SR.NO. TABLE NAME ATTRIBUTE DATA KEY/CON

NAME TYPE STRAINTS
ID VARCHAR2 PRIMARY
NAME VARCHAR2 -
CONTACT NUMBER -
EMAIL VARCHAR2 UNIQUE
GENDER VARCHAR2 -
1 ADMIN EDUCATION VARCHAR2 -
PASSWORD VARCHAR2 -
ADDRESS VARCHAR2 -
DOB DATE/TIME -
ID INT PRIMARY
2 DEPARTMENT DEPTNAME VARCHAR2 -
DESCRIPTION VARCHAR2 -
DEPTCODE VARCHAR2 -
CENTERCODE VARCHAR2 -
PERMISSIONS VARCHAR -
ID INT -
3 TASK ROLE VARCHAR2 -
NAME VARCHAR2 -
STATUS VARCHAR2 -
DATE DATE -

ID VARCHAR2 PRIMARY
NAME VARCHAR2 -
ROLE VARCHAR2 -
EMAIL VARCHAR2 UNIQUE
REPORT VARCHAR2 -
4 REPORT DATE DATE -
DETAILS VARCHAR2 -
STATUS VARCHAR2 -
ID INT -
5 TRAINING NAME VARCHAR2 -
ROLE VARCHAR2 -
JOIN DATE DATE -
TRAINING DATE -
DAE
DETAILS VARCHAR2 -
ID INT -
6 PROJECT CUSTOMER VARCHAR2 -
NAME
PROJECT VARCHAR2 -
NAME
EMPLOYEE’S VARCHAR2 -
NAME
DETAILS VARCHAR2 -
DESCRIPTION VARCHAR2 -
DATE DATE -
Table 6.1.1 Data Dictionary

6.2 GUI IMPLEMENTATION

1. HOME PAGE

2. LOGIN PAGE

3. ADMIN SECTION PAGE

4. HR SECTION PAGE

5. EMPLOYEE SECTION PAGE

6. LIST OF EMPLOYEE PAGE

6.2 CODE DETAILS
1. HOME PAGE
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-
awesome.min.css">
<style>
ul {
list-style-type: none;
margin: 25px;
padding: 6px;
overflow: hidden;
background-color: rgb(128,128,128);
}
li {
float: left;
}
ul li {
font-size:20px;
}
li:last-child {
border-right: none;
}
li a {
display: block;
color: rgb(193, 0, 0);
text-align: center;
padding: 14px 16px;
text-decoration: none;

}
#nav{
float:left;
width: 25%;
margin-top: 10px;
margin-left: 10px;
margin-right: 5px;
border-right: 1px solid #cccccc;
border-bottom: 1px solid #cccccc;
padding-right: 10px;
background-color: white;
}
#nav1{
float:right;
width: 15%;
margin-top: 20px;
margin-left: 20px;
margin-right: 1px;
border-right: 1px solid #cccccc;
border-bottom: 1px solid #cccccc;
padding-right: 10px;
}
#main{
float: left;
width: 50%;
margin-top: auto;
margin-left: 1 ;
}

#footer{
clear: both;
border: 1px solid #cccccc;
font-size: 50%;
color: #cccccc;
margin-top: 250px;
padding: 15px 15px 15px 15px;
}
#content{
width: 1000px;
margin-left: auto;
margin-right: auto;
}
#container {
position: relative;
width: 10px;
}
</style>
<style>
table {
border-collapse: collapse;
width: auto%;
}
th, td {
text-align: left;
padding: 5px;
}
tr:nth-child(even){background-color: white}
th {
background-color: rgb(128,128,128);
color: rgb(193, 0, 0);
}

</style>
</head>
<body>
<hr>
<h1 style ="color:#eb9494; text-align:center; ">KOPRAN PVT.LTD</H1>
<hr style =" border-bottom: 2px solid red;">
<ul>
<li><a href="mainhome.php">Home</a></li>
<li><a href="contact.php">Contact</a></li>
<li><a href="about.php">About Us</a></li>
<li><a href="gallery.php">Gallery</a></li>
<li style="float:right"><a href="a.php">Login</a></li>
</ul>
<div id="container">
</div>
<?php
include("connect-db.php");
$fetch=mysql_query("select * from news limit 5");
if(mysql_num_rows($fetch))
{
?>
<marquee behavior="scroll" scrollamount="6" font-size="20" direction="left"
onmouseover="this.stop();" onmouseout="this.start();">
<?php
while($row=mysql_fetch_array($fetch))
{
$newsid=$row['id'];
$headlines=$row['headlines'];
?>

<?php echo $headlines; ?>
<?php } ?>
</li>
<?php } ?>
</ul>
</marquee>
<div id="nav">
<h3>Calender</h3>
<?php
$monthNames = Array("January", "February", "March", "April", "May", "June", "July",
"August", "September", "October", "November", "December");
?>
<?php
if (!isset($_REQUEST["month"])) $_REQUEST["month"] = date("n");
if (!isset($_REQUEST["year"])) $_REQUEST["year"] = date("Y");
?>
<?php
$cMonth = $_REQUEST["month"];
$cYear = $_REQUEST["year"];
$prev_year = $cYear;
$next_year = $cYear;
$prev_month = $cMonth-1;
$next_month = $cMonth+1;
if ($prev_month == 0 ) {
$prev_month = 12;
$prev_year = $cYear - 1;
}
if ($next_month == 13 ) {
$next_month = 1;
$next_year = $cYear + 1;
}

?>
<html>
<head>
<link type="text/css" rel="stylesheet" href="sty.css"/>
</head>
<body>
<table width="200">
<tr align="center">
<td bgcolor="#999999" style="color:#FFFFFF">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50%" align="left"> <a href="<?php echo $_SERVER["PHP_SELF"] . "?month=".
$prev_month . "&year=" . $prev_year; ?>" style="color:#FFFFFF">Previous</a></td>
<td width="50%" align="right"><a href="<?php echo $_SERVER["PHP_SELF"] . "?month=".
$next_month . "&year=" . $next_year; ?>" style="color:#FFFFFF">Next</a> </td>
</tr>
</table>
</td>
</tr>
<tr>
<td align="center">
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tr align="center">
<td colspan="7" bgcolor="#999999" style="color:#FFFFFF"><strong><?php echo
$monthNames[$cMonth-1].' '.$cYear; ?></strong></td>
</tr>
<tr>
<td align="center" bgcolor="#999999" style="color:#FFFFFF"><strong>S</strong></td>
<td align="center" bgcolor="#999999" style="color:#FFFFFF"><strong>M</strong></td>
<td align="center" bgcolor="#999999" style="color:#FFFFFF"><strong>T</strong></td>
<td align="center" bgcolor="#999999" style="color:#FFFFFF"><strong>W</strong></td>
<td

align="center" bgcolor="#999999" style="color:#FFFFFF"><strong>T</strong></td>
<td align="center" bgcolor="#999999" style="color:#FFFFFF"><strong>F</strong></td>
<td align="center" bgcolor="#999999" style="color:#FFFFFF"><strong>S</strong></td>
</tr>
<?php
$timestamp = mktime(0,0,0,$cMonth,1,$cYear);
$maxday = date("t",$timestamp);
$thismonth = getdate ($timestamp);
$startday = $thismonth['wday'];
for ($i=0; $i<($maxday+$startday); $i++) {
if(($i % 7) == 0 ) echo "<tr>n";
if($i < $startday) echo "<td></td>n";
else echo "<td align='center' valign='middle' height='20px'>". ($i - $startday + 1) . "</td>n";
if(($i % 7) == 6 ) echo "</tr>n";
}
?>
</table>
</td>
</tr>
</table>
</body>
<html>
<hr><br/><br/>
</div>
<div id="nav1">
<h3>Notifications</h3>
<hr><br/><br/>
<?php
include('connect-db.php');
$result = mysql_query("SELECT * FROM notify")
or die(mysql_error());

while($row = mysql_fetch_array( $result )) {
echo "<table border='1' >";
echo "<tr>";
echo '<td>' . $row['notification'] . '</td>';
echo "</tr>";
}
echo "</table>";
?>
</div>
<div id="main">
<div id="content">
<div id="head">
<img src="home.jpg">
</div>
</div>
<div id="footer">
<h1> News</h1>
</div>
</div>
</body>
</htm

CHAPTER 7: PROJECT TESTING
7.1 MANUAL TESTING

7. PROJECT TESTING
7.1 MANUAL TESTING

These tests were performed by developers and tester in controlled situation and we got expected
result from these tests. Also, this application was handed out to our friends and even they got the expected
result to be satisfying.
Sr. No Test Case Title Description Expected Output Result
1 Username and User entering wrong User entering wrong Failed

password username and password. username and password.
2 username and User entering correct System login to next Passed
password username and password. page.
3 View Employee Employee details should be Employee details should Passed
details display. be display successfully.
4 Add Employee Adding New Employee to New Employee should Passed
database . be added successfully.
5 Edit/Delete Admin should be able edit or Employee details should Passed
Employee details delete Employee. be edited or deleted
successfully.
6 Search Employee Admin should be able to Admin should be search Passed
search employee and employee and display
display. successfully.
7 Add Department Adding new Department to New Department Passed
database. should be added to the
database successfully.
8 Generate Report Admin shoud be able to Admin shoud be Passed
generate report. generate report
successfully.
9 Put new Admin should be able to put Admin should be put Passed
Notifications new notification. new notification
successfully.

10 Assign Task HR should assign task to HR can assign task to Passed
employee. employee successfully.
11 Create Project HR should able to create HR should create Passed
Team project team of employee’s. project team of
employee’s
successfully.
12 Aply for leave Employee should apply for Employee should apply Passed
leave. for leave successfully.
13 View details Employee should be able to Employee should be Passed
view his/her personal details. able to view his/her
personal details
successfully.
14 View Tasks Employee should be able to Employee should be Passed
view his/her task assign by able to view his/her task
HR. assign by HR
successfully.
Generate progress Employee should be able to Employee should be Passed
15 report generate progress reports. able to generate
progress reports
successfully.
16 Contact Contact details should be Contact details should Passed
display on home page. be display on home
page successfully
17 Logout Admin, HR and Employee User should logout Passed
click on logout successfully
Fig: 7.1 Manual testing

CHAPTER 8: FUTURE ENHANCEMENT
8.1 FUTURE ENHANCEMENT

8. FUTURE ENHANCEMENT
8.1 FUTURE ENHANCEMENT

 Providing attendance online to parents on this system
 To provide status online that whether their admission is confirmed or not in college
 Making software more secure and reliable
 Making Defaulter List on this System for Management

CHAPTER 9: CONCLUSION AND

REFERENCES
8.2 CONCLUSION
8.3 REFERENCES

9. CONCLUSION AND REFERENCES
9.1 CONCLUSION
This system was developed after detailed study and research on existing systems and applications. We
feel very glad to conclude this report.This was our first experience to perform such professional and large
project work. Objective of this project was to satisfy user’s requirement, successful implementation of
system, design a user friendly and easy to operate system while providing privacy and security at user end.
We have got the opportunity to learn conceptual and practical knowledge of software engineering,
software analysis and real time experience of project implementation in Android.
At last we are very thankful to university to include this project as a part of our engineering in diploma.
This project work was really gives us chance to learn something out of typical reference book.
It is our pleasure to say thanks once again to all of you on completion of our project work. By
developing this system, we found ourselves on pathway to industry requirement.
9.2 REFERENCES
www.youtube.com
www.tutorialspoint.com
www.stackoverflow.com
https://design.google.com
www.mysql.com
www.w3schools.com
http://en.wikipedia.org/wiki/Human_resource_management

Chapter 1: Introduction To Project

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Chapter 1: Introduction To Project

Hochgeladen von

Copyright:

Verfügbare Formate

Online Student Administration System

CHAPTER 1: INTRODUCTION TO PROJECT

1.1 PROJECT BACKGROUND

1.2 LITERATURE SURVEY

1.3 PROBLEM DEFINATION

1.4 SOFTWARE REQ UIREMENT SPECIFICATION

1.5 REQUIREMENT AND CONSTRAINTS

`1 | P a g e CO-6 G, G.V.Acharya Polytechnic

 Time and Money is saved.

 Nothing is done manually.

 Long lines in the department for these issues.

1.2 LITERATURE SURVEY

1.3 PROBLEM STATEMENT

`3 | P a g e CO-6 G, G.V.Acharya Polytechnic

1.4.2 Project Scope

1.5 . REQUIREMENT AND CONSTRAINTS

`4 | P a g e CO-6 G, G.V.Acharya Polytechnic

1.5.2 Functional Requirements:

`5 | P a g e CO-6 G, G.V.Acharya Polytechnic

Processor-Intel Core 2 Duo and Higher

LANGUAGE USED BY SYSTEM

`6 | P a g e CO-6 G, G.V.Acharya Polytechnic

CHAPTER 2: AIM AND OBJECTIVE OF THE

2.1 AIM OF THE PROJECT

2.2 OBJECTIVE OF THE PROJECT

2.3 NEED OF THE PROJECT

`7 | P a g e CO-6 G, G.V.Acharya Polytechnic

2. AIM AND OBJECTIVES OF THE PROJECT

2.1 AIM OF THE PROJECT

Students can fill Admission form anytime and anywhere.

2.2 OBJECTIVE OF THE PROJECT

`8 | P a g e CO-6 G, G.V.Acharya Polytechnic

2.3 NEED OF THE PROJECT

`9 | P a g e CO-6 G, G.V.Acharya Polytechnic

CHAPTER 3: PROJECT PLANNING AND

3.1 PROJECT DEVELOPMENT LIFECYCLE

3.2 TASKS AND MILESTONES

`10 | P a g e CO-6 G, G.V.Acharya Polytechnic

3. PROJECT PLANNNING AND MANAGENMENT

2.1.2 System Concept Development:

2.1.4 Requirement Analysis:

2.1.7 Integration and Test:

`11 | P a g e CO-6 G, G.V.Acharya Polytechnic

2.1.9 Operations and Maintenance:

3.2 TASKS AND MILESTONES

Sr. No Test Case Step Expected Cases Status Build Test

1 Database Connectivity successful Connectivity done Yes

2 Admin Login Admin should be Admin Log In Yes

3 Users Registration System must be able to New user is successfully Yes

5 Add Employee Employee should be Employee is added Yes

`12 | P a g e CO-6 G, G.V.Acharya Polytechnic

Table 3.2 Tasks and Milestones

`13 | P a g e CO-6 G, G.V.Acharya Polytechnic

CHAPTER 4: PROJECT ANALYSIS

4.1 USE CASE MODEL WITH SCENARIO

4.2 ACTIVITY DIAGRAMS

`14 | P a g e CO-6 G, G.V.Acharya Polytechnic

Head Of Department (HOD)

Human Resource (HR)

Figure 4.1.1 Employee Use Case

`15 | P a g e CO-6 G, G.V.Acharya Polytechnic

Figure 4.1.2 HOD Use Case

`16 | P a g e CO-6 G, G.V.Acharya Polytechnic