Course Planning Project in Java

System Requirements Document for Course-Planning

  1. Problem

The Administration performs following functions like managing Professors and managing Students and managing Subjects and managing Streams and managing Schedules. Administration manages time schedule to the Professors for teaching. Suppose when add a new professor Administration checks all the Professors schedules and assign subjects to new professor. Suppose change in schedule of any  professor may or may not collapse other professors schedule so every time Administration need to check all the professors schedules and  this same issue may occur at Student level also, which makes problem to Professors and Student schedule.

This problem can be overcome through using Course-Planning software. Which automatically arrange Professors and Student schedule.  Course-Planning software also saves time it provides accuracy, reduce work, save cost , improve performance, requires less time to plan.

Implementation Module:

  • Course-Planning/Schedule management.

Course-Planning/Schedule management:-

Course-Planning/Schedule is designed to offer time-saving services:

  • Add / Update / Delete professors.
  • Add / Update / Delete students.
  • Add / Update / Delete subjects.
  • Add / Update / Delete streams.
  • Add / Update Schedules for Course-Planning in this manage professors to teach their subjects and students to assign their subjects.
  1. Objectives
  • Improve the speed of managing schedule.
  • Improve the accuracy of the schedule.
  • Improve the accuracy of the schedule during update or deleting schedule.
  • Improve managing professors or subjects or students or streams or subjects.
  • Reduce the time and work to managing schedule to Professors.
  • Reduce the time and work to managing schedule to Students.
  • Reduce cost and faster performance.
  1. Existing system

Administration manages time schedule to the Professors for teaching. Today any new Professor or Student add to Course-Planning Administration checks all the Professors schedules and assign subjects to new professor. Suppose change in schedule of any  professor may or may not collapse other professors schedule so every time Administration need to check all the professors schedules and  this same issue may occur at Student level also, which makes problem to Professors and Student schedule.

The Administration has identified these problems:

  • Administration makes errors entering a new Professor time schedule.
  • Administration makes errors entering a new Student time schedule.
  • Administration makes errors determining and giving out change.
  • Administration takes more time to check out other Professors time schedules.
  • Director does not have a way to check all the Professors schedules.
  • Director also takes more time to check out other Professors time schedules if update time schedule of any professor.
  1. Functional Requirements
  1. Maintain Professors information (add, update, delete)
  1. Professor First Name
  2. Professor Last Name
  3. Professor Email-Id
    1. Maintain Student information (add, update, delete)
  4. Student First Name
  5. Student Last Name
  6. Student Email-Id
  1. Maintain Subject information (add, update, delete)
  1. Subject Name
  2. Subject Description
    1. Maintain Stream information (add, update, delete)
  3. Stream Name
    1. Maintain Schedule information (add, update, delete)
      1. Professor Schedule
        1. Professor First Name
        2. Professor Last Name
        3. Professor Email-Id
        4. Courses per semester
        5. Semester
  1. Student Schedule
    1. Student First Name
    2. Student Last Name
    3. Student Email-Id
    4. Courses per semester
    5. Semester
  1. Control access to all management functions (maintenance)
  1. Identify specific user either Administration/Director
  2. Ensure the user either Administration/Director login in is who they say they are (single password is sufficient)
  1. Non-Functional Requirements
  • Usability
    • The system must be easy to use so that Administrator can quickly make schedule. There are often new professors or students so it is important for the system to be quick to create a new schedule.
      • Administrator should be able to maintain new schedule after enter any new professor or student.
      • Administrator should be able to effectively operate the functions.
    • Reliability
      • The system must be highly reliable since, if the system is not available, the Administrator can’t easily make schedules.
    • Performance
      • All schedules should be performed in under 1 second.
      • All functions look ups should be performed in under 1 second.
  • Supportability
    • The system will be able to automatically install updates received from the software development team.
  • Training
    • The system should provide a training mode that can be used by Administrator/Director being trained. In training mode, the system does not log actual tasks.
    • The system should provide on screen help.
    • The system should come with training documentation.
  1. Target Environment

