1

Project Report
On
BTES ERP SYSTEM MODULE: STUDENT SERVICES


SUBMITTED IN PARTIAL FULFILLMENT OF THEREQUIREMENTS
FOR THE AWARD OF THE DEGREE OF

MASTER OF
COMPUTER SCEINCE
(SOFTWARE)

SUBMITTED BY
DEEPAK
University Roll Number-366925

UNDER THE SUPERVISION OF
Dr. Abhishek Taneja
(HEAD)
DEPARTMENT OF COMPUTER SCIENCE
S.A. Jain (P.G) College
AmbalaCity







KURUKESHETRA UNIVERSITY
KURUKSHETRA


2

INDEX

Acknowledgement I
Declaration II
Abstract III
1. Introduction................................................................................... 9-22
1.1 Company Profile...............................................................9
1.1.1. Introduction of Company............................................... 9
1.1.2. Vision of the Company.................................................. 9
1.1.3. Company Expertise ....................................................... 11
1.2. Overview of Project.................................................................. 13
1.2.1. Introduction of Project.................................................. 13
1.2.2. Purpose............................................................................ 14
1.2.3. Need of System................................................................ 15
1.2.4. System Attributes............................................................. 17
1.2.5 Objective & Module Description ...................................19

2. Feasibility Study............................................................................23-26
2.1. Feasibility Study........................................................................24
2.2. Types of Feasibility Study..........................................................24
3.2.1 Technical Analysis............................................................24
3.2.2 Operational Analysis.........................................................25
3.2.3 Economical Analysis.........................................................25
3. Software Requirements Analysis..................................................27-31
3.1. System Requirements.................................................................28
3.2. Requirement Analysis..................................................................29
4.2.1 Requirements Gathering29
4.2.2 Analysis of Gathered Requirement...30
3

4.3 Requirement Specification............................................................30

4. System Design...................................................................................32-45
5.1 Designing.......................................................................................33
5.2 Types of Designing........................................................................33
5.3 Data Flow Diagram........................................................................35
5.4 Gantt & Pert Chart..........................................................................42

5. Scripting Language..........................................................................46-51
5.1. About Scripting Language.............................................................47
5.2. Technology Used...........................................................................47
6. Database............................................................................................52-57
6.1. Database Tables.............................................................................52
7. Screen Shots......................................................................................58-74
7.1. Screen Shots...................................................................................58
8. Testing...............................................................................................75-78
8.1. S/W Testing..................................................................................75
8.2. Objective of Testing..................................................................... 75
8.3. Testing Procedure........................................................................ 76
8.3.1. Unit Testing76
8.3.2. Integration Testing.77
8.3.3. Subsystem Testing.77
8.3.4. System Testing..77
8.4 Maintanance................................................................................78
8.4.1 Types of Maintenance ........................................................78
8.4.2Corrective Maintenance........................................................78
8.4.3Adaptive Maintenance..........................................................78
8.3.4 Perfective Maintenance.......................................................78
4

9. Conclusion.....................................................................................79-80
10.1 Conclusion.........................................................................80
10 BIBLOGRAPHY...........................................................................81-82
10.1 Websites and Books...........................................................82

5


ACKNOWLEDGEMENT

Words often fail to express ones inner feelings of gratitude to his benefactors and mentors.
We express our deep sense of gratitude to the Faculty of M.SC Computer Science, for giving us an
opportunity to do project for the partial fulfillment of the requirements for the degree of M.SC
Computer Science from Shri Atmanand Jain (P.G) College Ambala City affiliated to Kurukshetra
University, Kurukshetra.
We are highly thankful to Mr. Abhishek Taneja(Head of Computer Department),Shri
Atmanand Jain (P.G) College, Ambala City for providing the opportunities and facilities to
carry out this project work and for his valuable guidance that helped out in completing the
project
We wish to express our sincere gratitude to the faculty of Shri Atmanand Jain (P.G) College ,
Ambala City for providing us such a good opportunity.
Finally thanks to all Team members who helped in completing the project successfully.
Deepak












6


