Category: MySQL Projects

MySQL is the backend database system, We have developed projects with MySQL DB. Students and Projects Lovers can Download Projects with MySQL Database and enjoy executing.

Posted on

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.

Posted on

Communal Contact Java Project

Abstract:

Communal contact is a java project developed to provide a platform for users to communicate with each other’s by exchanging messages and to maintain good friendship. This system allows the user to maintain good relationships with social network and promote their relations.

Introduction:

Communal contact is a java based web application which maintains the data in a centralized manner. This project is developed to allow communication between the people who are from different cultures and different places. This communal contact is considered as a social unit for two or more people who share something in common.

This system provides the users to share or discuss their ideas from any place. Users can exchange or get knowledge about norms, values, identity. By sharing this type of information it can be very helpful to future generations to know the social responsibilities and ethics in society.

The system helps the user to find their present and old friends by submitting a few of their details like name. user will get registered to this system by using username and password. The system provides support for online communities, so that users can maintain both personal relationships and social fabrics. The system provides a number of interfaces through which one can send mails or participate in forums and other such related activities.

Objective:

The main objective of this Communal Contact Java Project is to allow users to communicate with each other by sharing messages and pictures. To provide a easy way of communication.

Modules:

Admin Module:

Administrator maintains the entire application and has all access rights. Administrator can manage user details and decides the privileges of each user

User Module:

User must be registered to access the application. User can create a personal profile. User can search for friends and also find new friends. User can provide answers to the questions posed by other users.

Polls Module:

This module allows users to create polls and participate in polls created by other users. This feature allows to check how many users have similar views about a topic.

Gangs Module:

This module allows a user to create one’s own gang or to enroll in other gangs. This feature allows a user to bond friendships with a close group of members.

Questioning Module:

This module allows user to create a new question or to answer other question asked by other users and can view the list of answers given by different users.

Opinions Module:

This module allows users to share their opinions regarding cars, schools, bikes and movies.

Reports Module:

This module allows administrator to generate various reports based on different criteria such as number of users, poll results and so on.

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                         :           My SQL 5.0

Operating System                         :           Windows XP/2000/2003, LINUX

Web Server                                   :           Tomcat 5.5 / 6.0

Browser                                         :           IE/Mozilla

Posted on

E Farming System Java Project

Abstract:

E-Farming is a Java & MySQL-based application which gives an idea to the farmers how to use e-farming to sell their products. Farmers will get all the new ideas to improve their productivity and they can buy and sell their products online.

Introduction:

E-Farming is a web application developed for farmers. This application gives suppose to the village farmers who want to use this facility and who want to learn how is it possible and how they can use e-farming to sell their products.

If the farmers have knowledge of computer then they can directly register in the site and sell their product otherwise they can contact company’s computer professional who will schedule classes to teach the basics of computers and internet. They can know how they can open this site and register with it and sell their products online etc.

E-Farming is a project developed to build a website which will help farmers from to sell their products to different cities through online. Farmers can use this facility and can learn how is it possible and how they can use e-farming to sell their products.

Objective:

The main objective of this project is to build a website which will help farmers from Indian villages to sell their products to different cities.

Modules:

This E-Farming Java Project has the major modules below:

Admin:

Admin should be able to see all record from any users. The records shown for selling should be available in a format of Quantity name, Quantity available, price.  The database should be robust enough to handle all the online transactions which will be happening parallel.

Users:

People can register on the site for some basic e-learning like if some user wants to learn how to operate a computer, they can go and learn about it from the site. The site should also be available in local languages as per States.

Computer professionals:

Automatic transfer of emails to company’s computer professional if some user enrolled for basic course There should be a facility of scheduling classes for farmers who enrolled for basic courses.

Seller:

The seller can fill the registration form and get his credentials. All the details of the product will be uploaded by the seller. Seller will fix the rates of the products. The seller can view the result page. Seller will add the details of the item. The seller can update the details of the item.

Buyer:

Buyer will get the username and password by filling the registration form. Buyer will view all the details of the product. Buyer will see the list of products that he want to buy. Buyer can view the sales rate details.

Reports:

Daily report of enrollment to Admin. Monthly report of enrollment as per states to Admin.  Work hours use of Computer professionals on a monthly basis to Admin.

