HIMANSHU

PROJECT REPORT
ON
e-Student Zone
Submitted By:
HIMANSHU SHEKHAR SAHOO
12DIT-141
6th Semester
Under Guidance of
BHABASANKAR DAGAR
RAVENSHAW UNIVERSITY
CUTTACK
CERTIFICATE
This is to certify that HIMANSHU SHEKHAR SAHOO has
successfully completed the assigned module of the project entitled as e-
Student Zone in partial fulfillment of the requirement for the 3 rd year
B.Sc. I.T.M. course for the degree Of “Bachelor of Science in
Information Technology Management”.
The project has been carried out under my direct supervision and
guidance. This report or a similar report on the topic has not been
submitted for any other examination and does not form part of any other
course undergone by the candidate.
Signature of Project Guide

DECLARATION
I HIMANSHU SHEKHAR SAHOO do hereby declare that this
project work has been done by me along with the help of my guide Mr.
BHABA SANKAR DAGAR.
To the best of my knowledge, this project work has not been
submitted for the award of any degree and is a part of B.Sc. ITM course
of RAVENSHAW UNIVERSITY, Cuttack.

B.SC ITM (3RD YEAR)
6TH SEMESTER
12DIT-141
IDENTIFICATION
PROJECT CODE :PJ(3.6.37)
NAME :HIMANSHU SHEKHAR SAHOO
ROLL NO :12DIT-141
PROJECT TITLE :e-Student Zone
COMMENCING DATE :12TH MARCH, 2O15
DUE DATE :5TH MAY, 2015
SUBMISSION DATE :14TH MAY, 2015
APPROVED BY Internal External

Guide Examiner Examiner
ACKNOWLEGEMENT
What I write or mention in this sheet will hardly be

adequate in return for the amount of help and co-operation. I have
received from all of the people who have contributed to make this
project a reality. But I will still try my level best to thank them.
First of all I wish to express my sincere thanks to

Mr. BHABASANKAR DAGAR, my project guide in this undertaking,
who has always there for me to offer help in all possible ways, ready to
solve any problem with a smiling face owe him a lot due to boost that he
provided me which further the successful completion of the project
within the stipulated time.
Finally I wish to express my heartiest thanks to

my parents, all my teachers and friends who played a very important part
in making my project complete and successful.
Thanking You!
Yours truely

Preface
The project report on “e-Student zone” is a part of our
B.Sc.I.T.M. course provided by Ravenshaw University, Cuttack. The
project is designed according to the requirements and its contents E-
Student zone details and other reports.
I have made every effort to rectify the errors from the

project reports. Even then it is hope that the report in the present form is
suitable practically.
Project Members
1. HIMANSHU SHEKHAR SAHOO 12DIT-141

2. DINESH KUMAR NAYAK 12DIT-172
3. AMIYA RANJAN MOHAPATRA 12DIT -167
4. PRAMOD KUMAR BARIK 12DIT-304
TABLE OF CONTENTS
1. Introduction 5
7
2. System Analysis
3. Development Process
4. Requirement Analysis & Specification
5. System Design
6. Screen Layout
7. Technical Overview
8. Coding
9. Testing
10. System implementation and maintenance
11. System Security Measures
12. Future Scope
13. Conclusion
14. Bibilography
INTRODUCTION
1.1 OBJECTIVE OF THE PROJECT
The purpose of the project is to develop a website that can handle students
online query ,attendance, courses, results. The purpose is to completely
automate the old manual procedure. Overall, it’ll make Student
Information Management an easier job for the administrator, lecturer(s)
and the student of any organization.
1.2 PROJECT DESCRIPTION

e-Student Zone can be used by education institutes to maintain the records of
students easily. Achieving this objective is difficult using a manual system as the
information is scattered, can be redundant and collecting relevant information may
be very time consuming. All these problems are solved using this project
1.3 MODULE DESCRIPTION
ADMIN MODULE
In admin module only admin has to login with the system. Admin has to add
subjects with the course name. Admin has to register faculty members with
respected course and Department and their total Studental details. Registered
faculty members are appointed to the respective branches. They have to add
feedback questions to the system.
LECTURER MODULE
Lecturers can view course, subject, student attendance as well as give
feedback.
STUDENT MODULE
Students can view their details by providing registration number or by
name and course. They can also view result, attendance, exam notice and
provide feedback.
SYSTEM ANALYSIS
1.1 EXISTING SYSTEM :
Till date the organisation has been using pen and paper to record their
transaction and phone as the medium of communication between two remote
offices. The process flow of existing system is outlined below along with data
entry points
1.2 DRAW BACKS OF EXISTING SYSTEM:
1. The existing system is totally manual.

2. Time-consuming.
3. The system is totally expensive.
4. If the Admin wants to see the status of his consignment it is necessary to come
to the agency, which is not user friendly. Consists redundancy.
5. Duplicacy of records occurred.
DEVOLOPMENT PROCESS
1.1 WATER-FALL MODEL

Planning the development process involves several important considerations.
The first consideration is to define a product life-cycle model.A software LIFE-
CYCLE model encompasses all activities required to define, test, and develop.
Requireme
nt analysis-
v&v
ana
Design- v&v
Implementation
-v&v
Testing- v&v
Maintenance-v&v
V&V -Validation and Verification
REQUIREMENT ANALYSIS & SPECIFICATION
1.1 REQUIREMENT GATHERING ANALYSIS

The goal of the requirement gathering activity is to collect all relevant information
from the student and lecturer regarding the student and teacher information to be
developed with a view to clearly understanding the Student requirements and
weeding out the incompleteness and inconsistencies in these requirements. An
inconsistent requirement is one where some part of the requirement contradicts
with some other part. On the other hand, an incomplete requirement is one where
some parts of the requirement may have been omitted altogether.
The requirement analysis activity is begun by collecting all relevant data regarding
the product to be developed from the users of the product and from the Student
through interviews and discussions. In this project we interviewed all accountant of
the organization to ascertain his or her requirements. The collected from such a
group of users usually contain several contradictions and ambiguities. Since each
user typically has only a partial and incomplete view of the system. Therefore, it is
necessary to identify all ambiguities and the contradictions in the requirements and
resolve them through further discussion with the Student. After all ambiguities,
inconsistencies and incompleteness have been resolved and all the requirements
properly understood, the requirement specification activity starts. During this
activity, the user requirements are systematically organized into a Software
Requirement specification (SRS) document.
REQUIREMENT ANALYSIS
1. The problem is system is manual and needs to computerize.
2. In ability to find the status of the current system rapidly.
3. The system needs to be web based for convenient of the Student.
1.1.2 REQUIREMENT SPECIFICATION