DECLARATION
I hereby declare that the project report entitled BTES ERP SYSTEM (MODULE: STUDENT
SERVICES submitted to Kurukshetra University, Kurukshetra, in partial fulfillment of the
requirements for the Degree of M.SC Computer Science under the supervision of Mr
Abhishek Taneja and that it has not formed the basis either in full or in part there for the award
of any Degree/ Diploma / Associate ship / Fellowship / or similar title to any candidate of any
university.

Date: Signature of the Candidate
(Deepak)










7


ABSTRACT

This project is based on the ERP (Enterprise Resource Planning) concept where the integration of
different departments in a single portal is the fundamental idea put across. One organization is the
co-ordination of the different departments like in ours it is comprised of different technologies like
Java, .NET, Testing etc. Nowadays every enterprise requires a solution where they can
intercommunicate with each other at the end of the day they can come to a conclusive part which
will justify the process flow in the organization and that will generate filtered data and the reports
which will help the department heads to concentrate more on the decision making process and share
those reports with each other.








8







Chapter 1:
Introduction














9

INTRODUCTION OF THE ORGANIZATION






bebo Technologies Pvt. Ltd., an ISO 9001:2008 compliant company, has now emerged into
providing practical training on various software technologies under the banner of bebo Technical
Education Services (BTES).

BTES focuses on strategic and practical approach in providing training to students and working
professionals. Under the close guidance and supervision of our experienced professionals, you will
be trained on various technical aspects to tackle industry challenges faced regularly in your
professional life.

Our courses cover everything necessary to build a strong professional foundation. Through our
courses, which are developed by industry experts, we bring their learning and experience to you so
that you excel in your professional life. This brings you at par with working professionals and thus,
meets the industry expectations.



Our Vision
BTES, the success through a positive mental attitude...

"We, being the gateway to professional education ensure industry ready and day
one productive resources."
Quality Policy
o We, being the gateway to professional education ensure industry ready and day one
productive resources with comprehensive, strategic and practical hands on training.
o Ensure that our training is of the highest quality, aligned with the career objectives
and expectations of our customers, and best value for their time and money.
o Serve the community by providing access to our campus wide activities & career
resources.
10

o We shall also comply with the requirements and continually improve the
effectiveness of ISO 9001:2008 standards.
Quality Objectives
o The management and employees of BTES Pvt. Ltd. Chandigarh are fully committed
to adopt and continuous compliance of international quality management system.
o To provide our students with latest skill sets and courseware designed by industry
experts commensurate with the expectations of the Industry.
o To provide satisfactory customer service through continuous improvement of the
existing product quality and adding new products.
o Optimize training as per customer's technical and soft skills need while meeting their
career objectives.
o Ensure that the training is a perfect blend of industry examples and real time case
studies.
o 100% in time, every time delivery.
o Adding new facilities for BTES in next 12 months.

COMPANY EXPERTISE

1. Domain,Tools & Technologies

We have a dedicated group of vastly experienced and skilled professionals who consistently
research, evaluate, and develop state-of-the-art solutions with the newest tools and
technologies. Our engineers, domain experts, and multi-million dollar infrastructure work
together to help our clients of various products successfully go-to-market, time after time.
We help our clients perform software engineering without delay because we know how to
work with all the leading domains, tools, and technologies.

2. Software Product Development Services

Software product development is in our DNA; we know your challenges and mitigate them
with the right mix of programming expertise, communication best practices, proven
development methodologies, and management. Your bebo Technologies teams adopt the
product vision on behalf of your business, your customer, and your users and serve to
augment your current software product development capabilities. We provide end-to-end
development services from inception to delivery and work to release high quality product
and minimize delivery delays. Our skilled professionals build products that maximize value
to the end-user and minimize product support costs.





11

3. Data Migration Services

bebo Technologies's vast experience employing different data warehousing techniques
allows us to create data repositories whose data models support your reporting and analysis
needs. We understand the strategic importance of ensuring reliable data for the purpose of
making business models, forecasts or other projections. That is why bebo Technologies
focuses on making consolidated, integrated and consistent data despite issues in underlying
source systems.

Our Data Warehousing and Data Migration services help various clients in industries such
as banking, financial services, healthcare and retail to transform and manage their data. We
deliver end-to-end services from requirements evaluation through development,
deployment, and post-implementation maintenance. As an extension of our client's teams,
we work with various technologies and tools that will best integrate given the infrastructure
systems and in-house skills for supporting the solution.


4. Software Support Services

bebo Technologies knows software support; it's about wise management and the right
knowledge, people and processes. We solely support U.S.-based companies and understand
both cultures well. We deliver international-standard quality, strict adherence to deadlines
and total client/partner satisfaction.

bebo Technologies' engineers are all formally and continually trained in the areas of new
methodologies, effective and efficient communication and best-practice processes. Turnover
at bebo Technologies is an incredible 9%, due to hiring people who love working hard,
appreciate the company's "promote from within" policy and enjoy constantly improving
their domain knowledge. Our highly skilled professionals learn the product or system
quickly, and our high employee retention helps us be effective with that product knowledge
for the long term, thus continually improving the support services that we deliver.

12



1.2. INTRODUCTION OF THE PROJECT

Enterprise Resource Planning:

Enterprise resource planning (ERP) is a business management softwareusually a suite of
integrated applicationsthat a company can use to store and manage data from every stage of
business, including:
Product planning, cost and development
Manufacturing
Marketing and sales
Inventory management
Shipping and payment
ERP provides an integrated real-time view of core business processes, using common databases
maintained by a database management system. ERP systems track business resourcescash, raw
materials, production capacityand the status of business commitments: orders, purchase orders,
and payroll. The applications that make up the system share data across the various departments
(manufacturing, purchasing, sales, accounting, etc.) that entered the data. ERP facilitates
information flow between all business functions, and manages connections to outside stakeholders.
Enterprise system software is a multi-billion dollar industry that produces components that support
a variety of business functions. IT investments have become the largest category of capital
expenditure in United States-based businesses over the past decade. Though early ERP systems
focused on large enterprises, smaller enterprises increasingly use ERP systems.
Organizations consider the ERP system a vital organizational tool because it integrates varied
organizational systems and facilitates error-free transactions and production. However, ERP system
development is different from traditional systems development. ERP systems run on a variety of
computer hardware and network configurations, typically using a database as an information
repository.







13



1.2.1 Purpose

This project is based on the ERP (Enterprise Resource Planning) concept where the integration of
different departments in a single portal is the fundamental idea put across. One organization is the
co-ordination of the different departments like in ours it is comprised of different technologies like
Java, .NET, Testing etc. Nowadays every enterprise requires a solution where they can
intercommunicate with each other at the end of the day they can come to a conclusive part which
will justify the process flow in the organization and that will generate filtered data and the reports
which will help the department heads to concentrate more on the decision making process and share
those reports with each other.



The present solution is being developed using the Java technology, which is considered the finest
technology to integrate different technologies and platforms. As far as the future enhancement are
concerned the application is platform and architecture independent and re-deployable and reusable.
The project has taken the departmental details in the corresponding modules and has found
integration among other modules. The goal of this application is:



To provide web based interface where Trainees information including the Batch description
which can be saved and a profile will be created which can later be used.

To provide with a portal environment for placement news, grades and attendance record etc.

Project allocation records and any change in it and along with that a evaluation records will be
included too.
Save the data in a print ready form.








14

1.2.2 Why we need ERP System?

It's taking longer and longer to reconcile financials at the end of the month. Your sales forecasts are
based more on guesswork than solid figures. Your business is having trouble keeping up with its
order volume and customer satisfaction is faltering as a result. You have no idea how much
inventory you have in your warehouse, and it's a pain to find out. If this sounds like your business
or close to itthen it may be time to consider an ERP system.
Because every company is unique, there's no single indicator that says, "You need ERP now!"
However, the companies that would benefit most from ERP software often face similar problems
and frustrations. Is your business facing some of these same issues? Read on to discover the top five
signs that your company is ready for ERP.

1: You Have Lots of Different Software for Different Processes
Spend a few minutes thinking about how employees at your company record, track and process
information. Do accounting staff use one system for receivables and payables, and sales use another
to enter in customer orders? Is the process of taking those orders and getting them fulfilled and into
accounting a time-sucking manual process? Do employees in your warehouse use a completely
different solution to track shipping and receiving?
When various front- and back-end systems run separately, it can wreak havoc on the processes that
are meant to ensure your company is running smoothly. Without accurate data from sales, inventory
management may suffer, while not having the latest information from accounting can trigger a
ripple effect on everything from marketing budgets to payroll.
ERP software integrates these systems so that every business function relies on a single database.
With one source of information that contains accurate, real-time data, an ERP solution breaks up
information logjams, helps staff make better decisions more quickly and frees up their time to work
on more high-value exercises like helping the business grow even faster.

2: You Don't Have Easy Access to Information About Your Business
If someone asked you what your average sales margin is, how long would it take you to find out?
What about other key performance metrics, like orders per day or sales to date? For companies that
rely on siloed systems and spreadsheets that need to be constantly updated and reconciled manually,
it could be a long wait.
15

The pace of business is faster than ever before, which means employees across your company need
immediate access to key data. With an ERP solution, executives can get a holistic view of business
operations at any time, while other staff can get the information they need to do their jobs more
effectively. For example, sales representatives should be able to view a customer's full transaction
history and more proactively improve renewal rates while increasing upsell and cross-sell
opportunities.

3: Accounting Takes Longer and Is More Difficult
Often, the first noticeable signs that your company needs ERP software will come from your
accounting department. If your employees rely on paper-based invoices and sales ordersand
spend hours every week manually entering them into different accounting and sales systemsyou
need to consider how much time is being wasted on tasks that ERP software can handle in an
instant.
The same goes for financial reportingif it takes ages to consolidate or reconcile financial
information across systems and through countless spreadsheets, an ERP solution can make a
significant impact. With all financials in a single database, accounting staff won't have to spend
hours cross-posting information, rekeying numbers, or reconciling data manually. Your accounting
staff will be more productive, freeing them to deliver critical reports without delays and frustration.

4: Sales and the Customer Experience Are Suffering
As companies grow, one of their biggest challenges is often inventory management. Ensuring that
the right amount of products is in the right location at the right time is a vital part of business
operations.
When sales, inventory and customer data are maintained separately, it can create serious problems
across your company. If you run out of a popular product, sales will be off until the next shipment
arrives. Meanwhile, if a customer calls to inquire about an order and employees can't track it to see
if it's been shippedor if it's even in stockyour company will start to develop a poor reputation
for reliability and service.
With an ERP system, on the other hand, staff in every department will have access to the same, up-
to-the-minute information. Customer-facing reps should be able to answer customers questions
about order and shipping status, payment status, service issues, etc., without having to hang up the
phone and check with another department. Better yet, customers should be able to simply go online
to their account and view status information. Meanwhile, the warehouse manager can see that stock
is getting low and can reorder.
16

5: Your IT Is Too Complex and Time-Consuming
One of the biggest downsides of having multiple systems across your business is that IT
management can become a nightmare. Customizing these systems, integrating them and
maintaining them with patches and upgrades can be complex, costly and sap critical time and
resources.
If your patchwork of systems includes on-premise, legacy business software, system upgrades can
be more trouble than they're worth. Not only are these updates expensive and time-consuming, but
they may also undo customizations implemented by IT staff. Given that, it's no surprise that two-
thirds of mid-size businesses are running outdated versions of their business software.
1

Rather than adding more softwareand complexityto an already ineffective system, ERP
technology can give you the agility to respond to changing business needs rapidly. That's why
selecting a cloud-based ERP provider like NetSuite is critical. With NetSuite, system updates are no
longer an issue, and new functions are easy to add as your business grows and changes.


1. 2.3.1 Software System Attributes

Usability:
The links are provided for each form. The user is facilitated to view and make entries in the forms.
Validations are provided in each field to avoid inconsistent or invalid entry in the databases. Some
forms consists Hyper Links, which provides further details. Reports screen contains textboxes and
drop down lists, so that reports can be produced.

Security:
Application will allow only valid users to access the system. Access to any application resource will
depend upon users designation. There are two types of users namely Administrator and Student.
Security is based upon the individual user ID and Password.

Maintainability:
The installation and operation manual of examination management system will be provided to the
user.
Availability:
17

System will be available around the clock except for the time required for the back up of data.





Portability:
The application is developed in JAVA. It would be portable to other operating system provided
JAVA Framework is available for the OS. As the database is made in DB2, porting the database to
another database server would require some development effort.

1.2.3.2 Acceptance Criteria

The software should meet the functional requirement and perform thefunctionality effectively and
efficiently.
A user-friendly interface with proper menus.
Data transfer should be accurate and with in a reasonable amount of time keeping in mind
the network traffic.
The system should not allow entry of duplicate key values.
System should have the ability to generate transactional Logs to avoid any accidental loss of
data.
Log file should also be generated.
18

Objective/Aim:

In the nutshell the Objective of the project is to provide the organization with a planned and
systematic ways that will make all kind of professional work automated and online so that a
proper report of all the subjects can be made and that too whenever needed. It is a systematic
approach of recording progress report of Trainees and attendance report of Trainees and
Trainers as well.



1.3.1 PROPOSED SYSTEM

The proposed system is designed be a part of a large ERP Application and shall
be responsible for maintaining information about Trainers and Trainees

departments,
projects undertaken,
projects list,
warnings,
Performance record,
evaluation reports,
administration,
work changes and several ad hoc reports,
Batch records.


The major advantage of the proposed system are :

Its online, so that information is available anytime.
High integrity and security.
Ability to incorporate newly available data.
It is user friendly
Speed and accuracy is increased
Fully automated.
Security is associated with user authentication
Duplication of information is curbed.
Change in technology used.


All these above mentioned features will make sure that this application will be
highly interactive and a solid combination of secure and reliable interface which
indeed is the core of a good application. Thus the kind of system integration that
is the core idea of enterprise resource planning system is explored in above
mentioned configuration module.
19


1.4. Methodology/ Planning of work



1.4.1 User Class and Characteristics:

There are 3 types of user for this application-

1. Trainee

2. Trainer

3. Administrator







A) Trainees can use the system to view results,attendance record and project
other important news will be updated and there will be a very interactive and
organized way for displaying them and put into ones knowledge.