The system must normally function on a standalone Windows 10 based PC with 4G of memory and 200 GB hard drive.

Software Requirements:

Languages: Java Swings
Operating Systems: Window7
Databases Server: MySql 5.0
Tools/IDE : Eclipse SDK
  1. Use Cases

This is a list of use cases identified for this system.  The definition of each use case follows.

  1. Sign in
  2. Sign out
  3. Add Professor
  4. Update Professor
  5. Delete Professor
  6. Add Student
  1. Update Student
  2. Delete Student
  3. Add Subject
  4. Update Subject
  5. Delete Subject
  6. Add Stream
  7. Update Stream
  8. Delete Stream
  9. Add Schedule
  10. Delete Schedule
  11. Update Schedule
  12. View Professors
  13. View Students
  14. View Subjects
  15. View Streams
  16. View Schedules

System Authorization Use Cases

  1. Sign In
  2. Sign Out
Name Sign in
Description Grant a user access as an authorized user either Administrator/Director
Actor(s) Administrator/Director
Flow of Events 1. Administrator/Director wants to use the system.

2. Administrator/Director selects to Log in

3. Administrator/Director enters credentials

4. System tests the credentials and grant access or shows and error.

Special Requirements Require credentials (username and password)

 

Pre- Conditions Administrator/Director has previously be set up in the system
Post- Conditions Administrator/Director is authorized to the system if requirements and exceptions are met.
Exceptions Credentials do not match shows error/exception

 

Name Sign out
Description Remove a Administrator/Director access to the System
Actor(s) Administrator/Director
Flow of Events 1. Administrator/Director wants to end using the system.

2. Administrator/Director selects to log out.

3. System logs out the Administrator/Director.

Special Requirements
Pre- Conditions Administrator/Director is currently authorized to the system
Post- Conditions No Administrator/Director is currently authorized if requirements and exceptions are met.
Exceptions There must be a Administrator/Director authorized before a use can be logged out.

 Professors Maintenance Use Cases

  1. Add Professor
  2. Update Professor
  3. Delete Professor
Name Add Professor
Description Add the information for a new Professor to the Course-Planning.  This happens when new Professor arrive in the system.  For the newProfessor, first name and last name and email-id added.
Actor(s) Admin
Flow of Events 1. A new Professor arrives in the Course-Planning.

2. Admin  selects to add a new Professor

3. Admin enters information about the Professor

4. Admin selects to save the Professor

Special Requirements Require Professor first name and last name and email-id.

 

Pre- Conditions Admin has be authorized to the system
Post- Conditions Professor is added to system if requirements are met and there are not special exceptions.
Exceptions Do not add if Professor exists in system
Name Update Professor
Description Update the information for an existing Professor in the system.  This happens when a correction is required.
Actor(s) Admin
Flow of Events 1. A change in Professor information is detected.

2. Admin selects to update a Professor.

3. Admin selects Professor to update.

3. Admin enters information about the Professor.

4. Admin selects to update the Professor.

Special Requirements Require first name and last name and email-id

 

Pre- Conditions Admin has be authorized to the system
Post- Conditions Professor is updated in system if requirements and exceptions are met.
Exceptions Validation must follow for first name and last name and email-id when update Professor.

 

Name Delete Professor
Description Delete the information for an existing Professor in the system.
Actor(s) Admin
Flow of Events 1. Professor is identified that needs deletion.

2. Admin selects to delete a Professor.

3. Admin selects Professor to delete.

4. Admin deletes Professor.

Special Requirements
Pre- Conditions Admin has be authorized to the system
Post- Conditions Professor is deleted from system if requirements and exceptions are met.
Exceptions Do not delete when exception occur.

 

 

Students Maintenance Use Cases

  1. Add Student
  2. Update Student
  3. Delete Student
Name Add Student
Description Add the information for a new Student to the Course-Planning.  This happens when new Student arrive in the system.  For the new Student, first name and last name and email-id added.
Actor(s) Admin
Flow of Events 1. A new Student arrives in the Course-Planning.

