Office Correspondence and Auto Questionnaire Java Project

INTRODUCTION

GENERAL: Office correspondence and auto questionnaire java based project are developed as per the requirements of the mechanical department.

OFFICE CORRESPONDENCE

Mechanical department deals with the different type of letters. The letters which are received by the mechanical department are incoming letters and the letters which are sending through the department are the outgoing letters.

The different types of letters received and sent by the mechanical department are as follows:

  • Local letters
  • Headquarters letters
  • Others


office correspondence

LOCAL LETTERS

The letters received from and send to other departments of Vijayawada division are termed as local letters.

INCOMING LOCAL LETTERS

The letters received from other departments of Vijayawada division are termed as incoming local letters.

OUTGOING LOCAL LETTERS

The letters sent to other departments of Vijayawada division are termed as outgoing local letters.

HEADQUARTER LETTERS

Secundrabad division is headquarters of the Vijayawada division. So the letters received from and send to Secunderabad division are termed as headquarters letters.

INCOMING HEAD QUARTER LETTERS

The letters received from Secunderabad division are termed as incoming head quarter Letter.

OUTGOING HEAD QUARTER LETTERS

The letters sent to Secunderabad division are termed as outgoing headquarters Letters.

OTHERS

The letters received from and send to the divisions other than Vijayawada and Secunderabad are termed as other letters.

INCOMING OTHER LETTERS

The letters received from the divisions other than Vijayawada and Secunderabad are termed as incoming other letters.

OUTGOING OTHER LETTERS

The letters sent to the divisions other than Vijayawada and Secunderabad are termed as outgoing other letters.

If the reply for the above letters is to be given immediately then those letters are marked as demi official letters.

So different types of demi official letters can be

  • Incoming Local demi official letter
  • Outgoing Local demi official letter
  • Incoming Head quarters demi official letters
  • Outgoing Head quarters demi official letters
  • Incoming Other demi official letters
  • Outgoing Other demi official letters

All the incoming letters are received by the chief office superintendent and are marked to different sections of the mechanical department with the authorized signature of the senior divisional mechanical engineer. Then the respective task is performed by section accordingly to the letter which is received by it and sends the reply to the chief office superintendent. Then the chief office superintendent with authorized signature of the senior divisional mechanical engineer sends the letter as an outgoing letter.

The mechanical department consists of seven sections.

  • Contract/tenders
  • Carriage & wagon staff
  • General/pass
  • Rolling stock
  • Stores
  • Budget
  • Power

AUTO QUESTIONNAIRE

The test to avail the promotion is conducted for the employees of the Vijayawada division. The question bank offered to the employees for preparation comprises of the following type of questions.

  • Long answers
  • Short answers
  • Fill in the blanks
  • Multiple choices
  • Expansions

auto questionnaire

STATEMENT OF THE PROBLEM 

OFFICE CORRESPONDENCE

To maintain the details of different types of letters, to show the status of the letter and also to generate the reports. 

AUTO QUESTIONNAIRE

To maintain the questions and to generate the questions randomly when appropriate type of question is selected.

EXISTING SYSTEM

OFFICE CORRESPONDENCE

In the existing system, the details of the letter are being maintained manually by entering different types of letters in different books. To know the present status of the letter, it is very difficult in the existing system because one has to verify all the entries in that particular book. So it is time-consuming. 

AUTO QUESTIONNAIRE

In the existing system, question paper is set manually by selecting the type of questions from the printed question bank. It is very difficult and time-consuming to set question paper manually because when selecting a question one has to verify whether it was previously given or not.  One has totally the maximum marks for which paper was given and marks allotted for each question and he should also consider the choices for each type of question.

PROPOSED SYSTEM 

OFFICE CORRESPONDENCE

The proposed System is a web-based application. It maintains details of all the letters within the mechanical department. The present system shows the pending letters and reports. 

AUTO QUESTIONNAIRE

In the proposed system the question paper is set automatically by selecting random questions when an appropriate number of question type is selected.

OBJECTIVES OF STUDY 

OFFICE CORRESPONDENCE

  • Automating the manual work.
  • To generate the status of the letter
  • reminder  provision for pending letters

AUTO QUESTIONNAIRE

  • To generate the question paper quickly from the available database.         

REQUIREMENT ANALYSIS   

FUNCTIONAL REQUIREMENTS

OFFICE CORRESPONDENCE

  • The user can add the details of all the letters into the database and view the pending letters.
  • The authorized user can edit the details of the letters and delete the letters from the database.

AUTO QUESTIONNAIRE

  • The authorized person can add, delete and update the questions in the database.

SYSTEM DESIGN SPECIFICATION 

SOFTWARE REQUIREMENTS

Operating system: Windows XP professional

Programming Language: JAVA

Web Technology J2EE (JDBC, Servlets, JSP, HTML)

Browser: Internet Explorer

Web application serverApache Tomcat

Model Design: Rational rose

IDE: Net Beans 6.7.1

Data Base: Oracle 10g, MS Access. 

HARDWARE REQUIREMENTS

Processor: Intel p4

RAM: 256MB RAM

Hard disk: 20GB or more

Required Software’s:

  • Oracle 9i
  • Java
  • Netbeans 6.7.1
  • Mozilla Firefox

Instructions to Deploy:

1. Install the required software’s
2. Open Netbeans and open the project from source code
3. Configure database connections from DBConn package of Source Packages under the root PPO & Technical
4. Right click on CreateTab.java under Test Packages under the root PPO & Technical and click on run
5. Right click on root and click on run

Note: In case of reference problems right click on root and click on resolve reference problems, and select the library files.

Output Screens:

  • Homepage in office correspondence
  • Selection of letter type in office correspondence
  • Reports generation using a serial number in office correspondence
  • Report generation using by date in office correspondence
  • Report generation using between dates in office correspondence
  • Report generation using marked in office correspondence
  • Report generation using received from in office correspondence
  • Report generation using send to in office correspondence
  • Report generation using general in office correspondence
  • Report generation using remainders in office correspondence
  • Pending letters in office correspondence
  • Editing of the letter in office correspondence
  • Login page for deleting the letter in office correspondence
  • Letter deleted successfully in office correspondence
  • Login page in the auto questionnaire
  • Operations on question bank in the auto questionnaire
  • View of multiple choice questions in the database
  • Default question paper in the auto questionnaire
  • Question generator in the auto questionnaire
  • window to open or cancel generated question paper in the auto questionnaire
  • Generated question paper opened in MS word in the auto questionnaire

CONCLUSION 

The primary goal of this project is to reduce the work which is being done manually. By maintaining the details of all the letters in the database we view the letters based on different fields such as serial number, marked to, date and so on. The letters which are pending can be viewed easily and the remainder is generated. Editing and deleting the details of letters is also possible.