Existing System:

In the existing system buying and selling a product is done manually. Price of the product is fixed by the seller. All the details of the product to be sold or purchased is maintained manually. Sellers or buyers not able to get the complete information about the product.

Proposed System:

The proposed system buyers or sellers can directly register in the site and sell/buy the product otherwise they can contact with a seller directly. Buyers can open the site and register with it and sell their products online. E-Farming is a project builds a website which will help businessman to sell their products in different cities online.

Conclusion:

Our project has been successfully implemented the idea of online business. Buyers and sellers can purchase anything from anywhere. Our project helps buyers and sellers in saving a lot of time and money.

Output Screens below:

  • HOME PAGE:
    ADMIN LOGIN PAGE:
    Admin home:
    VIEW BUYERS PAGE:
    VIEW SELLERS:
    VIEW RATES:
    SELLER REGISTRATION PAGE:
    SELLER LOGIN PAGE:
    HOME PAGE
    Add Item:
    Profile:
    View rates:
    Sales page:
    Buyer registration page:
    Buyer login page:
    Buyer homepage
    View rates
    BUY
    RESLUTS PAGE:

Download the E farming System Java Based Project.

Posted on

Fraud and Corruption Control Java Project

Abstract:

Fraud and Corruption Control is a project which is developed to maintain the flow of money released by government, and internal control corruption with involvement of budget officer, department officers, districts commissioners, contractors to citizens, CCTBM investigates complete transparency.

Introduction:

Fraud and corruption is a web application  which will guarantee transparency in budget allocation, distribution and utilization. Fraud and corruption control management is an integral component of effective corporate governance.

This application satisfies the requirement of transparent and accountable process. This application operates to protect the user as a good citizen and helps to reduce the livelihood of financial loss or reputation damage by the staff.

This application informs people about how and who has utilized the money and for what purpose. This creates an online platform where people can get a complete information about budget of the year.

People can know all the development works undertaken. This project will provide an encourage to the citizens to actively participate in Corruption control through budget and to maintain the  transparency and flexibility in system.

Objective:

The main objective of this project is to maintain the flow of money released by government, and intern control corruption.

Modules:

Administrator:

Administrator can generate reports .shared documents and media library that can help in active learning of a student are provided. Administrator will provide users valid use rid and password to login by creating their individual profile.

Citizen Module:

User should be able to create new account, log in to their existing  accounts which will give them the authority to use the services provided by the system.

Software Requirement:

Language                                :           Java

Web technologies                   :           JEE (Servlets/JSP)

Front-end Design                    :           Html, CSS, JSP

Database                                 :           MYSQL 5.0

Scripting                                  :           JavaScript, Ajax

Operating System                   :           Windows/Linux

Posted on

E-Healthcare Advisor Java Project

Abstract:

E-healthcare advisor is a project developed to provide internet based health care information system. This application helps the user to identify certain diseases by answering certain questions asked by the patient.

Introduction:

E-healthcare advisor is a web based application which acts as a communication bridge between the doctor and patient. This application maintains a centralized repository of all information related to diseases and medicines.

E-healthcare application provides online service to the users. By using this application the user need not go to any clinic and meet any doctor. This application is based on the diagnose received by the user and the user will be getting some suggestion of medicines that are available in the local chemist without prescription with an advice to  visit the doctor.

Users/patients need to get registered to this application. They can  simply open the E-Healthcare website and send the request for medicines by  mentioning their disease. It maintains the data and information in a proper way. One can easily browse through the various details using the well defined interfaces provided by the system.

Objective:

To provide online service to the users without wasting time. To increase the performance and serve thousands of people in mille seconds.

Modules:

Administrator:

Administrator related functionalities are performed in this module. Administrator manages the entire application and manages all the Patients and non members details. Administrator is authorized to add, delete and edit, User details, Medicines and Diseases Details.

Patients:

Patients should register to the website. User can send the request to the medicines mentioning their disease details.

Non Members:

In this module non members can also visit the web site. They can get all the information about the diseases and medicines.

Report:

This module allows administrator to generate reports based on different criteria such as Diseases and Medicines.

Software Requirements:

Language                                :           Java