2. Admin  selects to add a new Student

3. Admin enters information about the Student

4. Admin selects to save the Student

Special Requirements Require Student first name and last name and email-id.

 

Pre- Conditions Admin has be authorized to the system
Post- Conditions Student is added to system if requirements are met and there are not special exceptions.
Exceptions Do not add if Student exists in system

 

Name Update Student
Description Update the information for an existing Professor in the system.  This happens when a correction is required.
Actor(s) Admin
Flow of Events 1. A change in Student information is detected.

2. Admin selects to update a Student.

3. Admin selects Student to update.

3. Admin enters information about the Student.

4. Admin selects to update the Student.

Special Requirements Require first name and last name and email-id

 

Pre- Conditions Admin has be authorized to the system
Post- Conditions Student is updated in system if requirements and exceptions are met.
Exceptions Validation must follow for first name and last name and email-id when update Student.

 

Name Delete Student
Description Delete the information for an existing Student in the system.
Actor(s) Admin
Flow of Events 1. Student is identified that needs deletion.

2. Admin selects to delete a Student.

3. Admin selects Student to delete.

4. Admin deletes Student.

Special Requirements
Pre- Conditions Admin has be authorized to the system
Post- Conditions Student is deleted from system if requirements and exceptions are met.
Exceptions Do not delete when exception occur.

 

 Subject Maintenance Use Cases

  • Add Subject
  • Update Subject
  • Delete Subject
Name Add Subject
Description Add the information for a new Subject to the Course-Planning.  This happens when new Subject arrive in the system.  For the new Subject, subject name and subject description.
Actor(s) Admin
Flow of Events 1. A new Subject arrives in the Course-Planning.

2. Admin  selects to add a new Subject

3. Admin enters information about the Subject

4. Admin selects to save the Subject

Special Requirements Require Subject fields subject name and subject description.

 

Pre- Conditions Admin has be authorized to the system
Post- Conditions Subject is added to system if requirements are met and there are not special exceptions.
Exceptions Do not add if Subject exists in system

 

Name Update Subject
Description Update the information for an existing Subject in the system.  This happens when a correction is required.
Actor(s) Admin
Flow of Events 1. A change in Subject information is detected.

2. Admin selects to update a Subject.

3. Admin selects Subject to update.

3. Admin enters information about the Subject.

4. Admin selects to update the Subject.

Special Requirements Require subject name and subject description
Pre- Conditions Admin has be authorized to the system
Post- Conditions Subject is updated in system if requirements and exceptions are met.
Exceptions Validation must follow for subject name and subject description when update Subject.

 

Name Delete Subject
Description Delete the information for an existing Subject in the system.
Actor(s) Admin
Flow of Events 1. Subject is identified that needs deletion.

2. Admin selects to delete a Subject.

3. Admin selects Subject to delete.

4. Admin deletes Subject.

Special Requirements
Pre- Conditions Admin has be authorized to the system
Post- Conditions Subject is deleted from system if requirements and exceptions are met.
Exceptions Do not delete when exception occur.

 

 Stream Maintenance Use Cases

  • Add Stream
  • Update Stream
  • Delete Stream
Name Add Stream
Description Add the information for a new Stream to the Course-Planning.  This happens when new Stream arrive in the system.  For the new Stream, stream name.
Actor(s) Admin
Flow of Events 1. A new Stream arrives in the Course-Planning.

2. Admin  selects to add a new Stream

3. Admin enters information about the Stream

4. Admin selects to save the Stream

Special Requirements Require Stream fields stream name.

 

Pre- Conditions Admin has be authorized to the system
Post- Conditions Stream is added to system if requirements are met and there are not special exceptions.
Exceptions Do not add if Stream exists in system
Name Update Stream
Description Update the information for an existing Stream in the system.  This happens when a correction is required.
Actor(s) Admin
Flow of Events 1. A change in Stream information is detected.