The admin requirement identified during the requirement gathering and analysis
activity is organized into a SRS document. The important documents of these
documents are the functional requirements, the non-functional requirements, and
the goals of implementation. Documenting the functional requirement involves the
identification of the function to be supported by the system. Each function can be
characterized by the input data, the processing required on the input data and the
output data to be produced. The non-functional requirement identifies the
performance requirements, the required standard to be followed, etc. The SRS
document is written using the end-user terminology. This makes the SRS
document understandable by the Student. After all, it’s important that SRS
document be reviewed and approved by the Student. The SRS document normally
serves as a contract between the admin and lecturer & student. Any future
Student and developer can be settled by examining the SRS document. It is
therefore and important document, which must be thoroughly understood by the
developer team and reviewed jointly by the Student
1. FEASIBILITY STUDY
Feasibility is the measure of how beneficial the development of
information system would be to an organization. Feasibility analysis is the
process by which feasibility is measured. The main aim he feasibility study
activity is to determine whether it is financially and technically feasible to
develop the product. The feasibility study activity involve the analysis of
the problem and collecting relevant information relating to the product to
the such as different data items which would in to the system, the
processing required to be carried out on these data, the output data required
to be produced by the system.
1.1 OPERATIONAL FEASIBILITY
Operational feasibility criteria measure the urgency of the problem or acceptability

of this problem. This project will provide necessary information about university
or college as well as how to handle activities. It is very difficult to say whether
mutation of a particular record is done or not to verify it. One should go to the
respective lecture or student, which is a time consuming, expensive and a tedious
job. Which can be avoided by this project, through this, the Zonal admin can see
the status of client.
1.2 TECHNICAL FEASIBILITY
The feasibility can only be evaluated after those phases during which technical
issues are resolved. It looks what is practical and reasonable.
If we cannot afford the technology is not practical and is infeasible Java Domain
Business Solutions has the required hardware and trained Studentdetails to handle
this system and to make the portal user friendly and compatible. Technical
feasibility includes two main aspects:
1. Hardware feasibility 2. Software feasibility.
1. HARDWARE FEASIBILITY
For develop this project or implement this project we need different types of
hardware configuration for server and client. If we will use different type of
hardwares then it may not work properly.
For server
Processor : Intel(R ) core i3
Memory : 1 GB RAM
Hard Drive : 500 GB HDD or Higher
CPU Speed : 2.0Ghz
Monitor : LED
Keyboard : Standard
Printer : Laser
UPS : 5KVA
For client
Processor : Intel(R ) core i3
Memory : 1 GB RAM
Hard Drive: 500 GB HDD or Higher
CPU Speed: 2.0Ghz
2. SOFTWARE FEASIBILITY
Using different types of software, which have listed below so these software’s also
need for implement this project, developed this project. If we will use different
types of software then this project will not work.
Operating System : WINDOWS 8
Front-end Tool : PHP
Back-end Tool : My Sql
Server : Xampp(Apache,MySql)
IDE : Dreamweaver CS6
Browser : Google Chrome, Internet Explorer 11
1.3 ECONOMICAL FEASIBILITY
As soon as the specific requirements and solutions have been identified

then the cost of and benefits of each alternative would be evaluated.
SYSTEM DESIGN
UML
UML is a language for creating models. As in case of any other language, UML
has its syntax and semantics. It provides a set of notations to create models of
systems that would be useful in documenting the design and analysis result.
USE CASE DIAGRAM:
DEFINITION OF USE CASE DIAGRAM:-
 Use case diagram show the various activities that users can perform on the
system. System is something that performs a function.
 They model the dynamic aspects of the system.
 It provides a user’s perspective of the system.
 Use case diagrams are important for visualizing, specifying, and
documenting the behavior of an element.
COMPONENTS OF USE CASE DIAGRAM:-
The components of use case diagram are:
1) Actor.
2) Use Case.
3) System Boundary.
4) Actor relationship.
ACTOR:-
1. An actor is a user of the system playing a particular role.

2. An actor is someone or, something that must interact with the system under development.
3. Actors are shown with a stick figure in UML.
4. Actors carryout use cases and a single actor may perform more than one use case.
5. Actors are determined by observing the direct uses of the system.
ACTOR
USE CASE:-
1. Use case is description of set of sequence of actions that a system perform that yields an
observable result of values to a particular actor.
2. It’s represented by an ellipse.
3. Use case is a pattern of behavior that the system exhibits.
4. Each use case is a sequence of related transactions performed by an actor and the system
in dialogue.
5. Use case is dialogue between an actor and the system.
6. A use case typically represents a major piece of functionality that is complete from
beginning to end.
7. The use case may be decomposed into other use cases.
8. Use cases also present a good vehicle for project planning.
USE CASE
SYSTEM BOUNDARY :-
1. It helps to identify what is external Vs internal, and what are the responsibilities of the
system.
2. It’s shown as a rectangle.
3. The external environment is represented by only actors.
SYSTEM BOUNDARY
ACTOR RELATIONSHIP :
 Relationship between actors.
 Relationship between generalized actor and specialized actors.
 An actor may input information to the system, receive information from the system and
input to and out from the system.
 4 categories of an actors are :-
Principle : who uses the main system functions .
Secondary : who takes care of administration and maintenance .
External Hardware : the hardware devices which are part of application domain and must
be used .
Other System : The other system with which the system must interact.
Use Case for e-Student Zone
LOGIN
Manage course
Manage subject
Manage lecture
Manage student
Manage Attendance
ADMIN Controls Examination
Accept contact
LOGIN
View course
View subject
View student
Take Attendance
LECTURER
STUDENT
Examination
STATE CHART DIAGRAM

A state chart diagram shows the behavior of classes in response to external stimuli.
This diagram models the dynamic flow of control from state to state within a
system.
(a) Basic State chart Diagram Symbols and Notations
1) States
States represent situations during the life of an object. You can easily Draw by
using a rectangle with rounded corners.
2) Transition
A solid arrow represents the path between different states of an object. Label the
transition with the event that triggered it and the action that results from it.
3) Initial State
A filled circle followed by an arrow represents the object's initial state.
4) Final State
An arrow pointing to a filled circle nested inside another circle represents the
object's final state.
5) Synchronization and Splitting of Control

A short heavy bar with two transitions entering it represents a synchronization of
control. A short heavy bar with two transitions leaving it represents a splitting of
control that creates multiple states.
ADMIN LOG IN
Enter ID & Password
Validate ID & Password
If
ERROR
Valid
OPEN ADMIN PAGE

LECTURER LOG IN
Enter ID & Password
Validate ID & Password
If
ERROR
Valid
OPEN LECTURER PAGE

VIEW STUDENT DETAILS
Enter Roll No. Enter Name & Course
Validate Roll no./Name & Course
If
ERROR
Valid
OPEN STUDENT DETAILS PAGE

ADD COURSE
Enter Course Details
Validate Course Details
If
ERROR
Valid
Data Saved in Database Successfully

UPDATE COURSE
Fetch Course Details From Database
Enter new Course Details
Validate Course Details
If
ERROR
Valid
Data Updated Successfully
Entity Relationship Diagrams