Web technologies                   :           JEE (Serve lets/JSP)

Front-end Design                    :           Html, CSS, JSP

Database                                 :           Oracle 10G

Scripting                                  :           JavaScript, Ajax

Browser                                   :           IE 6.0/ Mozilla

Operating System                   :           Windows/Linux

Posted on

Satvara Matrimony PHP Project

Introduction Of Project:

SatvaraMatrimony is an organized web based Marriage service facilitating wishful men and women to find their suitable life partners.

Home page

SatvaraMatrimony caters to people spread across the globe with the help of internet.

SatvaraMatrimony sites register users, after which they are able to upload their profile onto a searchable database maintained by the website.

Match making process of system is complex and based on Caste, Religion, Job status ,Age, Height ,Family back ground etc.

Context Level DFD

It’s self-operative and easy task.

Provides a choice to search brides and grooms by caste, city and education.

Update and check profile functions.

E-R Diagram

Requirements:

Project Title : www.matrimony.com
Objective : Online find jivan shathi
Plate Form : Front End : PHP,HTML,JAVA SCRIPT
Back End : MYSQL.

User Registration

Posted on

Work In Progress (WIP) Java Project

Work In Progress  (Production and Stores Accounting System)module will accept the process sheet details from the Methods department. By using this information, the PPC prints the documents for required work order for the given Number. The new Work order is launched as per the Number with the Work In Progress status ‘R’. The cost center, machine code & batch quantity are also chosen.

When a new work order is to be launched WIP forwards Material Requisition to Material Management. Then MM, in turn, propels the material requisition to the Store, to confirm the availability of the material. If the required material is existing, Store mails Material Requisition Issue to WIP so that a new Work order may be successfully launched.

If the material is withdrawn from the store for a new work order, it indicates that the Work order is ‘ready for loading’ and the status of the WIP is updated to ‘R’ (Ready for Loading). When the Work order is loaded to the machine, the WIP status is altered to ‘L’ (Loaded) from the shop. When a particular operation is in progress then the status is reorganized as ‘N’ (Not Completed) by SFM module.

In the SFM module itself, the machine card/labor card is booked for that work order with respect to Operation number. When a Work order is completed, the WIP status is updated as ‘C’, which indicates the completion of the Operation.

Inspection of manufactured parts is done not only after each operation but also after the completion of the final operation. When the PPC offers the component for each operation then WIP status is updated as ‘I’. After the completion of the final operation for that particular Work order, the refined component is credited to the store & the WIP status is updated as ‘F’. Hence by screening the status of WIP user can predict the phase of the work order.

Software Requirements:

Operating System: Windows 7

Technology             :  Java/J2EE(Servlets,JSP,JDBC)

Web Technologies  :  Html,Javascript,CSS

Web Server: Linux ad-hoc server

Database: Oracle 11G(Grid Computing), Oracle 9I  (forms and reports)

Software ’s: JDK 1.6

Hardware Requirements:

Hardware: Pentium based systems with a minimum of P4

RAM: 1GB (minimum)

Download the attached Work In Progress (WIP) Java Project Code & Database.

Posted on

Issue Tracking System Java Project

Abstract

Issue Tracking for Improving Software Reliability is an automated system that can be useful to admin and developers in any functional organization. Issue Tracking System gives the facility to define the tasks in the organization and also allows the admin to track the issues spent by the developer for that particular task. It can help admin for Issue estimation per project or application.

This project aims at creation of Issue Tracking System. This project will be accessible to all developers and its facility allows developers to focus on creating the database schema and while letting the application server define table based on the fields in JSP and relationships between them. This system provides the following facilities.

Existing System:

In manual system to solve an issue we have to contact the person directly and provided solutions can be viewed by only that person so it will take time.

Drawbacks of Existing System:

  • It time consuming process.
  • User satisfaction is less.
  • We can’t get more solutions to one problem
  • Less efficient.

Proposed System:

Issue Tracking for Improving Software Reliability is an automated system that can be useful to admin and developers in any functional organization. Issue Tracking System gives the facility to define the tasks in the organization and also allows the admin to track the issues spent by the developer for that particular task.