The question paper is being generated by selecting the questions randomly from the database. We need to mention the maximum marks and the type of question. Creation of our own template is also possible. This system is very user-friendly.

SCOPE 

The application i.e., office correspondence which we developed is a standalone one i.e., within the department we can use. The letters are received in paper format and then they are saving them in the database. Due to this time gets wasted. If we develop a web-based application the letters received by the department are sent through emails then a lot of time gets saved.

Download Office Correspondence and Auto Questionnaire Java Project Code

Planning & Technical Management System in Java

The manual procedure for interaction between the PPO users and the other users in ELS (Electric Loco Shed) is prone to certain limitations.  The existing system has been facing certain limitations like communication gap between various departments of ELS and maintaining the details manually which is a time-consuming process. So, it is becoming very difficult to maintain the Loco information, its Schedule, its Failures and the time to time communications between the departments.

To Overcome these drawbacks The Proposed system is an enhancement to the existing system covering some of its limitations by automating the process. The PPO which maintains the information of the Locos, Schedules the Locos, Assigns the work to different departments, Finds the repairs and all other work is computerized. This general introduction includes the scope of the system.

Home page of Planning & Technical Management System

SCOPE OF SYSTEM

  • View all the details regarding the Locos.
  • Maintain all the details regarding locos like a loco number, loco schedule.
  • Maintain the Loco failure details.
  • Activities like the update, deletions, and creations done in the system by the developer in future.

PURPOSE OF THE SYSTEM

The main aim of the Planning & Technical Management System project is to reduce the paperwork and duration of work process and to maintain the data of Electric Loco Shed efficiently the maintenance of all details is undergoing manually in the existing system. So it is becoming very difficult for the communication between the various departments of ELS and also to maintain & refer to the Loco information.

To overcome these drawbacks, computerizing the details of the Locos related to a particular Electric Loco Shed is needed. So this system is built to access the information of the loco in an easier way. The system also provides information regarding the staff attendance so that the top management can have an easy way to handle the staff members’ regularity.

EXISTING SYSTEM

The existing system is entirely being operated manually. All the registers are being maintained in hardcopy files, which is quite difficult to maintain and harder to access. It is very much time consuming and requires a lot of requisites for the information to be passed from one department to another department. And in case of replacements, if spares are not readily available, tenders are being issued so as to opt for the best quote that is obtained which is more cost efficient. Also, there is a possibility of encountering errors due to the human intervention.

PPO Department Work Description Page

PROPOSED SYSTEM

The proposed system is the computerized version of the existing system wherein all the files are digitized and stored in a database which can be accessed by only privileged users. Information regarding any worker or a loco can be instantly known at any time. Our proposed system also enhances security by maintaining the digital signatures of workers who work on a particular loco for future reference. The communication between the users of different departments is made very easier in the system.

OBJECTIVES OF STUDY

  • Maintaining digitized data for easier access.
  • Remote access to data for all the departments of ELS.
  • User-friendly environment to get the required information. 

REQUIREMENT ANALYSIS 

FUNCTIONAL REQUIREMENTS

This section describes the functional requirements of the system for those requirements which are expressed in the natural language style. They are as follows:

  • Automate tedious manual work.
  • Automatic alert provision for task completion on locos.
  • They should be able to view the required reports related to locos.

NON-FUNCTIONAL REQUIREMENTS

  • Performance: The completely separate business logic at the server side from the user interface ensures good performance.
  • Interface: the User interface is web browser based. The client-side user interface is developed using HTML and JSP.
  • Usability: This section includes all of those requirements that affect usability. It will be very easy to use for the naïve user.
  • Supportability: Choosing Java platform makes this system cross-platform independent.
  • Reliability: The system is more reliable as it inherits the Java platform qualities.

SYSTEM REQUIREMENTS AND SPECIFICATIONS 

SOFTWARE REQUIREMENTS

Operating System: Windows XP Professional

Programming Language: JAVA

Web Technology: J2EE (JDBC, JavaScript, JSP, HTML)

Browser: Mozilla Firefox

Web application server: Apache Tomcat 6.0

Model Design: Rational Rose

Data Base: Oracle 9i

IDE: NetBeans 6.7.1 

HARDWARE REQUIREMENTS

Processor: Intel P4/AMD Athlon

RAM: 256MB RAM

Hard Disk: 20GB or more

Output Screens of the project:

1 The home page of Planning & Technical Management System
2 Login page for all departments
3 Daily Schedule Page
4 Loco Schedule Update Page
5 Loco Important Parts Update Page
6 View Loco History Page
7 PPO department Work Allotment Page
8 PPO Department Work Description Page
9 General Work Allotment View Page
10 Sectional Work Allotments Page
11 Sectional View Work Page
12 Staff Description Page
13 Attendance Report Type Selection Page
14 Daily Attendance Report of the whole Department
15 Monthly Attendance Report of the whole Department
16 Daily Attendance of Individual Staff Member
17 Monthly Attendance Report of Individual Staff Member
18 Yearly Report of Individual Staff Member

Conclusion:

The primary goal of this project is to computerize the entire process being done in the Electric Loco Shed (ELS/BZA) and provide instant access to the work that is being carried out in various departments to the authorities. It further aims at providing a digital database of all the records that are currently being stored in hard copies. This is all done with user-friendly GUI and easy to understand functionalities.

The project has been successfully completed by including all the specified features. Our project team members worked hard with the help of our guide to develop the system in such a way that we can retrieve information in all dimensions.  We can confirm that the entire project has been completed as per the stated requirements.

Download Planning & Technical Management System Java Project Source Code and Database.

Car Rental System Oracle Application

A Brief Description

The aim of my Car Rental System project is to achieve an Oracle Application able to store and manipulate data. The idea is to let the manager of a car rental to control all money transactions and keep track on of available cars, clients, employees and suppliers. A main issue is to take into consideration security matters. Here Oracle appears to be satisfying from this side.

My Car Rental System project consists of a main page that has six buttons connecting it to different parts of the main database. The cars button takes us to a form that shows the car ID, brand, type, supplier ID, price per day, insurance company and most important whether the car is rented or not.

The Clients button takes us to the client’s form where the manager can view the available clients, add a client or search for a specific client. Each client has ID, first name , last name , age, country, city, road, building, stage, sex, civil state, telephone, portable, fax, email, and the most important, the cars ID that was rented by the client. The employee button takes us to the employee form that gives the Employee ID, first name, last name, age, country, city, road, building, stage, sex, salary, civil state, job and department.

Car rental system Oracle project