In software engineering, an entity-relationship model (ER model for short) is an abstract
and conceptual representation of data. Entity-relationship modeling is a database
modeling method, used to produce a type of conceptual schema or semantic data
model of a system, often a relational database, and its requirements in a top-
down fashion. Diagrams created by this process are called entity-relationship
diagrams or ER diagrams.
Entity
An entity is an object or concept about which you want to store information.
Weak Entity
A weak entity is an entity that must defined by a foreign key relationship with another
entity as it cannot be uniquely identified by its own attributes alone.
Key attribute
A key attribute is the unique, distinguishing characteristic of the entity. For example, an
employee's social security number might be the employee's key attribute.
Multivalued attribute
A multivalued attribute can have more than one value. For example, an employee entity
can have multiple skill values.
Derived attribute
A derived attribute is based on another attribute. For example, an employee's monthly
salary is based on the employee's annual salary.
relationships
Relationships illustrate how two entities share information in the database structure.
Learn how to draw relationships:
First, connect the two entities, then drop the relationship notation on the line.
Cardinality
Cardinality specifies how many instances of an entity relate to one instance of another
entity.
Ordinality is also closely linked to cardinality. While cardinality specifies the occurences
of a relationship, ordinality describes the relationship as either mandatory or optional. In
other words, cardinality specifies the maximum number of relationships and ordinality
specifies the absolute minimum number of relationships.
Recursive relationship
In some cases, entities can be self-linked. For example, employees can supervise other
employees.
LOG IN
e-STUDENT ZONE
ADMIN LECTURER STUDENT
LOGIN
LOGIN
ADD COURSE COURSE COURSE DETAILS
COURSE DELETE COURSE SUBJECT SUBJECT DETAILS
UPDATE COURSE STUDENT STUDENT DETAILS
ADD SUBJECT ATTENDANCE ATTENDANCE DETAILS
SUBJECT DELETE SUBJECT EXAMINATION EXAMINATION DETAILS
UPDATE SUBJECT
ADD LECTURER
VIEW DETAILS
LECTURER DELETE LECTURER
UPDATE LECTURER BY ROLL NO. BY NAME & COURSE
ADD STUDENT
STUDENT DELETE STUDENT
UPDATE STUDENT
ATTENDANCE ATTENDANCE DETAILS
EXAMINATION EXAMINATION DETAILS
CONTACT CONTACT INBOX

USER BROWSER DATABASE
Request for Login Form ()
Response ()
Input user ID & password ()
Validate ()
Response ()
Response ()
ADD COURSE
ADMIN BROWSER DATABASE

Request insert course details Form ()
Response ()
Input course details ()
Validate ()
Response ()
Response ()
UPDATE COURSE
Request insert course details Form ()
Response ()
Input course details ()
Fetch course details ()
Response ()
Response ()
ADD SUBJECT

Request insert subject details Form ()
Response ()
Input subject details ()

validate()
Response ()
Response ()
UPDATE SUBJECT
Request insert subject details Form ()
Response ()
Input subject details()
Fetch subject details()
Response ()
Response ()
ADD LECTURER

Request insert lecturer details Form ()
Response ()
Input lecturer details ()

validate()
Response ()
Response ()

Request insert lecturer details Form ()
Response ()
UPDATE LECTURER
Fetch lecturer details()
Response ()
Response ()
ADD STUDENT

Request for insert student details Form ()
Response ()
Input student details ()

validate()
Response ()
Response ()
UPDATE STUDENT

Request insert student details Form ()
Response ()
Input student details ()

Fetch student details ()
Response ()
Response ()
SEARCH ATTENDANCE DETAILS

Input criteria for Search form()
Response ()
Request for search Form ()

Search in Database()
ADD ATTENDANCE
Response ()
Response ()

Request for add attendance Form ()
Response ()
Input criteria to add attendance details()
validate()
Response ()
Response ()
SEARCH EXAMINATION DETAILS

Input criteria for Search exam form()
Response ()
Request for search exam Form ()

Search in Database ()
Response ()
Response ()
UPDATE ADMINDETAILS
ADD EXAMINATION

Request for add exam details Form ()
Response ()
Input criteria to add exam details ()

Validate ()
Response ()
Response ()
ADD ADMIN

Request for Insert Admin details Form ()
Response ()
Input Admin Details ()

Validate ()
Response ()
Response ()
Request for insert admin details Form ()
Response ()

Fetch student details ()
Response ()
Response ()
SCREEN LAYOUT
TECHENICAL OVERVIEW
HTML
HTML is a language for describing web pages.
* HTML stands for Hyper Text Markup Language
* HTML is not a programming language, it is a markup language
* A markup language is a set of markup tags
* HTML uses markup tags to describe web pages
HTML Tags
HTML markup tags are usually called HTML tags
* HTML tags are keywords surrounded by angle brackets like <html>
* HTML tags normally come in pairs like <b> and </b>
* The first tag in a pair is the start tag, the second tag is the end tag
* Start and end tags are also called opening tags and closing tags
<html>
<body>
<h1>My First Heading</h1>
<p>My first paragraph.</p>
</body>
</html>
HTML Example Explained

The <p> element:
<p>This is my first paragraph.</p>
The <p> element defines a paragraph in the HTML document.
</html The element has a start tag <p> and an end tag </p>.
The element content is: This is my first paragraph.
The <body> element:
<body>
</body>
The <body> element defines the body of the HTML document.
The element has a start tag <body> and an end tag </body>.
The element content is another HTML element (a p element).
The <html> element:
<html>
<body>
</body>
HTML Images - The <img> Tag and the Src Attribute

In HTML, images are defined with the <img> tag.
The <img> tag is empty, which means that it contains attributes only, and has no
closing tag.
To display an image on a page, you need to use the src attribute. Src stands for
"source". The value of the src attribute is the URL of the image you want to
display.
Syntax for defining an image:
<imgsrc="url" alt="some_text"/>
HTML Style Example - Background Color

The background-color property defines the background color for an element:
Example
<html>
<body style="background-color:yellow">
<h2 style="background-color:red">This is a heading</h2>
<p style="background-color:green">This is a paragraph.</p>
</body>
</html>
HTML Tables
Tables are defined with the <table> tag.
A table is divided into rows (with the <tr> tag), and each row is divided into data
cells (with the <td> tag). td stands for "table data," and holds the content of a data
cell. A <td> tag can contain text, links, images, lists, forms, other tables, etc.
HTML Forms - The Input Element