Advantages of Proposed System:

  • Improve the quality of software
  • Increase satisfaction of users and customers
  • Ensure requests accountability
  • Improve communication in the team and also to customers
  • Increase of productivity of the team
  • Reduce expenses.

Modules:

Admin:

This module has the entire access to all other modules, assign tickets and update tickets.

Developer: 

Developer can access the task or issue assigned by the admin, view assigned tickets and upload patch files. Developer can view the issue list assigned by the admin.

Guest:

Guest can access to view tickets, update tickets and upload patch files.

Issues:

Admin, Developer and Guest can access this module and to change the status.

Technology:

Soft Ware Requirements:

Operating System                :            Windows XP/7/8

Server Side                           :           JSP with Tomcat Server

Client Side                            :            HTML ,JavaScript

Services                                 :            JDBC

Database                               :            My SQL

IDE                                        :             Net Beans 7.4

Posted on

Home Improvement System Management Portal

Employee signup: Employee sign up(registration form) should not be there. We can assume that admin will maintain employee userid and password details. Query to insert userid and password details into database by admin should be there. Employee login only should be provided. Change password, Forgot password with security questions can be added.

Online Application:

Middle name and Address line 2 should not be mandatory.

State – update it to drop down with list of states from the word doc attached

Application Search – Search can be done with entering only one field i.e. only date can be given and search can be done with name and status as blank.(Please show that in video file)

Review/Modify application: Button ‘Save and go to Edit project’ not there.It is displayed only when there is a project created for the application.

New Project:

  • All applications which are approved and with no project created from the database should be displayed in the table. Using the ‘Last Name’ search option, one record corresponding to the value in search field should be displayed.

For example if there are three records a,b,c in the database with status approved, and record b has project created then recordsa,c should be displayed in the new project search page. When I give ‘a’ in last name field, only record ‘a’ should be displayed instead of all 2 records.

  • If no application corresponding to search field are present ‘ No Approved application with given last name found’ should be displayed.
  • Remove ‘Project Assigned’ search option.
  • Address displayed in table should be address line 1 instead of city.
  • Application ID should be added as first field. Name and address fields details should as per application page.

Name – First Middle Last

Address – Line 1, Line 2, City, State, Zip

  • Quantity field should allow characters – to enter units (e.g. lbs, meters etc)
  • Material and quantity table should automatically add another empty row if the entire table is filled.

Add Volunteer:

Name and address fields should be as per application page.

Name – First Middle Last

Address – Line 1, Line 2, City, State, Zip

 

View/Modify Volunteer Details

Volunteer Search:   Can you show me the record being displayed when only one search field is given for example only Volunteer name and no Organization details given.

  • Skill and email fields are not displayed correctly in the table.

Assign Volunteer and Modify Volunteer:

Functionality developed for these pages is not clear.

First after projects are created we will assign volunteers to the projects. To make any modifications to the volunteers assigned to the projects we go to View/Modify volunteers tab.

Assign volunteers:

All projects with no volunteers assigned should be displayed in the projects table.

Skill and organization search fields should be added to ‘Assign Volunteers’ page. Based on the values given for search fields Volunteers details should be displayed in the table. We then select the volunteers and update task and house captain fields and hit the button ‘assign’.(Please refer mockup screens document again for reference)

Modify Volunteer:

In this page volunteers assigned to the project should be displayed. Buttons ‘Unassign’, ‘add volunteers’, ‘save’ and ‘cancel’ should be there. (Please refer mockup screens document again for reference)

Add Sponsor:

Name and address fields should be as per application page.

Name – First Middle Last

Address – Line 1, Line 2, City, State, Zip

 

Volunteer Login:

Volunteer sign up page is not shown. Volunteer login should have name and password instead of phone no. Forgot password and security questions to be added. Sample pages shown below.

Volunteer Home page:

Please print message “Welcome To Home Improvement System Management Portal !!”

Message mentioned above should be displayed after May 1st of current year. This is to set activation of the volunteer for current year one day program (held on last Saturday of April). If ‘Yes’ is selected then volunteer is participating in current year program and he is active for year 2016(May 1st 2015 to May 1st 2016). If volunteer is active for current year, “Thank You for registering for current Year one day event. Project details can be seen in the next tab” should be displayed.

Volunteer Home page