The suppliers button takes us to the supplier form where information like the supplier ID, telephone number and address are viewed. Then the transactions form shows the transaction ID, some information about the client, and the master credit card ID and pin code. Here we should note that, the data concerning credit cards should be connected to banks or to online services supported by banks to provide validation to the input information.

The next button named “search by picture” takes us to a form with a set of pictures each having two buttons underneath it. One button named “See” and the other “Rent”. If “See” was clicked, it will call the cars form so directly we can get other information about the selected car. If “Rent” was clicked, the client form will appear and collecting the information from the client can start directly.

All what we were talking about was the main page. But for security issues, a “Log in” page was added with a username and password that must be with the manager only. The application creator, or simply I, is the only one who is able to change the password.Car rental Oracle project Home page

Tables Creation

I created a list of tables to handle this database.

The tables are: SUPPLIER, CARS, Clients, Employee, Transactions and Authentication.

Each table has a primary key. The primary keys are the first column of each table and named by the table name adding ID. I connected the clients table with the cars table through a foreign key. An illustrating picture is shown below:

Car rental system tables creation

And for more information about table creation using sql language refer to the text file included with the project on the CD.

Procedure of Work

After creating the tables, we enter the form builder which is part of the Developer Suite 10g. An important thing here to be mentioned is one should start OC4J service before running a form.

We create a new form and start dropping Text Items in the layout editor. Then In the Object Navigator, select Data Blocks and then go to menu and select edit > create. I usually used the manual way to create a new item. After the new item is created, double click it to open the properties. In the Database panel chose the suitable table that will be connected to this Data Block Item. After that, start adding new child items to this item that will represent the columns of the table.

Here comes the step concerning connection between Text Items and Data Blocks. In fact, this is an easy step to accomplish. Just double click the Text Item and adjust the database connection in the properties panel. Specifically input in the column name, the name of the column that should appear.

A good thing to mention here is that each button has a pl-sql statement behind it to execute the command. To call other forms I used CALL_FORM(‘C:\ahmad\main’) for example. That is why placing the project in the C drive is a must for the application to run.

As mentioned above, security of such a program is a must. That’s why I added a page to log in. The code behind the log in button is the following:


DECLARE

USERNAME VARCHAR2(20);

PASSWORD1 VARCHAR2(20);

alert11 number(10);

BEGIN

SELECT UserNameww,passwordww INTO USERNAME,PASSWORD1

FROM Authentification

WHERE UserNameww = :USER1 AND passwordww = :PASS1;

IF (USERNAME = :USER1 AND PASSWORD1 = :PASS1) THEN

alert11 := SHOW_ALERT('Valid');

CALL_FORM('C:\ahmad\MAIN');

END IF;

EXCEPTION

WHEN OTHERS THEN

alert11 := SHOW_ALERT('INVALID');

END;

The code simply declares three variables username, password and alert. It queries the authentification table for all usernames and passwords specified. If found, the access is verified and an alert is called saying that the entrance is valid. If not, then the access is denied and an Invalid message is thrown.

Each time a form is called, I added in the triggers an item called when the form is loaded. I wrote “Execute_Query;”

 

E-Admissions Project in Java using Servlets and Oracle

ABSTRACT

In present day scenario, a student goes to a counseling center to get admission in an institution. This is time consuming. Moreover the colleges are not able to select the students of their choice. The main aim of this project is to convert the existing paper filling admission process into electronic filling for all new under graduate student admissions.

We create a web application for prospective students to apply for admission into the list of available colleges and courses of desired university and track the status of their application. We create an administrative web interface for the college admissions officers to review, track, and process new student applications.

class diagram of E-ADMISSIONS Project

The visitors to the E-ADMISSIONS can be both students and colleges. The student can search and fill the admission forms of selected colleges. College administration selects the students based on their academic performance and confirms their admissions. Student can also pay the fees through online after receiving the confirmation.

The fees payment can be done in two ways using credit card or DD number through online. There is also an access control system, which prevents unauthorized public to access all the information, whereas subscribed users can have full access to all available information.

MOTIVATION

The colleges for which this application has been developed were facing huge problems in the management of the admission process. Every year, students in thousands queue up for collecting admission forms and then again for submitting them. This leads to problems in managing the applications, resulting in annoyed parents and students (alike). Also, the admission process is not transparent, leading to scope for widespread malpractices.

In order to rectify these shortcomings, the online admissions system is developed. Here students need not collect physical forms, they are required to fill the admission form and submit it online. This saves a lot of time and effort on the part of the college as well as for the students. Since students interact with colleges, only the deserving candidates can get admission into the college.

PROBLEM DEFINITION:

Generally in order to get admission into an institution, the student should definitely go to the Counseling Center. In this process, colleges will not be able to pick the students of their choice. There is no proper scope of interaction between Colleges and Students. This process is quiet time consuming and hectic mainly for the students who come from long distances.

  • Present system involves more human power. As the students who apply for the colleges are not small in number, much coordination is required in order to organize the counseling process.
  • The students coming from long distances cannot afford to stay for long time near the counseling centers.

HARDWARE SPECIFICATIONS

  • Intel P-IV Processor
  •  512 MB RAM
  • 10 GB Hard Disk 

SOFTWARE SPECIFICATIONS

  • Operating System       :   Windows NT/ XP, Windows 98
  •  Languages                  :   JAVA using Servlets,

JSP with JDBC Drivers, JavaScript, HTML

  • Database                     :   Oracle
  • Web server                  :   Tomcat 5.5

Source Code of INBOX file:

<%@ page import="java.sql.*,java.util.*,Db.*"%>
<%

Connection con=DBConnect.getConnection();

String sname=(String)session.getAttribute("uname");
PreparedStatement pstmt=con.prepareStatement("select cname,status,sdate,code,branch,appid from sinbox where sname=?");
PreparedStatement pstmt1=con.prepareStatement("select appid from sinbox where sname=?");

pstmt.setString(1,sname);
pstmt1.setString(1,sname);
ResultSet rs=pstmt.executeQuery();
ResultSet rs1=pstmt1.executeQuery();
%>
<html>
<title>student inbox</title>
<center>
<font size="5" >
<b><p style="color='#7c7cba';font-family:'Perpetua'"><marquee behavior='alternate'>ONLINE ADMISSIONS SYSTEM</marquee> </p></b></font>
<table width='100%'>
<tr><td width='100%' bgcolor="#a2a2ce"><font size='5px'><center>
Welcome
<%
out.println(sname);
%></center></font></td></tr><tr align='left'><a href='studentlogin.html'>LOGOUT</A></tr></table>

<br><br>
<center>