The most important form element is the input element.
The input element is used to select user information.
An input element can vary in many ways, depending on the type attribute. An input
element can be of type text field, checkbox, password, radio button, submit button,
and more.
The most used input types are described below.
Text Fields
<input type="text" /> defines a one-line input field that a user can enter text into:
<form>
First name: <input type="text" name="firstname" /><br />
Last name: <input type="text" name="lastname" />
</form>
Password Field
<input type="password" /> defines a password field:
<form>
Password: <input type="password" name="pwd" />
</form>
How the HTML code above looks in a browser:
Password:
Radio Buttons
<input type="radio" /> defines a radio button. Radio buttons let a user select
ONLY ONE one of a limited number of choices:
<form>
<input type="radio" name="sex" value="male" /> Male<br />
<input type="radio" name="sex" value="female" /> Female
</form>
Male
Female
Checkboxes
<input type="checkbox" /> defines a checkbox. Checkboxes let a user select ONE
or MORE options of a limited number of choices.
<form>
<input type="checkbox" name="vehicle" value="Bike" /> I have a bike<br/>
<input type="checkbox" name="vehicle" value="Car" /> I have a car
</form>
I have a bike
I have a car
Submit Button
<input type="submit" /> defines a submit button.
A submit button is used to send form data to a server. The data is sent to the page
specified in the form's action attribute. The file defined in the action attribute
usually does something with the received input:
<form name="input" action="html_form_action.asp" method="get">

Username: <input type="text" name="user"/>
<input type="submit" value="Submit"/>
</form>
Submit
Username:
If you type some characters in the text field above, and click the "Submit" button,
the browser will send your input to a page called "html_form_action.asp". The
page will show you the received input.
JavaScript
* JavaScript was designed to add interactivity to HTML pages
* JavaScript is a scripting language
* A scripting language is a lightweight programming language
* JavaScript is usually embedded directly into HTML pages
* JavaScript is an interpreted language (means that scripts execute without

preliminary compilation)
Writing to The HTML Document

The example below writes a <p> element with current date information to the
HTML document:
<html>
<body>
<h1>My First Web Page</h1>
<script type="text/javascript">
document.write("<p>" + Date() + "</p>");
</script>
</body>
Section 1.02 </html>
JAVASCRIPT VARIABLE
As with algebra, JavaScript variables are used to hold values or expressions.A
variable can have a short name, like x, or a more descriptive name, like car name.
Rules for JavaScript variable names:
 Variable names are case sensitive (y and Y are two different variables)
 Variable names must begin with a letter or the underscore character
JavaScript Arithmetic Operators

Arithmetic operators are used to perform arithmetic between variables and/or
values.
Given that y=5, the table below explains the arithmetic operators:
Operator Description Example Result

+ Addition x=y+2 x=7 y=5
- Subtraction x=y-2 x=3 y=5
* Multiplication x=y*2 x=10 y=5
/ Division x=y/2 x=2.5 y=5
% Modulus (division remainder) x=y%2 x=1 y=5
++ Increment x=++y x=6 y=6
x=y++ x=5 y=6
-- Decrement x=--y x=4 y=4
x=y-- x=5 y=4
JavaScript Functions
To keep the browser from executing a script when the page loads, you can put your
script into a function.A function contains code that will be executed by an event or
by a call to the function.You may call a function from anywhere within a page (or
even from other pages if the function is embedded in an external .js file).
Functions can be defined both in the <head> and in the <body> section of a
document. However, to assure that a function is read/loaded by the browser before
it is called, it could be wise to put functions in the <head> section.
Section 1.03 How to Define a Function

(a) Syntax
Function functionname(var1,var2,...,varX)
{
some code
}
PHP (Hypertext Preprocessor)

 PHP stands for PHP: Hypertext Preprocessor
 PHP is a server-side scripting language, like ASP
 PHP scripts are executed on the server
 PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid,
PostgreSQL, Generic ODBC, etc.)
 PHP is an open source software
 PHP is free to download and use
PHP File
 PHP files can contain text, HTML tags and scripts

 PHP files are returned to the browser as plain HTML
 PHP files have a file extension of ".php", ".php3", or ".phtml"
 PHP combined with MySQL are cross-platform (you can develop in
Windows and serve on a Unix platform)
Basic PHP Syntax

A PHP scripting block always starts with <?php and ends with ?>. A PHP
scripting block can be placed anywhere in the document.
Each code line in PHP must end with a semicolon. The semicolon is a separator
and is used to distinguish one set of instructions from another.
There are two basic statements to output text with PHP: echo and print. In the
example above we have used the echo statement to output the text "Hello World".
Comments in PHP
In PHP, we use // to make a single-line comment or /* and */ to make a large
comment block.
PHP Functions
In this chapter we will show you how to create your own functions.
To keep the script from being executed when the page loads, you can put it into a
function.A function will be executed by a call to the function. You may call a
function from anywhere within a page. Create a PHP Function. A function will be
executed by a call to the function.
Syntax
functionfunctionName()
code to be executed;
}
PHP Form Handling
The most important thing to notice when dealing with HTML forms and PHP is
that any form element in an HTML page will automatically be available to your
PHP scripts.
Example
The example below contains an HTML form with two input fields and a submit
button:
<html>
<body>
<form action="welcome.php" method="post">
Name: <input type="text" name="fname" />
Age: <input type="text" name="age" />
<input type="submit" />
</form>
</body>
</html>
When a user fills out the form above and click on the submit button, the form data
is sent to a PHP file, called "welcome.php":
"welcome.php" looks like this:
<html>
<body>
Welcome <?php echo $_POST["fname"]; ?>!<br />
You are <?php echo $_POST["age"]; ?> years old.
</body>
</html>
Output could be something like this:
Welcome John!
You are 28 years old.
2 SQL (Structured Query Language)
SQL is a standard language for accessing databases. MySQL, SQL Server, Access,
Oracle, Sybase, DB2, and other database systems.SQL is a standard language for
accessing and manipulating databases.
What is SQL?
 SQL stands for Structured Query Language

 SQL lets you access and manipulate databases
 SQL is an ANSI (American National Standards Institute) standard
Database Tables
A database most often contains one or more tables. Each table is identified by a
name (e.g. "students" or "lecturers"). Tables contain records (rows) with data.
P_Id First Name LastName Address City
1 HIMANSHU Mohapatra Ravenshw university cuttack
2 DINESH Sahoo Ctc cuttack
3 AMIYA Nayak BBSR BBSR
The table above contains three records (one for each Student) and five columns
(P_Id, LastName, FirstName, Address, and City).
SQL Statements
Most of the actions you need to perform on a database are done with SQL
statements.The following SQL statement will select all the records in the
"Studentdetails" table:
SELECT * FROM Studentdetails
SQL DML and DDL
SQL can be divided into two parts: The Data Manipulation Language (DML) and
the Data Definition Language (DDL).The query and update commands form the
DML part of SQL:
 SELECT - extracts data from a database

 UPDATE - updates data in a database
 DELETE - deletes data from a database
 INSERT INTO - inserts new data into a database