2. Admin selects to update a Stream.

3. Admin selects Stream to update.

3. Admin enters information about the Stream.

4. Admin selects to update the Stream.

Special Requirements Require stream name
Pre- Conditions Admin has be authorized to the system
Post- Conditions Stream is updated in system if requirements and exceptions are met.
Exceptions Validation must follow for stream name when update Stream.

 

Name Delete Stream
Description Delete the information for an existing Stream in the system.
Actor(s) Admin
Flow of Events 1. Stream is identified that needs deletion.

2. Admin selects to delete a Stream.

3. Admin selects Stream to delete.

4. Admin deletes Stream.

Special Requirements
Pre- Conditions Admin has be authorized to the system
Post- Conditions Stream is deleted from system if requirements and exceptions are met.
Exceptions Do not delete when exception occur.

 

 View Professors/Students/Subjects/Streams/Schedules Maintenance Use Cases

  • Update Schedule
  • View Professors
  • View Students
  • View Subjects
  • View Streams

View Schedules

Name View Professor
Description View Professors to see all the Professors data.
Actor(s) Admin / Director
Flow of Events 1. Admin / Director selects to View Professors
Special Requirements No requirements
Pre- Conditions Admin / Director has be authorized to the system
Post- Conditions At least one professor is there in the System.
Exceptions No Exceptions

 

Name View Student
Description View Student to see all the Students data.
Actor(s) Admin / Director
Flow of Events 1. Admin / Director selects to View Student
Special Requirements No requirements
Pre- Conditions Admin / Director has be authorized to the system
Post- Conditions At least one student is there in the System.
Exceptions No Exceptions

 

Name View Subject
Description View Subjects to see all the Subjects data.
Actor(s) Admin / Director
Flow of Events 1. Admin / Director selects to View Subjects
Special Requirements No requirements
Pre- Conditions Admin / Director has be authorized to the system
Post- Conditions At least one subject is there in the System.
Exceptions No Exceptions

Name
View Streams
Description View Streams to see all the Streams data.
Actor(s) Admin / Director
Flow of Events 1. Admin / Director selects to View Streams
Special Requirements No requirements
Pre- Conditions Admin / Director has be authorized to the system
Post- Conditions At least one stream is there in the System.
Exceptions No Exceptions
Name View Schedules
Description View Schedules to see all the Schedules data in this to see Professors and Students schedules.
Actor(s) Admin / Director
Flow of Events 1. Admin / Director selects to View Schedules to see all the Schedules data in this to see Professors and Students schedules
Special Requirements No requirements
Pre- Conditions Admin / Director has be authorized to the system
Post- Conditions At least one schedule is there in the System.
Exceptions No Exceptions

 

Name Update Schedule
Description Update the Schedule information for an existing Schedule. It contains Professor Schedule and Student Schedule. Professor schedule contains Professor First name and Last name and Courses per semester and Semester and Student schedule contains Student First name and Last name and Courses per semester and Semester.
Actor(s) Admin / Director
Flow of Events 1. A change in Schedule information is detected.

2. Admin / Director selects to update a Schedule.

3. Admin / Director Schedule Stream to update.

3. Admin / Director enters information about the Schedule.

4. Admin / Director selects to update the Schedule.

Special Requirements Require stream name
Pre- Conditions Admin / Director has be authorized to the system
Post- Conditions Schedule is updated in system if requirements and exceptions are met.
Exceptions Validation must follow for Schedule at backend.

 Subject Maintenance Use Cases

  • Add Schedule
  • Delete Schedule
Name Add Schedule
Description Add the Schedule. It contains Professor Schedule and Student Schedule.   Professor schedule contains Professor First name and Last name and Courses per semester and Semester and Student schedule contains Student First name and Last name and Courses per semester and Semester.
Actor(s) Admin
Flow of Events 1. A new Schedulearrives in the Course-Planning.

2. Admin  selects to add a new Schedule

 