<table border=1 cellspacing='0' cellpadding='4' bgcolor='lightyellow' style="font-family:'Perpetua';font-size:'19'">
<tr>
<th align='center'>CNAME</th>
<th align='center'>APPLICATION-ID</th>
<th align='center'>BRANCH</th>
<th align='center'>SUBJECT</th>
<th align='center'>DATE</th>
</tr>
<%
while(rs.next()){
%>
<tr><td align='center'><%=rs.getString(1)%></td>
<td align='center'><%=rs.getString(6)%><input type='hidden' name='appid' value='<%=rs.getString(6)%>' readonly ></td>
<td align='center'><%=rs.getString(5)%></td>
<td align='center'><%=rs.getString(2)%></td>
<td align='center'><%=rs.getString(3)%></td>
</tr>
<%
}
%>
</tbody>
</table>

<form action="link.jsp" method="post">

<b>Application id &nbsp; :&nbsp;&nbsp;&nbsp;</b><select name="appid">

<%
while(rs1.next()){
%>
<option><%= rs1.getString(1)%></option>
<%
}
%>
</select><br>
<br>
<input type="submit" value="select" style="font-size:'16';font-family:'Times new roman'">
</form>
</center>
</body>
</html>

Online Course Reservation System Project in VB & Oracle

Online Course Reservation System

Aim

To develop a problem statement, SRS document, UML Diagrams, Technical, Domain & Service layers for Online Course Reservation System.

Problem Statement

The Online Course Reservation System helps a student to reserve a course from a college of his or her choice online. If a student is already registered, they can log in. Else, they have to fill up the registration form provided by the administrator. After registering, the student can log in to the system. Then the student selects the college and courses.

Then based on the qualifications of the student the system determines if the student is eligible for the course he has opted for. If the course is available the student can proceed to the payment step, where the course fee can be paid online. After paying the fee, a receipt stating the details of the student and course they selected is provided by the Administrator. Then the student successfully logs out the system.

Welcome to Online Course Reservation System

Result

Thus the problem statement for Course Reservation system is written.

GANTT CHART

AIM:

To develop Gantt chart for Online Course Reservation System.

gantt chart

RESULT:

Thus the Gantt chart for Online Course Reservation System was successfully developed.

Modern Software Requirements Specification

Introduction

This SRS contains the documentation of the requirements used in creating the Online Course Reservation System. It also contains the Use case model hierarchy and the diagrams of the use case model. The software requirement specification is mainly used for requirement elicitation .The users of SRS are the client, the users, the system analysts and the system designers.

Purpose

The main purpose of SRS document is to illustrate the user requirement of the stock maintenance system. This document is developed after a number of consultations with the client. This document will also act as a contract between the client and the developer in case of any dispute during the delivery.

Scope

The scope of the Online Course Reservation System is :

1. A student should be able to

  • Login to the software through the first page of the application
  • Enter the details clearly
  • Enter the courses information clearly

2. The administrator should recognize the personal and account details

3. The course requested by the student should be reserved.

Definitions, Acronyms and Abbreviations

VB Visual Basic, Front end
OCRS Online Course Reservation System

Overview

The Online Course Reservation System helps a student to reserve a course from a college of his or her choice online. Based on the qualifications of the student the system determines if the student is eligible for the course he has opted for. Next, student can proceed to the payment step, where the course fee can be paid online.

Overall Description

This section describes the functions of the project and their aims. It also includes the constraints and the requirements of the project. The Online Course Reservation System is aimed at helping student to reserve a course in a college of their preference. The perspective of project is to efficiently manage reservation of seats online in a simple and convenient manner. The product has a simple and easy user interface.

Use-Case Model Survey

  • Login
  • Registration for new user
  • Enter students details
  • Check student information
  • Select the college
  • Select the course
  • Online fees payment
  • Course reservation

Introduction

It is a graph of actors, a set of use cases enclosed by a system boundary and the association between actors and the use cases. A use case is a special flow of event that occurs in the system. An actor is a user playing a role with respect to the system.

 Survey Description

  • Login- Existing user can enter in to the account
  • Registration for new user- New userto create their account
  • Enter student details- Students will give academic certificates
  • Check student information- Administrator will check eligibility of the student
  • Select college- The user will select the college
  • Select the course- Students will select the course
  • Online fees payment- Online fees payment will be made using credit/debit card or net banking.

Use-Case Model Hierarchy

Following are the actors in the in the system:

   Student– One who wants to Register through online and fill the form for writing the exam

Administrator– One who get the personal details and check the eligibility of the candidate.

Diagrams of the Use-Case Model

Diagrams, primarily use-case diagrams, of the entire use case model are included here

Assumptions and Dependencies

  • The user must have connected to the internet to use the system
  • The user’s computer  must be Windows 98 or later version platform
  • TCP/IP protocol must be installed to communicate  through HTTP message
  • The accuracy of the information of users is the responsibility of all users

Requirements

Online Course Reservation System requires Visual Basic 6.0 and Oracle 10g to be installed in the system. Also there will be a database which will keep all the records done by user while registration and course selection.

Use-Case Specifications

The various use cases are

  • Student details
  • Student Login
  • Course Selection
  • Payment
  • Course reservation
  • Update database

Functionality

The main functionality of system is that we can get from online even at our home itself.

Usability

Online Course Reservation System is very user friendly. Users can easily register and reserve a course of their choice.

Reliability

The system shall operate 95% of the time. The number of defect should not exceed 10 per function. In addition, before the submission of the final release the calendar must be tested in case of the defects over 10 per function.

Performance

  • The system shall accommodate 500 users during the peak usage time  window of  8:00am to 10:00am local time, with estimated average session duration of 45
  • All web pages generated by the system shall be fully downloadable in not more than 10 seconds over a 40KBps modem connection.
  • The system can display confirmation message to users within 4 seconds after the user submits information to the system.

Supportability

The system is supported by Visual Basic for design and Database Management Concepts for backend database storage.

Design Constraints

The design constraints of Hardware and Software

The Hardware:

The various hardware constraints needed are CPU, Processor speed, Coprocessor speed etc.

 The software:

The various software constraints are Front end, Back end and OS.

Online User Documentation and Help System Requirements

None

Purchased Components

None

Interfaces

It describes the various interface needed for the user

User Interfaces

The user interface is Windows XP Operating System.

Hardware Interfaces

The Hardware interfaces are:

CPU                            :           Core 2 Duo

Processor speed           :           2 GHZ

Coprocessor                :           Built in

Total RAM                  :           3 GB

Hard Disk                   :           250 GB

Keyboard                    :           105 Keys

Mouse                         :           Logitech Mouse

Operating system        :           Windows XP/2007/Vista,

The software interfaces are:

Front end                    :           VB

Back end                     :           Oracle

Operating System       :           Windows XP

