Propro 1

Index
COMPUTER CENTER MANAGEMENT ----------------------------------------------------------- Error! Bookmark not defined.

ACKNOWLEDGEMENT -------------------------------------------------------------------------------- Error! Bookmark not defined.
DECLARATION-------------------------------------------------------------------------------------------- Error! Bookmark not defined.
Ch1. Introduction---------------------------------------------------------------------------------------------------------------------------------- 1
1.1 SCOPE OF THE PROJECT------------------------------------------------------------------------------------------------------------ 1
1.2 Project Description ----------------------------------------------------------------------------------------------------------------------- 1
1.2.1 Existing System --------------------------------------------------------------------------------------------------------------------- 2
1.2.2 Implementation of Proposed System ------------------------------------------------------------------------------------------- 2
1.3 Advantages of IMS ----------------------------------------------------------------------------------------------------------------------- 2
Ch2. Project Category Tools & Environment ---------------------------------------------------------------------------------------------- 3
2.1 Project Category--------------------------------------------------------------------------------------------------------------------------- 3
2.2 Front End ----------------------------------------------------------------------------------------------------------------------------------- 3
2.3 Back End ------------------------------------------------------------------------------------------------------------------------------------ 3
2.4 Software and Hardware Requirements----------------------------------------------------------------------------------------------- 4
2.4.1 HARDWARE TOOLS------------------------------------------------------------------------------------------------------------- 4
2.4.2Software TOOLS:-------------------------------------------------------------------------------------------------------------------- 4
Ch3. Project Development Stages ------------------------------------------------------------------------------------------------------------- 5
3.1 SYSTEM DEVELOPMENT LIFE CYCLE ------------------------------------------------------------------------------------------- 5
3.2 Recognition of Needs ----------------------------------------------------------------------------------------------------------------- 5
3.3 Feasibility Study ----------------------------------------------------------------------------------------------------------------------- 5
3.4 System Analysis DFD (Data Flow Diagram & E-R Diagram)----------------------------------------------------------------- 7
3.3.1 DFD’s ---------------------------------------------------------------------------------------------------------------------------------- 8
3.3.2 Entity Relationship Diagram -----------------------------------------------------------------------------------------------------------17
3.4 System Analysis (Structure Charts, Structure of Data Tables etc).) ------------------------------------------------------18
3.4.1Data Dictonary -----------------------------------------------------------------------------------------------------------------------------18
3.5 System Development ----------------------------------------------------------------------------------------------------------------21
3.6 Testing, Implementation & Maintenance ---------------------------------------------------------------------------------------21
Ch4. OUTPUT OF THE PROJECT: --------------------------------------------------------------------------------------------------------23
4.2 CODING -----------------------------------------------------------------------------------------------------------------------------------38
CONCLUSION --------------------------------------------------------------------------------------------------------------------------------- 102
FUTURE ENHANCEMENT--------------------------------------------------------------------------------------------------------------- 102
BIBLOGRAPHY------------------------------------------------------------------------------------------------------------------------------- 103
Ch1. Introduction
This is a web base project consist the list of programs manage the student database, courses detail ,any
query, fees management and other detail.
It is an platform independent project which can be access by any type of system.
Here admin can access the all information student can view there details any external person can visit on
web and can ask any kind of query and visit on course section .
It include modules such as-
 Student management
 Fees management
 Query& Support
1.1 SCOPE OF THE PROJECT

It may help collecting perfect management in details. In a very short time, the collection will be obvious,
simple and sensible. It will help a person to know the management of passed year perfectly and vividly. It
also helps in current all works relative to Center. It will be also reduced the cost of collecting the
management & collection procedure will go on smoothly.
The present project has been developed to meet the aspirations indicated in the modern age. An attempt
has been made through this project to do all work ease & fast. It provide current add, Update, Move Next,
Move Previous, Move Last, Find & Delete all facilities to accomplish the desired objectives. The facility
Include in this project and the suggested activities have been organized to impart knowledge & develop skill
& attitude in the official works.
And also help students to access the result of past years and details
About the course.
1.2 Project Description

IMS gives the various facility to handle the Institute, It give the ability to student any one can
register with us from the home and join or enrol in the course. It have various Modules like Course Module,
Student Module, Teacher Module, Certificate Module etc.
1
1.2.1 Existing System
 It is less time consuming process.
 Student comes to the Institute then owner have to made entry on offline system.
 Fee/Salary details records are on the offline.
 As the current system is totally computeraized but offline.
 It require more time for completion of any work..
1.2.2 Implementation of Proposed System

 The new system is also computerised with online working.
 The Institute having number of students and staff can directly manage the registration from more then
one student or staff.
 To provide easy to institute information in computerized system so it can be easy available for retrieval.
 To make calculation easily.
 To provide easily and fast searching facility.
 New system gives immediate response to the possible query.
 To reduce main power involve in the procedure
 It becomes more helpful to save the time.
Administrator can handle the system from anywhere using internet.
1.3 Advantages of IMS

1. Reducing the workload
2. Increase the Productivity
3. Full Control Control
4. Security
5. Real Time Report
6. Up-to-date information
2
Ch2. Project Category Tools & Environment
2.1 Project Category
2.2 Front End
1. HTML
HTML is a markup language which is used by the browser to manipulate text images and other content to display
it in required format. HTML was created by Tim Berners Lee in 1991. HTML stands for Hyper Text Markup
Language. It is used to design web pages using markup language. HTML is the combination of Hypertext and markup
language. Hypertext defines the link between the web pages. Markup language is used to define the text document
within tag which defines the structure of web pages. The First ever version of HTML was HTML 1.0 but the first
standard version was HTML 2.0 which was published in 1999.
Features of HTML
1. It is easy to learn and easy to use.

