How to Troubleshoot Apps for the Modern Connected Worker
Project report college information management system on Advanced Java
1. Project Report
On
College Information Management System
Submitted for partial fulfillment of the requirement
for the award of the degree of
Bachelor of Technology
In
Computer Science and Engineering
Kashi Institute of Technology
Mirzamurad, Varanasi
AKTU Lucknow
Submitted by:
Rishabh Kumar
Mukesh Kumar Vishwakarma
Under the guidance of
Mr. Anand Prasad
2. ii
Declaration
We hereby declare that this submission is our own work and that, to the
best of our knowledge and belief, it contains no material previously
published or written by any other person nor material which to a
substantial extent has been accepted for the award of any other degree
or other institution of higher learning, except where due
acknowledgement has been made in the text.
................. …………............. .....................
Signature HOD (computer
Science and
Engineering)
External Examiner
3. iii
Certificate
This is to certify that Project Report entitled as “College Information
Management System” submitted by Rishabh Kumar, Mukesh Kumar
Vishwakarma in partial fulfillment of the requirement for the award of
degree B.Tech in department of Computer Science and Engineering of
Abdul Kalam Technical University, is a record of the candidates own
work carried out by them under my supervision. The matter embodied
in this report is original and not has been submitted for the award of any
other college.
Supervisor Date:
Mr. Anand Prasad
Department of Computer Science and
Engineering
Kashi Institute Of Technology, Varanasi
Uttar Pradesh
India
../../..17
4. iv
Acknowledgement
It gives us a great sense of pleasure to present the report of the B.Tech
Project undertaken during B.Tech Final Year. We own special debt of
gratitude to Mr. Anand Prasad, Department of Computer Science &
Engineering, Kashi Institute of Technology, Mirzamurad Varanasi, for his
constant support and guidance throughout the course of our work. His
sincerity, thoroughness and perseverance have been a constant source
of inspiration for us. It is only his cognizant efforts that our endeavors
have seen light of day.
We also take the opportunity to acknowledge the contribution of Mr.
Anand Prasad of Department of Computer Science & Engineering, Kashi
Institute of Technology, Mirzamurad, for his full support and assistance
during the development of the project.
We also do not like to miss the opportunity to acknowledge the
contribution of all faculty members of the department for their kind
assistance and cooperation during the development of our project. And
at last but not the least, we acknowledge our friends for their
contribution in the completion of the project.
Student
Rishabh Kumar
(1342810081)
Mukesh Kumar Vishwakarma
(1342810055)
5. v
Table of Contents
Declaration ii
Certificate iii
Acknowledgement Iv
Table of contents v
1. Introduction vi
1.1 Introduction vii
1.2 Purpose viii
1.3 Scope viii
1.4 Technologies viii
2. Basic Concept and description ix
2.1 Product Perspective x
2.2 Functions x
2.3 Characteristics xi
2.4 Constraints xii
2.6 Use Case Model xii
2.6.1 Admin xiii
2.6.2 Faculty xiii
2.6.3 Student xiii
2.7 Assumptions and Dependencies xiv
6. vi
3. Requirements xv
3.1 Specific Functions xv
3.2 Functional Requirements xxvi
3.2 Non-Functional Requirements xxvi
4. Design xxvii
4.1 Objectives xxvii
4.2 System Architecture xxvii
4.3 Data design xxviii
4.4 Functional Design xxix
5. Technological Description xxx
5.1 HTML xxx
5.2 CSS xxxi
5.3 JAVASCRIPT xxxi
5.4 MySQL xxxi
5.4 J2EE xxxii
5.6 BOOTSTRAP xxxii
6. Project Description xxxiii
7. Scope lxix
7. vii
1
Introduction
1.1 Introduction
The objective of College Information Management System is to allow the administrator
of any organization to edit and find out the personal details of a student and allows the
student to keep up to date his profile .It’ll also facilitate keeping all the records of
students, such as their id, name, mailing address, phone number, DOB etc. So all the
information about a student will be available in a few seconds. Overall, it’ll make
Student Information an easier job for the administrator and the student of any
organization. The main purpose of this project is to illustrate the requirements of the
project College Information Management System and is intended to help any
organization to maintain and manage personal data.
It is a comprehensive project developed from the ground up to full fill the needs of
colleges as they guide their students. This education edge integrated information
management system connects daily operations in the college environment ranging from
registration to finance, faculty, and library. This reduces data error and ensures that
information is always up-to-date throughout the college.
It provides a single source of data repository for streamlining your business processes
and for all reporting purposes.
It has a simple user interface and is intuitive. This insures that the users spend less time
in learning the system and hence, increase their productivity. Efficient security features
provide data privacy and hence; increase their productivity.
8. viii
1.2 Purpose
The purpose of College Information Management System is to allow the administrator of any
organization to edit and find out the personal details of a student and allows the student to
keep up to date his profile .It’ll also facilitate keeping all the records of students, such as their
id, name, mailing address, phone number, DOB etc. So all the information about a student will
be available in a few seconds.
Overall, it’ll make Student Information Management an easier job for the administrator and the
student of any organization.
The main purpose of this SRS document is to illustrate the requirements of the project College
Information Management System and is intended to help any organization to maintain and
manage its student’s personal data.
The main purpose of the project College Information Management System, is to reduce the
consumption of time during maintaining the records of college. Separate logins are provide to
maintain the records of teachers, students, and admin.
1.3 Scope
The CIMS will permit process impact gathering information about students from admission cell
and give it to staff. And another very important impact is taking classes, conducting exams,
maintaining fee details and examination etc., this is important features of college information
system.
1.4 Technologies
HTML (Hyper Text Markup Language)
CSS (Cascading Style Sheet)
BOOTSTRAP
Advanced Java (JSP)
JAVASCRIPT
MySQL
9. ix
2
Basic Concept and Definitions
2.1 Product Perspective
The CIMS is a system that can help to maintaining student and staff information easily
and it will maintain the student records, library, schedules, important events and many other
important information related to college management.
The website is aimed towards recording a considerable number of student records and need
assistance for managing their data. Website is user-friendly, quick to learn and reliable.
CIMS is a stand-alone product and doesn’t depend upon the availability of any other websites.
The system will have an administrator who has full-fledged rights with regards to performing all
actions related to control and management of the website and all relevant data.
2.2 Functions
There are three different users who will be using this product:
Admin who can view and edit the details of any students.
Faculty who can view their schedules, library, their profile information
as well as they can edit their information
Students who can view their details, library, course material, as well as
they can edit their information.
10. x
The features that are available to administrator are:
An administrator can login into the system and perform any of the
available operations
˗ can delete user
˗ can accept/decline user registration request
˗ can edit user information records into database
˗ can access all details
The features that are available to faculty are:
An faculty can login into the system and perform any of the
available operations
˗ can view his/her information
˗ can edit their details
˗ can access library records
˗ can view their schedule
The features that are available to faculty are:
An student can login into the system and perform any of the
available operations
˗ can view his/her information
˗ can edit their details
˗ can access library records
˗ can view their course detail and related material
2.3 Characteristics
User should be aware of internet.
11. xi
User should have a valid login ID and password.
Admin, faculty and student can access
Guest user send their registration request
2.4 Constraints
Every user must be comfortable using computer
All operations are in English so user must have basic knowledge of
English.
2.6 USE CASE MODEL :
12. xii
2.6.1 ADMIN
Responsible for managing user records.
Login into the website
Update the information
Accept/Decline user request
View user details
2.6.2 FACULTY
Rights to view and edit their personal details.
Login into the website
View their details
Edit their details
View schedule information
2.6.3 STUDENTS
Rights to view and edit their personal details.
Login into the website
Edit their details
View their details
View course details
13. xiii
2.7 Assumptions & dependencies
Administrator is created in the system already.
Roles and tasks are predefined.
Guest’s users can view college details.
Guest can send application request.
14. xiv
3
Requirements
7.1 Specific Functions
Administrator: Responsible for managing student details.
Use-case: Login into the website
Goal: Gain access into the website
Brief: This use case is when the administrator wants to access
the website to accept/decline/update details of the student.
Perquisites: The admin must be logged onto the website in
order for this se case to begin.
Basic Flow:
The application asks the admin for the username and password
The administrator enter his/her details.
15. xv
The website validates and then verifies the details and send it to
admin page.
The administrator now given access to the website to perform their
tasks.
Alternative Flow:
The administrator enters invalidate username and password,
then not allowed to do any operations.
Use-case: Display user details
Goal: View user details
16. xvi
Brief: This use case is when the administrator wants to view the
personal details of users that are already existing in the database.
Perquisites:
The admin must be logged onto the website in order for this se case
to begin.
The details of the users must pre-exist in the database.
The student id must be entered correctly.
Basic Flow:
The administrator logs onto the system.
The administrator search the user by
o Email
o Name
The system view the user detail.
Alternative Flow:
User not found
17. xvii
If in the display, a user with the specific Id does not exist, system
generates an error message. The administrator can then enter a different Id or
cancel the operation, when error occurred.
Use-case: Edit user details
Goal: Edit the details of user
18. xviii
Brief: This use case is when the administrator wants to edit the
personal details of users that are already existing in the database.
Perquisites:
The admin must be logged onto the website in order for this se case
to begin.
The details of the users must pre-exist in the database.
Basic Flow:
The administrator logs onto the system.
The administrator edit the user details
o Email
o First Name/Last name
o DOB
o Qualification
o City
o Contact No
o Address
The website updates the database according to the edited details.
19. xix
Alternative Flow:
No alternative flow for this use case.
User: Student
Use-case: user registration
Goal: Registration of user
Brief: This use case is when the user send registration request
himself/herself in the database online.
20. xx
Perquisites:
The student must access the website in order for this
use case to start.
The input must be entered correctly.
Basic Flow:
The student enters into the website.
The student fill his/her details from the following:
o Email
o Password
o First name/Last name
o Gender
o DOB
o Contact No
o Qualification
o Address
Alternative Flow:
Validates all the user
22. xxii
Brief: This use case is when the user wants to access the
website.
Perquisites:
The student must access the website in order for this
use case to start.
User input valid credentials.
Basic Flow:
The website prompt user for details.
The user enters the username and password.
The websites verifies the password.
The user is given access to the website to form his tasks.
Alternative Flow:
The student enters invalid credentials then he will not be
allowed to enter the website.
23. xxiii
Use-case: Edit user registration
Goal: details of user registration
Brief: This use case is when the user wants to edit their details of
himself/herself already existing in the database.
Perquisites:
The user must be logged into the system in order for
this use case to start
The details of the user must pre-exist into the database.
The user must be enabled by administrator.
24. xxiv
Basic Flow:
The user logs onto the system.
The user can edit the following keys:
o Address
o Contact No
o DOB
o Qualification
Alternative Flow:
There is no alternative for this diagram.
25. xxv
3.2 Functional Requirements
The Administrator will be given more powers (accept/decline/update) than
other users.
It ensures that the information entered is of correct format. For example
name field cannot contain numbers. In case if incorrect information is given,
the user will be asked to fill the information again.
The applications can be accessed any time.
3.3 Non-Functional Requirements
The database may get crashed at any certain time due to virus of
operating system failure. Therefore, it is required to take the database
backup.
The proposed system we are going to develop will be used as the major
performance system for providing help to the organization in managing
the whole database of the student studying in the organization.
26. xxvi
4
Design
4.1 Objectives
The overall design objective is to provide an efficient, modular design
that will reduce the system’s complexity, facilitate change and result in
an easy implementation. This will be accomplished by designing strongly
cohesion system with minimal coupling. In addition, this document will
provide interface design models that are consistent user friendly and will
provide straight forward transition through the various system
functions.
The purpose of the design phase is to develop a clear understanding of
what the developer want people to gain from his/her project. As you the
developer work on the project, the test for every design decision should
be "Does this feature fulfill the ultimate purpose of the project?"
The Design Document will verify that the current design meets all of the
explicit requirements contained in the system model as well as the
implicit requirements desired.
4.2 System Architecture
The CIMS is a system which contain major part which include: user
detail, user records and other options.
The user selects one of the available options as an input to the system.
27. xxvii
According to the input by the user the system acts and the rest of the
functions are performed accordingly. The administrator can operate on
any user details. But the normal users can only access their details of all
the functionalities.
4.3 Data Design
Entity-Relationship Diagram
29. xxix
5
Technological Description
The technology selected for implementing College Information
Management System is JSP/MySQL. Glassfish is used as the HTTP server.
The development was done in a ‘windows operating system’ using Net
Beans IDE.
5.1 HTML
HTML (Hypertext Markup Language) is the most basic building block of
the Web. It describes and defines the content of a webpage. Other
technologies besides HTML are generally used to describe a webpage's
appearance.
"Hypertext" refers to links that connect webpages to one another, either
within a single website or between websites. Links are a fundamental
aspect of the Web. By uploading content to the Internet and linking it to
pages created by other people, you become an active participant in the
World Wide Web.
HTML uses "markup" to annotate text, images, and other content for
display in a Web browser. HTML markup includes special
"elements" such as <head>, <title>, <body>, <img>, <p>, <header>,
<footer> and many others.
30. xxx
5.2 CSS
Cascading Style Sheets (CSS) are a stylesheet language used to describe
the presentation of a document written in HTML or XML(including XML
dialects like SVG or XHTML). CSS describes how elements should be
rendered on screen, on paper, in speech, or on other media.
CSS is one of the core languages of the open web and has a
standardized W3C. Developed in levels, CSS1 is now obsolete, CSS2.1 is a
recommendation, and CSS3, now split into smaller modules, is
progressing on the standardization track.
5.3 JAVASCRIPT
JavaScript is a lightweight, interpreted programming language. It is
designed for creating network-centric applications. It is complimentary
to and integrated with Java. JavaScript is very easy to implement
because it is integrated with HTML. It is open and cross-platform.
5.4 MySQL
MySQL is a relational database management system (RDBMS) that runs
as a server providing multi-user access to a number of databases.
MySQL is a popular choice of database for use in web applications and is
an open source product. The process of setting up a MySQL database
varies from host to host, however we will end up with a database name,
a user name and a password. Before using our database, we must create
a table. A table is a section of the database for storing related
information. In a table we will set up the different fields which will be
used in that table. Creating a table in MySQL is simple, we just type the
name, select the number of fields and click the ‘go’ button. we will then
be taken to a setup screen where you must create the fields for the
31. xxxi
database. Another way of creating databases and tables in MySQL is by
executing simple SQL statements. We have used this method in order to
create our database and tables.
5.5 J2EE
J2EE is a platform-independent, Java-centric environment from Sun for
developing, building and deploying Web-based enterprise applications
online. The J2EE platform consists of a set of services, APIs,
and protocols that provide the functionality for developing multitier,
Web-based applications.
Java Server Pages (JSP) is a server-side programming technology that
enables the creation of dynamic, platform-independent method for
building Web-based applications. JSP have access to the entire family of
Java APIs, including the JDBC API to access enterprise databases.
JSP enables us to write HTML pages containing tags, inside which we can
include powerful Java programs. Using JSP, one can easily separate
Presentation and Business logic as a web designer can design and update
JSP pages creating the presentation layer and java developer can write
server side complex computational code without concerning the web
design. And both the layers can easily interact over HTTP requests.
5.6 BOOTSTRAP
Bootstrap is the most popular HTML, CSS, and JavaScript framework for
developing responsive, mobile-first web sites.
Bootstrap (currently v3.3.7) has a few easy ways to quickly get started,
each one appealing to a different skill level and use case.
32. xxxii
6
Project Description
6.1 Introduction
Student Information Management System can be used by education
institutes to maintain the records of students easily. Achieving this
objective is difficult using a manual system as the information is
scattered, can be redundant and collecting relevant information may be
very time consuming. All these problems are solved using this project.
The directory structure of the project is as follows:
67. lxvii
Scope of the Project:
The College Information Management System (CIMS) can be enhanced to
include some other functionality like marks, attendance management.
Talent management of students based on their performance evaluation can
be added.
Social networking can also be added wherein students can interact with
each other.
Online class functionality can be added.
Can evolve as an online institution.
Functionality of chat and messages can be added.
Online exam functionality can be added.
68. lxviii
Bibliography
The Complete reference on JSP
JSP Black book
www.google.com.
www.wikipedia.com
www.tutorialspoint.com
www.getbootstrap.com
Head First Servlets and JSP
www.studytonight.com
www.stackoverflow.com
www.roseindia.net