Online Banking Application Project

Baseline Application Description: Online banking application for tellers to perform transactions such as withdraws/deposits, fund transfers, and view transaction statements on user accounts

Baseline Application Features:

  • The system shall provide a login/logout interface for bank tellers
  • Tellers shall be allowed to create/edit customer information
  • Tellers shall be allowed to create accounts for customers
  • Tellers shall be allowed to deposit/withdraw money from accounts
  • Tellers shall be allowed to transfer funds between two of a customer’s accounts
  • Tellers shall be allowed to check the account balances
  • Tellers shall be allowed to check the transaction history of accounts
  • Tellers shall be allowed to close accounts

Note: This banking application only accounts for non-interest-bearing accounts. It does not consider interest, tax, commission, overdrafts, etc.

Reliability Requirements:

  • The client shall automatically fail over to another server without any noticeable effects on the front-end client screen aside from, at most, a 30-second delay for the fail over
  • A client, or a transaction, shall not be affected by a single server failure
  • The system shall be available 24×7 without any critical system failures
  • No account shall ever be in an inconsistent state
  • The teller shall never observe system level error on the client screen/interface

Real-Time Requirements:

  • Each transaction (except for transaction history queries) shall be completed within 1 second in the testing environment with at most 1000 user accounts
  • Each transaction history query of up to 1000 items shall be completed within 5 seconds in the testing environment with at most 1000 user accounts
  • Balance updates as a result of deposit, withdrawal, and/or fund transfer transactions shall take effect immediately (less than 50 ms) upon completion of those transactions

Performance Requirements:

  • The system shall support at least 100 concurrent and at most 500 concurrent client sessions
  • The system shall support up to 1000 TPS (transactions per second)

Baseline Application

Fault-Tolerant Baseline Application

  1. Fault Detection:
    1. How can a Client detect failure?
    2. How many faults can be tolerated?
  2. Fail-Over
    1. How can a Client check if a server bean instance is alive? 1
  3. Recovery
  4. Check Pointing
  5. Sequence diagram

Education Loan Management System .Net Project

Abstract: Education Loan Management System is an application which gives information of various types of loans for students. This application makes the progress of a student easy in providing the right way of information about education loan. Education has been the central human resource development and empowerment throughout the world. Both national and state level policies are framed to ensure the basic need of the population.

This project provides the information about various details of education loans which are allocated for students. This project gathers all the information of the loans. This education loan provides a website to the users. Various modules like home, about us, student , bank details, contact us and logout are provided to the user in this site. In the home page user can know about the education loan system and the details about  applying the loan.

Education Loan Management System 01

In the education loan system,the about us page provides the basic information about applying loan online and details about various banks Education Loan Management System 02

Contact us page provides the details of the management by which the user can contact them for any queries like address, mobile number and email id Education Loan Management System 03

Student module provides students a few options to be selected such as apply for loan, see details and logout Education Loan Management System 04Students who approaches this project will be provided with a unique username and password for this they need to get register to the site by filling the fields by giving the basic information like first name, last name, last college university appeared, name of the last course completed and marks obtained in last course. After filling all the information student should click the continue button which saves the information given and provides authorization to the student to access the site and apply for loan Education Loan Management System 05After giving all the personal and educational information to the management they will display a few fields where the student need to check whether the provided information is correct or he can make changes if any incorrect information is shown. To go to the next page student should click the continue button Education Loan Management System 06

Student need to check the information provided by the management which includes course details like id,college/university name,course type,course name and course duration. Student can make changes if any incorrect information is given and click the continue button Education Loan Management System 07Students will also be provided with the loan details which includes student id, total fee for all years,select bank,interest rate and loan amount. After filling all the information student need to click the continue button to save the details Education Loan Management System 08Student must give the co-borrower details which include student id, name of the employee/business, profession of the co-borrower, designation of co-borrower and net monthly income/salary Education Loan Management System 09

Last page  after giving all the information will appear as applied for loan successfully. A login button will also available there Education Loan Management System 10Students can select the amount to pay by giving the student id and the amount and click the to pay button.Education Loan Management System 11Student can select the amount and click the to pay button.Education Loan Management System 12After submitting the amount student can view the details  of all the  transactions made by him.Education Loan Management System 13The banking system in this loan process is a very important module because it maintains all the transaction details. This module provides options to be selected which involves ICICI ,SBI,AXIS and logout Education Loan Management System 14 Education Loan Management System 15