Coach Management System Project in Java

Though, all the user requirement have been meet , the road does not end here. Future development can be undertaken to enhance the functionality and to increase the efficiency of the “Traction Loco Control ”

Poh shop detailas

The fact that this system is going to evolve everyday in the upcoming month. The team can’t just sit back new technologies package has to be incorporated in the system to make it fully secure and full proof. Also additional care has to be take to maintain the database which is going to increase and migrate it to other platform which can handle excessive load.

Coding:


import javax.swing.*;

import java.awt.*;

import java.awt.event.*;

import java.sql.*;

class help implements ActionListener

{

private JDialog dialog = new JDialog((Frame)null, "Help", true);

JLabel l1=new JLabel("COACH MAINTANANCE SYSTEM");

JLabel l2=new JLabel("Please Contact :- Sujeet Kumar Singh");

JLabel l3=new JLabel("Address             :-  C/O-R.C.Matho,Veer Sivajee path");

JLabel l4=new JLabel("North S.k.puri,dist-Patna");

JLabel l5=new JLabel("Bihar,   pin-800013");

JLabel l6=new JLabel("Contact no        :- 9308105802");

JLabel l7=new JLabel("Special Thanks For Mr. Rajesh Kumar");

JLabel l8=new JLabel("And Logic Solution");

JLabel image=new JLabel(new ImageIcon("logo2.gif"));

JButton b1=new JButton("Ok");

JPanel p=new JPanel();

help()

{

Container Pane=dialog.getContentPane();

dialog.setBounds(200,200,500,400);

p.setLayout(null);

l1.setBounds(50,30,475,30);

l1.setFont(new Font("",Font.BOLD,22));

l2.setBounds(100,75,300,30);

l2.setFont(new Font("",Font.BOLD,16));

l3.setBounds(100,100,400,30);

l3.setFont(new Font("",Font.BOLD,16));

l4.setBounds(230,125,300,30);

l4.setFont(new Font("",Font.BOLD,16));

l5.setBounds(230,150,300,30);

l5.setFont(new Font("",Font.BOLD,16));

l6.setBounds(100,180,300,30);

l6.setFont(new Font("",Font.BOLD,16));

l7.setBounds(95,275,400,25);

l7.setFont(new Font("",Font.BOLD,16));

l8.setBounds(175,300,400,25);

l8.setFont(new Font("",Font.BOLD,16));

image.setBounds(200,225,100,50);

b1.setBounds(210,325,80,30);

p.add(l1);p.add(l2);p.add(l3);p.add(l4);p.add(l5);

p.add(l6);p.add(l7);p.add(image);p.add(l8);p.add(b1);

b1.addActionListener(this);

Pane.add(p,"Center");

dialog.setVisible(true);

}

public void actionPerformed(ActionEvent e)

{

if(e.getSource()==b1)dialog.setVisible(false);

}

public static void main(String sr[])

{

new help();

}

}

Future Application

This Project can be easily updated according to the needs of Mechanical Department of any railway zone.  This is made in such a way that it can be easily modified in a more advanced form if there will be such need.  The database of this software maintains the records of the details of Coaches who have been attached to the rake and the details of maintenance schedule of the coach.  These records will have a lot of use in future related to any enquiry.

This database can seamlessly be used by other candidate systems to be developed in future. It can be further developed as a net-centric database. The transactions are also revealed in this project.  Any financial enquiry can be satisfied easily through this software.  Hence, this project covers all-important details regarding the “Number Allocation System for Coach” of the Railway Zone. Therefore in future it will help to provide some important information’s, which may help in development of the company.

The main scopes and future enhancements are as follows

  • Proposed system can be delivered on a 3-tier architecture so as to improve scalability and performance
  • Browser Enabled User Interface for distributed Application
  • Arrangement for automatic back up and replication of database.
  • Enhanced security features like e-signature and public key encryption technology features for secure transfer of confidential data
  • On-Line help feature for “Expert Advice and Error Shooting”.

INTRODUCTION OF THE PROJECT 

Indian Railway is lifeline of India.. Ever Since the evolution of human being on this earth it has been a matter of immense curiosity for them to invent new things in life to make life easier and hassle free. Owing to its nature humans have always kept inventing and discovering for better livelihood. Going back to our past we see some Great inventions of mankind and one such is that of Railway.

The noval plan for the introduction of Indian rail system, Transformed whole history of INDIAN RAILWAY. The innoavative plan was first propsed in 1832, however auxiliary actions were taken for over a decade. In the year 1844, private enterpreneurs were allowed to launch a rail system by lord Hardinge, who was the Governer-Genral of India. By the year 1845, two companies were formed and east India Company was requested to support them in the matter.

  INDIAN RAILWAY have been divide into nine (9) zones- Western, Central, Northan, North Eastern, Northeast, Frontier, Southern, South Central, South-central & South-eastern covering the largest route length of cover 63000 kms of total Indian boundary. The last stations of the four directional boundaries are West-Mumbai South-Kanyakumari, East-Guwahati, and North-Jammu.

There are five types of trains which are running in the Indian Railways that are given below:

  1. Passenger train

                     2. Mail/Express

                     3. Shatabadi train

                     4. Jan-Shatabdi

                     5. Rajdhani

The Shatabdi train is the fastest among all these trains and covering only some of the destination. In the Indian Railway Coach Maintenance Department is the most important. There are many work handles in POH SHOP, these are given below:

  • Carraige Poh Shop
  • Wagon Poh Shop
  • Diesel Poh Shop
  • Production Poh Shop
  • Electric Rolling Poh Shop
  • Electric Shop

There are many production-units from where the coaches are newly manufactured that are:

  • Chittaranjan Locomotive Works
  • Diesel Locomotive Works, Varanasi
  • Integral Coach  Factory, Perambur
  • Rail Coach Factory, Kapurthala
  • Wheel & Axle Plant, Bangalore
  • Diesel Component Works, Patiala
  • The research Design and Standard Organization, Lucknow, provides vital inputs in R&D towards modernization.
  • 6 prestigious public sector undertaking : IRCON, RITES, CRIS, CONCOR, IRFC and Konkan Railway corporation. 

When, the coach is prepared in the POH SHOP. The train go to the yard. A Railway yard is an area having a network of railway tracks and siding for Storage and maintenance of cars and engineers. In the marshalling yard of Indian railway in which trains are assembled and good are loaded. In the marshalling yard railway wagons are Shunted and made up into trains.

In the yard, the  coaches are maintained in 3-schedules namely:-

1.A-Schedule

2.B-Schedule and