The DDL part of SQL permits database tables to be created or deleted. It also
defines indexes (keys), specifies links between tables, and imposes constraints
between tables. The most important DDL statements in SQL are:
 CREATE DATABASE - creates a new database

 ALTER DATABASE - modifies a database
 CREATE TABLE - creates a new table
 ALTER TABLE - modifies a table
 DROP TABLE - deletes a table
 CREATE INDEX - creates an index (search key)
 DROP INDEX - deletes an index
The SQL SELECT Statement
The SELECT statement is used to select data from a database.
The result is stored in a result table, called the result-set.
(b) SQL SELECT Syntax

SELECT column_name(s) FROM table_name
and
SELECT * FROM table_name
The WHERE Clause
The WHERE clause is used to extract only those records that fulfill a specified
criterion.
(c) SQL WHERE Syntax

SELECT column_name(s)
FROM table_name
WHERE column_name operator value
WHERE Clause Example
The "Studentdetails" table:
P_Id LastName FirstName Address Course
1 Kour Nabneet Rajlit pur Arts
2 Nehe Rahul harmitpur Itm
3 Singh Kari Gurmitpur Arts
Now we want to select only the Studentdetails living in the city "ludhiana" from
the table above.
We use the following SELECT statement:
SELECT * FROM Studentsdetails

WHERE Course=Arts
The result-set will look like this:
1 Singh Kari gurmitpur 10 Arts

2 kour Ranjeet rajlitpur Arts
Quotes Around Text Fields
SQL uses single quotes around text values (most database systems will also accept
double quotes).However, numeric values should not be enclosed in quotes.
For text values:
This is correct:
SELECT * FROM Studentdetails WHERE FirstName=`kour`
This is wrong:
SELECT * FROM Studentdetails WHERE FirstName=kour
For numeric values:
This is correct:
SELECT * FROM Studentdetails WHERE Year=1965
This is wrong:
SELECT * FROM Studentsdetails WHERE Year='1965'
Operators Allowed in the WHERE Clause
With the WHERE clause, the following operators can be used:
Operator Description
= Equal
<> Not equal
> Greater than
< Less than
>= Greater than or equal

<= Less than or equal
BETWEEN Between an inclusive range
LIKE Search for a pattern
IN To specify multiple possible values for a column
The INSERT INTO Statement
The INSERT INTO statement is used to insert a new row in a table.
It is possible to write the INSERT INTO statement in two forms.
The first form doesn't specify the column names where the data will be inserted,
only their values:
INSERT INTO table_name

VALUES (value1, value2, value3,...)
The second form specifies both the column names and the values to be inserted:
INSERT INTO table_name (column1, column2, column3,...)

VALUES (value1, value2, value3,...)
SQL INSERT INTO Example
We have the following "Studentdetails" table:
P_Id LastName FirstName Address City
1 E E E E
2 Tt Tt Tt Tt
3 Tt Tt Tt tt
Now we want to insert a new row in the "Studentdetails" table.
We use the following SQL statement:
INSERT INTO Studentdetails

VALUES (4,'Nilsen', 'Johan', 'Bakken 2', 'Stavanger')
The "Studentdetails" table will now look like this:
1 Kour Nabneet Rajlit pur Arts
2 Nehe Rahul harmitpur Itm
3 singh Kari Gurmitpur Arts
The UPDATE Statement
The UPDATE statement is used to update existing records in a table.
(d) SQL UPDATE Syntax

UPDATE table_name
SET column1=value, column2=value2,...
WHERE some_column=some_value
SQL UPDATE Example
1 Hansen Ola Timoteivn 10 BA

2 Svendson Tove Borgvn 23 BA
3 Pettersen Kari Storgt 20 Physics
4 Nilsen Johan Bakken 2 Chemistry
5 Tjessem Jakob
Now we want to update the Student "Tjessem, Jakob" in the "Studentdetails" table.
UPDATE Studentdetails
SET Address='Nissestien 67', City='Sandnes'
WHERE LastName='Tjessem' AND FirstName='Jakob'
1 Hansen Ola Timoteivn 10 Sandnes
2 Svendson Tove Borgvn 23 Sandnes
3 Pettersen Kari Storgt 20 Stavanger
4 Nilsen Johan Bakken 2 Stavanger
5 Tjessem Jakob Nissestien 67 Sandnes
The DELETE Statement
The DELETE statement is used to delete rows in a table.
SQL DELETE Syntax

DELETE FROM table_name
WHERE some_column=some_value
SQL DELETE Example
5 Tjessem Jakob Nissestien 67 Sandnes
Now we want to delete the Student "Tjessem, Jakob" in the "Studentdetails" table.
We use the following SQL statement:
DELETE FROM Studentdetails

WHERE LastName='Tjessem' AND FirstName='Jakob'

Delete All Rows
It is possible to delete all rows in a table without deleting the table. This means that
the table structure, attributes, and indexes will be intact:
DELETE FROM table_name

or
DELETE * FROM table_name
CODING
Index.php(home page)
<?php
error_reporting(0);
session_start();
?>
<!doctype html>
<html lang="en-US">
<head>
<meta charset="UTF-8" />
<title>Student Information System</title>
<link href="style.css" rel="stylesheet" type="text/css">
<link href="styles/print/main.css" rel="stylesheet" type="text/css" media="print">