For Trainees there will be certain amounts of forms which they will have to fill
one of them being the feedback form.


B) Trainer are core users of this application here they will fill in the attendance
records and performance records of the students and that information will further
be viewed by coordinatiors of the program and will automatically be updated to
trainees profile.


C) Administrators can add, edit & delete the studentsrecord and can change any
errors reported to them.





20

1.4.1 MODULE DESCRIPTION

Module Name:- Student Services

Purpose : This module primarily deals with all the services that a Trainee will get which
includes placement information, feedback form that they will fill and in this module they
can share their thoughts and report the problems if they have any(for example: change of
batch).
Scope:-



Student Attandance
Courseware Records
Student Break Form
Training Confermation
Project Completion.
No due Certificate
Final Certificate
Student Notice
Soft Skil Calenderl


Features : List of features required in this module are as below:-

1. Managing Admission: Managing the admission list of all the students that will be
handed to us from training department and assign them a clear status to students
after their fees registration.

2. Training Batch Plan: This TBP data will be hand over to us from admon
department it will list the information of all the trainees their batch timings, batch
schedules, and lab assigned to them.

3. Student Attandance: It will show the records of the attendance information of
students given by training department.

4. Coursware Record: It will comprise the resource allocation of corresponding
course to the student.

5. Training Confirmation: In this we will issue the training confirmation letter to
corresponding college for the student that he/she undergoing training with our
company.