3.C-Schedule

  1. A-Schedule:- A Schedule is primary schedule. This schedule is done every month for any coach.
  2. B-Schedule:- This schedule is done in any coach after 3-month in the yard.
  3. C-Schedule:- This schedule is done in any coach after 6-month in the yard.

IOH means intermediate over holding. In this shop the coaches are maintained any time when necessary.

Apart from these register the organization has to publish reports about the coaches to supervisior.

Seceondary Detachment

Some times during running of the train some faults occur in a coach or number of coaches or entire rake. Then coaches are detached from that rake and sent for maintenance. This is called secondary detachment of coach.

My Job is to convert these entire manual jobs to a computerized system. My project work is the outcome as solution to the aforementioned manual jobs. This project is being done under DRM Office, Danapur (ECR).

Online Crime Investigation System Project in Java

Project Abstract: This Online Crime Investigation System software presents the part of an organization work as per the requirements , specifications and conditions mentioned in the user manual . This application s/w has been developed and completed successfully and also tests successfully by taking “Test Cases” It is user friendly and has all the needed menu options , which can be utilized by the user to perform the desired operations .Moreover help messages are provided which will help any authorized user from using the system without trouble.

The proposed system is not limited presently. Presently we have to login to the system online and post the complaints. We can further develop the system by using “Voice Recognition System”. So this project has got scope to get developed in the near future. The scope of the project exists throughout the life of the product development, testing and implementation.

Deployment of  Application:

1) Copy Online Crime Investigation System application folder to

F:\Tomcat5.5.9\webapps\

2) Click on start.bat in bin folder of tomcat

3) Create User in Oracle as following:

CREATE USER OCR IDENTIFIED BY OCR;

GRANT DBA TO OCR;

CONN OCR/OCR

Now place the all tables in table.txt file at the SQL Command Line

And type following command

COMMIT;

4) Create user DataSourceName(DSN) as

click  –> Start —> Control Panel—> Administrative Tools

Software Requirements:

  • Operating System: Windows 98 or above
  • Front end : HTML & JAVA SCRIPT,J2EE(JSP,servlets,Ajax),
  • Back end : Oracle 8i
  • Web Server: Tomcat 5.5.9
  • Front end  : HTML & XML
  • Middleware : J2EE(JSP)
  • Back end  : Oracle 8i
  • Application server : Web logic 7.0

Crime Investigation System Screen Shots:

1.    Crime Investigation System

HomePage

Homepage for the Crime Investigation System Application

Overview

Functional Overview

This module/screen is the Homepage for the Crime Investigation System Application.

Technical Overview

This module Admin or Police Department or Customer can login through screen and customer can register.

Navigations

Customer Login ->Customer LoginScreen

AdminLogin ->Admin Login Screen

Home ->Application Homepage

Department Login ->Department Login Screen

Registration ->Customer Registration Form

ADMIN MODULE

2.    Admin Login Screen

Admin Login Screen

2.1.1    Overview

Functional Overview

This module/screen is used to Admin Login Process.

Technical Overview

  1. This module takes the valid Admin Username and password.
  2. The particulars are valid you will get Admin Homepage otherwise it will displays the message “Invalid Login Information”.

Navigation

AdminLogin->AdminLoginScreen

Action Controls

Control
Name
Type Description Action
Login button Gets the particulars of the Admin Login Details. Admin Homepage
Clear Button Clear the fields on the form Login Screen

3.    Admin Home Screen

3.	Admin Home Screen

3.1.1    Overview

Functional Overview

This module/screen is used to operate Administration Module.

Technical Overview

  1. This module is used to create new Police Departments and updating the existed department details.
  2. This module is used to create new thief Information and updating the existed thief information
  3. Creating New Caution Information.

Navigation

AdminLoginProcess->AdminHomePage Screen

Action Controls

Control
Name
Type Description Action
New Department HyperLink Displays the New Department  registration Form Department Registration Form
All Departments HyperLink Displays the existed department details screen List of departments
New Thief Information Hyperlink Displays the New thief  registration Form Thief  Registration Form
Thief Information HyperLink Displays the existed thief details screen List of Thief Information
Caution HyperLink Displays Caution registration Screen Caution Registration Form

4.    Department Registration Screen

Department Registration Screen

4.1.1    Overview

Functional Overview

This module/screen is used to register New Department Information.

Technical Overview

  1. This module takes the valid new Department Information and Login details.
  2. These New Department particulars will be stored into “POLICE_DEPARTMENT” database table and login details into “LOGIN_MASTER” table.

Navigation

New Department->Department Registration Screen

Action Controls

Control
Name
Type Description Action
Register button Gets The new Department    information and login details from the form. Stores the department data into table POLICE_DEPARTMENTlogin details into table LOGIN_MASTER
Clear Button Clears the field in the form New Department Registration form will be displayed

5.    Updating Department Details Screen

SCREEN1

5.	Updating Department Details Screen

SCREEN2

Updating Department Details Screen1

5.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Department and Updating the department  Information according  to the Department Id.

Technical Overview

  1. Click on Update then it will takes the Department Id and displays Screen2 (Popup Window).

Navigation

All Departments->Department Details

Action Controls

Control
Name
Type Description Action
Update button Displays the Department  information of selected Department Id. Displays the Department Information Screen(Screen2)
Close Button Closes the Department Modification form Displays All Department Screen (Screen1)

6.    Thief Registration Screen

Thief Registration Screen

6.1.1    Overview

Functional Overview

This module/screen is used to register New Thief Information.

Technical Overview

  1. This module takes the valid new Thief Information.
  2. These New Thief particulars will be stored into “THIEVES” database table .

Navigation

New Thieves Information->Thief Registration Screen

Action Controls

Control
Name
Type Description Action
Register Button Gets The new Department    information and login details from the form. Stores the thieves data into table THIEVES
Clear Button Clears the field in the form New Thieve Registration form will be displayed

7.    Updating Thief Details Screen

Updating Thief Details Screen

SCREEN1 

7.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Thieves and Updating the thief Information according  to thief Id.

Technical Overview

  1. Click on Update then it will takes the thief Id and displays Screen2 (Popup Window).
  2. If you select thief category then according to the selected Category it will Displays Screen3

Navigation

Thieves Information->Thieved Information

Action Controls

Control
Name
Type Description Action
Update button Displays the Thief   information of selected Thief Id. Displays the Thief Information Screen(Screen2)
Close Button Closes the Thief Modification form Displays All Department Screen (Screen1)

8.     Caution Registration Form

Caution Registration Form

7.1.2    Overview

Functional Overview

This module/screen is used to Create New Cautions.

Technical Overview

  1. This module takes the valid caution Information and will be stored into CAUTIONS Data Base Table.

Navigation

Caution->Caution Registration Form

Action Controls