<script type="text/javascript">
function Openeditcourse(a)
var links = "courseinsert.php?slid=" + a + "&view=course";
var ReturnedValue = showModalDialog(links,"Passed

String","dialogWidth:450px; dialogHeight:400px; status:no; center:yes");
//alert("Modal Dialog returned '" + ReturnValued + "'");
</script>
</head>
<body>
<div id="wrap">
<section id="top">
<nav id="mainnav">
<h1 id="sitename" class="logotext">
<a href="index.php"> <marquee direction="right" width="336"

behavior="alternate" onMouseOver="100">e-Student Zone</marquee></a>
</h1>
<ul>
<li class="active"><a href="index.php"><span>Home</span></a></li>
<?php if(!empty($_SESSION["userid"]) && !empty($_SESSION["adminid"])){?>
<li class="active"><a href="dashboard.php"><span>Dashboard</span></a></li>
<?php }?>
<?php if(!empty($_SESSION["lecname"]) && !empty($_SESSION["userid"])){?>
<li class="active"><a
href="lectureaccount.php"><span>Dashboard</span></a></li>
<?php }?>
<li><a href="viewresult.php"><span>STUDENTS INFO</span></a></li>
<li>
<?php if(empty($_SESSION["userid"]) && empty($_SESSION["adminid"])){?>
<a href="admin.php"><span>LOGIN</span></a>
<?php }else{?>
<a href="logout.php"><span>LOGOUT</span></a>
<?php }?>
</li>
<li><a href="photos.php"><span>photos</span></a></li>
<li><a href="contact.php"><span>cONTACT-US</span></a></li>
</ul>
</nav>
</section>
<section id="page"><font color="#FFFFFF"></font>
<header id="pageheader" class="homeheader">
<h1 class="sitedescription"></h1>
</header>
<article class="post">
<header class="postheader">
<h1><a href="#">E-Student Zone</a></h1><h3> </h3>
<h3><i>Ravenshaw University</i></h3>
<a href="#"></a></p>
</header>
<p><b><big>e-Student Zone is a primary system for operating colleges. The
Student Information System is a student-level data collection system that allows
the Department to collect and analyze more accurate and comprehensive
information. It provides capabilities for entering student records, tracking student
attendance, and managing many other student-related data needs in a college or
university.</big></b></p>
</article>
<header class="postheader">
<h1>e-Student Supports:</h1><p class="postinfo"> </p>
</header>
<p><b><big>• Handling inquiries from prospective students.</big></b></p>
<p><b><big>• Handling the Student details.</big> </b></p>
<p><b><big>• Maintaining the Student Marks Details.</big> </b></p>
<p><b><big>• Handling Student Attendance Records. </big> </b></p>
<p><b><big>• Maintaining records of absences and attendance. </big>

</b></p>
<p><b><big>• Maintaining records of Internal marks.</big></b></p>
</article>
<div class="clear"></div>
</section>
</div>
<footer id="pagefooter">
<div id="f-content">
<div id="credits">
<marquee>
<class="sitecredit">2015 @ All Rights Reserved |
<class="designcredit">Student Information System
</marquee>
</div>
</div>
</footer>
</body>
</html>
Admin.php
<?php
ob_start();
error_reporting(0);
session_start();
//echo $_SESSION["uid"];
if(isset($_SESSION["adminid"]))
{
if($_SESSION["type"]=="admin")
header("Location: dashboard.php");
else
header("Location: lectureaccount.php");
include("header.php");
include("conection.php");
if(isset($_POST['login_button'])){
if(!empty($_POST["uid"]) && !empty($_POST["pwd"]) )
// echo "sdfsd". $_POST[uid];
$result = mysql_query("SELECT * FROM administrator WHERE

adminid='$_POST[uid]'");
while($row = mysql_fetch_array($result))
{
$pwdmd5 = $row["password"];
$_SESSION["adminid"] = $row["adminid"];
if(md5($_POST["pwd"])==$pwdmd5)
$_SESSION["userid"] = $_POST["uid"];
$_SESSION["type"]="admin";
header("Location: dashboard.php");
else
$log = "Login failed.. Please try again..";
}else{
$log = "All fields required";
?>
<section id="page">
<header id="pageheader" class="normalheader">

<h2 class="sitedescription">
</h2>
</header>
<section id="contents" style="width:585px;background:none;padding-

left:135px">
<header class="postheader" style="text-align:center">
<h2><u>Admin Login</u></h2>
<h2><?php echo $log;?></h2>
</header>
<article class="contactview">
<section class="entry">
<form action="" method="post" class="form">
<p class="textfield">
<label for="author">
<big><strong>Login ID (required)</strong></big>
</label>
<input name="uid" id="uid" value="" size="22" tabindex="1" type="text">
</p>
<p class="textfield">
<label for="email">
<big><strong>Password (required)</strong></big>
</label>
<input name="pwd" id="pwd" value="" size="22" tabindex="2"

type="password">
</p>
<p>
<input type="submit" name="login_button" id="submit" tabindex="5"

value="SUBMIT" class="loginbtn logoiutbtn">
<input name="comment_post_ID" value="1" type="hidden">
</p>
</form>
<form action="admin.php" method="post" class="form">
<div class="clear">
<hr />
<h4>
<a href="lecturelogin.php">Lecture Login</a>
</h4>
</article>
</section>
</article>
<section id="sidebar" style="width:0px;">
</section>
</section>
</div>
<?php
include("footer.php");?>
TESTING
The aim of testing process is to identify all defects existing in a software product. However, for most
practical systems, even after satisfactorily carrying out the testing phase, it is not possible to guarantee
that the software is error free. This is because of the fact that the input data domain of most software
product is very large. It is not practical to test the software exhaustively with respect to each value that the
input data may assume. Even with this practical limitation of the testing process, we should not
underestimate the importance of testing. We must remember that testing does expose many defects
existing in a software product. Therefore, we can safely conclude that testing provides a practical way of
reducing defects in a system and increasing the users’ confidence in a developed system.
WHAT IS TESTING?
Testing a program consists of subjecting the program to a set of inputs (or test cases) and
observing if the program behaves as expected. if the program fails to behave as expected, then the
condition for which error occurs are noted for later debugging and correction. The following are the
following commonly used terms associated with testing.
 A failure is a manifest of an error (or defects or bug). But the mere presence of an error may
not necessarily lead to a failure.
 A test case is the triplet [I, S, O], where I is the data input to the system. S is the state of the
system at which data is input, and O is the expected o/p of the system.
 A test suite is the set of all test cases with which a given software product is to be tested.
Design the test cases:
There are essentially two main approaches to systematically designing the test cases:
1) Black box approach
2) White box (or glass box) approach
In black box test cases are designed using only the functional specification of the software. i.e.
without any knowledge of the internal structure of the software. For this reason black box testing is also
known as functional testing. On the other hand, designing white box test cases requires the thorough
knowledge of the software. For this reason white box testing otherwise known as structural testing.
BLACK BOX TESTING:
In black box testing, test cases are designed from an examination of the input/output values only
and no knowledge of design or code is required. In this strategy some test cases are generated as input
conditions that fully execute all functional requirements for the program. This testing has been uses to
find errors in the following categories:
a) Incorrect or missing functions
b) Interface errors
c) Errors in data structure or external database access
d) Performance errors
e) Initialization and termination errors.
In this testing only the output is checked for correctness. The logical flow of the data is not checked.
The following are the two main approaches to designing black box testing:
 Equivalence class partitioning.
 Boundary value analysis.
EQUIVALENCE CLASS PARTIONING:
In this approach, the domain of input values of a program is partitioned into a set of equivalences
classes. Equivalence classes for a s/w can be designed by designing both input and output data. The
following are some general guidelines for designing the equivalence classes:
1) If the input data values to a system can be specified by a range of values, then one valid and two
invalid classes should be defined.
2) If the input data assumes values from a set of discrete members of some domain, then one input class
for valid input values and another for invalid input values should be defined.
BOUNDARY VALUE ANALYSIS:
Boundary value analysis leads to selection of test cases at the boundaries of different equivalence
classes. For e.g.- programmer may improperly use < instead of <= or conversely <= instead of <.
WHITE-BOX TESTING:
One white-box testing is said to be stronger than another strategy, if all types of errors detected by
the first strategy (say b) are also detected by the second testing (say a) and the second strategy
additionally detects some more types of errors. When two testing strategies detect errors that are different
at least with respect to some type of errors, they are then called complementary.
Types of errors
detected by testing
strategy A
Types of
errors
Types of errors
detected
detected by
by testing
Types of errors testing
strategy B
detected by testing strategy B
strategy A
<Stronger Testing> <Complementary
Testing>
Statement Coverage
The statement coverage strategy aims to design test cases to that every statement in a program is executed
at least once. The principal idea governing the statement coverage strategy is that unless we execute a
statement, we have no way of determining if an error exists in that statement. Unless a statement is
executed, we cannot observe whether it causes failure due to some illegal memory access, wrong result
computation, etc.
Branch Coverage
In the branch coverage-based testing strategy, test cases are designed to make each branch condition
assumes true and false values in turn. Branch testing is also known as edge testing as in this scheme, each
edge of a program’s control flow graph is traversed at least once.
(e) Condition Coverage