Special Requirements In the database must contain professors and students and subjects data and backend run automatically create a new Schedule by the Course-Planning software

 

Pre- Conditions Admin has be authorized to the system
Post- Conditions At least one professor or student or subject data exists.
Exceptions Do not add if no Subjects or Professors or Students data exists in Database.
Name Delete Schedule
Description Delete the information for an existing Schedulein the system.
Actor(s) Admin
Flow of Events 1. Scheduleis identified that needs deletion.

2. Admin selects to delete a Schedule.

3. Admin selects Scheduleto delete.

4. Admin deletes Schedule.

Special Requirements
Pre- Conditions Admin has be authorized to the system
Post- Conditions Scheduleis deleted from system if requirements and exceptions are met.
Exceptions Do not delete when exception occur.

 Glossary

Term Definition
Admin Admin employee who is responsible for the Add/Update/Delete Professors or Add/Update/Delete Students or Add/Update/Delete Subjects or Add/Update/Delete Streams or Add/Update/Delete Schedules data.
Director A Director employee who is responsible for the View Professors / Students / Subjects/ Streams/ Schedules data and Update Schedule data.
Professor Professor employee who is responsible for the teaching Subjects according to his/her schedule.
Student Student who is responsible for studying subjects according to his/her schedule.
Stream Stream is dividing Courses/Streams like Electronics / Computers/Software/Mechanical
Schedule A schedule or a timetable, as a basic time-management tool, consists of a list oftimes at which possible tasks, events, or actions are intended to take place, or of a sequence of events in the chronological order in which such things are intended to take place.
System In this document System means Course-Planning
Subject A branch of knowledge studied or taught in university

Download Course Planning System Java Project.

Safe Internet – Internet Content Filtering tool Project

ABSTRACT

Safe Internet is an Internet Content Filtering tool that can primarily be used to keep the teenage Internet browsing risk free.  The complete features of the tool are listed below.

  1. Block websites
    2. Block Web Pages that contains inappropriate contents on the fly.
    3. Website redirection
    4. Proxy service
    5. Report Generator etc.

The Safe internet is a browser free application so that it will work with any web browser like IE, Mozilla, and Opera etc. The application will monitor the downloading contents as well as the uploading contents.

Applications

Safe Internet can be used as a parental control solution that helps parents protect their children and monitor their Internet use. This can also be used in corporate environment to reduce the Internet Slacking.

Implementation

The Internet Content Filtering tool project Safe Internet can developed using Java. The application has the same working principles of a proxy server. The Safe Internet plus programme aims to promote safer use of the Internet and new online technologies, particularly for children, and to fight against illegal content and content unwanted by the end-user.

EXISTING SYSTEM:

In Existing system there is no facility to block the Web Pages and website directly. To recharge your mobile or you need to go particular website to do such actions.

PROPOSED SYSTEM:

Here we proposed a Internet Content Filtering tool system which contains to block any websites or Web Pages directly with a small operation. And also there is registration for users. By this registration the user can recharge their mobile phones or DTH directly from our application.

MODULES:

There are two Modules in our application

  1. Admin
  2. User

Admin:

In this module admin can block the websites or Web Pages directly by some login. And the admin can view the users who are using our application.

User:

Here in this module user contains a small registration which gives some login id and password. By using that login id and password user can use this application. On user side user can view their profile, recharge their mobile, DTH, etc.., and the user has a right to change their password.

SOFTWARE REQUIREMENTS

  • Application Server           :   0/6.X
  • Front End :   HTML, Java, Jsp
  • Database :  Oracle10g

Advanced Systems Project

In this course, you will work independently on the analysis and development of a specific business computer application. You will come up with your own project based on the broad guidelines provided below for each kind of technology.

After careful consideration, you must submit the project proposal by June 10. The project proposal should include:

1- The problem statement

You need to describe key functionalities of your system from the user perspective.

2- Your choice of technology/tools to be used for project implementation.

Project proposal should be submitted in the corresponding link in Blackboard. See sample research proposal document for an illustration.