2. It is platform independent.
3. Images, Videos and audio can be added to a web page.
4. Hypertext can be added to text.
5. It is a markup language.
2. CSS
Cascading Style Sheets, fondly referred to as CSS, is a simply designed language intended to simplify
the process of making web pages presentable. CSS allows you to apply styles to web pages. More
importantly, CSS enables you to do this independent of the HTML that makes up each web page. CSS is
easy to learn and understood bu it provides powerful control over the presentation of an HTML document.
Features of HTML
1. CSS saves time

2. Easy Maintenance
3. Search Engines
4. Superior styles to HTML
5. Offline Browsing
3. JSP (Java Server Page)
JSP is a technology that helps software developers create dynamically generated web pages based on
HTML, XML or other document types. It released in 1999 by Sun micro system, JSP is similar to PHP and
ASP but it uses java programming language.
2.3 Back End

A database is a collection of information that’s related to a particular subject or purpose, such as
tracking customer orders or maintaining a music collection .If your database isn’t stored on a computer, or
only parts of it are , you may be tracking information from a variety of sources that you have having to
coordinate and organize yourself.
3
For example, suppose the phone numbers of your suppliers are stored in various locations: in a card
file containing supplier phone numbers, in product information file cabinet, and in a spreadsheet containing
order information .if a supplier’s phone number changes, you might have to update that information in all
three places in database, however, you only have to update that information in one place- the supplier’s
phone number is automatically updated wherever you use it in database.
Using MYSQL, you can manage all your information from a single database file. With in the file, you can
use:
 Tables to store your data.

 Queries to find and retrieve just the data you want
 Forms to view add and update data in tables.
 Reports to analyze or print data in a specific layout.
Data access pages to view, update, or analyze the database’s data from the internet.
2.4 Software and Hardware Requirements

During the creation of project we requires and we uses several hardware & software tools:
2.4.1 HARDWARE TOOLS-

1. Core 2 Duo or Above
2. 512 MB RAM
3. 15 GB Hard Disk
4. Optical Mouse
5. a general Color Monitor
2.4.2Software TOOLS:-
1. Operating System : Window 7 and above
2. Front end : Java (jdk 1.7),html,css,jsp
3. Back end : My sql
4
Ch3. Project Development Stages
3.1 SYSTEM DEVELOPMENT LIFE CYCLE
Software development is a complex process so we divide the process in a small module. These modules are
called system development phases. These phases are combinedly known as system development life cycle.
These linear cycle phases are given below: -
i. Recognition of Needs: - It includes preliminary survey and initial investigation by personnel

interviews and questionnaires.
ii. System Analysis: - Detailed evaluation of present system and data collection is done. The various
reports and documents used are studied in detail. After that the interview of various levels of
management is carried out. The DFD. Data dictionary, Menu chart are the tools used for it.
iii. System Design: - It involves general and detailed design specification, output, input files, files,
program construction plans, all these details are submitted to user and got signed.
iv. System Construction: - It involves implementation of total construction plan i.e. coding. It is done in
a language i.e. known to user, analyst and programmer.
v. Testing: - Each and every input and output program is executed separately and tested for bugs. Whole
of the system is executed and test data is prepared and is fed in to the system and the output reports are
compared with the parameters.
vi. Implementation:- It checks that users requirement are fulfilled or not. Response time is checked and
finally the user manual is prepared and is submitted.
3.2 Recognition of Needs

1. Computerize management of student’s database
2. Reduce paper work
3. Faculty and course’s management
4. Various limitation description and management
5. Very brief guidance to student’s and faculty
3.3 Feasibility Study

In this phase a discussion is arrive between the members of management on the requirement of S.R.S and
the objective of company there are several cases for discussion such as:-
Is project satisfies the company objective?

Is project is under budget?
Is project can be done on available technology?
Duration time of project?
Future scope of project?
A.Economical feasibility:- in this we study about-
All hardware and software cost has been burned here

We have estimate the overall benefit of the organization
5
B. Technical feasibility:- we discuses that required functionality of S.R.S can be achieve on available
technology or not.
And in last we decides should project be taking or not
6
Modules Of Project
• AA Student management
Fees management
Query and support
Student management:- it include:-
 Maintenance structure
 Admission process
 Course details & proper classes
Fees management - it include:-
 Course fees
 Balance ammount
Query and support:- it include:-
 Any type of query

 Fast solution
3.4 System Analysis DFD (Data Flow Diagram & E-R Diagram)
 SYSTEM DEFINATION
A system may be defined as any set of modules and ideas and its inter-relationships that is ordered to
achieve a common goal .A system processes the input to produce outputs .The process in a manual system
usually employs various types of elements.
 Physical
 Procedural
 Conceptual
 Social etc.
7
A system is limited by its boundary. A system is composed of sub-systems, which are also systems
as this developed Institute Management System. It was decided to develop a system which having
following features:
1. Student
2. Course
3. Fee
4. Salary
5. Staff
Therefore, the system has the characteristics of frequently available information.
 PERFORMANCE REQUIREMENTS:
1. USER-FRIENDLY: The system should be user friendly so that it can be easily understood by the
user without any difficulty.
2. EASY TO MAINTAIN: The system is easy to maintain and use. The system should be less time
consuming whish could be achieved by good programming.
3. PORTABILITY: The system probability should be taken care of without any interventions.
4. SECURITY: The system should be secure from the unauthorized access and should be password
protected so that no other user can access it.
5. ERROR FREE: The system should easily handle the use error in any case.
 GENERAL ATTRIBUTES:
1. AVAILABILITY
2. MAINTAINABILITY: This software can be maintained with the help of extensive documentation
to be provided to the client.
TRANSFERABILITY/CONVERSION: Product can easily be transferable to new version of windows.
3.3.1 DFD’s
Introduction:
System design is a solution, “How to approach” to the creation of a new system. This important phase is
composed of several steps. It provides the understanding and procedural feasibility study. Design goes
through a logical and physical stage of development. Logical design reviews the present physical system,
prepares input – output specification, makes edit, security and control specification, detail implementation
plans, and prepares a logical design walkthrough. The physical design maps out the details of the physical
system, plans the system implementation and specifies any new hardware and software.
System design is a highly created process that can be greatly facilitated by the following:
 Strong problem definition,

 Pictorial description of the existing system, and
 Set of requirements of the new system.
Input Design
8
The most common cause of errors in data processing is inaccurate input data errors entered by the data entry
operator. It can be controlled by the input design. Input design is the process of converting user oriented
inputs to the computer based formats. The goal of the input design is to make data entry as easy, logical and
free from as many errors as possible.
Output Design
Computers are the most important sources of information to the users are fed into the computers to acquire
the necessary outputs. The computers can provide the well enough output in the form of information
regarding various items to the users. The major form of output is a hard copy from the printer. Printouts are
designed around the output requirements of the user(s).
Interface Design
Forms are designed to control the redundancy, increased operator accuracy maximum readability, easy data
entry and elimination of unnecessary data to provide easier checking and correction of data. Keeping in view
the user’s requirements, the input/output forms have been designed
And developed for easy data entry and query handling. Based on the various types of inputs to be fed into
the computer in using this system, several inputs forms have been designed to make data entry easier and
accurate.
Database Design
Information stored in the database, despite system crashes or attempts at unauthorized access. The collection
of data is usually referred to as the database. The database contains information about the particular
enterprise. Database systems are designed to manage larger bodies of information. The management of data
involves both the definition of the structures for the storage of the information and the provision for the
mechanism to manipulate the information. In addition the database system must provide the safety of this.
9
DEBUGGING
This stage is the discovery & correction of programming errors. Few programs run correctly the first time,
so debugging is important & time-consuming stage of the software development. Programming theorists &
testing as verification & validation, respectively. Verification ensures that the program does what the
programmer intend to do. It is the checking or testing of the items, including software, for conformance and
consistency with an associated specification. Validation ensures that the program produces the correct
results for a set of test data. It refers to the different set of activities that ensures that the software that has
been built is traceable to custom requirements.
BOEHM states these terms as
VERIFICATION—“Are we building the product right?”

VALIDATION—“Are we building the right product?”
The debugging of microprocessor programs is generally quite difficult because of the inability to observe
register contents directly, the primitive debugging aids, the close interaction between hardware & software,
the frequent dependence of programs on precise timing, and the difficulty of obtaining adequate data for
real-time applications, The tools that can be used by programs with brief description are given below: -
Simulators: It is a Computer program that simulates the execution of programs on another computer.
Logical Analyzers: It is a test instrument that is the digital bus-oriented version of the oscilloscope. It
detects the states of digital signals during each clock cycle & stores them in the memory. It then displays the
information on a CRT, much as an oscilloscope does.
Breakpoints: It is place in a program at which execution can be halted, in order to examine the current
contents of registers, memory locations & I/O ports.
Trace Routines: A trace is a program that prints information concerning the status of the processor at
specified intervals. Most simulator program & some microcomputer development system have trace
facilities.
Memory Dumps: A memory dump is a listing of the current contents of a section of the memory. Most
simulator programs, microcomputer development systems & monitors can produce memory dumps.
Software Interrupts: The software interrupts or trap instruction is frequently used for debugging purposes.
The instruction usually saves the current value of the program counter & then branches to a specified
memory location. That information location can be the starting point of a debugging program that lists or
displays status information – breakpoint may be inserted with trap instructions.
10
SYSTEM ANALYSIS
Introduction:
System Analysis is a set of techniques and graphical tools to develop a new kind of specification that are
easily understandable to the users. The system Analysis has the following attributes:
1. It is graphical. The DFD, for example, depicts a picture of what is being specified and
conceptually easy to under to understand the presentation of the application and flow the data to
/from/with in the system.
2. The process is partitioned so that we have clear picture of progression from general to specific in the
system flow.
3. It is logical rather then we have clear picture of progression from general to specific in the system
flow.
4. It collects regroups study of the user area, a commitment that is often taken likely in the traditionally
advent of the system analysis.
5. Certain tasks that are normally carried out late in the system development cycle are moved to the
analysis phase. For example, user procedure documented during the analysis rather than later in the
application.
The end result of the system analysis is that produces a structured specification has uses several basics tools,
such as:
 Context diagram
 Data flow diagram
 Structured chart
Context Diagram:
Context diagram is the starting point of the structured analysis. They are constructed to show the highest-
level model of the system. It is used to represent pictorially, the scope of boundaries of the system, or what
we call “AREA UNDER STUDY”.
11
D.F.D.(Data Flow Diagram)
A data flow diagram (DFD) maps out the flow of information for any process or system. It uses defined
symbols like rectangles, circles and arrows, plus short text labels, to show data inputs, outputs, storage
points and the routes between each destination.
There are 3 level of D.F.D.
 0 LEVEL OR CONTEXT LEVEL

 1 LEVEL DFD
 2 LEVEL DFD