Personal Details:

Name and address fields should be as per application page.

Name – First Middle Last

Address – Line 1, Line 2, City, State, Zip

Assigned Project:

Address of the project, Time – 9:00 am, Date – April 25,Year of registration, Task assigned fields should be present in the table. These should be displayed if registered for current year. If not, ‘No project assigned’ message should be displayed.

Project Materials: Below fields should be displayed. Name is the name of home owner of the project. Address is the address of the home for which project is created(name and address from application form). Same as table from View/modify project page

 

Navigation:

Online Application

Once the online application is submitted and the pop-up saying inserted is shown, the page is redirected to the home page. It should either display a message saying “Your Application has been submitted successfully“. It should not be directed to the home page.

Employee Login

After employee gives his credentials i.e., username and password to login, the home page of the employee is left blank. Instead it should display a message saying “Welcome back (name of the employee) !!”

New Application under Employee Login:

After the employee submits the “New Application”, the employee is signing out and is redirected to the initial home page i.e., Home Improvement Portal home page. The employee should not log out until he selects the logout button and also after the New Application is submitted, the employee should get a message saying that ” The Application for ” the homeowner’s first name and last name” has been submitted successfully“.

Review or Modify Application under Employee Login:

After the search criteria is given and the modifications are made and changes are submitted the page is redirected to the initial “review or modify application page” where no search criteria is given. It shouldn’t be like this. Once the changes are submitted, the application should direct the page to the list the applications shown in the table as per the search criteria given previously.

View or Modify Volunteer under Employee Login:

After the search criteria is given and the changes are made and submitted, the employee should land back again on the same page with project details and volunteers assigned details now displaying the changes to the volunteers.

Assign Volunteers under Employee Login:

After a volunteer is added and the pop-up is displayed the page is redirected to the employee home page. Instead it should return back the Project TABLE page displaying projects for which no volunteers are assigned.

Posted on

Healthcare Hospital System Java Project

The main goal of the Healthcare Hospital System project is to view the hospital statistics by Directors and management or by those who are authorized to see it. Information included in this project is all users registration, payments,  consultation statistics, pharmacy, surgery, transplants, equipment’s, patients and doctors, healthcare bill, multi valued diagnosis, preventive health care, corporate counseling, welfare programmers, claims administration, patient care co-ordination, doctor achievements, staff details and Human Resources.

The attributes  included  in the hospital system are street address, city, county, zip code, birth date, admission/discharge dates, date of death, social security numbers,  record numbers, health plan beneficiary numbers, account numbers, telephone numbers, fax numbers, e-mail addresses. As the information about the patient is already stored in the database, it is easy to retrieve back and to identify the concerned doctor to the patient.

The best way to achieve cost goal is to analyze and interpreting the data and to produce visualization reports.

Project Requirements and Thoughts

  • Identify a topic of interest and run with it!
  • Identify a topic of interest and run with it! Pick a topic that will keep you interested and motivated over the next 14 weeks.
  • Ask the following question: Which answers am I trying to mine or solve?
  • Formulate a hypothesis question. Additional hypothesis questions are encouraged (maximum of 3 questions) are encouraged.  A hypothesis question contains both a null and alternative question.
  • What kind of data is being mined?  Where does the data originate? Can the data be imported into a database (i.e. for formulating updated queries).
  • List Class and/or Concepts related to characteristics and discriminations.
  • Is you project identifying patterns, associations, and/or correlations.
  • Within the project, statistics (e.g. central tendency, range, IQR, variance, etc.) should be presented.
  • Does your dataset contain outliners, if so, please identify them.
  • Projects should list attributes (e.g. nominal, binary, ordinal, and/or numeric)
  • If possible, data should be presented visually (iPython, R, MatLab, Excel, etc.).
  • Was the collected data consider of good or poor quality?
  • Does the data contain missing values or noisy data?
  • Does the dataset contain redundant data? If so, how did you remove duplicated values?
  • When analyzing the data, did you perform OLAP or OLTP processing?
  • Which data models were used for your project (e.g. Stars, Snowflakes, or Fact Constellations)?
  • If OLAP processing was used, did you incorporate bitmap or join indexing into the processing?
  • Did did you determine the size of your data set?