Control
Name
Type Description Action
Save button Gets the required input details. caution Information and will be stored into CAUTIONSData Base
Clear Button Clears the fields data New Caution Form will be displayed

DEPARTMENT MODULE 

8.    Department Login Screen

Department Login Screen

8.1.1    Overview

Functional Overview

This module/screen is used Department Login Process.

Technical Overview

  1. This module takes the valid Username and password.
  2. The particulars are valid you will get Department Homepage otherwise it will displays the message “Invalid Login Information”.

Navigation

Department Login->Department Login Screen

Action Controls

Control
Name
Type Description Action
Login button Gets the particulars of the Department Login Details. Department   Homepage
Clear Button Clears the Form Details New Login Screen Will be displayed

  

9.    Department HomePage

Department HomePage

9.1.1    Overview

Functional Overview

This module/screen is used to process the Department operations.

Technical Overview

  1. In This module department can see his complaint details and thief information.
  2. Updating complaint status and modifying the selected thief informtaion.

Navigation

Department Login Process -> Department Homepage. 

10.    Requested Complaints

Requested Complaints

10.1.1    Overview

Functional Overview

This module/screen is used Display the complaints Information.

Technical Overview

  1. Updating the complaint status by changing the options in the Modify column.
  2. In options when the complaint status is ‘Closed’ then only you will get new option ‘ReOpen’ in the options

Navigation

Requested Complaints->Complaints Status

Action Controls

Control
Name
Type Description Action
Update button Gets the modified details. Changes the status of the complaint in COMPLAINT_REG Table

 

11.    Thief Details Screen

Thief Details Screen

11.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Thieves and Updating the thief Information according  to thief Id.

Technical Overview

  1. Click on Update then it will takes the thief Id and displays Screen2 (Popup Window).
  2. If you select thief category then according to the selected Category it will Displays Screen3

Navigation

Thieves Information->Thieve Information

Action Controls

Control
Name
Type Description Action
Update button Displays the Thief   information of selected Thief Id. Displays the Thief Information Screen(Screen2)
Close Button Closes the Thief Modification form Displays All Department Screen (Screen1)

 

12. Customer Information

Customer Information

11.1.2    Overview

Functional Overview

This module/screen is used to Display all registered Customer Details

Navigation

Customer Information->Customers Information Screen

CUSTOMER MODULE 

12.    Customer Registration Screen

Customer Registration Scree

12.1.1    Overview

Functional Overview

This module/screen is used to Customer Registration.

Technical Overview

  1. This module takes the valid new Customer Information and Login details.
  2. These New Customer particulars will be stored into “CUSTOMER_MASTER” database table and login details in “LOGIN_MASTER”.

Navigation

Registration->Customer Registration Screen

Action Controls

Control
Name
Type Description Action
Register Button Gets The new Customer information and login details from the form. Stores the employee data into table CUSTOMER_MASTER
Clear Button Clears the field in the form New Registration form will be displayed

13.    Customer Login Screen

13.	Customer Login Screen

13.1.1    Overview

Functional Overview

This module/screen is used Customer Login Process.

Technical Overview

  1. This module takes the valid Username and password.
  2. If The particulars are valid you will get Department Homepage otherwise it will displays the message “Invalid Login Information”.
  3. If you forgot your password then click on Forget Password option.

Navigation

Customer Login->Customer Login Screen

Action Controls

Control
Name
Type Description Action
Login button Gets the particulars of the Customer  Login Details. Customer    Homepage
Clear Button Clears the Form Details New Login Screen Will be displayed

 

14.    Customer HomePage

Customer HomePage

14.1.1    Overview

Functional Overview

This module/screen is used to process the Customer operations.

Technical Overview

  1. In this module customer can register his complaints and update the complaints.
  2. Customer can modify the complaint information, if the status is “Pending”.
  3. Checking the status of the complaints.
  4. Displaying all department details.
  5. Displaying all thief information.
  6. Changing the personal details.
  7. changing the password.

Navigation

Customer  Login Process -> Customer  Homepage

15.    Complaint Registration Screen

Complaint Registration Screen

15.1.1    Overview

Functional Overview

This module/screen is used to register the new Complaint

Technical Overview

  1. This module takes the valid new Complaint Information.
  2. These New Complaint particulars will be stored into “COMPLAINT_REG” database table.

Navigation

Complaint Registration->Complaint Registration Screen

Action Controls

Control
Name
Type Description Action
Register button Gets The new Compliant   from the form. Stores the Complaint data into table COMPLAINT_REG
Clear Button Clears the field in the form New Complaint  Registration form will be displayed

16.    Thief Details Screen

Thief Details Screen

16.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Thieves Information.

Navigation

Thieve Information->Thieve Information

17.    Department Details Screen

 Department Details Screen

17.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Departments Information.

Navigation

Departments->Department Information

18.    Changing Customer Profile

Changing Customer Profile

18.1.1    Overview

Functional Overview

This module/screen is used to Change the Customer Information.

Technical Overview

  1. This module takes the modified Customer Information from (Screen1).
  2. These New modified   particulars will be updated into “CUSTOMER_MASTER” database table.
  3. If u want update these modified details then click on “Update” in SCREEN1
  4. If you want to change the password then click on “Change Password” then “SCREEN2” will be displayed

Navigation

Change Profile->Customer Information

19.    Complaint Status Details Screen

 Complaint Status Details Screen

19.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Complaints.

Technical Overview

  1. This module takes the valid search options like datewise and compliant type.
  2. According to the selected search option the complaints will be displayed.
  3. Click on “Show All” button, If no option selected then it will display all complaints information.
  4. Click on “Search”  button without selecting any search option then it will display message “Select Valid Search option”

Navigation

Complaint Status->Complaint Information.

Retail Business Analytical Process Osmania University CSE Final Year Project Report

This Project gives an idea of analyzing the business requirements to make a decision. The data warehousing demonstrates the principle idea to store and evaluate the data.

The Project entitled Retail business analytical processing gives the idea to demonstrate all evaluated and strategic necessities of the business requirements related to sales, stock evaluation and the systematic approach for the decision making and support.

The Project usually deals with the supermarkets, departmental store processing and the customer requirements to evaluate to develop the business by constant providing the customer requirements.

The Existing System

The current system is the database system. The usual concept of the database is to manage information in the integrated form. The data base is the record of the related information maintained in the single record or system without any error and effort for the easy accessibility of the user. The principle is to provide information in an easy, fast and less cost and effective way to the user. The database designing needs the various criteria’s.

The Proposed System

The database warehousing is simple and general in use but the application software provides the various applications.

Recording and Storing Data

The recorded data is reliable and protected  as the other user cannot retrieve the data.

Reading data online and reports