When the student selects the axis bank all the details which include about us and the contact us will be provided. If the student is comfortable with the bank he can apply there by selecting the category and get more details Education Loan Management System 16

When the student clicks on ICICI bank all the details which include about us and contact us will be provided. If the student is comfortable with the bank he can apply and get more details Education Loan Management System 17

In the ICICI bank student need to provide few information like select loan category and education. Mobile banking is also available in this bank.

Online Form Request Java Project

OBJECTIVE:

Our main objective is to receive any type of certificates/forms from the college, we have to do lots of stuff like submitting letters , filling forms etc., so to avoid all these things we are planning to implement an app,so that is useful to send a request to receive any type of forms from the collage.  (example: bonafide , custodian, etc,.)

ABSTRACT:

Online form request is used to request a form from our personal mobile instead of going to the administration offices and filling up all the details and waiting to receive for the forms .so by this online form request we can apply  for the form from anywhere. This is controlled by admin and admin will accept the requests and sends an SMS to the user to receive the form needed.

EXISTING SYSTEM:

Traditionally, online form request is not existed this form request existed manually in the collage.

PROPOSED SYSTEM:

Our goal is to implement online form request. In this project we want to implement an android app of requesting for forms(example: custodian, bonafide and transfer certificate etc.,) .so passed out students can also apply for transfer certificate online. As soon as they recieve SMS from the admin they can come and collect the form .

TECHNOLOGIES USED:

Technology:java2 standard edition
Web server: tomcat7.0.
Client side technologies: html, css, javascript.
Database server: sql
Operating system: Microsoft windows.

Defect Tracking System C#.Net Project

Abstract:

Defect Tracking System is a project developed to detect the defects in the system. This system also  provides the complete information concerning the defects detected. Defect tracking system is to test the application for the defects and report it. All the reports generated will be send to the project manager and developer.All the defects  information will be stored in the system with a unique id in the database for future reference.The defect tracking system will make the job of handling the defects easily.

The defect tracking system provides a website to the users to get access to the system. The starting page contains the fields which will open the further process of  the defect tracking system which include QA engineer, project manager, developer and defects.

Defect Tracking System 01

User need to get registered to the website first. He needs to fill all the information in the provided fields which include name,phone,address,gender,userid,password,secques,answer and type and finally click the submit button.This opens the popup menu with submit message and ok option wher user need to click the ok button to save his information.

Defect Tracking System 02

After completing the registration process user will be provided with a userid and password. User can give the type of option he need and get logged in by clicking on the login button.User can find the option regarding the account like signup, forgotpwd and changepwd

Defect Tracking System 03

With respect to the user given option the QA engineer details will be opened which displays the options like QA id, QA name, phone no, address, skills, qualification and experience. User can edit the details if any incorrect data is entered

Defect Tracking System 04

User  need to give the manager id and qa id to view the project details.

Defect Tracking System 05

After that user have to provide all the information regarding the project which includes project name,defect name,priority,description,developer name,date and the status.  Click the submit button to save the information.

Defect Tracking System 06

All the defects and the reports of the defects dected will be shown in detailed to the user in a tabuler form.

Defect Tracking System 07

User need to give the information to the fields to see the details of the project manager and click the submit button

Defect Tracking System 08

User will be provided with a username and password along with type of field he needs to enter in.

Defect Tracking System 09

In the project manager page user can enter into other fields provided as employ id, project info, assigned info, project status.

Defect Tracking System 10

User can view all the details of the project manager whenn he clicks the project managerdetails field on the left of the page.

Defect Tracking System 11

User can also see the details of the employee by selecting the employee info option. Defect Tracking System 12

User can submit the information about the project which include project id,project name,no of people,duration,client and requirements of the project.And click the submit button.

Defect Tracking System 13

After submitting the project details user need ot provide additional info like empid, field, managerid ,duration and asigned date.And click the submit button.

Defect Tracking System 14