In this structural testing, test cases are designed to make each component of a composite conditional
expression assumes both true and false.
Article II. Path Coverage
The path coverage-based testing strategy requires us to design test cases such that all linearly independent
paths in the program are executed at least once.
(i) McCabe’s Cyclomatic Complexity Metric
1) The McCabe’s Cyclomatic Complexity is also called the structural complexity of the
program. It defines an upper bound on the number of independent paths in a program.
(ii) Data Flow-Based Testing

The data flow-based testing method selects the paths of a program according to the locations of
the definitions and uses of the different variables in a program.
Mutation Testing
In mutation testing we will make a few arbitrary changes to a program at a time. Each time the
program is changed, it is called a mutated program and change effected is called a mutant. A mutated
program is tested against the full test suite of the program. If there exists at least one test case in the suite
for which a mutant gives an incorrect result, then the mutant is said to be dead. If a mutant remains alive
even after all the test cases have been exhausted, the test data is enhanced to kill the mutant. The process
of generation and killing of mutants can be automated by predefining a set of primitive changes that can
be applied to the program.
INTEGRATION TESTING:
The primary objective of the integration testing is to test the module interfaces in order to ensure
that there are no errors in the parameter passing, when one module invokes another module. During
integration testing, different modules of a system are integrated in a planned manner using an integration
plan. The integration plan specifies the steps and order in which modules are combined to realize the full
system.
There are different types of approaches in this test plan. These are:
1) Big-Bang approach
2) Top-Down approach
3) Bottom-Up approach
4) Mixed approach
Big-Bang approach:
It is the simplest testing approach, where all the modules making up a simplest approach, where all the
modules making up a system are integrated in a single step. In simple words, all the modules of the
system are simply tested. However this technique is practicable only for very small systems.
Top-Down Approach:
Top-down integration testing starts with main routine and one or two subordinate routines in the system.
After the top-level skeleton has been tested, the immediate subroutines of the skeleton are combined with
it and tested.
Bottom-Up Approach:
In Bottom-Up testing, each subsystem is tested separately and then the full system is tested. A subsystem
might consist of many modules which communicate among each other through well-defined interfaces.
Mixed integration testing:

A mixed (also called sandwiched) integration testing follows a combination of top-down and
bottom-up testing approaches, testing can start only after the top-level modules have been coded and unit
tested.
System Testing
System tests are designed to validate a fully developed system to assure that it meets its requirements.
Three type of system testing:
1. Alpha Testing: Alpha Testing refers to the system testing carried out by the test tem within
the developing organization.
2. Beta Testing: Beta testing is the system testing performed by a select group of friendly
customers.
3. Acceptance Testing: Acceptance testing is the system testing performed by the customer to
determine whether to accept or reject the delivery of the system.
Performance Testing
Performance Testing is carried out to check whether the system meets the nonfunctional
requirements identified in the SRS document. All performance testing can be considered as black box
testing.
Stress Testing
Stress testing is also known as endurance testing. Stress testing evaluates system
performance when it is stressed for sort period of time.
Volume Testing
It is especially important to check whether the data structures (arrays, queues, stacks,
etc) have been designed successfully for extraordinary situations.
Configuration Testing
Configuration testing is used to analyze system behavior in various hardware and

software configurations specified in the requirements.
Compatibility Testing
This type of testing is required when the system interfaces with other types of systems.
Recovery Testing
Recovery testing tests the response of the system to the presence of the faults or loss of
power, devices, data, etc.
Documentation Testing
Documentation is checked to ensure that the required user manual, maintenance manuals
and technical manuals exist and are consistent.
Usability testing
Usability testing pertains to checking the user interface to see if it meets all the user
requirements. During usability testing, the display screens, message, report formats, and other aspects to
the user interface requirements are tested.
SYSTEM IMPLEMENTATION AND MAINTENANCE

System Implementation
The implementation stage is actually a working model of the analyzed
and designed system. Implementation includes all those activities that take place to
convert from old system to the new. The new system may be totally new, replacing
the existing manual or automated system or it may be a major modification to an
existing system.
The success of software not only depends on the excellent code but
also on the related documentation. The advantages of documentation are:
 Increase in efficiency training.
 Reduce cost and time spent on maintenance.
 Newly introduced Student may take upon the operation without much
disruption.
 Standardize processing’s that it becomes easy to understand.
Need of Maintenance
Maintenance is the enigma of system development. Analysts and programmers
spend far more time maintaining programs than they do writing them. Maintenance
accounts for 60-80 percent of total development. Whereas the cost of hardware has
steadily declined.
The cost of producing programs has skyrocketed. The problems in
maintenance e occur largely because software is a handmade product designed in
ad hoc fashion with few standards. Poor documentation makes maintenance of the
programs even more difficult.
There are other problems such as:
 Standards, guidelines and procedures are poorly defining and enforced.
 Maintenance is not as rewarding and exciting as developments. It is
received as requiring neither skill nor experience.
 Users are not fully cognizant of the maintenance problem or high cost.
 There are minimal standard of maintenance.
 Maintenance is viewed as unnecessary evil often delegation to junior
programmers.
 A good test plan lacking.
 Programmers except that they will not be in their current commitment by
the time their programs go into the maintenance cycle.
IMPLEMENTATION
User Testing/ User Manual
Even well designed system can succeed or fail because of the way they are
operated and used. Therefore the training received by the Studentnel involved
with the system in various capacities helps and hinders and my even prevent
the successful implementation of management information system.
System operators Training
Running of the system successfully depend on the Studental working in the

computer. They are responsible depends on the Studental working in the
computer center.
User Training
User must be trained on use of equipment. It is imperative that user be properly

trained in methods of entering transactions, editing data formulating queries,
deleting and inserting of records. Weakness in any aspect of training my lead to
awkward situations that creates errors.
1. Fundamentals of computer
2. Training to provide input to the system
3. Training to get all required information’s from the system
PROPOSED SOLUTIONS:-
To develop a system that would recomplish the following:-
o Reduce the paperwork and storage area.

o Improve the output of operators.
o Improve accuracy in result..
Manage the man and machine resources efficiently.
 It has user friendly interface having quick authenticated access to

documents
 Easily scalable to grow with changing system requirement.
 Secured check in, check out & updates.