21

6. Project Completion: In this the student have to submit the project completion
form to the corresponding authority so that final training certificate can be allotted
to the student.

7. No Due Certificate: this certificate will be issues to the student before allotting
them their final certificate. If any dues are pending then the certificate will not be
issued.

8. Student Notice: it will display the student notices to inform the student regarding
aany particular activity and also display notice expire status when the notice date
is over.

9. Soft Skill Calender: It will list the session information conducted by the soft skill
mentor.














22





Chapter 2:
FEASIBILITY STUDY





23

FEASIBILITY STUDY

Once scope has been identified, it is reasonable to ask: Can we build software to meet
this scope? Is the project feasible? All too often, software engineers rush past this
questions, only to become mired in a project that is doomed from the onset.

When we are developing the system, we must know the proposed system will be feasible
or i.e. practically implemented or not it may possible the proposed system may not
implemented due to many reasons like it may take long time in development than the
specified time limit. Therefore we must analyze the feasibility of the system.

Feasibility is the analysis of risks, costs & benefits relating to economics, technology &
user operation. There are several types of feasibility depending on the aspect they covers.
Some important feasibilities is as follows:-

(I) Technical Feasibility
(II) Operational Feasibility
III) Economical Feasibility

2.1 TECHNICAL FEASIBILTIY:-

The technically feasibility study basically centers on alternatives for hardware, software
and design approach to determine the functional aspects of system.This project on Online
Examination will be platform independent since it is being coded in JAVA language
(using JSP and SERVLETS).HTML is used to create web pages. MS-Access database
will be used for storing data.Hardware requirements used are compatible with all O.S.
Only authorized person would be able to use the website so it would be secure. The
system can also be expanded as per the needs of requirement specification.

24

BTES ERP SYSTEM can also be easily upgraded as when required; the server used
will be JSP for utilizing AJAX and java scripts. MySQL will be being used for storage
purposes as it is best for Internet application and easy retrieval.
Technically Online Practice Test is feasible as it is quite easy to develop this system
using Java tools. J2EE framework provides sufficient tools which make development of
this system feasible

2.2 OPERATIONAL FEASIBILTY:-

Operational Feasibility is a measure of how people are able to work with system. This type of
feasibility demands if the system will work when developed and installed.Since website is
very user friendly so users will find it comfortable to work on this site.

People are inherently resistant to change and computer has been known to facilitate
changes. An estimate should be made of how strong the user is likely to move towards
the development of computerized system. These are various levels of users in order to
ensure proper authentication and authorization and security of sensitive data of the
organization. This project is feasible as far as operational feasibility is concerned as
candidates are using computers and internet more and more for online tests and getting
their solutions. They dont have to learn any new skill for using this system.

2.3 ECONOMICAL FEASIBILITY

Economic analysis is most frequently used for evaluation of the effectiveness of the
system. More commonly known as cost/benefit analysis the procedure is to determine the
benefit and saving that are expected from a system and compare them with costs, then the
decision is made whether to design and implement the system or not.
This part of feasibility study gives the top management the economic justification for the
new system. This is an important input to the management, because very often the top
management does not like to get confounded by the various technicalities that bound to
25

be associated with a project of this kind. A simple economic analysis that gives the actual
comparison of costs and benefits is much more meaningful in such cases.
In this system, the organization is most satisfied by economic feasibility. Because, if the
organization implements this system, it need not require any additional hardware
resources as well as it will be saving lot of time. Only costs involved will be for
development of the system and in purchasing the domain name. No other cost will be
incurred as this is an online system every thing is online, no extra hardware, software or
any other resource need to be deployed for running this system. Thus the proposed
system is economically feasible













26




Chapter 3:

SOFTWARE
REQUIREMENT
SPECIFICATION











27

SOFTWERE REQUIREMENTS
SPECIFICATIONS

The requirement Analysis and Specification phase is undertaken because BTES ERP
SYSTEM feasibility study phase is complete and this project is technically and
financially feasible for the Majesty Group. After completion of analysis, the analyst has a
firm understanding of what is to be done.
This phase consists of two things i.e.
Requirement Analysis
Requirement Specification

3.1 SYSTEM REQUIREMENTS
System Configuration

H/w Requirement

Resources Minimum Hardware
Requirement


Recommended Hardware
Requirement

Processor Intel P3, AMD dual core Intel Dual Core(or equivalent)
RAM 512 MB 1GB
Space Required 100 MB(on the installation
drive)
1 GB(on the installation drive)
Display 16 bit color 32 bit color(Recommended)

3.2 Software Specification:

Operating System Windows Xp,Windows 7,Windows
8,8.1,OSx 9.0(and above)

Application Server Tomcat 5.0, Glassfish
(Tomcat is the most popular and abstract
server thats been used since java 1.0).
28


Front End HTML, Java Server Pages
Scripts JavaScript
Server side Script Java Server Pages
Database Mysql
Database Connectivity JDBC,ODBC

3.2 REQUIREMENT ANALYSIS
It involves obtaining a clear and thorough understanding of the product to be developed
i.e. what is the problem? Why is it important to solve the problem? What are the
solutions? Etc.

It includes two things:-
Requirement Gathering:
In the Requirement Gathering we take the interviews of end-users and customers to
collect all possible requirements regarding the BTES ERP SYSTEM .After that the
Questionnaires are used to get the requirements for the ERP System which are as follows:
o This system should provide an integrated portal to access all the modules
associated with the system.
o Only authorized user should be allowed to access the system and make
easy retrieval of data.
o Only authorized user of specific module should be able to update the
crucial data.
o if any kind of enhancement is needed in one module that should not affect
the other modules.
o The system should be user friendly not complex in use
o The new system should provide the easy way to provide good
coordination among various modules.
o The system should be efficient and fast.