If you are going to work with a different instructor (given that the instructor has agreed to advise you), please email me to let me know about this. Also check and confirm with your instructor that the internal roster (shared among faculty) is updated accordingly. This roster is not available on Blackboard or shared with students.

This project is your individual project and grading of advanced systems project is based on how well you implemented the project – based on the specifications that were agreed upon before you started your project.

Students are expected to turn in their original work and are prohibited from reusing past students’ projects for submissions. If any part of the project utilizes code/work used from other sources, the relevant code must be appropriately acknowledged/cited. The final submission must consist of at least 50% of original work done by the student.

Project final submission should include:

1- Completed application

2- Application documentation (requirements document, diagrams, test data etc.).  Depending on the type of project, you may have several UML diagrams, but I expect at least use diagrams and detailed use cases for all projects.

3- Project notes.They are documentation of your research effort to learn about technologies/tools that you had to use for the project.

Following submission of the above items, you will schedule an individual demonstration session. Demonstration involves more than simply showing how the application works. Your grade will depend significantly on your ability to explain your design decisions, implementation and every other aspect of your project.

Final demonstration has to be in person. Intermediate demonstrations can be online and scheduled based on mutual convenience and necessity. Your instructor will advise in this regard.

Below is a list of general project requirements for various technologies:

Networking Projects:

Project requires actual hands-on work on some of the latest technologies in Networking.  This includes Storage Area Networks, Virtualization and Cloud Computing.  Projects will be graded based on their complexity and completion of requirements.  You can use a single platform (Windows Server for example) or multiple platforms (Linux and Windows Server, for example).

ASP.NET projects

  1. Web site should be able to store and modify data using databases.
  2. Web site design should apply concepts of master pages, navigational controls, validation controls and styles/themes.
  3. Parts of the web site should only be accessible to registered users. This includes role-based security and profiles.
  4. Project should include application of state management techniques.
  5. Application of a tiered design using components.
  6. Use of Ajax.

Database Projects

  1. Complete Entity-relationship diagram or Database diagram (at least 4 tables).
  2. Database SQL script file for a specific DBMS.
  3. Query statements used for related reports and analysis (proto typed design).
  4. SQL statements for forms used in data input (proto typed design)
  5. Technology used in database layer in the application (such as ADO.NET) and sample code.

Software Development in C# or Java or any other programming language

  1. Documentation includes detailed use cases, class diagrams, sequence diagrams, package and architecture (optional).
  2. Consist of at least 8 non trivial use cases (leading to at least 8-10 Business tier classes)
  3. Should be at least 3 tiers.
  4. Should implement one or more design patterns.
  5. Code should have global documentation (publish API relevant for your environment)
  6. Involve reasonable data tier and follow DB design norms.
  7. Create a few unit test cases for demo.
  8. While demonstrating, the working code should map to your class diagrams.

Mobile Computing – any platform

  1. Documentation includes detailed use cases, and wire frame of the app (you may use any tool)
  2. Should involve storing data in a local DB or using services.
  3. Should be innovative and useful (similar app should not be available in the web) – so get the concept approved before you start.
  4. Should be able to publish and copyrights belong to UCM.
  5. Performance of the app is important criteria for evaluation.
  6. Web apps cannot qualify as one in this category (follow the web development norms published)

Web based project (other than ASP.NET)

  1. The website should be complete and involve data storage.
  2. Appropriate documentation.
  3. Should use HTML5
  4. Use at least 1 technology that is not covered in the Internet Track.
  5. May use any web development tools.
  6. Follow UI norms/patterns (refer to any UI patterns and cite it in the project note that has to be submitted for such project)
  7. Should have all validations and your website must look professional.

Alumni Portal Java Project

Abstract:

Alumni portal is a java & Oracle project which develops a repository and search engine for the alumni of the college. This allows  old and new students of a university or college to associate with each other’s and to know about each others.

Introduction:

Alumni portal is a web based java final year project which maintains a centralized database of the university or college. This system will automatically list all the students of the university  as alumni on their graduation and transfer their student module to alumni module.