SYMBOLS
ENTITY
DATA FLOW
DATA STORE
PROCESS
12
CONTEXT OR 0 LEVEL DFD
Admin
Institute
Management Output
System
Student
13
LEVEL 1 DFD
Fee
Mgnt
Admin
Login
Course Student
Mgnt
Query
Login
View
Student
Details
Student
14
LEVEL 2 DFD
REGISTRATION STAFF INFO.
STAFF
NEW INFORTION
STAFF ADMIN
ID CREATE
STAFF INFORMATION
STUDENT INFORMATION LOGIN DETAIL
INPUT STUDENT INFORMATION PASSWORD CHANGE
STUDENT STAFF
STAFF
APPLICATION
15
E.R
DIAGRAM
16
3.3.2 Entity Relationship Diagram
Ad_ID Ad.Nam
e Query
Resp
Admin
Ask
S _ID C_ID
Reg.
WHICH
ADMISSION
STUDENT S_ID WHICH
NAME CONTACT
DURATION
COURSE’S
CLASS
C_ID
SYLABUS
ALORT FEES
CL-ID B_ID
NO
BATCH
B_TIME B_ID
17
3.4 System Analysis (Structure Charts, Structure of Data Tables etc).)
3.4.1Data Dictonary
A set of information describing the contents, format, and structure of a database and the relationship
between its elements, used to control access to and manipulation of the database.
it is just like a information container in this a detail of every module is note down during creation of module
for the future changing and maintenance purpose.
DATABASE OF PROJECT
1. Admission Table
FIELD DATA TYPE DESCRIPTION
E no. Auto number Roll number
Name Varchar Name
F Name Varchar Father Name
Address Varchar Address
D.O.B Date Date of birth
Contact Varchar Mobile number
Course Varchar Course
Duration Varchar Course duration
Batch Varchar Timing
Timing
Fees Varchar Total fee
Status Varchar Fee status
Mode Varchar Fee mode
Password Varchar Student password
Balance Varchar Remaining amount
18
2. Login Table
ID Varchar Admin ID
Password Varchar Password
Contact Varchar Contact No.
3. Fee Table
E no. Integer Student enrollment
number
Fee Varchar Submit Amount
Date Date Date of submit
4.Query Table
Problem Varchar Any Query
Email Varchar Email
19
20
3.5 System Development
3.6 Testing, Implementation & Maintenance

TESTING
At this phase when our application is ready we test it on different parameters to ensure is our application
fulfil the customer requirements or not if there is any error accrue during the run time of software.
 The various testing are-

o BLACK BOX TESTING
o WHITE BOX TESTING
o GREY BOX TESTING
 Testing are also categorize in several phases:
o Unit Testing
o Integration Testing
o Validation Testing
o User Acceptance Testing
o System Testing
21
1:BLACK BOX TESTING:- BLACK BOX TESTING, also known as BehavioralTesting, is a
software testing method in which the internal structure/design/implementation of the item being tested is not
known to the tester. These testscan be functional or non-functional, though usually functional.
2:WHITE BOX TESTING:- WHITE BOX TESTING (also known as Clear Box Testing, Open Box Testing,
Glass Box Testing, Transparent Box Testing, Code-Based Testing or StructuralTesting) is a
software testing method in which the internal structure/design/implementation of the item being tested is
known to the tester.
3:GRAY BOX TESTING:- Gray box testing, also called gray box analysis, is a strategy for software
debugging in which the tester has limited knowledge of the internal details of the program. A gray box is a
device, program or system whose workings are partially understood.
22
Ch4. OUTPUT
OF THE
PROJECT:
23
4.1 Output Screen
24
25
26
27
28
29
30
31
32
33
34
35
36
37
4.2 CODING
38
<!doctype html>
<html>
<head>
<title>welcome paage</title>
<link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
<link rel="stylesheet"type="text/css"href="style.css">
<link rel="stylesheet"type="text/css"href="vender/css/Grid.css">
<link rel="stylesheet"type="text/css"href="vender/css/normalize.css">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-
awesome/4.7.0/css/font-awesome.min.css">
</head>
<body>
<header>
<marquee scrollamount="10" behavior="alternate" direction="right"
class="mar">A place to develop your programming skills</marquee>
<div class="row">
<h1 style="font-size: 24px">welcome to i-act the learning hub</h1>
</div>
<a href="studata.html" class="btn1">student</a>
<a href="login.html" class="btn">admin</a>
</header>
39
<section class="course">
<div class="row">
<h3>our Courses</h3>
</div>
<div class="row">
<ul class="course-shokage">
<li>
<figure class="adjust">
<img src="resources/img/c1.jpg"alt="c">
</figure>
</li>
<li>
<img src="resources/img/c++1.jpg"alt="c++">
</figure>
</li>
<li>
<img src="resources/img/java.jpg"alt="java">
</figure></li>
<li>
<img src="resources/img/python1.jpg"alt="python">
40
</figure>
</li>
</ul>
</div>
<div class="row">
<ul class="course-shokage">
<li>
<img src="resources/img/web.jpg"alt="web-designe">
</figure>
</li>
<li>
<img src="resources/img/android.jpg"alt="android">
</figure></li>
<li>
<img src="resources/img/ccc.jpg"alt="ccc">
</figure></li>
41
<li>
<img src="resources/img/tally.jpg"alt="tally">
</figure></li></ul>
</div>
<div class="row">
<a href="course.html" class="details">view-more</a>
</div>
</section>
<section class="testomonial">
<div class="row">
<h3>what our student says</h3>
</div>
<div class="row">
<div class="col span-1-of-3">
<blockquote>
Enivornment is Very Good, facultoies are Hard working, guides
carrier oriented courses.
<cite><img src="resources/img/toshu%20(2).jpg">Tushar
Rohila</cite>
</blockquote>
42
</div>