The data can be observed online

Analyzing data for identifying the business trends

The application module summarizes the data and presenting various summaries for each other databases. The process is called data warehousing.

The data warehousing is important tool in the information technology. The data warehousing gives the business to make strategic decisions. The data ware housing brings out the stored data to be evaluated.

The Oracle has already implemented the data ware housing application added in the Oracle 7 version in the early 1990. The Oracle 8, Oracle 8i, Oracle 9i has the additional features of the data ware housing to enhance the performance and management of the huge data warehouses. 

UML Diagrams of Java and Oracle Mobile Management System

UML Diagrams of Mobile Management System

The unified modeling language is a language for specification, constructing, visualizing and documenting the software and its components.

The UML is a graphical language with set of rules and syntaxes. The goal of UML is to keep the modeling simple.

ACTIVITY DIAGRAM

            Activity diagram is used to model an entire business process. The purpose of the E-R Diagram and activity diagram is below.


Activity Diagram for Computerized Mobile Store Management System

Activity Diagram for Computerized Mobile Store Management System                                                                                             

 Activity Diagram for Mobile Phone Administration

Activity Diagram for Mobile Phone Administration

 Activity Diagram for Customer Administration

Activity Diagram for Customer Administration

 Activity Diagram for Bill administration

Activity Diagram for Bill administration

 Activity Diagram for Sales Reports

Activity Diagram for Sales Reports

USE CASE DIAGRAM

 

Usecase Diagram for Computerized Mobile Store Management System

 Usecase Diagram for Computerized Mobile Store Management System.

Use Case Descriptions

  • Mobile Phone Administration:

In the “Mobile Phone Administration” the Administrator adds, updates, searches, and deletes the Mobile Phones details on his system.

Add a new Mobile Phone:

Here the administrator adds the new Mobile Phones into his system. Here administrator enters the Mobile details like MobileId, MobileModel, Mobile Price, Mobile Phone Color, etc.

Search for a Mobile Phone:

Here the administrator searches a Mobile Phone details by entering the input like Mobileid, Mobile Phone, and Price.

Update a Mobile Phone Details:

Here the Administrator Updates the Mobile Phone details by modifying the Mobile Phone details.

Delete a Mobile Phone:

            Here the Administrator Deletes a Phone details by entering the details like MobileId or IMEI no.

  • Customer Administration:

In the “Customer Administration” the administrator adds, updates, searches, and deletes the customer details on his system.

                   Add a new Customer:

Here the administrator adds the new Customer details into his system. Here administrator enters the Customer Name, Customer Address, Mobile purchased, MobileId etc.

Search for a Customer:

            In the ‘Search for a Phone’ system the administrator searches a Customer details by entering the input like CustomerId, Customer Name.

Update a Customer Details:

            In the ‘Update a Customer Details’ system the administrator Updates the details by modifying the details like Customer Address, Customer credit details.

Delete a Customer:

            In the ‘Delete a Customer’ system the administrator Deletes a Customer Details by entering input like CustomerId. 

  • Bill Administration:

In the “Bill Administration” the administrator generates and searches the bills.

Generate a Bill:

Here the Administrator generates the bill for sold Mobiles. Here he enters the information like Customer Name, Customer Address, Mobile Purchased, MobileId.

Search for a Bill:

Here the Administrator searches the bills by entering the details like Billid. 

  • Sales Reports:

                        In the “Sales Reports” the administrator can generate the Sales Reports for daily, monthly and yearly.

                        Daily Reports:

                        Here the Administrator can generate the Daily Sales Reports by giving the  input information like Date on which the Sales Reports are needed.

                        Monthly Reports:

                        Here the Administrator can generate the Monthly Sales Reports by giving  the input information like Month and Year on which the Sales Reports are                             needed.

                        Yearly Reports:

                        Here the Administrator can generate the Yearly Sales Reports by giving the input information like Year on which the Sales Reports are needed. 

SEQUENCE DIAGRAM

Sequence Diagram For Computerized Mobile Store Management System

Sequence Diagram For Computerized Mobile Store Management System 

CLASS DIAGRAMS

Relationships between identified classes

Relationships between identified classes.

E-R Diagrams & Database of Mobile Shop MCA Project

Oracle Database Table Description for Mobile Store Java Project Report

Tables: Login

Description: Stores the information of User Id and password

  Field    Type    Size    Key Description
Username Varchar 30 Not null Admin Identification
Password Varchar 20   Password

Tables: newcustomer_details

Description: Stores the information of Customer.

  Field    Type    Size    Key Description
Cid  Int 4 Not null Customer Identification
Cname Varchar  20     Customer Name
Pdate Date     Purchase Date
Paidamt Int 7   Paid Amount
Balamt Int 7   Balance Amount
Refid Int 3   Reference Id
Date Of Birth Date     Date of Birth
Age Int 3   Age
Gender Varchar 7   Gender
Dno Varchar 10   Door No
Street Varchar 15   Street
City Varchar 20   City
State Varchar 20   State
Phno Bigint 15   Phone Number
Mob_Purchase Varchar 2000   Mobiles Purchased

Tables: newmobile_details

Description: Stores the information of Mobile Phones.

  Field    Type    Size    Key Description
Phone_Id  Varchar 20 Not null Mobile Phone Id
Mobile_model Varchar 15   Mobile Phone Model
Mobile_name Varchar 20   Mobile Phone Name
Pcolor Varchar 10   Mobile Phone color
Imeino Varchar 20   IMEI No.
Mdate Date     Manufacture Date
Accessories Varchar 55   Accessories

 Tables: newbill

Description: Stores the information of Mobile Related Bill Details.

  Field    Type    Size    Key Description
Bid Int 4 Not null Bill Id
Bill Date Date     Bill Date
Cname Varchar 20   Customer Name
Price Int 7   Total Price
Amtpaid Int 7   Amount Paid
Mob_purchased Varchar 2000   Mobiles Purchased
Mob_Name Varchar 20   Mobile Name
Mob_Price Int 8   Mobile Price
Mob_color Varchar 10   Mobile Color
Mob_imei Varchar 20   Mobile Imei

Entity Relationship diagrams of Mobile Shop MCA Project

E-R Diagrams & Database of Mobile Shop MCA Project

Related Academic Project: Shop Management System

  • In this application, a user (Admin), can log in as an Admin or Staff to perform different activities.
  • By using this application the admin user can maintain the Staff and Customer Bill records and also manipulate it.

Methods of Software Development:

  • Rapid application development for making the user interface screens.
  • Prototyping Model used for development

Operating System and Languages:

  • Shop Management System is designed in .net.
  • Admin Or staff can Manage Products and Bill. The application is connected with Database using JDBC architecture.