User will be displayed all the details of the project in a tabular form with an extra option to edit or delet the information.

Defect Tracking System 15

User can insert the information by filling the details to the fields projectid, project name, managerid, empid, projectstatus, projectstartingdate and click the submit button where all the information will be inserted into the table.user can view the inserted information by clicking on the display button.

Defect Tracking System 16

User can enter into developers page by selecting the type as developer.

Defect Tracking System 17

Usere needs to fill the details to enter and click the submit button.

Defect Tracking System 18

User will be provided with an username and password to get logged in.

Defect Tracking System 19

In the developer page the fields include developer details, updatedetails, projectdetails and defect info.

Defect Tracking System 20

User need to fill the information like id,name,address,phoneno,gender,qualification,skills,joiningdate and exp and click the submit button to view the developers details.

Defect Tracking System 21

User can view the qa details and will be able to edit the information.

Defect Tracking System 22

can view all the details of the  project  by providing the managetid and developerid.

Defect Tracking System 23

User can view the defect info by selecting the defectinfo option.This displays all the detailed information of the  defects detected in the project

Defect Tracking System 24

To enter into the defects page user need to give the type as defect along with username and password.

Defect Tracking System 25

User need to fill the information regarding the defects field to display the defect field.

Defect Tracking System 26

In the defect field two options are provided to the user i.e.,defectsdet and defectsins.

Defect Tracking System 27

To detect the defect  user need to give the name,priority ,descr,date,projectname and the status and click the submit button.

Defect Tracking System 28

All the defects details will be displayed in a tabular form.

Defect Tracking System 29

District Collector Magistrate System Java Project

Abstract:

District collector magistrate system is an application which is developed to automate the processes at the collector office in a district. This application is designed to manage all the related information in a systematic manner.

Introduction:

District collector magistrate system is a web based application. This application is developed to store the information without any damage. The application will  store the entire collected information in a centralized database. This application makes the process of managing data  very easy and effective.

This application makes the users feel free in searching and retrieving the necessary data. All the information will be automatically  placed to the database in a secure way this reduces the users to maintain the data or information in files and ledgers. This application gives rights to the user to access and  communicate with the employees to provide well defined interface.

By using this application the user can easily retrieve the data very easily without any mismanagement or loss of data. This application increases the productivity and helps government employees to provide better service without any difficulty and duplication.

Objective:

The main objective of this system is to maintain and manage the data in an easy and effective manner. To provide automated service. To allow the users to interact with the application and execute various operations in a easy way and short period of time.  

Modules:

Administrator module:

Administrator manages the entire application. Administrator is responsible to issue various certificates such as birth certificate, death certificate, income certificate, residence certificate, caste certificate and others. When a request is made administrator may either approve or reject. Administrator can also assign and allot works and tenders to contractors.

User module:

Users include general public and contractors and people from other service sector. Users can apply for various certificates online and also view the status of request. Interested users can also view and apply for tender notices and similar announcements.

Officer module:

This module can be used by police and other public sector departments. They can view the information for the details of citizens, to ascertain and verify personal details of users, in cases such as passport and certificate issues.

Report module:

The administrator and officials can generate various reports based on various criteria as and when required.

Audit Report System Java Project

Abstract:

Audit report system is a java web based UI manager along with audit report tool. This audit report system tool is to display a calendar. The audit calendar displays the details of the current month and the preceding month details to the executives. This audit report system project makes the work of  executives easy by viewing the details of scheduled dates.

Introduction:

Audit report system is a java based web application project developed to manage and display the coming up appointments in detail to the employees in an organization. This application allows the executives to select a date  from the displayed calendar to schedule and view ones appointments.

This audit report system maintains the relevant details of an organization. This application  straightly maintains the  task of scheduling and fixing the appointments. This application manages  all the  other activities including  official or personal.

This audit system makes the process of scheduling much easier and computerized. In this system the manager or top level designated employee can fix the schedule of the executive working under him and can check whether the executive is free at the particular time or in other times. By this application the  management can easily fix the process of scheduling, and even can change the appointment which is reflected immediately to the related employee.

Objective:

The main objective of this audit report system is to maintain the necessary data and view the details of scheduled dates easily. To reduce the paper work, time  and provide support the organization by making use of simple interface .

Modules:

Administrator Module:

Administrator controls the entire application. Administrator can add, delete, edit and view all employee details. Administrator also manages the data related to organizations and businesses. Administrator generates reports based on various criteria.

Employee Module:

Employees must have a valid login information to access the application. Each employee can view the details of companies, events, schedules and appointments.

Report module:

This module allows administrator to generate various types of reports such as event reports, meeting reports, contract reports, feedback reports and attendance reports.

Online Itemization Structure Java Project

Abstract:

Online itemization structure is an application developed to provide online news service. This system allows the users to read the updated news anytime and from anywhere without any difficulty.

Introduction:

Online itemization structure is a web application. This application provides the updated news periodically. The purpose of developing this application is to become a substitute for the print media.

This application reduces the problem of print media and provides online updated news and articles without any stipulation of time. By using this application users can get updated news without any time gap between the occurrence of an event and the published news. This application saves lot of effect to the organization by reducing the manual activities.

Online itemization structure also clears the difficulty of various reporters and journalist to coordinate with each other to share the information and get the alerts about the news happening.

Objective:

This main objective of this online itemization structure is to reduce the manual effort like workers, papers, reporters, publishers and various other permissions from government. This application saves lot of time and provides updated news to the users from their place.

 

Modules:

Administrator module:

Administrator monitors all activities. Administrator authenticates and verifies all news information before it gets published. Administrator coordinates with all reporters and journalists for reliable information. Administrator also monitors all user activities.

User module:

The user can read the news paper by downloading it. User can access information based up on categories and relevance. User can also become a reporter with administrator permission.

Reporter module:

The reporter gathers the news related to a particular domain assigned to the reporter such as crime, sports, political etc. The reporter gets information through various sources and contacts or directly by interacting with concerned people.

Software Requirements:

Programming Language               :           Java

Web based Technologies              :           Servlets, JSP

Database Connectivity                  :           JDBC

Java Version                                  :           JDK1.6

Backend Database                        :           Oracle 9i

Reckoning Inquisitors Java Project

 Abstract:

Reckoning Inquisitors is an java application which provides an effective and easy way of conducting online examinations. This application acts as an excellent test management system that provides a complete solution for Computer Based Test.

Introduction:

Reckoning Inquisitors is an effective system which is completely computerized. This is an online process which the user of this application can conduct examination  for the employees of an organization or any other work station with large number of pupils in an effective manner without any confusion.

This application is even used in academic institutions and training centers. This system provides the user to maintain the received data or records in a secured way. This is an excellent application which  gives accurate results without any duplications that saves the time of the user. All the information about exams conducted, score reports and the records of pupil are maintained by this application.

This application enables fast evaluation of pupils skills and abilities. This application is completely computerized system which removes the drawbacks of the existing system and maintains clear data. This application provides the user a very simple way of exam which can be conducted with negative marking and even without negative marking.

Objective:

The main objective of this system is to develop an effective  system that is used to conduct online test based on various domain and functional areas. By this system the test can be conducted and evaluates easily in a computerized way. To provide a safe and secure database.

Modules:

Administrator Module:

This module provides admin related functionalities. In this module administrator can view, add, delete and edit questions in the question bank. Administrator may allow or ban the users. Administrator may view the details of all tests and also the results. Administrator can generate the appropriate reports.

User Module: 

A user must be registered to use the services. A user can enroll for an exam on ones chosen subject and domain. The user can give their opinion on  negative marks. The user can view the result of a test immediately after completion of the examination and also view the results of tests one has taken previously. A user is allowed to edit ones profile.

Test Module:

Test module allows the candidate to take the test by choosing a subject of interest. Questions will be generated randomly from the database. To answer each question one minute of time will is given. If the question is not answered in time, then automatically it will skip the present question and goes to the next question. It evaluates the test finally by taking negative & non-negative marking into consideration and displays the result.

Software Requirements:

Programming Language               :           Java

Web based Technologies              :           Servlets, JSP

Database Connectivity                  :           JDBC

Java Version                                  :           JDK1.6

Backend Database                         :           MySQL 5.0

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