Analysis of Gathered Requirements:
29

The main purpose of analysis of the collected information is to clearly
understand the exact requirements of the clients and resolve anomalies, conflicts,
and inconsistencies in the gathered requirements.
1. The system will give the appropriate error message if wrong input is provided by
the user.
2. The system will provide the information about the volume for which call have
been made.
3. The system will provide role base security.
4. The unique login_id should be assigned to each user.
5. The system will be easy to use.

3.3 REQUIREMENT SPECIFICATION:

It includes SRS document i.e. Software Requirement Specification.
An SRS document should clearly include the following:
Functional requirements of the system
Non functional requirements of the system

Functional Requirements of System
The system is basically a web based application thus it should be secure and only
authorized user access should be allowed to access it.
Following functionality is developed in the system in which user:
Managing admission task
Maintaining training batch plan.
Showing BAF(Batch Allocation Form)
Showing courseware details.
Showing Studednt Break form and updating them.
Generating the undertaking for training confermation
30

Project completion certificate.
Issue of No Due Certificate to students and update them.
Issue of final certificate.
Display the notice for students and maintain the record of previous notices.



Non-functional requirements
This includes the characteristics that can not be expressed such as maintainability,
usability, security etc.
1. Portability: The system is portable as it can be easily made to work with
different operating systems and in different machines because JSP and
Servelets technology is being used.
2. Usability: The different category of users can easily invoke the functions of
the project because links are provided for the guidance, terms and conditions,
provided on the home page.
3. Maintainability: At any time when information is to be updated, previous
information is also shown so that updations can be done easily and new
functions can also be easily added.
4. Security: The system is safe to use and provides reliable information
regarding tests at various level and only authorized user can view the detail. If
an unauthorized user tries to access the application, an error message with
wrong name and user id would appear.
5. Interfaces: GUI based interface with user


31













Chapter 4:
DESIGNING









32


DESIGNING PHYSICAL & LOGICAL
Introduction
Designing aim to identify the modules that should be in the system, the
specification of these modules and how they interact with each other to produce
the desired result.System design provides the understandings and procedural
details necessary for implementing the system recommended in the system study.
Designing has two phases:-
Logical Design
Physical Design.
4.1 Logical and Output Design:
The logical design of an information system is analogous to an engineering blue
print of an automobile. It shows the major features and how they are related to
one another. The detailed specification for the new system was drawn on the
bases of users requirement data. The outputs inputs and databases are designed in
this phase.
4.2 Input Design:
The input design is the link that ties the information system into the users world.
Input specifications describe the manner in which data enters the system for
processing. Input design features can ensure the reliability of the system and
produce results from accurate data, or they can result in the production of
erroneous information.

33

4.3 Data Flow Diagram:
Data Flow Diagramming is a means of representing a system at any level of detail
with a graphic network of symbols showing data flows, data stores, data
processes, and data sources/destination.

Terms used in DFD

Process:A process transforms data values. The lowest level processes are pure
functions without side effects. An entire data flow graphics high-level process.




Data flows:A data flow connects the output of an object or process to input of
another object or process. It represents the intermediate data value within a
computation. It is represented by an arrow and labeled with a description of
data, usually its name or type.





Actors: An actor is active object that drives the data flow graph by producing
or consuming values.
Data store:A data store is a passive object with in a data flow diagram that
stores data for later access.



External Entity: A rectangle represents an external entity such as a librarian, a
library member.
Graphical Representation:



Graphical Representation:


Graphical Representation:

34


Graphical Representation:

35









Output Symbol: This box represented data production during human computer
Interaction









Graphical Representation:

36

4.3.1 DFD OF ERP SYSTEM

(i) Users

FIGURE : 7.3.1.1






37

(II) Users Abstract


FIGURE : 7.3.1.1












38


4.3.2 LOGIN FORM


FIGURE 7.3.2.1

Admin and User enter the username and password and system verify username and
password if the username and password is incorrect the system generate message
username & password is invalid
39

4.3.3 MODULE DFD
FIGURE : 7.3.3.1
40

4.4 GANTT CHART

A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts
illustrate the start and finish dates of the terminal elements and summary elements of a
project. Terminal elements and summary elements comprise the work breakdown
structure of the project. Some Gantt charts also show the dependency (i.e. precedence
network) relationships between activities. Gantt charts can be used to show current
schedule status using percent-complete shadings and a vertical "TODAY" line
Advantages and limitations:
Gantt charts have become a common technique for representing the phases and
activities of a project work breakdown structure (WBS), so they can be
understood by a wide audience.
Gantt chart is useful and valuable for small projects that fit on a single sheet or
screen; they can become quite unwieldy for projects with more than about 30
activities.
Gantt charts do not represent the size of a project.
The horizontal bars of a Gantt chart have a fixed height, they can misrepresent the
time-phased workload (resource requirements) of a project
41

.



PERT CHART

A PERT chart is a graphic representation of a projects schedule, showing the sequence
of tasks, which tasks can be performed simultaneously, and the critical path of tasks that
must be completed on time in order for the project to meet its completion deadline. The
chart can be constructed with a variety of attributes, such as earliest and latest start dates
for each task, earliest and latest finish dates for each task, and slack time between tasks.
A PERT chart can document an entire project or a key phase of a project. The chart
allows a team to avoid unrealistic timetables and schedule expectations, to help identify
and shorten tasks that are bottlenecks, and to focus attention on most critical tasks.

When to use it:
Because it is primarily a project-management tools, a PERT chart is most useful for
planning and tracking entire projects or for scheduling and tracking the implementation
phase of a planning or improvement effort.

42

How to use it:
Identify all tasks or project components.
Identify the first task that must be completed.
Identify any other tasks that can be started simultaneously with task #1
Identify the next task that must be completed.
Identify any other tasks that can be started simultaneously with task #2