<blockquote>
Faculties give right direction to students and use modern teaching
technology for dovelopment of skills. <cite><img
src="resources/img/sann.jpg">Sanawwar Husain</cite>
</blockquote>
</div>
<blockquote>
For best computer knowledge join here, various workshops are
orgonize to increes your skills.
<cite><img src="resources/img/rti.jpg">Aaru Saini</cite>
</blockquote>
</div>
</div>
</section>
<section class="about">
<div class="row">
<h3>about-us</h3>
</div>
<div class="row">
43
<p class="detail">Since 2008, i-act is committed to excellence in
computer training and education and its mission is to impart latest technical
knowledge to the students. We prepare the students for the competitive job
market, gearing them up to face the challenging work environment. i-act is the
study center of NIELIT. i-act is Certified by ISO 9000-2015. <a
href="query.html" class="myprob">ask a question</a></p>
</div>
</section>
</body>
</html>
44
package view;
import java.sql.*;
public class ViewEno
{
private int eno;
public ViewEno(){}
public void setEno(int eno)
{
this.eno=eno;
}
public int getEno()
{
return eno;
}
public ResultSet view(int eno)
{
String s=null;
try
{
Class.forName("com.mysql.jdbc.Driver");
Connection
con=DriverManager.getConnection("jdbc:mysql://localhost/computer?user=root
&password=");
String q="select * from admison where eno=?";
45
PreparedStatement p=con.prepareStatement(q);
p.setInt(1,eno);
ResultSet rs=p.executeQuery();
return rs;
}
catch(Exception e)
{
return null;
}
public ResultSet view_all()

{
try
{
Connection
&password=");
String q="select * from admison";
return rs;
46
}
catch(Exception e)
{
return null;
}
}
}
47
<jsp:useBean id="f" class="studentfee.Fee"/>
<%@page import="java.sql.*"%>
<%
try
{
ResultSet rs1=f.displayAllStudent();
%>
<center><h1>Student Records</h1>
<table border=1 style="text-align: center;text-
transform:capitalize;width:100%"><tr style="background-
color:black;color:white"><td>eno</td><td>name</td><td>father_name</td><td
>address</td><td>dob</td><td>contact</td><td>course</td><td>duration</td>
<td>batch_timing</td><td>fees</td><td>status</td><td>mode</td></tr>
<%
int n=0;
while(rs1.next())
{
n++;
int eno=rs1.getInt(1);
String name=rs1.getString(2);
String father_name=rs1.getString(3);
String address=rs1.getString(4);
String dob=rs1.getString(5);
String contact=rs1.getString(6);
String course=rs1.getString(7);
48
String duration=rs1.getString(8);
String batch_timing=rs1.getString(9);
String fees=rs1.getString(10);
String status=rs1.getString(11);
String mode=rs1.getString(12);
%>
<%
if(n%2==0)
out.println("<tr>");
else
out.println("<tr style='background-color:gray'>");
%>
<td><%=eno%></td><td><%=name%></td><td><%=father_name%></td><td
><%=address%></td><td><%=dob%></td><td><%=contact%></td><td><%=c
ourse%></td><td><%=duration%></td><td><%=batch_timing%></td><td><%
=fees%></td><td><%=status%></td><td><%=mode%></td></tr>
<%
}
%>
</center>
</table>
<%
49
}
catch(Exception ee){
out.println(ee);
}
%>
50
<!doctype html>
<html>
<head>
<title>fees</title>
<link rel="stylesheet"type="text/csss"href="vender/css/Grid.css">
<link rel="stylesheet" type="text/css" href="view.css">
</head>
<body>
<header>
<nav>
<ul class="main-nav">
<li><a href="DisplayQuery.jsp">query</a></li>
<li><a href="show.html">by-eno</a></li>
<li><a href="feeview.jsp"> fees</a></li>
<li><a href="viewall.jsp">view-all</a></li>
</ul>
</nav>
</header>
</body>
</html>
51
header
{
background-image: url(resources/img/view3.jpeg);
background-position: center;
background-size: cover;
height: 100vh;
margin: 0,0,0,0;
}
.main-nav
{
position: absolute;
left: 60%;
color: #000;
word-spacing: 15px;
font-size: 25px;
text-transform: none;
height: 20px;
}
.main-nav li
{
display: inline-block;
text-decoration: none;
}
52
.main-nav li a
{
text-transform: capitalize;
color: white;
.for
{
font-size: 20px;
}
.mid
{
margin-left: 250px;
margin-top: 100px;
}
.subm
{
position: absolute;
top: 25%;
left: 30%;
}
53
<%
String name=(request.getParameter("name"));
try{
int i=1;
Connection
&password=");
String q="insert into try values(?,?)";

p.setInt(i);
p.setString(name);
i++;
int t=p.executeUpdate();
if(t==1)
{
out.println("record add successfully");
}
else
54
{
out.println("record not add");
}
}
catch(Exception e){
out.println("excepion is:"+e);
}
%>
55
<!doctype html>
<html>
<head>
<title>forget password</title>
<link rel="stylesheet"type="text/css"href="p.css">
</head>
<body>
<form method="get" action="try.jsp" class="center">
<div class="row">
<label class="pro">enter name:</label>
</div>
<input type="text" name="name" class="sub">
</div></div><div class="row">
<input type="submit" value="ok">

</div>
</form>
56
</body>
</html>
57
<%
String id=(request.getParameter("id"));
String contact=(request.getParameter("contact"));
String pass=(request.getParameter("pass"));
try{
Connection
&password=");
58
header
{
background-image: url(resources/img/wc.JPG);
height: 100vh;
}
.btn
{
position: absolute;
top: 45%;
left: 54%;
width: 80px;
height: 28px;
border: 1px solid black;
font-size: 25px;
color: black;
background-color: rgba(255, 69, 0, 0.81);
border-radius: 30%;
padding-left: 2px;
59
text-align: center;
}
.btn li:active
{
background-color: green;
}
.btn li:hover
{
}
.btn1
{
position: absolute;
top: 45%;
left:36%;
width: 80px;
height: 28px;
font-size: 25px;
color: black;
border-radius: 30%;
padding-left: 2px;
60
text-align: center;
}
.btn1 li:active
{
}
.btn1 li:hover
{
}
.mar
{
font-size: 25px;
color: blue;
}
h1
{
position: absolute;
color: red;
top: 30%;
left: 32%;
}
/*-----------------------------*/
61
/*-----------------------------login html----------------------------*/
.mid
{
margin-left: 250px;
margin-top: 100px;
}
.log
{
font-size: 20px;
}
.holder
{
margin-top: 0px;
margin-left: 30px;
}
.new_log
{
position: absolute;
top: 38%;
left: 32%;
}
62
.forget
{
position: absolute;
margin-left: 60px;
list-style: none;
}
/*-----------------------course-----------------------*/
.course
{
list-style: none;
width: 100%;
background-color: gainsboro;
padding: 0;
}
.course li
{
display: block;
float: left;
width: 25%;
margin: 0;
padding: 0;
}
.adjust
63
{
width: 100%;
margin: 0;
}
.course-shokage
{
margin: 0;
padding: 0;
overflow: hidden;
background-color: #000;
}
.course-shokage img
{
margin: 0;
width: 100%;
height: auto;
transform: scale(1.15);
transition: transform 0.5s, opacity 0.5s;
}
.course-shokage img:hover
{
64
transform: scale(1.03);
opacity: 1;
}
.details
{
position: absolute;
left: 88%;
font-size: 20px;
color: red;
padding-left: 2px;
text-align: center;
}
.details li:active
{
}
.details li:hover
{
}
65
/*------------------customer testomonial-----------------*/
h3
{
text-align: center;
font-weight: 300;
font-size: 40px;
}
.testomonial{
background-image: url(resources/img/view4.jpg);
background-attachment: fixed;
color: #;
}
blockquote
{
padding: 2%;
font-style: italic;
line-height: 145%;
font-size: 30px;
}
blockquote:before
66
{
content: "\201c";
font-size: 400;
display: block;
}
cite
{
font-size: 90%;
margin-top: 25px;
display: block;
}
cite img{
height: 45px;
border-radius: 50%;
margin-right: 10px;
vertical-align: middle;
}
.admin
{
height: 47px;
position: absolute;
border-radius: 50%;
67
margin-right: 10px;
vertical-align: middle;
left: 59%;
top: 18%;
/*-----------------about-us---------------------*/
.about
{
}
.detail
{
color: #fff;
font-size: 30px;
}
.myprob
{
color: red;
position: absolute;
left: 88%;
68
font-size: 18px;
}
/*--------------n------------navigtion-----------------------*/
.main_nav
{
position: absolute;
left: 36%;
top: 40%;
word-spacing: 2px;
font-size: 17px;
}
.main_nav li
{
display: inline-block;
}
.main_nav li a
{
69
text-transform: uppercase;
color: red;
}
h2
{
position: absolute;
top: 30%;
left: 35%;
color: blue;
font-size: 30px;
}
/*-----------------------admision-------------------*/
h4
{
font-size:20px;
}
70
<jsp:useBean id="f" class="studentfee.Fee" />
<%
int eno=Integer.parseInt(request.getParameter("eno"));
String amt=(request.getParameter("amt"));
String my=f.feeDeposit(eno,amt);
out.println(my);
%>
71
<%
String pass=(request.getParameter("password"));
try
{
response.setContentType("text/html");
Connection
&password=");
String q="select * from admison where eno=? and password=?";
p.setInt(1,eno);
p.setString(2,pass);
if(rs.next())
{
%>
<jsp:forward page="showrecord.jsp"/>
<%
}
else
72
{
%>
<%
out.print("wrong id or password");
}
catch(Exception e)
{
out.println("exception is"+e);
}
%>
73
<!doctype html>
<html>
<head>
<title>student portal</title>
<link href="https://fonts.googleapis.com/css?family=Lato"
rel="stylesheet">
</head>
<body>
<section class="background1">
<form method="get" action="studata.jsp">
<div class="center">
<div class="row">
<label
class="pro">E_no</label> &nbsp
</div>
74
<input type="text" name="eno" placeholder="enrollment-number"
class="sub"required><br>
</div>
</div>
<div class="row">
<label class="pro">password</label>
</div>
<input type="password" name="password" placeholder="student
password" class="sub"required><br>
</div>
</div>
<div class="row">
<input type="submit" value="show" class="store">
</div>
</div>
</form>
</section>
</body>
</html>
75
<jsp:useBean id="e" class="studentfee.Fee"/>
<%
try
{
ResultSet rs1=e.searchStudent(eno);
%>
<h1 style="text-align: center">Student Record </h1>
<table border=1 style="text-align: center;width:90%"><tr
style="background-
color:black;color:white"><td>eno</td><td>name</td><td>father_name</td><td
>address</td><td>dob</td><td>contact</td><td>course</td><td>duration</td>
<td>batch_timing</td><td>fees</td><td>status</td><td>mode</td><td>balance
</td></tr>
<%
int n=0;
if(rs1.next())
{
n++;
int eno1=rs1.getInt(1);
String name=rs1.getString(2);
String father_name=rs1.getString(3);
String address=rs1.getString(4);
String dob=rs1.getString(5);
76
String contact=rs1.getString(6);
String course=rs1.getString(7);
String duration=rs1.getString(8);
String batch_timing=rs1.getString(9);
String fees=rs1.getString(10);
String status=rs1.getString(11);
String mode=rs1.getString(12);
String balance=rs1.getString(14);
%>
<%
if(n%2==0)
else
%>
<tr><td><%=eno1%></td><td><%=name%></td><td><%=father_name%
></td><td><%=address%></td><td><%=dob%></td><td><%=contact%></td>
<td><%=course%></td><td><%=duration%></td><td><%=batch_timing%></t
d><td><%=fees%></td><td><%=status%></td><td><%=mode%></td><td><
%=balance%></td></tr>
<%
}
else
77
{
out.println("no recod found");
}
%>
</table>
<%
}
catch(Exception ee){
out.println(ee);
}
%>
78
<!doctype html>
</div>
<html>
<head>
<title>view</title>
<link rel="stylesheet"type="text/csss"href="vender/css/normalize.css">
<link rel="stylesheet" type="text/css" href="view.css">
</head>
<body>
<form method="get" action="showrecord.jsp">
<div class="mid">
<div class="row">
<label class="for">enter eno:</label>
<input type="text" name="eno" class="view" placeholder="eno">
<br>
<div class="row">
<input type="submit" name="view" value="view" class="subm">
</div>
</div>
79
</div>
</form>
80
<%
try
{
String q2=(request.getParameter("q1"));
String q3=(request.getParameter("email"));
Connection
&password=");
String q="insert into query values(?,?)";
p.setString(1,q2);
p.setString(2,q3);
int t=p.executeUpdate();
if(t==1)
{
out.print("query added successfully we will response you
soon");
}
else
{
out.print("query does not added");
}
81
}
catch(Exception e)
{
}
%>
82
<!doctype html>
<html>
<head>
<link rel="stylesheet"type="text/css"href="query.css">
</head>
<body>
<section class="full">
<form method="get" action="query.jsp">
<div class="row">
<label class="question">ask your question:</label>
</div>
<textarea rows="5" cols="50" placeholder=" ask your query" class="query"
name="q1">
</textarea>
83
</div>
</div>
<div class="row">
<label class="question1">email</label>
</div>
<input type="email" name="email" placeholder="your mail" required
class="mail">
</div>
</div>
<div class="row">
<input type="submit" name="submit" class="result">
</div>
</form>
</section>
</body>
</html>
84
.question
{
position: absolute;
top: 5.5%;
font-size: 25px;
left: 14px;
color: gold;
}
.question1
{
position: absolute;
top: 14%;
font-size: 25px;
left: 14px;
color: gold;
}
.mail
{
position: absolute;
top: 14%;
}
85
.query
{
position: absolute;
left: 33%;
top: 5%;
width: 52%;
height: 3%;
}
.result
{
position: absolute;
top: 22%;
left: 40%;
}
.full
{
background-image: url(resources/img/query.jpg);
height: 100vh;
86
<!doctype html>
<html>
<head>
<title>forget password</title>
</head>
<body>
<form method="get" action="forget.jsp" class="center">
<div class="row">
<label class="pro">enter id:</label>
</div>
<input type="text" name="id" class="sub">
</div>
</div><div class="row">
<label class="pro">enter contact no:</label>
</div>
87
<input type="text" name="contact" class="sub">
</div></div><div class="row">
<label class="pro">enter new password:</label>
</div>
<input type="text" name="pass" class="sub">
</div></div>
<div class="row">
<input type="submit" value="submit" class="store">
</div>
</form>
</body>
</html>
88
/*-------------------admision--------------------*/
.mid
{
position: absolute;
left: 30%;
}
.pro
{
font-size: 23px;
}
.sub
{
margin-left: 25px;
}
.store
{
position: absolute;
top: 109%;
left: 80%;
}
.center
{
89
position: absolute;
left: 30%;
top: 20%;
}
.background1
{
background-color: rebeccapurple;
}
90
<!doctype html>
<html>
<head>
</head>
<body>
<header>
<marquee scrollamount="15" behavior="alternate" direction="right"
class="mar">Admin Section</marquee>
<div class="row">
<img src="resources/img/shobhu.jpg" class="admin">
</div>
</div>
<nav>
<ul class="main_nav">
<li><a href="admision.html">admision</a></li>
<li><a href="fees.html">fee</a></li>
<li><a href="view.html">report</a></li>
<li><a href="delete.html">delete</a></li>
91
</ul>
</nav>
<h2>welcome admin</h2>
</header>
</body>
</html>
92
<%
try
{
String id=(request.getParameter("uid"));
Connection
&password=");
String q="select * from login where id=? and password=?";
p.setString(1,id);
p.setString(2,pass);
if(rs.next())
{
%>
<jsp:forward page="nav.html"/>
<%
}
else
{
93
%>
<jsp:forward page="login.html"/>
<%
out.print("wrong");
}
catch(Exception e)
{
}
%>
94
<!doctype html>
<html>
<head>
</head>
<body>
<form method="get" action="login.jsp">
<div class="mid">
<div class="row">
<label class="log"> user id:</label>

<input type="text" name="uid" placeholder="enter id" class="holder">
</div>
<br>
<div class="row">
<label class="log">password:</label>
<input type="password" name="pass" placeholder="enter
password" class="holder">
95
</div>
<br>
<div class="row">
<a href="password.html" class="forget">forget password</a>
<div class="row">
<input type="submit" name="log-in"
value="log_in" class="new_log">
</div>
</div>
</form>
</body>
</html>
96
<%
String id=(request.getParameter("id"));
String contact=(request.getParameter("contact"));
try{
Connection
&password=");
String q1="update login set password=? where id=?

and contact=?";
PreparedStatement p1=con.prepareStatement(q1);
p1.setString(1,pass);
p1.setString(2,id);
p1.setString(3,contact);
int t=p1.executeUpdate();
if(t==1)
{
out.println("password updated successfully");
97
}
else
{
out.println("id or contact does not match");
}
}
catch(Exception e){
out.println("excepion is:"+e);
}
%>
98
<jsp:useBean id="v" class="studentfee.Fee"/>
<%
try{
ResultSet rs1=v.displayAllFees();
%>
<h1 style="text-align: center">Fee Record</h1>
<table border=1 style="text-align: center;width:90%"><tr
style="background-color:black;color:white"
><td>eno</td><td>ammount</td><td>date</td></tr>
<%
int n=0;
while(rs1.next()){
n++;
int eno=rs1.getInt(1);
String ammount=rs1.getString(2);
String date=rs1.getString(3);
if(n%2==0)
else
99
%>
<tr><td><%=eno%></td><td><%=ammount%></td><td><%=date%></td
></tr>
<%
}
%>
</table>
<%
}
catch(Exception e){
out.println(e);
}
%>
100
package myfee;
import java.sql.*;
public class FeeView
{
private FeeView(){}
public ResultSet fee()
{
try
{
Connection
&password=");
String q="select * from fees";
return rs;
}
catch(Exception e)
{
return null;
}
}
101
}
CONCLUSION
Computer centre management System has been created keeping in mind the needs of information Small and
Medium scale in Centre. It’s efficient software that includes all the basic functionalities like making data
entries for new Students, registering a new Student, editing and deleting records that are required for
smooth functioning . Additionally the Student login and Student history are also stored and can be accessed
by the administrator. And details about courses and faculty database
FUTURE ENHANCEMENT
To make the project reliable the student can make fee payment online and also certificate is generated online
for the student. The management of faculty such as salary management is done itself by the software.
102
BIBLOGRAPHY
BOOKS:-
 Herbert Schildt ,The complete refrence (9th edition), 1996
 E Balaguruswamy, programming with java
 Peggy Fisher , Get programming with java , MEAP publication
WEBSITES:-
 WWW.JavaTpoint.COM
 WWW.Java2S.COM
 WWW.RoseIndia.in
 WWW.Fadduengineer.com
 WWW.JavaTutorialpoint.COM
 WWW.Oracle.COM
 www.youtube.com
103
104

Propro 1

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Propro 1

Enviado por

Direitos autorais:

Formatos disponíveis

Index

COMPUTER CENTER MANAGEMENT ----------------------------------------------------------- Error! Bookmark not defined.

It is an platform independent project which can be access by any type of system.

It include modules such as-

1.1 SCOPE OF THE PROJECT

About the course.

1.2 Project Description

1.2.2 Implementation of Proposed System

Administrator can handle the system from anywhere using internet.

1.3 Advantages of IMS

1. It is easy to learn and easy to use.

1. CSS saves time

3. JSP (Java Server Page)

2.3 Back End

 Tables to store your data.

2.4 Software and Hardware Requirements

2.4.1 HARDWARE TOOLS-

5. a general Color Monitor

i. Recognition of Needs: - It includes preliminary survey and initial investigation by personnel

3.2 Recognition of Needs

3.3 Feasibility Study

Is project satisfies the company objective?

A.Economical feasibility:- in this we study about-

All hardware and software cost has been burned here

And in last we decides should project be taking or not

Query and support

Student management:- it include:-

Fees management - it include:-

Query and support:- it include:-

 Any type of query

 Strong problem definition,

BOEHM states these terms as

VERIFICATION—“Are we building the product right?”

There are 3 level of D.F.D.

 0 LEVEL OR CONTEXT LEVEL

REGISTRATION STAFF INFO.

STUDENT INFORMATION LOGIN DETAIL

INPUT STUDENT INFORMATION PASSWORD CHANGE

STUDENT S_ID WHICH

3.6 Testing, Implementation & Maintenance

 The various testing are-

<div class="col span-1-of-3">

public ResultSet view_all()

String q="insert into try values(?,?)";

<input type="submit" value="ok">

String q1="update login set password=? where id=?

Você também pode gostar