This application students will be provided with a username and password. Student once registered will be member of the alumni portal. He can search the details of the other student. This system also provides a easy access to the students to easily obtain information about other registered users.

Alumni portal will also provide public posts on the system about possible job opportunities and news related to other colleges. This project maintains a high privacy feature. In this portal students can share the information, find  old friends and search for new friends. This alumni portal provides the chat feature which enables students to chat without revealing their mobile numbers or personal mail IDs.

Objective:

The main objective of this Alumni Portal Java Project to allow students to communicate with each other and share their ideas. To provide information about of the institution, college or university. To provide effective data management and retrieval process.

Modules:

Administrator Module:

The administrator is responsible for maintaining information of students. When a student submits the registration form, administrator will complete the verification process and, if successful, the student details are added into the database. The administrator maintains the passwords of Event Manager and that of himself.

Event Manager Module:

This module maintains the information about various events that are conducted by various colleges and universities. Details of notifications are also maintained. The manager can add, delete, edit and view event details.

Alumni & Student Module:

The Alumni/Students can register themselves and after the approval from the administrator, they can logon into their account and can send mails, post queries, update their profiles and even search for other student details. one can view the event details and search for specific information. The module provides mail and query functionalities.

Software Requirements:

Web Presentation                         :           HTML, CSS

Client – side Scripting                   :           JavaScript

Programming Language               :           Java

Web based Technologies              :           Servlets, JSP

Database Connectivity                  :           JDBC

Java Version                                  :           JDK1.6

Backend Database                        :           Oracle 9i

Offender Management Service Java Project

Abstract:

Offender management service is a project developed to improve and manage the security of prison. This project high level security to the data about the prisoners. This system enables the law enforcement people to access the data.

Introduction:

Offender management service is a java web application developed to maintain data without any duplication and losses. All the information related to the prisoners are maintained automatically. Information about the prisoners or prisons can be provided quickly and efficiently.

This system provides complete details of each prisoner. This system also maintains details of all the cases against each prisoner. All the activities of the prisoner will be pre planned and listed clearly in this system. Details like entry date, allocated prison and the release data will be mentioned. All the activities of the prisoner like in time and out time will be automatically updated.

Ledgers and files regarding the prisoner can be maintained with a high level security. This project provides the user to access the data without any in convince and difficulty. In this system data will be organized in a proper way without doesn’t lead to any inconsistency.

Objective:

The objective of this Offender Management Service Java Project is to update all the information and to provide information about the prisoner. To make the work of the government easy by generating the  reports and documents automatically. To provide security for sensitive data.

Modules:

Administrators:

Administrator can maintain different registers such as nominal rolls, case register, automated release register, parole register, duty register and in-out register. Other tasks done by the administrator are generation of reports, maintenance of log files, backup, and recovery of data any time. Administrator also manages details of number of cells and their usage. Administrator is also responsible for managing finances of prison.

Police officers:

Police officers can seek information regarding prisoners and convicts. The information is used to make decisions regarding court hearings, remands, release dates etc.

Data Managers:

On the behalf of administrator data manager prepares all the registers with appropriate data. They can have the privilege to add and update data in the different registers.

Nominal Rolls:

The details of the prisoner and his/her demographic details should be captured. A digital photo comprising different views of the prisoner and the list of articles surrendered by prisoner during nominal roll are to be recorded.

Reports:

The system allows the generation of various reports based on different criteria such as prisoners details.

Software Requirements:

Web Presentation                            :           HTML, CSS

Client – side Scripting                      :           JavaScript

Programming Language                  :           Java

Web based Technologies                 :           Servlets, JSP

Database Connectivity                     :           JDBC

Java Version                                     :           JDK1.6

Backend Database                           :           Oracle 9i

Operating System                            :           Windows XP/2000/2003,LINUX

Web Server                                      :           Tomcat 5.5 / 6.0

Browser                                            :           IE/Mozilla