Overview of COCOMO
The COCOMO cost estimation model is used by thousands of software project managers,
and is based on a study of hundreds of software projects. Unlike other cost estimation
models, COCOMO is an open model, so all of the details are published, including:
The underlying cost estimation equations
Every assumption made in the model (e.g. "the project will enjoy good
management")
Every definition (e.g. the precise definition of the Product Design phase of a
project)
The costs included in an estimate are explicitly stated (e.g. project managers are
included, secretaries aren't)
43

Because COCOMO is well defined, and because it doesn't rely upon proprietary
estimation algorithms, Costar offers these advantages to its users:
COCOMO estimates are more objective and repeatable than estimates made by
methods relying on proprietary models
COCOMO can be calibrated to reflect your software development environment,
and to produce more accurate estimates
The most fundamental calculation in the COCOMO model is the use of the Effort
Equation to estimate the number of Person-Months required to develop a project. Most of
the other COCOMO results, including the estimates for Requirements and Maintenance,
are derived from this quantity.
Source Lines of Code
The COCOMO calculations are based on your estimates of a project's size in Source
Lines of Code (SLOC). SLOC is defined such that:
Only Source lines that are DELIVERED as part of the product are included -- test
drivers and other support software is excluded
SOURCE lines are created by the project staff -- code created by applications
generators is excluded
One SLOC is one logical line of code
Declarations are counted as SLOC
Comments are not counted as SLOC
The original COCOMO 81 model was defined in terms of Delivered Source Instructions,
which are very similar to SLOC. The major difference between DSI and SLOC is that a
single Source Line of Code may be several physical lines. For example, an "if-then-else"
statement would be counted as one SLOC, but might be counted as several DSI.


44







Chapter 5:
SCRIPT LANGUAGES USED












45

ABOUT SOFTWARE LANGUAGES

5.1 Introduction
Technology and tools are strongly related to the approach of software development.
While selection of a particular methodology may imply use of certain tools, the tools
themselves often leave significant room for developers to choose how to use them.
The selection has therefore been based mainly on the objective of the project, while
the methodologies were selected after the tools were selected, due to the fact that
technologies and tools poses certain restrictions of how development can be done.
Technologies
Given the challenges a developer faces, he also has to decide which key technologies
and products and architectural platform to use in order to meet these challenges. The
problem is there are simply too many of them and it is hard to come up with your own
architecture or framework where everything is in a well integrated and cohesive
form..
5.1.1 Technologies Used
JAVA TM 2 Platform
Java server pages technology (JSP)
Java database connectivity (JDBC)
MYSQL(as back end)
Microsoft windows(as operating system)






46


5.2 JAVA SERVER PAGES (JSP) TECHNOLOGY
JSP gives an ideal platform for creating web application easily and quickly. There
are various features supported by JSP which makes this possible. JSP provides an
attractive alternative to other dynamic scripting languages. These features are
described below.
1. Platform and server Independence:
The JSP technology follows the Write Once, Run Anywhere. Rule which is the
basis of the Java language. JSP technology can run on various web servers
including Apache, J2EE, Web logic etc.
2. Environment:
JSP uses pure Java and takes full advantages of its objects-oriented nature. JSP
technology lets you separates contents generation from layout by accessing
components from the page. JSP provides components based on JavaBeans
technology or JSP tags.
3. Reusability across platforms:
The JSP pages components like Enterprise JavaBeans, JavaBeans or custom JSP
tags which are usable. This gives the JSP reusability capabilities. These reusable
components help the pages to keep simple and run faster.
4. Ease of Administration:
The use of JSP eliminates the need for high-level technical expertise, thereby
helping web developers, designers, content creators, and content managers to
work together and develop java applications in less time and with less effort
47

5. Ease of Use:
All JSP applications run on major web servers and operating systems, including
Microsoft IIS, Netscape Enterprise Server, and Apache Web Servers.
5.2.1 JSP ARCHTECTURE
JSPs are built on top of Suns servlet technology. JSPs are essential an HTML page
with special JSP tags embedded. These JSP tags can contain Java code. The JSP file
extension is .jsp rather than .htm or .html. The JSP engine parses the .jsp and creates a
Java servlet source file. It then compiles the source file into a class file; this is done
for the first time and this why the JSP is probably slower the first time it is accessed.
Any time after this the special compiled servlet is executed and is therefore returns
FIGURE 8.2.1.1


48

5.3 Introduction to JSP Tags
In JSP tags can be divided into 4 different types. These are:
5.3.1Directives
In the directives we can import packages, define error handling pages or the
session information of the JSP page.JSP directives are always enclosed within the
two primary directives are

Page
Include
Page Directive


Include Directive
This directive can be used to include the contents of the indicated file at any
location within the JSP page


5.3.2Declarations
This tag is used for defining the functions and variables to be used in the JSP.

<%@ %>
<% @ page attributes %>
attributeslanguage, import

<%@ include file =filename.html %>

<%!.%>
49

5.3.3Scriplets
In this tag we can insert any amount of valid java code and these codes are placed
in jspService () method by the JSP engine.



5.3.4Expressions
We can use this tag to output any data on the generated page. These data are automatically
converted to string and printed on the output stream.


5.3.5 Hyper Text Mark-Up Language (HTML)
HTML = Hypertext Mark-up Language.
Universal, non-proprietary, structured, text mark-up language.
Used to publish documents on the World Wide Web.
Used to define the structure of documents and links between documents.
An application of Standard Generalized Mark-up Language.
SGML is a meta-language, used to describe a mark-up language.
Latest SGML-based version of HTML is 4.01 that supports
Scripting.
Accessibility.



<%
//java codes
%>

<%="Any thing" %>

50










Chapter 6:
DATABASES







51

DATABASES

6.1 ADMISSION1

Field Type Null Key Default Extra
regid varchar (45) NO PRI
sec_school varchar (45) YES NULL
inquiryid varchar (45) YES NULL
yearofpass varchar (45) YES NULL
admission_date varchar (45) YES NULL
perc1 varchar (45) YES NULL
course_duration varchar (45) YES NULL
ssecpass_yr varchar (45) YES NULL
Fee varchar (45) YES NULL
ssec_school varchar (45) YES NULL
dis_type varchar (45) YES NULL
yrofpass varchar (45) YES NULL
fafter_dis varchar (45) YES NULL
perc2 varchar (45) YES NULL
final_fee varchar (45) YES NULL
degpass_year varchar (45) YES NULL
fname varchar (45) YES NULL
coll_name varchar (45) YES NULL
lname varchar (45) YES NULL
yearof_pass varchar (45) YES NULL
perc3 varchar (45) YES NULL
father_occ varchar (45) YES NULL
employer_name varchar (45) YES NULL
dob varchar (45) YES NULL
52

job_duration varchar (45) YES NULL
gender varchar (45) YES NULL
job_desc varchar (45) YES NULL
nationality varchar (45) YES NULL
course_name varchar (45) YES NULL
per_add varchar (45) YES NULL
temp_add varchar (45) YES NULL
email varchar (45) YES NULL
sec_pass_year varchar (45) YES NULL



6.2 CNTABLE

Field Type Null Key Default Extra
refno Varchar(45) NO PRI auto_increment
dt date NO NULL
toarea Varchar(45) NO NULL
tf4 Varchar(45) NO NULL
tf5 Varchar(45) NO NULL
tf6 Varchar(45) NO NULL
tf7 Varchar(45) NO NULL
tf8 Varchar(45) NO NULL
tf9 Varchar(45) NO NULL
tf10 Varchar(45) NO NULL
tf11 Varchar(45) NO NULL
tf12 Varchar(45) NO NULL



53



6.3 FEEPAYMENT
















6.4 NODUETABLE

Field Type Null Key Default Extra
stid varchar(45) NO PRI NULL
regid varchar(45) NO PRI NULL
name varchar(45) NO NULL
course varchar(45) NO NULL
duration varchar(45) NO NULL
grade varchar(45) NO NULL
fdc varchar(45) NO NULL
ldc varchar(45) NO NULL
Field Type Null Key Default Extra
receiptno Integer(5) NO PRI NULL auto_increment
name varchar(45) NO NULL
regid varchar(45) NO NULL
course_name varchar(45) NO NULL
fee varchar(45) NO NULL
dt varchar(45) NO NULL
fee_amount varchar(45) NO NULL
duedt varchar(45) NO NULL
stus varchar(45) NO NULL
stsign varchar(45) NO NULL
offsign varchar(45) NO NULL
remark varchar(45) NO NULL
54

lfr varchar(45) NO NULL
cert varchar(45) NO NULL
issby varchar(45) NO NULL
appby varchar(45) NO NULL
issdt date NO NULL

Table : 4 SUBJECTINFO


6.5 NOTICETABLE

Field Type Null Key Default Extra
notno int (11) NO PRI NULL auto_increment
by varchar(45) YES NULL
dept varchar(45) YES NULL
msg varchar(45) YES NULL
dt date YES NULL

Table : 5 TESTINFO

6.6 VIEWATT

Field Type Null Key Default Extra
id int (11) NO PRI NULL auto_increment
name varchar(45) YES NULL
date varchar(45) YES NULL
attendence varchar(45) YES NULL



55


6.7 BREAKTABLE

Field Type Null Key Default Extra
fno Integer(5) NO PRI
f1 varchar (45) NO NULL
f2 varchar (45) NO NULL
f3 varchar (45) NO NULL
batchcode varchar (45) NO NULL
f5 varchar (45) NO NULL
f6 varchar (45) NO NULL
df varchar (45) NO NULL
dt varchar (45) NO NULL
f9 varchar (45) NO NULL
f10 varchar (45) NO NULL
f11 varchar (45) NO NULL
f12 varchar (45) NO NULL
f13 varchar (45) NO NULL
f14 varchar (45) NO NULL
f15 varchar (45) NO NULL
f16 varchar (45) NO NULL
f17 varchar (45) NO NULL
tec varchar (45) NO NULL


56






Chapter 7:
SNAPSHOTS








57

7.1 MODULE PAGE


FIGURE : 7.1

LIST OF ALL THE MODULES THAT WE STUDENT SERVICE
DEPARTMENT SHOULD HANDLE


58

7.2 MANAGE ADDMISSION


FIGURE : 7.2.1

THIS LINK WILL MANAGE ADMISSION OF ALL THE STUDENTS THAT
MARKETING DEPARTMENT WILL GIVE TO US. WE WILL ASSIGN THEM
ADDMISSION ID .WE CAN ALSO SEE THE ADMISSION LIST IN VIEW
ADMISSION LINK


59


FIGURE : 7.2.2


WE CAN SELECT THE VARIOUS DEPARTMENTS TO SEE THE LIST
ALLOTED TO US BY MARKETING DEPARTMENT .OBSERVE CAREFULLY
WE HAVE ASSIGNED STATUS=0 TO THESE STUDENTS BECAUSE THEY
HAVE NOT SUBMITTED THE FEES YET.ONCE THEY SUBMIT THE FEES
THEY ARE REGISTERED. WE CAN VIEW THE LIST OF STUDENTS WHO
GOT ADMISSION BY THE SIDE LINK.










60

7.3 TRAINING BATCH PLAN


FIGURE : 7.3.1

THIS WILL TELL THE DETAILS OF ALL THE TRAINERS IN TRAINING
DEPARTMENT .THIS DATA WILL BE GIVEN TO US BY TRAINING
DEPARTMENT












61

7.4 COURSE WARE RECORDS


FIGURE : 7.4.1


FIGURE : 7.4.2

62

IT WILL GIVE THE INFORMATION ABOUT ALL THE TRAINERS THAT
WHICH TRAINER IS ASSIGNED WHICH LAB. WHAT ARE THERE BATCH
CODE .WHAT ARE THERE BATCH TIMINGS ETC. AND BESIDE INSERING
A NEW RECORD ,AS WE CAN SEE IN THE SIDE LINK WE CAN ALSO VIEW
OR UPDATE ALL THIS INFORMATION.





7.5 STUDENT BREAK FORM


FIGURE : 7.5.1

THIS FORM IS FOR STUDENT LEAVE.THERE ARE TWO SUB FORMS IN IT
.ONE IS REGARDING GROUP LEAVE FORM .AND ONE IS REGARDING
INDIVIDUAL LEAVE FORM. FOLLOWING TWO SNAPSHOTS WILL SHOW
YOU BOTH THE FORM.
63



FIGURE : 7.5.2


THIS IS BATCH BREAK FORM . WHICH IS FILLED FROM THE STUDENTS
WHEN COMPLETE BATCH IS ON LEAVE.BY SIDE LINK WE CAN ALSO
SEE PREVIOUSLY FILLED BATCH BREAK FORM STORED IN OUR
DATABASE.











64



INDIVIDUAL BREAK FORM


FIGURE : 7.5.3


THIS IS INDIVIDUAL LEAVE FORM.IT IS FILLED BY
INDIVIDUAL STUDENT WHENEVER HE OR SHE WANTS
LEAVE.







65



VIEW TEST INFORMATION VIA USER
WE CAN ALSO VIEW THE FORM RESIDING IN OUR DATABASE.



FIGURE : 7.5.4


66


FIGURE : 7.5.5
















67


10.6 TRAINING CONFERMATION




FIGURE 7.6.1


THIS LETTER IS AN UNDERTAKING FOR THE STUDENT COLLEGE THE
MENTIONED STUDENT IS UNDERGOING THE TRAINING IN OUR
INSTITUTE.WE CAN ALSO SEE PREVIOUSLY STORED TRAING
CONFERMATION LETTERS IN OUR DATABASE.

68


FIGURE 7.6.2



PREVIOUSLY FILLED TRAINING CONFERMATION LETTERS STORED IN
DATABASE VIEWED BY SIDE LINK .














69



7.7 NO DUE CERTIFICATE


FIGURE : 7.7.1


THIS CERTIFICATE IS FILLED BY STUDENT BEFORE TAKING THE
TRAINING CERTIFICATE . IF THERE IS ANY DUE PENDING,THE STUDENT
MUST FILL THAT DUE AND THEN APPLY FOR THE CERTIFICATE. AND
ALSO BY CLICKING SIDE LINKS WE CAN SEE THE PREVIOUSLY FILLED
NO DUE CERTIFICATES.




70






7.8 STUDENT NOTICE





FIGURE : 7.8.1



THIS IS NOTICE FOR ALL THE STUDENT. THIS IS ISSUED FOR WORKING
TILL A PERTICULER DATE.TILL DATE NOTICE REMAIN LIVE AND
AFTER THAT IT AUTOMATICALLY GETS DELETED. WHICH WILL BE
SHOWN IN FOLLOWING FIGURE.

71







FIGURE : 7.8.2













72


7.9 TRAINING CERTIFICATE



FIGURE : 7.9.1


ISSUED AFTER THE SUCCEFUL COMPLETION OF TRAINING.




73












Chapter 8:
TESTING








74

SYSTEM TESTING
During system testing, the system is used experimentally to ensure that the
software does not fail i.e. it will run accordingly to specifications and in the way
users expects. Special test data are input for the processing and the result
examined. A limited number of users may be allowed to use the system so that
analyst can see whether they use it in unforeseen ways. It is preferable to discover
any surprise before the organisation implements the systems and encounters them
later on. This type of testing which allows only a few, selected users to work on
the system is known as beta testing. On the other hand the testing done by the
developer(s), they are known as alpha testing.
8.1 Objective of testing
Testing is vital to the success of a system. Testing is done at different stages
within the development phase. System testing makes a logical assumption that if
all parts of the system are correct, the goals will be successfully achieved.
Inadequate testing leads to errors that may not appear until months later when
correction will be extremely difficult. Another objective of testing its utility as
user oriented vehicle before implementation.
8.2 Testing Procedure: Following testing procedures were used:-
8.2.1 Unit testing
Unit testing is the testing of a single program module in an isolated environment.
The testing of the processing procedure is the main focus. In this, regard, the
entire module was separately tested first as isolated and complete entities. This
help a lot in discovering problems related to single module and rectifying them in
the context of the module itself, rather than considering module-related problems
in a global context.
75


8.2.2 Integration Testing
Integration testing is the process of the testing the interfaces among system
modules, such testing ensure that data moves between systems are intended. In the
regard of integration testing, it was seen that all the data was expected to be the
output of a particular module was obtained in the correct format, so that the next
module could accept it appropriately. This could be done
Either after the entire system was developed, or in stages after more than one
module was developed.
8.2.3 Subsystem Testing
In this many unit-tested modules are combined into subsystems, which are then
tested again. The goal here was to see that if the modules can be integrated
properly.
8.2.4 System Tesing
System testing is the testing of the system against its initial objectives. Such
testing is done either in a simulated environment or in a live environment.In the
case system, which I developed, the testing was done in a pseudo- real
environment..
All the above types of testing were carried out and various extreme cases were
also introduced to check for whether the system responded as expected. The
various forms, database packages, procedures, functions, modules and the events
were tested to discover.
They behaved in the manner expected of them and gave the accurate results.
However, the factor, which helped most in the modification and rectification of
the system, was the user response. The user after using the system would
76

invariable come up with some idea to improve the system. Such ideas, if feasible
were incorporated into the system. Thus leading to an improvement in the overall
efficiency of the system

8.3 MAINTAINANCE
Maintenance of a typical software product requires much more effort than the
effort necessary to develop the product itself. Many studies carried out in the past
conform this and indicate that the relative effort of development of the typical
software product to its maintenance effort is roughly in the 40:60 ratios.
8.3.1 Maintenance is generally of three types:
1. Corrective maintenance.
2. Adaptive maintenance.
3. Perfective maintenance.
Corrective maintenance:
Corrective maintenance means repairing processing or performance failures or
making changes because of previously uncorrected problems or false assumptions.
Adaptive maintenance:
Adaptive maintenance means changing the program function according to new
enhancement in surroundings like make it flexible on new operating system
Perfective maintenance:
Perfective maintenance means enhancing the performance or modifying the
program(s) to respond to the users additional or changing need

77








CONCLUSION















78







An organization that has no ERP will be running on many kinds of
software that do not allow interaction. Customization also may be difficult
it in some cases. This will negatively affect the optimized functioning of
organization's business activities.
The organization will be facing hardship in many areas of its functions.
The engineering design of the software will be needed in order to improve
the product, and to follow the client's behavior and choices since the first
contact is quite important. Administration of the different receipts
interdependence will be very complex, such as invoices regarding
materials purchases, general expenditures or salaries.
All of these things change when an ERP system is implemented.
Information flows constantly and allows you to follow a client's processes
at any moment, no matter which part of the process they are going
through. Purchases and expenditures are registered in a centralized
database which allows you to have close control over these activities. In
this regard ERP helps you to prevent possible abuse.
A powerfully integrated ERP system enables interactions of marketing,
sales, quality control, products processes, supply lines, stocks and many
other areas and it can be in a single database. This will eliminate the
occasional loss of and retyping errors. It integrates all departments and
functions across a company in a single computer system that is able to
serve all those different department's particular needs.
An ERP system also automates business processes by placing them into a
useful format that is standardized and common for the whole organization.
Moreover it could even be used between their suppliers and customers.



79






BIBLIOGRAPHY















80










BIBLIOGRAPHY
WEBSITES
http://www.java2s .com
http://msdn.microsoft.com
http://w3schools.com

BOOKS
SQL Book by Evan
JSP and Servlets by Head First
JAVA Book by Herbert Schildt