MAINTENANCE
Software maintenance is an extremely important activity. The activity is
defined as the process of modifying existing operational software while leaving
its primary function intact.
It is useful to divides software maintenance into two categories-
• Software updates – which results in a functional specification for the

software.
• Software repair-which leaves the functional specification intact.
H/W Maintenance :
The AMC (Annual Maintenance Cost) is free for one year run the s/w smoothly
on h/w in their organization.
S/W Maintenance :
I (developer) am responsible for loading the software and I will provide the fee
maintenance of this software for one year but this does not include future up
graduation.
Security Measures Taken

Authorization-
The Student who is in change of authorizations usually called the authorizer.
Database Security –
User identification and password provision to prevent unauthorized access.
Security From Viruses –
Authenticate Virus Software NortonAntivirus 2004 was installed on every

machine for virus prevention. Registration was done so as to get automatic
updates in future
Security of Software –
Passwords of the system user andadministrator were aesthetically kept eight

characters long and not easily guessable thought at the development time this
was avoided and it was only shared with database administrator and asked to
change from time to time.
Backup Backups were designed in proper manner. This include system

backup of NT, Oracle server backup and file system backup. There is a backup
option in the utility menu.
SYSTEM SECURITY MEASURES

Security is the technique, innovation and procedure applied to
the hardware and operating system to protect against deliberate or accidental
damage from a defined threat. It also used for protecting the database against
Student who are not authorized to access either certain part of database or the
whole database or specially protect the data from loss, disclosure, modification and
destruction. Various types of security used in the organization.
Security based upon two different types

 Internal security.
 External security.
 Internal Security:
Internal security has three inherent provisions for database. It provides.
 Login name
 Password
 Authentication
Login name: It is given to the system user who can access.
Password: It is the secret codes given by the authorized user to access its account
and the databases.
Security Testing:
Security testing attempts to verify whether the protection mechanisms are built into
the system or not. The following are the efforts that were taken in order to keep the
system tamper proof.
1. All the user of the system is given a separate user id. They
individually select their password.
2. The access rights of the user are checked when the user entering
into the system is asked by the system software to enter his
user_id and password.
Security of data is of paramount importance. It is an irreplaceable asset.
The software has two level security. Best Software recognizes that our customers
have concerns about the security of their data as it moves across the Intranet. We
therefore take very seriously the responsibility for keeping customers data safe.
Best Software protects a customer's data in two ways.
Data Security
The Software uses industry-leading SSL encryption technology to safeguard data
against unauthorized access and intrusion.
Our secure "firewall" server adds another layer of data security.
 Backups of customers online data are done regularly so customers can

remain confident that their data is safe.
(b) Facility Security
 Data is stored in an off-site security center with external doors secured by
electronic key access and pin code, biometric scanning and electronic key
access for internal security. .
(c) User Security

During login to the software user enter his/her respective user name and
password.
(d) Internet Security

Browser-level encryption protects all of your business information—before it
travels over the Web. To authorize and certify access, Best Software uses Equifax,
an advanced security solution designed to provide secure communications and
transactions over the Internet and private networks.
Future Scope
The Project e-Student Zone is useful in any Education Institution to facilitates
service to students, lecturers, in a convenient way .Students can know online their
marks, attendance, feedback and lectures without waiting for queue in college.
Everything is online and queries can be processed instantly with greater accuracy.
• To provide a user friendly environment where user can be serviced

better.
• Provide a system where details of lecture, student & attendance are
maintained.
• To minimize errors, monetary loss.
• As the project is developed using PHP and My SQL it is highly portable
and robust, user friendly.
CONCLUSION
After completion of this project; I would like to conclude that this project “e-
Student Zone” which has been done to convert a manual student information
record keeping to computerized system which will help a lot to a college or
university. Lastly it can be concluded that the project has a lot of advantages over
the present manual system it is one of the best projects to manage the student
information record keeping. It will give more comfort and much relief to the
lecturers and students of a college or university.
Bibliography
1. PHP and MYSQL Web Development by Luke Welling
2. Website: http://www.php.net/ and http://www.phpfreecode.com/
3. Software Engineering Roger.S. Pressman
4. HTML,CSS ,JAVA SCRIPT from http://www.w3schools.com/
5 PHP and MYSQL for dummies by Janet Valade

HIMANSHU

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

HIMANSHU

Hochgeladen von

Copyright:

Verfügbare Formate

PROJECT REPORT

HIMANSHU SHEKHAR SAHOO

Signature of Project Guide

HIMANSHU SHEKHAR SAHOO

PROJECT CODE :PJ(3.6.37)

NAME :HIMANSHU SHEKHAR SAHOO

PROJECT TITLE :e-Student Zone

COMMENCING DATE :12TH MARCH, 2O15

DUE DATE :5TH MAY, 2015

SUBMISSION DATE :14TH MAY, 2015

APPROVED BY Internal External

What I write or mention in this sheet will hardly be

First of all I wish to express my sincere thanks to

Finally I wish to express my heartiest thanks to

HIMANSHU SHEKHAR SAHOO

I have made every effort to rectify the errors from the

1. HIMANSHU SHEKHAR SAHOO 12DIT-141

4. Requirement Analysis & Specification

10. System implementation and maintenance

11. System Security Measures

12. Future Scope

1.2 PROJECT DESCRIPTION

1.2 DRAW BACKS OF EXISTING SYSTEM:

1. The existing system is totally manual.

1.1 WATER-FALL MODEL

V&V -Validation and Verification

REQUIREMENT ANALYSIS & SPECIFICATION

1.1 REQUIREMENT GATHERING ANALYSIS

1.1.2 REQUIREMENT SPECIFICATION

1.1 OPERATIONAL FEASIBILITY

Operational feasibility criteria measure the urgency of the problem or acceptability

1.2 TECHNICAL FEASIBILITY

1.3 ECONOMICAL FEASIBILITY

As soon as the specific requirements and solutions have been identified

USE CASE DIAGRAM:

DEFINITION OF USE CASE DIAGRAM:-

COMPONENTS OF USE CASE DIAGRAM:-

The components of use case diagram are:

1. An actor is a user of the system playing a particular role.

Use Case for e-Student Zone

ADMIN Controls Examination

STATE CHART DIAGRAM

5) Synchronization and Splitting of Control

Enter ID & Password

Validate ID & Password

OPEN ADMIN PAGE

Enter ID & Password

Validate ID & Password

OPEN LECTURER PAGE

Enter Roll No. Enter Name & Course

Validate Roll no./Name & Course

OPEN STUDENT DETAILS PAGE

Enter Course Details

Validate Course Details

Data Saved in Database Successfully

Fetch Course Details From Database

Enter new Course Details

Validate Course Details

Data Updated Successfully

Entity Relationship Diagrams

ADMIN LECTURER STUDENT

ADD COURSE COURSE COURSE DETAILS

COURSE DELETE COURSE SUBJECT SUBJECT DETAILS