Case Tools Lab

CS6511 CASE TOOLS LABORATORY LTPC 0032
SYLLABUS
To develop a mini-project by following the 9 exercises listed below.
1. To develop a problem statement.
2. Identify Use Cases and develop the Use Case model.
3. Identify the conceptual classes and develop a domain model with UML Class diagram.
4. Using the identified scenarios, find the interaction between objects and represent them
using UML Sequence diagrams.
5. Draw relevant state charts and activity diagrams.
6. Identify the User Interface, Domain objects, and Technical services. Draw the partial
layered, logical architecture diagram with UML package diagram notation.
7. Develop and test the Technical services layer.
8. Develop and test the Domain objects layer.
9. Develop and test the User interface layer.
SUGGESTED DOMAINS FOR MINI-PROJECT:
1. Passport automation system.
2. Book bank
3. Exam Registration
4. Stock maintenance system.
5. Online course reservation system
6. E-ticketing
7. Software personnel management system
8. Credit card processing
9. e-book management system
10. Recruitment system
11. Foreign trading system
12. Conference Management System
13. BPO Management System
14. Library Management System
15. Student Information System
TOTAL: 45 PERIODS
1
List of Experiments
S.No Experiments Page No

1 Passport automation system
2 Book bank management system
3 Exam registration system
4 Stock maintenance system
5 Online course reservation system
6 E-ticketing
7 Software personnel management system
8 Credit card processing
9 E-book management system

Recruitment system
10
11 Foreign trading system
12 Conference management system
13 Bpo management system
14 Student information system
2
EXNO: 1 PASSPORT AUTOMATION SYSTEM
DATE:
AIM
To develop the Passport Automation System using ArgoUML tools, Java and Mysql.
PROBLEM ANALYSIS AND PROJECT PLAN
To simplify the process of applying passport, software has been created by designing through
ArgoUML tool, using Java as a front end and Mysql as a back end. Initially the applicant login the passport
automation system and submits his details. These details are stored in the Database and verification process
done by the passport administrator, regional administrator and police the passport is issued to the applicant. .
Passport Automation System is used in the effective dispatch of passport to all of the applicants. This
system adopts a comprehensive approach to minimize the manual work and schedule resources, time
in a cogent manner.
The core of the system is to get the online registration form (with details such as name, address etc.,)
filled by the applicant whose testament is verified for its genuineness by the Passport Automation
System with respect to the already existing information in the Database.
This forms the first and foremost step in the processing of passport application. After the first round of
verification done by the system, the information is in turn forwarded to the regional administrator's
(Ministry of External Affairs) office.
The application is then processed manually based on the report given by the system, and any
forfeiting identified can make the applicant liable to penalty as per the law.
The system forwards the necessary details to the police for its separate verification whose report is
then presented to the administrator. After all the necessary criteria have been met, the original
information is added to the Database and the passport is sent to the applicant.
S.No. SOFTWARE REQUIREMENTS SPECIFICATION

1.0 Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms and Abbreviations
1.4 Reference
1.5 Technology to be used
1.6 Tools to be used
1.7 Overview
2.0 Overall Description
2.1 Productive description
2.2 System function
2.3 User Characteristic
2.4 Constraints
2.5 Assumption and Dependences
1.0 INTRODUCTION
Passport Automation System is an interface between the Applicant and the Authority responsible
for the Issue of Passport. It aims at improving the efficiency in the Issue of Passport and reduces the
complexities involved in it to the maximum possible extent.
1.1 PURPOSE
If the entire process of 'Issue of Passport' is done in a manual manner then it would take several
months for the passport to reach the applicant. Considering the fact that the number of applicants for
passport is increasing every year, an Automated System becomes essential to meet the demand. So this
system uses several programming and Database techniques to elucidate the work involved in this
process. As this is a matter of National Security, the system has been carefully verified and validated in
order to satisfy it.
1.2 SCOPE
The System provides an online interface to the user where they can fill in their personal details.
The authority concerned with the issue of passport can use this system to reduce his workload and process
3
the application in a speedy manner.
Provide a communication platform between the applicant and the administrator.
Transfer of data between the Passport Issuing Authority and the Local Police for verification of applicant's
information.
1.3 DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS
Administrator - Refers to the super user who is the Central Authority who has been vested with the privilege
manage the entire system. It can be any higher official in the Regional Passport Office of Ministry of External
Affairs.
Applicant He is the one who wishes to obtain the Passport.
PAS - Refers to this Passport Automation System.
1.4 REFERENCES
It is given in IEEE Software Requirement Specification format.
1.5 TECHNOLOGIES TO BE USED
Java 6.0
1.6 TOOLS TO BE USED
ArgoUML tool (for developing UML Patterns)
1.7 OVERVIEW
SRS includes two sections overall description and specific requirements - Overall description will
describe major role of the system components and inter-connections. Specific requirements will describe roles
& functions of the actors.
2.0 OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE
The PAS acts as an interface between the 'applicant' and the 'administrator'. This system tries to
make the interface as simple as possible and at the same time not risking the security of data stored in. This
minimizes the time duration in which the user receives the passport.
2.2 SYSTEM FUNCTIONS
Secure Registration of information by the Applicants.
Message box for Passport Application Status Display by the Administrator.
Administrator can generate reports from the information and is the only authorized Personnel to add the eligible
Application information to the Database.
2.3 USER CHARACTERISTICS
Applicant - They are the people who desire to obtain the passport and submit the information to
the Database.
Administrator - He has the certain privileges to add the passport status and to approve the issue of passport.
He may contain a group of persons under him to verify the documents and give suggestion whether or not to
approve the dispatch of passport.
Police - He is the person who upon receiving intimation from the PAS, perform a personal verification of
the applicant and see if he has any criminal case against him before or at present. He has been vetoed with the
power to decline an application by suggesting it to the Administrator if he finds any discrepancy with the
applicant. He communicates via this PAS.
2.4 CONSTRAINTS
The applicants require a computer to submit their information.
Although the security is given high importance, there is always a chance of intrusion in the web world
which requires constant monitoring.
The user has to be careful while submitting the information. Much care is required.
2.5ASSUMPTIONS AND DEPENDENCIES
The Applicants and Administrator must have basic knowledge of computers and English Language.
The applicants may be required to scan the documents and send.
UML DIAGRAMS
S. No. UML DIAGRAMS
1. Use Case diagram
2. Class diagram
4
3. Sequence diagram
4. Collaboration diagram
5. State Chart diagram
6. Activity diagram
7. Component diagram
8. Deployment diagram
9. Package diagram
1. USE CASE DIAGRAM
Use case is shown as an ellipse containing the name of use case .An actor is shown as a stick
figure with the name below it. Use case diagram is a graph of actors.
DOCUMENTATION OF USECASE DIAGRAM

The actors in use case diagram are Applicant, regional administrator, Database, passport
Administrator, Police.
The use cases are Login, give details, logout, collect details, verification and issue.
The actors use the use case is denoted by the arrow.
The login use case checks the username and password for applicant, regional administrator,
passport administrator and police.
The submit details use case is used by the applicant for submitting his details
The check status use case is used by the applicant for checking the status of the application
process.
The get details, verify and store verification use case is used by passport administrator,
regional administrator, and police.
The details use case is used for getting the details form the Database for verification The verify
use case is used for verifying the details by comparing the data in the Database.
The store verification use case is to update the data in the Database
And finally the issue passport use case is used by the passport administrator for issuing
passport whos application verified successfully by all the actor
2. CLASS DIAGRAM
A class is drawn as rectangle box with three compartments or components separated by horizontal
lines. The top compartment holds the class name and middle compartment holds the attribute and bottom
compartment holds list of operations.
5
DOCUMENTATION OF CLASS DIAGRAM
APPLICANT-The applicant has attribute such as name and password and operations are login, give
details and logout. The applicant login and fill the details that are required for applying the
passport .After applying the person can view the status of the passport verification process.
THE DATABASE-The Database has attributed such as name and operation is store. The purpose is
to store the data.
REGIONAL ADMINISTRATOR- The regional administrator has attribute such as name and
operation are get details, verify details and send. The regional administrator gets the details form
Database and verify with their Database
PASSPORT ADMINISTRATOR-The passport administrator has attributed such as name and
operation are get details, verify details and issue.
3. SEQUENCE DIAGRAM
A sequence diagram shows an interaction arranged in time sequence. It shows object participating
in interaction by their life line by the message they exchange arranged in time sequence. Vertical
dimension represent time and horizontal dimension represent object.
DOCUMENTATION OF SEQUENCE DIAGRAM:

The applicant login the Database and give his details and Database store the details.
The passport administrator get the details from the Database and do verification and the forward to
6
regional administrator.
The regional administrator get details form passport administrator and perform verification and send
report to passport administrator.
The police get the details form passport administrator and perform verification and send report to
passport administrator.
4. COLLABORATION DIAGRAM
A collaboration diagram is similar to sequence diagram but the message in number format. In
a collaboration diagram sequence diagram is indicated by the numbering the message. A collaboration
diagram, also called a communication diagram or interaction diagram.
DOCUMENTATION OF COLLABORATION DIAGRAM

The applicant, passport administrator, regional administrator, police and Database functions are show
in sequence number.
The applicant first login the passport automation system and submit his details the passport
administrator, regional administrator and police verification are denoted.
5. STATE CHART DIAGRAM
The state chart diagram contains the states in the rectangle boxes and starts in indicated by the dot and
finish is indicated by dot encircled. The purpose of state chart diagram is to understand the algorithm in the
performing method.
7
DOCUMENTATION OF STATE CHART DIAGRAM
The states of the passport automation system are denoted in the state chart diagram
Login state represent authentication for login the passport automation system.
Police, regional administrator and passport administrator get necessary details and verification of the
applicant are denoted from the Get detail state and verification state.
6. ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities and actions with
support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams can be
used to describe the business and operational step-by-step workflows of components in a system. An activity
diagram shows the overall flow of control. An activity is shown as a rounded box containing the name of the
operation
DOCUMENTATION OF ACTIVITY DIAGRAM

The activities in the passport automation system are login, submit details, get details, issue passport
and penalty and verification.
In the login activity applicant give username and password and then login into the passport
automation system after then fill the details that are required for application.
7. COMPONENT DIAGRAM
The component diagram is represented by figure dependency and it is a graph of design of figure
dependency. The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by communication
association.
8
DOCUMENTATION OF COMPONENT DIAGRAM
The components in the passport automation system are passport automation system, applicant,
passport administrator, regional administrator, and police.
8. DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical deployment of
artifacts on deployment targets Dependencies are represented by communication association.
The basic element of a deployment diagram is a node of two types:
DEVICE NODE A physical computing resource with processing and memory service to execute software
such as a typical computer or a mobile phone.
EXECUTION ENVIRONMENT NODE-- This is a software computing resource hat runs within an outer
node and which itself provides a service to host an execute other executable software element.
DOCUMENTATION OF DEPLOYMENT DIAGRAM

The device node is passport automation system and execution environment node is applicant passport
administrator, regional administrator, and police.
9. PACKAGE DIAGRAM:
A package diagram is represented as a folder shown as a large rectangle with a top attached to
its upper left corner. A package may contain both sub ordinate package and ordinary model elements. All
UML models and diagrams are organized into package. A package diagram in unified modeling language
depicts the dependencies between the packages that make up a model.
DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the passport automation system are user interface, domain and technical service
layers.
The user interface layer- represents the user interface components such as web, applicant, passport
administrator, police, and regional administrator.
9
The domain layer- has major actions such as give and get details, verification and issues.
Technical service layer- authenticated user only can access the technical services.
FORMS
package pass;
public class Main {
public static void main(String[] args) {
// TODO code application logic here
new pass().setVisible(true);
}
}
package pass;
public class select extends javax.swing.JFrame {
/** Creates new form select */

public select() {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new user().setVisible(true);
}

setVisible(false);
new login().setVisible(true);
}
10
setVisible(false);
}
setVisible(false);
}
package pass;
public class user extends javax.swing.JFrame {
/** Creates new form user */

public user() {
initComponents();
}
setVisible(false);
new registre().setVisible(true);
}

setVisible(false);
new alogin().setVisible(true);
}
import java.sql.Connection;
import java.sql.DriverManager;
11
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
import net.proteanit.sql.DbUtils;
public class registre extends javax.swing.JFrame {
/** Creates new form registre */

public registre() {
initComponents();
}
String name=jTextField3.getText();
String dob=jTextField1.getText();
String username=jTextField4.getText();
String password=jPasswordField1.getText();
String adds=jTextArea1.getText();
String id=jTextField2.getText();
try {
PreparedStatement psm=null;
Class.forName("com.mysql.jdbc.Driver")
conn = DriverManager.getConnection("jdbc:mysql://localhost:3306/stock", "root", "");
String sql="insert into pass
values('"+name+"','"+dob+"','"+username+"','"+password+"','"+adds+"','"+id+"')";
Statement stm=conn.createStatement();
stm.executeUpdate(sql);
JOptionPane.showMessageDialog(null, "Successfully Registered!!");
new cancel().setVisible(true);
} catch(Exception e) {
JOptionPane.showMessageDialog(null, "Error Occured!");
}
}
setVisible(true);
}
12
EX NO:2
DATE:
BOOK BANK MANAGEMENT SYSTEM
AIM:
To develop a project of Book bank management system using ArgoUML Software and to
implement the software in Java.
PROBLEM ANALYSIS AND PROJECT DESIGN
The book bank management system is software in which a member can register themselves and
then he can borrow books from the book bank. It mainly concentrates on providing books for engineering
students. The process of members registering and purchasing books from the book bank are described
sequentially through following steps: First the member registers himself if he was new to the book bank.
Old members will directly select old member button. They select their corresponding year. After selecting
the year they fill the necessary details and select the book.
SOFTWARE REQUIREMENT SPECIFICATION:
S.No. CONTENTS
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
FUNCTIONAL
11 REQUIREMENTS
12 SOFTWARE REQUIREMENTS
13 HARDWARE REQUIREMENTS
1. INTRODUCTION
This system would be used by members who are students of any college to check the availability
of the books and borrow the books, and then the Databases are updated. The purpose of this document is
to analyze and elaborate on the high-level needs and features of the book bank management system. It
also tells the usability, reliability defined in use case specification.
2. OBJECTIVE
The main objective of the system is to design an online book-bank monitoring system to enable a central
monitoring mechanism of the book-bank be more faster and less error prone. Apart from this, help the
students acquire the right books for the syllabus at the right time, ensure availability of basic textbooks to
students against limited funds and develop students ability to handle property loaned to them.
3. OVERVIEW
The overview of this project is to design a tool for book bank so that it can be used by any book banks to
lend their books as well as colleges.
4. GLOSSARY
TERMS DESCRIPTION
MEMBER The one who registers himself and purchase books from the bank.
DATABASE Database is used to store the details of members and books.
ADMINISTRATOR The one who verifies the availability of book and issue them.
USER Member
SOFTWARE REQUIREMENT This software specification documents full set of features and function
SPECIFICATION Book bank management system that is performed in company website.
5. PURPOSE
The purpose of the book bank management system is to reduce the manual intervention.
13 ISO 9001:2008
6. SCOPE: The scope of this book bank management system is to act as a tool for book bank
administrator for quick reference, availability of the books.
7. FUNCTIONALITY
Many members will be waiting to take the book from the book bank at a single day.
8. USABILITY
User interface makes the book bank management system to be efficient. That is the system will
help the member to register easily and helps them to get their books easily. The system should be
user friendly.
9. PERFORMANCE
It describes the capability of the system to perform the book bank management process of the
applicant without any error and performing it efficiently.
10. RELIABILITY
The book bank management system should be able to serve the applicant with correct information
and day-to-day update of information.
11. FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system. That is the
services that are provided to the member who borrows book.
12. SOFTWARE REQUIREMENTS
Front end: ArgoUML and Java.
Back end: Mysql.
13. HARDWARE REQUIREMENTS
Processor : Intel Core I5
RAM : 256 Mb
Operating system : Fedora v12
Free disk space : 1Gb
UML DIAGRAMS
1. USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between systems and
users in a particular environment and related to a particular goal. It is represented using ellipse. Actor is
any external entity that makes use of the system being modeled. It is represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are member and Database. The use cases are the activities
performed by actors.
The member will register himself in the book bank.
After registration he will select the year to which he belongs
14 ISO 9001:2008
After selecting he will select books
Database will verify the status of book and the books will be given.
2. CLASS DIAGRAM
Class diagram in the unified modeling language (UML) is a type of static structure diagram that describes
the structure of a system by showing the system's classes, their attributes, and the relationships between
the classes. It is represented using a rectangle with three compartments.
DOCUMENTATION OF CLASS DIAGRAM:

This class diagram has 8 classes:
Member details class- is the class name. Its attributes are name, father name, date of
birth, address, phone number, member id, college, degree, course and semester.
Administrator- is the class name. Its attributes are name, address, phone, mail id. Its operations
are authentication, verification and issue books.
Year-is the class name. Its attribute is year selection. Its operations are 1 st year,2nd year, 3rd year,4th
year.
Issue for 1st year-is the class name. Its attributes are member code, member name, book code,
book name, and quantity. Its operation is issue.
Issue for 2nd year-is the class name. Its attributes are member code, member name, book code,
Issue for 3rd year-is the class name. Its attributes are member code, member name, book code,
4. SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that
shows how processes operate with one another and in what order. It is a construct of a Message Sequence
Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
15 ISO 9001:2008
DOCUMENTATION OF SEQUENCE DIAGRAM:
The sequence diagram describes the sequence of steps to show
The member registers himself in book bank
He will select the year
He selects the books given and the Database will update the status of book.
Then administrator will log in and verify the status of books.
If the book is available he will issue the book.
4. COLLABARATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction diagram. A
sophisticated modeling tool can easily convert a collaboration diagram into a sequence diagram and the
vice versa. A collaboration diagram resembles a flowchart that portrays the roles, functionality and
behavior of individual objects as well as the overall operation of the system in real time.
The collaboration diagram is to show how the member registers himself and borrow the book from the
book bank. Here the sequence is numbered according to the flow of execution.
5.ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams
16 ISO 9001:2008
can be used to describe the business and operational step-by-step workflows of components in a system.
An activity diagram shows the overall flow of control. An activity is shown as a rounded box containing
the name of the operation.

This activity diagram flow of stepwise activities performed in book bank management system.
The member registers himself in book bank
After that he will select the year.
He will select the books.
Database will update the status of book.
Database will update the details
Then the administrator will log in to his account.
After authentication he will verify the availability of book.
If available he will issue the book.
6. COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships between the
components of a system. It is represented by boxed figure. Dependencies are represented by
communication association.
17 ISO 9001:2008
The main component in this component diagram is online book bank management systems. And member
details, issue for first year, issue for second year issue for third year and issue for fourth year are
components comes under the main component.
7.DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical deployment of
artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes according
to the Deployments defined between them. It is represented by 3-dimentional box. Dependencies are
represented by communication association.

The processor in this deployment diagram is the book bank which is the main part and which are the some
of the main activities performed in the system. And issue for first year, issue for second year issue for
third year and issue for fourth year are some activities performed in this system.
8.PACKAGE DIAGRAM
A package diagram in unified modeling language depicts the dependencies between the packages that
make up a model. A Package Diagram (PD) shows a grouping of elements in the OO model, and is a
Cradle extension to UML. PDs can be used to show groups of classes in Class Diagrams (CDs), groups of
components or processes in Component Diagrams (CPDs), or groups of processors in Deployment
Diagrams (DPDs).
There are three types of layer. They are User interface layer, Domain layer and Technical services layer.
18 ISO 9001:2008
The three layers in the Book bank management system are
The User interface layer - consists of the web and member details. This layer describes
how the member goes to book bank and registers himself..
The Domain layer shows the activities that are performed in the book bank
management system. The activities are register and book issues..
The Technical service layer - the member details and verification details are stored in
the Database.
CODING AND FORMS
public class book extends javax.swing.JFrame {

public book() {
initComponents();
}
setVisible(false);
}
19 ISO 9001:2008
public class login extends javax.swing.JFrame {
/** Creates new form login */

public login() {
initComponents();
}
String s1=jTextField1.getText();
String s2=jPasswordField1.getText();
System.out.println(s1);
try
{
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:bookbank");
String s="select * from pass where username = '" +s1+"'and password = '"+s2+"'";
Statement stmt=connect.createStatement();
rs=stmt.executeQuery(s);
int count=0;
while(rs.next())
{
count++;
}
if(count==1)
new bb().setVisible(true);
else
JOptionPane.showMessageDialog(null,"Wrong Password");
}
catch (Exception e)
{
JOptionPane.showMessageDialog(null, e.getMessage());
}
}
setVisible(false);
}
20 ISO 9001:2008
public class bb extends javax.swing.JFrame {
/** Creates new form bb */

public bb() {
initComponents();
}
String author=jTextField2.getText();
try
{
Connection conn=DriverManager.getConnection("jdbc:odbc:bookbank");
String sql="insert into book values('"+name+"','"+author+"')";
setVisible(false);
new verify().setVisible(true);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, " Successfully Registered!!");
}
}
}
21 ISO 9001:2008
public class verify extends javax.swing.JFrame {
/** Creates new form verify */

public verify() {
initComponents();
}
}

new payment().setVisible(true);
}

try
{
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:bookbank");
String sq="select * from book" ;
rs=stmt.executeQuery(sq);
System.out.println("query executed");
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
} catch(Exception e)
22 ISO 9001:2008
{
System.out.println(e.getMessage()); } }
DATE: 3 EXAM REGISTRATION SYSTEM

AIM
To develop a project Exam Registration using ArgoUML Software and to implement the software
in Java.
PROBLEM ANALYSIS AND PROJECT PLANNING
The Exam Registration is an application in which applicant can register themselves for the exam. The
details of the students who have registered for the examination will be stored in a Database and will be
maintained. The registered details can then be verified for any fraudulent or duplication and can be
removed if found so. The Database which is verified can be used to issue hall tickets and other necessary
materials to the eligible students.
PROBLEM STATEMENT
The process of students accessing the registration application and applying for the examination by filling
out the form with proper details and then the authorities verify those details given for truth and
correctness are sequenced through steps
The students access exam registration application.
They fill out the form with correct and eligible details.
They complete the payment process.
The authorities verify or check the details.
After all verification the exam registration Database is finalized.
1. INTRODUCTION
Exam Registration application is an interface between the Student and the Authority
responsible for the Exams. It aims at improving the efficiency in the registration of exams
and reduces the complexities involved in it to the maximum possible extent.
2. OBJECTIVE
The main objective of Exam Registration System is to make applicants register themselves and
apply for the exam. Exam Registration System provides easy interface to all the users to apply for
the exam easily.
3. OVERVIEW
The overview of the project is to design an exam registration tool for the registration process
which makes the work easy for the applicant as well as the Authorities of Exam. Authorities of
the exam can keep track of and maintain the Database of the registered applicants for the exams.
4.GLOSSARY:
TERMS DESCRIPTION
Applicant can register himself by filling out the registration form and
APPLICANT OR STUDENT finally paying the payment for attending the exam.
Database is used to maintain and store the details of registered
DATABASE applicants.
SOFTWARE REQUIREMENT This software specification documents full set of features and function
SPECIFICATION for exam registration system that is performed in company website.
5. PURPOSE The purpose of exam registration system is to register for the exam in an easier way and to
maintain the registered details in an effective manner.
6. SCOPE
The scope of this Exam Registration process is to provide an easy interface to the applicants
where they can fill their details and the authorities maintain those details in an easy and effective way.
7. FUNCTIONALITY
The main functionality of registration system is to make the registration and Database for it to
be maintained in an efficient manner.
8. USABILITY
User interface makes the Exam Registration system to be efficient. That is the system will help
23 ISO 9001:2008
the applicant to register easily and helps the authorities to maintain details effectively. The system
should be user friendly. It describes the capability of the system to perform the registration process of
the applicant without any error and performing it efficiently.
9. RELIABILITY
The Exam Registration system should be able to serve the applicant with correct information
and day-to-day update of information.
Functional requirements are those refer to the functionality of the system. That is the services
that are provided to the applicant who apply for the Exam.
10. EXTERNAL INTERFACE REQUIREMANTS

SOFTWARE REQUIREMENTS
Front end: ArgoUML and Java
Back end: Mysql
HARDWARE REQUIREMENTS
Processor : Intel Core I5
RAM : 256 Mb
Operating system : Fedora v12
Free disk space : 1Gb
UML DIAGRAMS
The following UML diagrams describe the process involved in the Exam Registration system
Use case diagram
Class diagram
Sequence diagram
Collaboration diagram
State chart diagram
Activity diagram
Component diagram
Deployment diagram
Package diagram
USE CASE DIAGRAM
requirements. The use case is made up of a set of possible sequences of interactions between systems and
users in a particular environment and related to a particular goal. It is represented using ellipse.
Actor is any external entity that makes use of the system being modelled. It is represented using stick
figure.
24 ISO 9001:2008
The actors in this use case diagram are Student, Interface and Database. The use cases are the
activities performed by actors.
Student Fills out the form in the form filling process.
The interface checks and validates registered details.
Then the Database is searched for details and verified.
Database stores the details and returns acknowledgement.
CLASS DIAGRAM
`A class diagram in the unified modeling language (UML) is a type of static structure diagram
that describes the structure of a system by showing the system's classes, their attributes, and the
relationships between the classes. It is represented using a rectangle with three compartments. Top
compartment have the class name, middle compartment the attributes and the bottom compartment with
operations.
DOCUMENTATION OF CLASS DIAGRAM .

This class diagram has three classes applicant, recruiter and Database.
25 ISO 9001:2008
Studentis the class name. Its attributes are name, Address, DOB, Gender, College, Subjects,
Semester, Year, Degree, Branch and Payment. The operations performed in the students class are
form filling, search Database and receiving acknowledgement.
Registrations Interface is the class name. Its attributes are Login, Password and Database.
The operations performed are form verification, store in Database and send
acknowledgement.
Database is the class name. The operations performed are storing Search and storing the values
SEQUENCE DIAGRAM
1.Vertical dimension-represent time.
2.Horizontal dimension-represent different objects.
DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show
The applicant filling form and registering for exam.
The verification done by the interface and sending acknowledgement for registration.
Searching the Database with login and displaying it for maintenance.
COLLABORATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction diagram,. A
sophisticated modeling tool can easily convert a collaboration diagram into a sequence diagram and the
vice versa. A collaboration diagram resembles a flowchart that portrays the roles, functionality and
behavior of individual objects as well as the overall operation of the system in real time
26 ISO 9001:2008
The collaboration diagram is to show how the Student registers and the authorities maintain the
details of the registered students in the registration system. Here the sequence is numbered according to
the flow of execution.
STATE CHART DIAGRAM
The purpose of state chart diagram is to understand the algorithm involved in performing a
method. It is also called as state diagram. A state is represented as a round box, which may contain one or
more compartments. An initial state is represented as small dot. A final state is represented as circle
surrounding a small dot.
This state diagram describes the behavior of the system.
First state is form filling where the student fill the form to registration
system.
The next state is form verification by the interface.
Then store the details in the Database.
The student receives acknowledgement for registering.
Search Database with login information.
Display the searched data in the interface.
ACTIVITY DIAGRAM
the name of the operation
27 ISO 9001:2008
This activity diagram flow of stepwise activities performed registration system.
First the student fills the form.
The student details are verified and stored in Database.
Acknowledgement sent is received by student.
Search Database with login and if data present in the Database.
The searched data is displayed if available. .
COMPONENT DIAGRAM
The main component in this component diagram is Exam Registration system. Register,
verification and search details are the components comes under the main component.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical deployment
of artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes
according to the Deployments defined between them. It is represented by 3-dimentional box.
Dependencies are represented by communication association.
28 ISO 9001:2008
The processor in this deployment diagram is the Exam Registration system which is the main part
and the devices are the register, verify and search which are the some of the main activities performed in
the system
PACKAGE DIAGRAM
A package diagram in unified modelling language depicts the dependencies between the packages
that make up a model. A Package Diagram (PD) shows a grouping of elements in the OO model, and is a
Cradle extension to UML. PDs can be used to show groups of classes in Class Diagrams (CDs), groups of
Diagrams (DPDs).

The three layers in the exam registration system are
The User interface layer - consists of the form and login. This layer describes how the
applicant logins to the search and apply for the exam.
The Domain layer shows the activities that are performed in the Exam Registration
system. The activities are register and search the Database.
The Technical service layer get student details and the selected applicant details are
stored in the Database.
CODING AND FORMS
29 ISO 9001:2008
public class opening extends javax.swing.JFrame {
public opening() {
initComponents();
}
new register().setVisible(true);
}
}
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new opening().setVisible(true);
}
});
}
private javax.swing.JButton jButton1;
private javax.swing.JButton jButton2;
private javax.swing.JLabel jLabel1;
// End of variables declaration}
public class register extends javax.swing.JFrame {

public register() {
30 ISO 9001:2008
initComponents();
}
// student sd=new student();
String a=jTextField1.getText();
String b=jTextArea1.getText();
String c=jTextField2.getText();
String d=(String) jComboBox1.getSelectedItem();
String e=jTextField3.getText();
String f=jTextField4.getText();
String g=(String) jComboBox2.getSelectedItem();
String h=(String) jComboBox3.getSelectedItem();
String i=jTextField5.getText();
String j=jTextField6.getText();
student s=new student(a,b,c,d,e,f,g,h,i,j);

public void run() {
new register().setVisible(true);
}
});
}
STUDENT:
import java.sql.*;
public class student

{
public String name;
private String address;
private String dob;
private String gender;
private String college;
private String sub;
private String sem;
private String year;
private String deg;
private String branch;
private int pay;
//public database theDatabase;
/**
@roseuid 54BE161601DA
*/
public student(String name,String address,String dob,String gender,String college,String subjects,String
sem,String year,String deg,String branch )
{
try{
System.out.println(name+address+dob+gender+college+subjects+sem+year+deg+branch);
Connection conn=DriverManager.getConnection("jdbc:odbc:exam");
31 ISO 9001:2008
String sql="insert into studentdetails
values('"+name+"','"+address+"','"+dob+"','"+gender+"','"+college+"','"+subjects+"','"+sem+"','"+year+"','
"+deg+"','"+branch+"')";
JOptionPane.showMessageDialog(null, "sucessfully registerd") }
catch(Exception ex)
{
System.out.println(ex.getMessage());
JOptionPane.showMessageDialog(null, "error occured in connection");
}
}

public login() {
initComponents();
}
database db=new database(s1,s2);
}
public void run() {
}
});
}
DATABASE:
import java.sql.*;
public class database
{
public database(String s1,String s2)
{
try{
PreparedStatement pstm;
ResultSet rs;
32 ISO 9001:2008
Connection connect=DriverManager.getConnection("jdbc:odbc:exam");
String sq="select * from userdetails where username = '" +s1+"'and password = '"+s2+"'" ;
int count = 0;
while(rs.next())
{
count ++;
}
if(count == 1)
{
}
else
{
JOptionPane.showMessageDialog(null, "INVALID PASSWORD");
}}
import java.sql.*;
public verify() {
initComponents();
}
try
{
//String s=jTextField1.getText();
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:exam");
String sq="select * from studentdetails ";
// System.out.println("check:"+rs.getInt("count")
}
catch(Exception ex){
JOptionPane.showMessageDialog(null, "error occurs");} }
33 ISO 9001:2008
new opening().setVisible(true); }
public void run() {
new verify().setVisible(true); } }); }
Ex. No: 4 STOCK MAINTENANCE SYSTEM

Date:
AIM
To develop a project stock maintenance system using ArgoUML Software and to implement
the software in Java.
The Stock Maintenance System, initial requirement to develop the project about the
mechanism of the Stock Maintenance System is caught from the customer. The requirement are
analyzed and refined which enables the end users to efficiently use Stock Maintenance System. The
complete project is developed after the whole project analysis explaining about scope and project
statement is prepared.
PROBLEM STATEMENT .
The process of stock maintenance system is that the customer login to the particular site to
place the order for the customer product. The stock maintenance system are described sequentially
through steps
The customer login to the particular site.
They fill the customer details.
They place the orders for their product.
The vendor login and views the customer details and orders.
SOFTWARE REQUIREMENT SPECIFICATION
S.NO CONTENT
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
11 FUNCTIONAL REQUIRMENTS
1. INTRODUCTION
This software specification documents full set of features and function for online stock
maintenance system that is performed in company website. In this we give specification about the
customer orders. It tells the usability, reliability defined in use case specification.
2. OBJECTIVE
The main objective of the stock maintenance system is to maintain the stock. It provides the vendor to
maintain the stock in a precise manner.
3. OVERVIEW
The overview of the project is to design an online tool for the stock maintenance process which eases the
work for the customer as well as the companies. Companies can create their company forms according to
their wish in which the applicant can register.
TERMS DESCRIPTION
34 ISO 9001:2008
The customer can have the username and password after login to the system.
After login they directed to fill the customer details. And the customer places
their order. After placing orders they lead to verify all the details in a single form.
CUSTOMER Then they place the order successfully.
DATABASE Database is used to verify the customer details and orders.
VENDOR Vendor has the login id. After login vendor verify the customer details and orders
and maintain the stocks.
SOFTWARE This software specification documents full set of features and function for stock
REQUIREMENT maintenance system that is performed in application.
SPECIFICATION
5. PURPOSE
The purpose of stock maintenance system is to maintain the stock in an precise manner.
6. SCOPE
The scope of this stock maintenance system is to maintain the stock.
7. FUNCTIONALITY
The main functionality of the stock maintenance system is to maintain the stock.
8. USABILITY
User interface makes the stock maintenance system to be efficient. That is the system will help
the customer to place the details and orders easily and helps the vendor to maintain the stock
accurate. The system should be user friendly.
9. PERFORMANCE
It describes the capability of the system to maintain the stock without any loss of stock and
performing it efficiently.
10. RELIABILITY
The stock maintenance system should be able to maintain the stock with correct updates from day
to day placement of new orders from customer.
Functional requirements are those refer to the functionality of the system. That is the
services that are provided to the customer who places the orders.
UML DIAGRAMS
The following UML diagrams describe the process involved in the online recruitment
system
Use case diagram
Class diagram
Sequence diagram
Collaboration diagram
State chart diagram
Activity diagram
Component diagram
Deployment diagram
Package diagram
USE CASE DIAGRAM
requirements. The use case is made up of a set of possible sequences of interactions between systems
and users in a particular environment and related to a particular goal. It is represented using ellipse.
Actor is any external entity that makes use of the system being modeled. It is represented using stick
figure.
35 ISO 9001:2008
The actors in this use case diagram are customer, vendor and Database. The use cases are the
CUSTOMER:
Customer logins to the particular system and fills the customer details and places the orders.
DATABASE:
All the details and orders given by customer are updated in the Database.
VENDOR:
Vendor logins and verify the customer orders and the stock details.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes, their attributes, and the relationships
between the classes. It is represented using a rectangle with three compartments. Top compartment have
the class name, middle compartment the attributes and the bottom compartment with operations.
36 ISO 9001:2008
This class diagram has three classes customer, vendor and Database.
Customer is the class name. Its attributes are username, password, name, phone no
and address. The operations performed in the customer class are login and places the
orders.
Vendor is the class name. Its attributes are views the Database.
Database is the class name. The operations performed are storing customer details,
and their orders.
SEQUENCE DIAGRAM
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
DOCUMENTATION
The customer login in to the system and fills the customer details.
Then the customer places the order. It updated to the Database.
The vendor login to the system and views the customer orders and the stock details.
A collaboration diagram, also called a communication diagram or interaction diagram. A
sophisticated modeling tool can easily convert a collaboration diagram into a sequence diagram
and the vice versa. A collaboration diagram resembles a flowchart that portrays the roles,
functionality and behavior of individual objects as well as the overall operation of the system in
real time.
37 ISO 9001:2008
The collaboration diagram is to show how the customer login and places the orders in the system.
Here the sequence is numbered according to the flow of execution.
STATE CHART DIAGRAM

The purpose of state chart diagram is to understand the algorithm involved in performing a
method. It is also called as state diagram. A state is represented as a round box, which may contain one or
more compartments. An initial state is represented as small dot.
.
This state diagram describes the behavior of the system.
First state is login where the customer login to the system.
The next state is to fill the customer details.
And the next state is to place the orders.
Update Database with the orders and details of customer
ACTIVITY DIAGRAM
the name of the operation.

This activity diagram flow of stepwise activities performed in stock maintenance system. First the
customer login then fills the details.
The customer places the order according to their needs.
After placing the order the Database is updated.
Vendor login to the system and verifies the customer orders and stock details.
38 ISO 9001:2008

COMPONENT DIAGRAM

The main component in this component diagram is stock maintenance systems. And customer
Database details and update Database then vendor views the Database are the Components comes under
the main component.
.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical deployment
of artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes
according to the Deployments defined between them. It is represented by 3- dimensional box.
Dependencies are represented by communication associations.
39 ISO 9001:2008
.
The processor in this deployment diagram is the stock maintenance system which is the main part
and the devices are the filling customer details and placing orders then vendor views which are the some
of the main activities performed in the system.
PACKAGE DIAGRAM
Package diagram in unified modeling language depicts the dependencies between the packages that make
up a model. A Package Diagram (PD) shows a grouping of elements in the OO model, and is a Cradle
extension to UML. PDs can be used to show groups of classes in Class Diagrams (CDs), groups of
Diagrams (DPDs).
User interface layer
Software objects representing domain concepts that fulfill application requirements, such as
calculation of a sale total.
Domain layer
Layer that contains domain objects to handle application logic work
Technical services layer
General purpose object and sub system that provide supporting technical
services, such as interfacing with a Database logging
40 ISO 9001:2008
The three layers in the stock maintenance system are
The User interface layer - consists of the web and login. This layer describes how the
applicant logins to the website and places the order.
The Domain layer shows the activities that are performed by the customer to place the
orders.
The Technical service layer - the vendor logins and verifies the customer orders and
stock details
FORMS
package Sample;
import java.sql.*;
public class Login extends javax.swing.JFrame {
public Connection con;
public Statement st;
public Login() {
initComponents();
try
{
Class.forName("com.mysql.jdbc.Driver")
con = DriverManager.getConnection("jdbc:mysql://localhost:3306/stock", "root", "");
st=con.createStatement();
JOptionPane.showMessageDialog(null, "You are now connected...!!!");
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to connect");
} }
try{
String user = jTextField1.getText();
String pass = String.valueOf(jPasswordField1.getText());
String sqlquery1 = "Select * from login where username='"+user+"'and password='"+pass+"'";
ResultSet rs = st.executeQuery(sqlquery1);
if(rs.next())
{
setVisible(false);
new New().setVisible(true);
}
else{
JOptionPane.showMessageDialog(null, "Wrong username or password");
}
}
41 ISO 9001:2008
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to login");
}
}

setVisible(false);
new Applicant().setVisible(true);
}
package Sample;
import java.sql.*;
public class Applicant extends javax.swing.JFrame {
/** Creates new form start */
public Applicant() {
initComponents();
try
{
Class.forName("com.mysql.jdbc.Driver");
con = DriverManager.getConnection("jdbc:mysql://localhost:3306/stock", "root", "");
}
catch(Exception e)
{
}
}
try{
String name = jTextField1.getText();
String dob = jTextField2.getText();
String addr = jTextArea1.getText();
String email = jTextField5.getText();
String mob = jTextField4.getText();
42 ISO 9001:2008
String sqlquery1 = "Insert into register
values('"+name+"','"+dob+"','"+addr+"','"+email+"','"+mob+"')";
st.executeUpdate(sqlquery1);
JOptionPane.showMessageDialog(null, "Data successfully inserted");
setVisible(false);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Data insertion failure");
}
new Login().setVisible(true);
}
package Sample;
import java.sql.*;
import java.lang.String.*;
/**
*
* @author Keerthana
*/
public class Status extends javax.swing.JFrame {
public Connection connect;
String category;
/** Creates new form Status */
public Status(String c) {
initComponents();
category=c;
try
{
connect = DriverManager.getConnection("jdbc:mysql://localhost:3306/stock", "root", "");
st=connect.createStatement();
}
catch(Exception e)
{
}
43 ISO 9001:2008
}
try{
String sqlquery1 = "Select * from details where category='"+category+"'";
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to display stock details");
}
}

try{
int count,count2;
String stock = jTextField3.getText();
int qty = Integer.parseInt(jTextField1.getText());
String sqlquery1 = "Select * from details where stock='"+stock+"'";
ResultSet rs1 = st.executeQuery(sqlquery1);
while(rs1.next()){
if(qty<=(rs1.getInt(3))){
count=rs1.getInt(3);
count-=qty;
String sqlquery2 = "Update details set qty='"+count+"' where stock='"+stock+"'";
JOptionPane.showMessageDialog(null, "Stocks purchased");
setVisible(false);
new Thanks().setVisible(true);
}
else
JOptionPane.showMessageDialog(null, "No stock available");
}
}
catch(Exception e)
{
//JOptionPane.showMessageDialog(null, "Unable to check details");
}
}

String reg = jTextField1.getText();
setVisible(false);
}
Ex No: 5 ONLINE COURSE RESERVATION SYSTEM

Date:
AIM:
To develop a mini-project implementing an interactive ONLINE COURSE RESERVATION
system.
44 ISO 9001:2008
PROBLEM ANALYSIS AND PROJECT PLANNING:
The requirement form the customer is got and the requirements about the course registration are
defined. The requirements are analyzed and defined so that is enables the student to efficiency select a
course through registration system. The project scope is identified and the problem statement is prepared.
PROBLEM STATEMENT
Whenever the student comes to join the course he/she should be provided with the list of course
available in the college.
The system should maintain a list of professor who is teaching the course. At the end of the
course the student must be provided with the certificate for the completion of the course.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
4 Collaboration diagram
5 State Chart diagram
6 Activity diagram
7 Component diagram
8 Deployment diagram
9 Package diagram
USE CASE DIAGRAM
DOCUMENTATION FOR USE CASE DIAGRAM

The use case diagram in the course registration system illustrates the sequence of steps followed
in the system related to the actions of the system
LOGIN :This usecase gives a entry to the student,professor and the register
SELECT COLLEGE AND COURSE : This use case list out the various courses offered by the
institution
SUBMIT GRADES : This usecase given the marks scored by the system
MAINTAIN PROFESSOR INFORMATION : This usecase maintain the information about professor
in the system
MAINTAIN STUDENT INFORMATION : This usecase maintain the information about the professor
in the system
CLOSE REGISTRATION : This usecase describes the certification of the student when he/she finishes
the course
CLASS DIAGRAM:
45 ISO 9001:2008
-The various classes involved in the system are registered student record, professor record all
administration grade and close registration
-The student register for the course
-After the course gets over each student will be asked to write a test
-Test mark are analyzed for the issue grade sheet after certification the registration of the student in
closes.
SEQUENCE DIAGRAM
DOCUMENTATION OF SEQUECE DIAGRAM

The single use case in the course registration is taken and sequence of operation followed in the
usecase
In the registration for the course usecase diagram illustration on the process of registering and select a
course
The student enters the institution and gets a catalog about the list of course offered by the system
The student can select a particular usecase and registration for the course
In the record usecase submit grade at the end of each course each student will be asked to write a
test.The result will evaluavate for the issue of grade sheet and the grade are submitted.
DEPLOYMENT DIAGRAM
46 ISO 9001:2008
The device node is online course reservation and execution nodes are course details, login
and college details
FORMS
package Sample;
public class Welcome extends javax.swing.JFrame {
/** Creates new form Welcome */
public Welcome() {
initComponents();
}
setVisible(false);
}
47 ISO 9001:2008
package Sample;
import java.sql.*;
initComponents();
try
{
con = DriverManager.getConnection("jdbc:mysql://localhost:3306/course", "root", "");
}
catch(Exception e)
{
}
}
try{
String fname = jTextField2.getText();
String dob = jTextField3.getText();
String clgcode = jTextField7.getText();
String drg = jComboBox3.getSelectedItem().toString();
String yr = jTextField6.getText();
String course = jComboBox1.getSelectedItem().toString();
String sch = jComboBox2.getSelectedItem().toString();
String payment="Unpaid";

values('"+name+"','"+fname+"','"+dob+"','"+addr+"','"+clgcode+"','"+drg+"','"+yr+"','"+email+"','"+mob+
"','"+course+"','"+sch+"','"+payment+"')";
48 ISO 9001:2008
JOptionPane.showMessageDialog(null, "Data successfully inserted");
setVisible(false);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Data insertion failure");
}
new Register().setVisible(true);
}
package Sample;
public class Register extends javax.swing.JFrame {
/** Creates new form Register */
public Register() {
initComponents();
try
{
connect = DriverManager.getConnection("jdbc:mysql://localhost:3306/course", "root", "");
}
catch(Exception e)
{
}
}
Ex No: 6 E-TICKETING
Date:
Aim:
To develop a mini - project for e-Ticketing.
Problem Statement:
This project enables a user to peform the following operations.
49 ISO 9001:2008
Online Booking of tickets
Online cancellation f tickets
Online Enquiry system
Online ticket status checking
The booking service accepts the source,destination derails along with the train name and date
of service. According to t he avilability of tickets,the particular passenger is alloted a seat on the particular
train.The tickets would be displayed in a particular passenger is alloted a seat on the particular train.the
ticket would bediaplayed in a printable format along with a unique seat number to differentiate between
online ticket reservations.
The cancellation services comes in very handy in case of emergency cancellation wherin a
passenger who has already booked his tickets can follow easy steps to cancel his ticket.The passenger
specifies his seat no and other unique identification parameter like credit card number and the details are
validated.If found legal,the ticket is cancelled and the transaction with the bank is nullified.
The train schedule and enquiry features of this system enable the user to interactively identify
a suitable configuration of train timimgs and fares.this module gives the user complete train details and
facilities the passenger to choose a train of his choice.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
6 Activity diagram
USECASE DIAGRAM:

The actors in this use case diagram are applicant, and E-ticketing DataBase. The use
cases are the activities performed by actors.
The actors in this use case diagram are
Applicant - logins the E-Ticketing and filling the required data fields.
E-Ticketing DataBase-verify the login and filling the details and selected applicant details are
stored in it.
The use cases in this use case diagram are
Login - applicant enter their username and password to enter in to the E-Ticketing form.
50 ISO 9001:2008
Filling Details applicants are used to enter the details in the requiredForm.
Selecting Flight it is used to selecting the flight for the applicants.
Book Ticket it is used to book the ticket through the E-Ticketing database.
Search it is used to search the flight details.
Cancel Ticket- it is used to cancel the ticket through the E-Ticketing DataBase
CLASS DIAGRAM:

This class diagram has two classes applicant, E-Ticketing DataBase.
Applicant - logins the E-Ticketing and filling the required data fields.
E-Ticketing DataBase-verify the login and filling the details and selected applicant
details are stored in it.
SEQUENCE DIAGRAM:

This sequence diagram describes the sequence of steps to show
Applicants are used to login the form. And then its verify the username and password.
If the password and username are correct then applicants are used to login the filling details.
Applicants are used to selecting the flights and book the tickets.
Now the E-Ticketing DataBase verify the filling Details.
51 ISO 9001:2008
And then the E-Ticketing DataBase display the ticket information.
Incase of any sudden change of the plan,the applicant can cancel the ticket.
COLLABORATION DIAGRAM:
DOCUMENTATION OF COLLABRATION DIAGRAM

This collaboration diagram is to show how the applicant login and register in the E-
Ticketing system. Here the sequence is numbered according to the flow of execution.
This collaboration diagram is to show the selection process of the applicant for the ticket
booking. The flow of execution of this selection process is represented using the numbers.
ACTIVITY DIAGRAM:

This activity diagram describes the behavior of the system.
First state is login where the applicant login to the E-Ticketing system.
The next state is filling details the applicant are used to fill the form.
Then applicant used to selecting the flight.
52 ISO 9001:2008
The applicant appears for book ticket and search details from E-Ticketing DataBase.
DEPLOYMENT DIAGRAM:

The processor in this deployment diagram is the E-Ticketing system which is the main
part and the devices are the login, appear for the filling details and selecting flights applicant
which are the some of the main activities performed in the system.
FORMS:
public class opening extends javax.swing.JFrame {
/** Creates new form opening */

public opening() {
initComponents();
}
}
53 ISO 9001:2008

public login() {
initComponents();
}
// TODO add your handling code here
if((s1.compareTo("admin")==0)&&(s2.compareTo("admin")==0))
{
new update().setVisible(true);
}
else{
customer s=new customer(s1,s2);
}
dispose();
}
import java.sql.*;
import javax.swing.table.TableModel;
//import org.apache.commons.dbutils.DbUtils;
public class NewJFrame extends javax.swing.JFrame {
54 ISO 9001:2008
/** Creates new form NewJFrame */
public NewJFrame() {
initComponents(); }
try
{
String s=jTextField1.getText();
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:aero");
String sq="select * from planedetails where number = '" +s+"'" ;
// System.out.println("check:"+rs.getInt("count"));
}
catch(Exception e)
{System.out.println(e.getMessage()); } }

new opening().setVisible(true); }
int j=Integer.parseInt(jTextField3.getText());
System.out.println("AD"+s1);
airdatabase l=new airdatabase(s1,j);
}
//DECREASE IN TICKET COUNT
SOFTWARE PERSONNEL MANAGEMENT SYSTEM

EX NO: 7
DATE
AIM
55 ISO 9001:2008
To develop a project software personnel management system using the Rational Rose Software
from the UML diagram and to implement the software in JAVA .
PROJECT ANALYSIS AND PROJECT PLANNING
The software personnel management system is used to manage our personnel things such as maintaining
databases in offices etc. this project is easy for the CEO to handle the details. This is personally used for
CEO.
PROBLEM STATEMENT
The CEO must enter the name and password to login the form and select the particular employee to view
the details about that employee and maintaining the employee details personally. This process of software
personnel management system are described sequentially through following steps,
The CEO login to the software personnel management system.
He/she search for the list of employees.
Then select the particular employee.
Then view the details of that employee.
After displaying the employee details then logout.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
5 State Chart diagram
6 Activity diagram
7 Component diagram
9 Package diagram
USE CASE DIAGRAM

The use case diagram in the software personnel management system illustrates the sequence of
sequencing and describing an interaction between a CEO and a system.
Login This use case gives as entry to the CEO and the database.
56 ISO 9001:2008
List of employee This will create the situation for the CEO to select particular employee from the
available list.
Employee details The CEO can able to view the details of the employee using this use case.
CLASS DIAGRAM

The Classes used in this project are
CEO: The CEO has to login the form by specifying the name and password of him.
Database: The database checks whether the CEO has given the name and password accordingly if not the
error message will be displayed.
Available employees: The database is connects to the list of available employees and the CEO if wants
then select the employee from it.

The CEO must enter his name and password to login the software personnel management system. The
verification process is undergone by the database .If the details are correct he can enter to the system
57 ISO 9001:2008
otherwise error is displayed. After login the details of the particular employee is viewed by the CEO.
Finally he is logged out from the system.
DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the software personnel management system
which is the main part and the devices are the ceo , database and available employee which are
the some of the main activities performed in the system.
FORMS
package personnel;
/**
*
* @author Elcot
*/

public login() {
58 ISO 9001:2008
initComponents();
}
try {
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:pers");
String s="select * from pass where username = '" +s1+"'and password =
'"+s2+"'";
int count=0;
while(rs.next()) {
count++;
}
if(count==1)
new employ().setVisible(true);
else
} catch (Exception e) {
}
}

setVisible(false);
}
package personnel;
/**
*
* @author Elcot
*/
59 ISO 9001:2008
public class employ extends javax.swing.JFrame {
/** Creates new form employ */

public employ() {
initComponents();
}
setVisible(false);
new employ().setVisible(true);
}

setVisible(false);
new details().setVisible(true);
}

try
{
ResultSet rs;
String sq="select id from empo" ;
{
package personnel;
60 ISO 9001:2008
public class details extends javax.swing.JFrame {
/** Creates new form details */
public details() {
initComponents(); }
try {
ResultSet rs;
String sq="select * from empo where id = '" +s+"'" ;
jTable1.setModel(DbUtils.resultSetToTableModel(rs)); }
catch(Exception e) {
System.out.println(e.getMessage()); }}
new employ().setVisible(true); }
new logout().setVisible(true);
CREDIT CARD PROCESSING

Ex. No: 8
Date:
AIM:
To develop and identify uml diagram for credit card processing and to implement the
software in Java.
PROBLEM ANALYSIS
The Credit Card Processing System which is use to purchasing an item from any shop mall, and it
is used to maintain the limitation of credit card balance and current transaction process could be update
via credit card machine. This project mainly used for large amount of item can be easy to buy from
anywhere and required transaction process should be maintained them.
PROBLEM STATEMENT:
To credit card processing first involves checking card number for validation. The credit card has
a credit limit. During billing changes upto the credit limit without any penalty. If charge is more then
credit limit over the limit is accessed when balance increases the credit decreases. At the end of billing,
the billing statement is provided. Billing statement includes balance of the beginning of billing cycle . It
provides details about credit card charges and payments and also credits and fee in the balance from
previous billing cycle while payment and credits are subtracted to come up with current balance. When
61 ISO 9001:2008
the payment is made on the credit card the amount is subtracted from balance. The balance decreases and
the credit increases.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
6 Activity diagram
7 Component diagram
9 Package diagram
USE CASE DIAGRAM:

The actors in this use case diagram are customer, vendor and card reader. The use cases are the activities
The actors in this use case diagram are Customer , Vendor ,Card reader .
Purchase item customer enter the shop to purchase some item by using credit card payment.
Bill issue vendor will make a bill for the selected item.
Swap the card vendor will swap the card.
Make transaction card reader will processes the amount transaction.
Print the statement after the transaction, balance amount should be printed.
Signature customer should put the signature and give it to vendor.
Deliver the itemvendor issued to deliver a item.
CLASS DIAGRAM:
62 ISO 9001:2008
The Classes used in this project are:
Customer is the class name. Its attributes are name, age, signature, and card number. The operations
performed in the customer class are purchase item and swap the credit card.
Vendor is the class name. Its attributes are name, address, and phone number. The operations performed
are making bill and then delivered item purchased by the customer.
Card Reader is the class name. Its attributes are machine number, software and company. The
operations performed are making the transaction and print balance statement.
SEQUENCE DIAGRAM:

The customer wants to purchase some item from the shop; Vendor makes a bill for the selected
item. The Customer gives the credit card to the vendor to the swap the card. The further
transaction is proceeding for if the credit card is validated. Vendor will issue the required balance
statement to the customer. Customer put the signature in the receipt and returns the one copy of
statement to the vendor.
COLLABORATION DIAGRAM:
63 ISO 9001:2008
DOCUMENTAION OF COLLABORATION DIAGRAM
In this diagram there is sequence of ordered relationship should performing in the CCP, then
Customer will performed a selecting item, putting signature, and deliver the item, Vendor should perform
the swap the card, issue the statement and Card reader should perform amount transaction and print the
balance statement.
ACTIVITY DIAGRAM:

The customers activity should contained an purchase item by using credit card and then his
referred to check the current transaction processing its completed or not.
The vendor should issue a bill copy to the customer and its swap the card to make amount
transaction by using card reader. The vendor should give required statement to customer will deliver the
item from the shop.
DEPLOYMENT DIAGRAM:
64 ISO 9001:2008
The processor in this deployment diagram is the credit card processing system which is the main
part and the devices are the purchase item, swap the card, make transaction, verify signature, delivery
item which are the some of the main activities performed in the system .
FORMS
public class Welcome extends javax.swing.JFrame {

public Welcome() {
initComponents();
}
setVisible(false);
new Status().setVisible(true);
}
public void run() {
new Welcome().setVisible(true);
}
});
}
65 ISO 9001:2008
/**
public class Register extends javax.swing.JFrame {

String itemname;
int amt;
/** Creates new form Register */
public Register(String n,int m) {
initComponents();
itemname=n;
amt=m;
try
{
connect = DriverManager.getConnection("jdbc:odbc:credit");
}
catch(Exception e)
{
}
}
try {
String name= jTextField4.getText();
String cno= jTextField1.getText();
String accno= jTextField2.getText();
String bank= jComboBox1.getSelectedItem().toString();
String payment;
int newamt;
66 ISO 9001:2008
String sqlquery2= "Select * from bank where name='"+name+"'";
ResultSet rs=st.executeQuery(sqlquery2);
while(rs.next()){
if(name.equals(rs.getString(1))&&cno.equals(rs.getString(2))&&accno.equals(rs.getString(3))&&
bank.equals(rs.getString(4))&&amt<=(rs.getInt(5))){
newamt=rs.getInt(5);
payment="Paid";
newamt-=amt;
String sqlquery3 = "Update bank set amt='"+newamt+"' where name='"+name+"'";
String sqlquery1 = "Update register set payment='"+payment+"' where
itemname='"+itemname+"'";
JOptionPane.showMessageDialog(null, "Successful payment");
JOptionPane.showMessageDialog(null, "Stocks purchased");
setVisible(false);
}
else
JOptionPane.showMessageDialog(null, "Low balance in your account");
}
}
catch(Exception e)
{
//JOptionPane.showMessageDialog(null, "Unsuccessful payment");
}
}
import java.sql.*;


public Status() {
initComponents();
try
{
67 ISO 9001:2008
connect = DriverManager.getConnection("jdbc:odbc:credit");
}
catch(Exception e)
{
}
}
try{
String sqlquery1 = "Select * from details";
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to display stock details");
}
}
try{
int price;
String payment="Unpaid";
String no = jTextField3.getText();
int qty = Integer.parseInt(jTextField1.getText());
String sqlquery1 = "Select * from details where itemno='"+no+"'";
while(rs1.next()){
String name =rs1.getString(2);
price=rs1.getInt(3);
price*=qty;
values('"+name+"','"+qty+"','"+price+"','"+payment+"')";
setVisible(false);
JOptionPane.showMessageDialog( null, "purchased successfully");
}
}
catch(Exception e)
{
//JOptionPane.showMessageDialog(null, "Unable to check details");
}
}
String reg = jTextField1.getText();
setVisible(false);
}
68 ISO 9001:2008
setVisible(false);
new Status().setVisible(true);
}

System.exit(0);
}
.
Ex No: 9 E-BOOK MANAGEMENT SYSTEM

Date:
Aim:
The aim of the project is to implement the E-book management system.This enables case of
purchasing,searching and managing the books online.
PROBLEM ANALYSIS
Ebook Management System gives an idea about how books are maintained in the particular
websites. The books that are to be purchased, the books that are to be sold are maintained here. . Further
some additional details of the current books that is available in the store are also given. Ebook
Management System in this project is done in an authorized way. The password and user id has been set
here.
PROBLEM STATEMENT:
Product perspective
The ebook system is a package to be used by any random user of internet who wants to buy or
sells his books online to improve the efficiency and frustrations of him buying or selling the same book
office. The system provides books catalog and information to users and helps them decide on the books to
buy from the E-book website. The Website administrator can keep the books catalog updated all the time
so that the users get the updated information all the time.
Product Functions
The E-book System provides real time information about the books available in the E-book and the
user information. The Product functions are more or less the same as described in the product perspective.
1. The member should be provided with the updated information about the books catalog.
2. Provisions for the users to buy the books they want, if all athe other required rules hold
good.
3. The member is given a provision to check his account information and change the
account information any time in the given valid period.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
69 ISO 9001:2008
6 Activity diagram
USE CASE DIAGRAM

The actors in this use case diagram are Supplier, Store Keeper and Database. The usecases are the
The website will give the books available.
Customer will login and check the list of ebooks in the database.
The database will be updated according to the purchase done and it will be up to date.
The use cases in the use case diagram are Quotation & Purchase, login, stock, purchase.
Select books will gives us the status of the purchasing order details
Login will gives us the entry for the customer of this project.
Database will gives us the details about the total ebook available.
Purchase will gives us the details about the details and the history of ebooks purchased.
CLASS DIAGRAM

This class diagram has three classes applicant, recruiter and database.
Customer is the class name. Its attributes are name, address and cont no. The operations
performed in the Supplier class are get order, supply goods and get money.
Books is the class name. Its attributes are operating system, computer architecture, dbms , web
technology and ooad. The operations performed are select and buy.
70 ISO 9001:2008
Database is the class name. Its attribute is operation. The operations performed is store .
SEQUENCE DIAGRAM

The Customer enters the Ebook website.
The list of books available are listed.
Customer checks the book list.
Database provides user id and pass.
Customer selects the book.
Pay money to the Website.

The first collaboration diagram is to show how the customer login and getting details of ebooks in
the ebook management system. Here the sequence is numbered according to the flow of execution.
ACTIVITY DIAGRAM
71 ISO 9001:2008
This activity diagram flow of stepwise activities performed in recruitment system.
First Customer login then checks books available.
The book list are verified and is given in a ordered format.
The needed book is selected.
Enter your account details and purchase the book .
DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the online recruitment system which is the main part
and the devices are the select and payment which are the some of the main activities performed in the
system.
FORMS
72 ISO 9001:2008
public class book extends javax.swing.JFrame {
public book() {
initComponents();
}
setVisible(false);
}

public login() {
initComponents();
}
73 ISO 9001:2008
try
{
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:Database4");
String s="select * from pass where username = '" +s1+"'and password = '"+s2+"'";
int count=0;
while(rs.next())
{
count++;
}
if(count==1)
else
}
catch (Exception e)
{
}
}
setVisible(false);
}
74 ISO 9001:2008
public class bb extends javax.swing.JFrame {
/** Creates new form bb */

public bb() {
initComponents();
}
String author=jTextField2.getText();
try
{
Connection conn=DriverManager.getConnection("jdbc:odbc:Database4");
String sql="insert into book values('"+name+"','"+author+"')";
setVisible(false);
}
catch(Exception e)
{
}

}
75 ISO 9001:2008
/** Creates new form verify */

public verify() {
initComponents();
}
}

new payment().setVisible(true);
}

try
{
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:Database4");
String sq="select * from book" ;
{
76 ISO 9001:2008
public class payment extends javax.swing.JFrame {
/** Creates new form payment */

public payment() {
initComponents();
}
String no=jTextField1.getText();
String acc=jTextField2.getText();
String amt=jTextField4.getText();
try {
ResultSet rs;
Connection conn=DriverManager.getConnection("jdbc:odbc:Database4");
String sql="insert into amt values('"+no+"','"+acc+"','"+amt+"')";
JOptionPane.showMessageDialog(null, "Successfully paid!!");
new logout().setVisible(true);
JOptionPane.showMessageDialog(null, "Successful inserted");
}
}
public class logout extends javax.swing.JFrame {
/** Creates new form logout */

public logout() {
initComponents();
new cancel().setVisible(false);
}
77 ISO 9001:2008
public class cancel extends javax.swing.JFrame {
/** Creates new form cancel */

public cancel() {
initComponents();
}
new book().setVisible(true);
}
RECRUITMENT SYSTEM
Ex No: 10
Date:
AIM
To develop a project on recruitment system using ArgoUML Software and to implement the project in
JAVA .

The Online Recruitment System is an online website in which applicant can register themselves
and then attend the exam. Examination will be conducted at some venue. The details of the examination,
venue & Date of the examination will be made available to them through the website. Based on the
outcome of the exam the applicant will be short listed and the best applicant is selected for the job.
PROBLEM STATEMENT
The process of applicants is login to the recruitment system and register for the job through online. The
resume is processed by the company and the required applicant is called for the test. On the basis of the
test marks, they are called for next level of interview. Finally the best applicant is selected for the job.
This process of online recruitment system are described sequentially through following steps,
The applicant login to the online recruitment system.
They register to the company for the job.
They appear for examination.
Based on the outcome of the exam, the best applicant is selected.
The recruiter informs the applicant about their selection.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
5 Activity diagram
USE CASE DIAGRAM:
78 ISO 9001:2008
The actors in this use case diagram are applicant, recruiter and database. The use cases are the activities
The actors in this use case diagram are Student,hr,admin .
Login student enter their username and password to enter in to the recruitment system
view student can view the list of students whon got recruited.
edit hr can refine the students in each round.
validate student appears for the test.
New fields based on the outcome of test talented student is selected.
Specify requirements hr select the students based on their capability.
CLASS DIAGRAM

This class diagram has three classes student, hr and admin.
student is the class name. Its attributes are username, password, name, phone no and address. The
operations performed in the applicant class are login, register and giving applicant details.
79 ISO 9001:2008
hr is the class name. Its attributes are name, designation, phone no, marks in apps and marks in
technical. The operations performed are selecting applicants based on apps and technical.
admin is the class name. The operations performed are storing applicant details, verifying login and
storing selected applicant details.

This collaboration diagram is to show how the student login and register in the recruitment system. Here
the sequence is numbered according to the flow of execution.
SELECTING STUDENT
This collaboration diagram is to show the selection process of the applicant for the job. The flow
of execution of this selection process is represented using the numbers.
ACTIVITY DIAGRAM

This activity diagram flow of stepwise activities performed in recruitment system.
First the student login then registers.
80 ISO 9001:2008
The student details are verified and interview details are send to student by hr.
students appear for test.
Hr select talented student.
Update the selected student details in the database.
DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the online recruitment system which is the main part
and the devices are the register, appear for test and select talented applicant which are the some of
the main activities performed in the system.
FORMS:
import java.sql.*;
public class Login extends javax.swing.JFrame {
public Login() {
initComponents();
}
try{
String user = jTextField1.getText();
81 ISO 9001:2008
String pass = String.valueOf(jPasswordField1.getText());
String sqlquery1 = "Select * from login where username='"+user+"'and password='"+pass+"'";
if(rs.next())
{
setVisible(false);
}
else{
}
}
catch(Exception e)
{
}
}
import java.sql.*;


initComponents()
}
try{
String percent = jTextField2.getText();
String qual = jTextField3.getText();
String post = jComboBox3.getSelectedItem().toString();
String exp = jTextArea2.getText();
82 ISO 9001:2008
values('"+name+"','"+qual+"','"+percent+"','"+exp+"','"+post+"','"+addr+"','"+email+"','"+mob+"')";
JOptionPane.showMessageDialog(null, " successfully inserted");
setVisible(false);
new New(name).setVisible(true);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "insertion successful");
}
}
import java.sql.*;

String n;

public Status(String x) {
initComponents();
}
try{
String sqlquery1 = "Select * from details";
}
catch(Exception e)
{
}
}
83 ISO 9001:2008
try
{
String sqlquery1 = "Select * from details where name='"+n+"'";
if(rs1.next()){
setVisible(false);
new New(n).setVisible(true);
}
else{
setVisible(false);
new Sorry().setVisible(true);
}
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to check details");
}
}
import java.sql.*;
public class New extends javax.swing.JFrame {

public New(String x) {
initComponents();
}
setVisible(false);
new Technical(n).setVisible(true);
}
setVisible(false);
new Test(n).setVisible(true);
}
setVisible(false);
}
84 ISO 9001:2008
public class Technical extends javax.swing.JFrame {
public Technical(String x) {
initComponents();
}
setVisible(false);
new Status(n).setVisible(true);
}
public class Test extends javax.swing.JFrame {

/** Creates new form Test */
public Test(String x) {
initComponents();
}
setVisible(false);
new Status(n).setVisible(true);
}
public class Thanks extends javax.swing.JFrame {
85 ISO 9001:2008
/** Creates new form Thanks */
public Thanks() {
initComponents();
}
setVisible(false);
new Login().setVisible(true);
}
.
FOREIGN TRADING SYSTEM

Ex No: 11
Date:
AIM
To design a project Foreign Trading System using ArgoUML Software and to implement the
software in JAVA
PROJECT ANALYSIS
The initial requirements to develop the project about the mechanism of the Foreign Trading
System is bought from the trader. The requirements are analyzed and refined which enables the analyst
(administrator) to efficiently use the Foreign Trading System.The complete project analysis is developed
after the whole project analysis explaining about the scope and the project statement is prepared.
PROBLEM STATEMENT
The steps involved in Foreign Trading System are:
The Foreign Trading system begins its process by getting the username and password from the
trader.
After the authorization permitted by the administrator, the trader is allowed to perform the sourcing
to know about the commodity details.
After the required commodities are chosen, the trader places the order.
The administrator checks for the availability for the required commodities and updates it in the
database.
After the commodities are ready for the trade, the trader pays the amount to the administrator.
The administrator in turn provides the bill by receiving the amount and updates it in the database.
The trader logouts after the confirmation message has been received.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
5 Activity diagram
USE CASE DIAGRAM
86 ISO 9001:2008
The actors in this use case diagram are customer, administrator and database. The usecases are the
activities that are represented in the ellipse.
Trader logins the foreign trading system and perform the sourcing to select the
required commodities and places the order.
The administrator checks for ordered commodities, after the commodities are ready trader pays the
amount.
The administrator provides the items along with the bill.
The database stores the all the details and updates it whenever there is a change in any part of the
trading process.
CLASS DIAGRAM

A class diagram in the unified modeling language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes, their attributes, and the relationships
between the classes. It is represented using a rectangle with three compartments. Top compartment have
the class name, middle compartment the attributes and the bottom compartment with operations.
SEQUENCE DIAGRAM
87 ISO 9001:2008
Vertical dimension-represent time.
Horizontal dimension-represent different objects.

A collaboration diagram, also called a communication diagram or interaction diagram. A sophisticated
modeling tool can easily convert a collaboration diagram into a sequence diagram and the vice versa. A
collaboration diagram resembles a flowchart that portrays the roles, functionality and behavior of
individual objects as well as the overall operation of the system in real time.
ACTIVITY DIAGRAM
88 ISO 9001:2008
Activity diagrams are graphical representations of workflows of stepwise activities and actions with
support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams can
be used to describe the business and operational step-by-step workflows of components in a system. An
activity diagram shows the overall flow of control. An activity is shown as a rounded box containing the
name of the operation
DEPLOYMENT DIAGRAM

FORMS
89 ISO 9001:2008
public login() {
initComponents();
}
try{
String username = jTextField1.getText();
String password = jPasswordField1.getText();
Connection conn=DriverManager.getConnection("jdbc:odbc:fore");
String sqlquery1 = "Select * from pass where username='"+username+"'and
password='"+password+"'";
Statement st=conn.createStatement();
if(rs.next()) {
setVisible(false);
new product().setVisible(true);
} else{
}
}
}
public class product extends javax.swing.JFrame {
90 ISO 9001:2008
/** Creates new form product */
public product() {
initComponents();
}
setVisible(false);

setVisible(false);
}
public class details extends javax.swing.JFrame {
/** Creates new form details */

public details() {
initComponents();
}
try
{
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:fore");
String sq="select * from pro" ;
91 ISO 9001:2008
}
catch(Exception e)
{
}

new purchase().setVisible(true); // TODO add your handling code here:

setVisible(false);
new thanks().setVisible(true);
}
public class purchase extends javax.swing.JFrame {
/** Creates new form purchase */

public purchase() {
initComponents();
}
String detail=jTextField2.getText();
try
{
92 ISO 9001:2008
Connection conn=DriverManager.getConnection("jdbc:odbc:pro");
String sql="insert into pro values('"+name+"','"+detail+"','"+no+"')";
new pay().setVisible(true);
}
catch(Exception e)
{
}
}

new purchase().setVisible(true);
}
CONFERENCE MANAGEMENT SYSTEM

Ex No: 12
Date:
AIM
To develop a project on Conference management system using ArgoUMLSoftware and to implement the
project in JAVA .
The Conference Management System is an online website in which candidate can submit the
paper and register themselves and then attend the conference. The paper will be reviewed. The details of
the conference, date and time will be made available to them through the website. After getting the
confirmation details the candidate should submit the revised and camera ready paper. Then the
registration process will be done.
PROBLEM STATEMENT
The process of the candidates is to login the conference system and submit the paper through
online. Then the reviewer reviews the paper and sends the acknowledgement to the candidate either paper
selected or rejected. This process of on conference management system are described sequentially
through following steps,
The candidate login to the conference management system.
The paper title is submitted.
The paper is been reviewed by the reviewer.
The reviewer sends acknowledgement to the candidate.
Based on the selection, the best candidate is selected.
Finally the candidate registers all details.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
USE CASE DIAGRAM
93 ISO 9001:2008
The actors in this use case diagram are candidate, reviewer and database. The use cases are the activities
The actors in this use case diagram are Candidate , Reviewer , Databases .
Login - Candidate enter their username and password to login to the conference system.
Paper sumbission Candidate submits the paper.
Review the paper The paper is been reviewed by the reviewer and the paper is selected.
Paper confirmation details The reviewer can send the confirmation details to the candidate.
Revised and camera ready paper After the paper is selected and the camera ready paper should be
submitted to the reviewer by candidate.
Registration After submitting the revised paper the candidate wants to register.

This class diagram has three classes candidate, reviewer and database.
Candidate Its attributes are name , collegename , department , paper title. The operations performed in
the candidate class are login, submit the paper, submit revised and camera ready paper and registration.
Reviewer Its attributes are name, department, reviewer ID The operations performed are review the
paper and send the paper confirmation details.
Database The operations performed are storing candidate details and verifying login
SEQUENCE DIAGRAM
94 ISO 9001:2008
This sequence diagram describes the sequence of steps to show

The candidate login in to the conference system and register for job.
The verification done in the database .
The candidate sumbit the paper.
The reviewer reviews the paper and sends acknowlegement to the candidate.
The candidate submits revised and camera ready paper.
This candidate will registers their detials.
DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the conference management system which is the
main part and the devices are the candidate, appear for do conference , reviewer will reviews paper ,
database will store all details which are the some of the main activities performed in the system.
CODING AND FORMS
package confer;
public class confer extends javax.swing.JFrame {
/** Creates new form confer */
public confer() {
initComponents();
}
95 ISO 9001:2008
}
setVisible(false);
}
package confer;

public login() {
initComponents();
}
try{
String username = jTextField1.getText();
String password = jPasswordField1.getText();
Connection conn=DriverManager.getConnection("jdbc:odbc:conf");
96 ISO 9001:2008
String sqlquery1 = "Select * from Login where Username='"+username+"'and
Password='"+password+"'";
Statement st=conn.createStatement();
if(!rs.next()) {
new paper().setVisible(true);
}
}
}
package confer;
/**
*
* @author Elcot
*/
public class paper extends javax.swing.JFrame {
/** Creates new form paper */

public paper() {
initComponents();
}
try {
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:conf");
String sq="insert into papername ";
97 ISO 9001:2008
setVisible(false);
new review().setVisible(true);}
catch(Exception e) {
JOptionPane.showMessageDialog(null, " not Successfully registered");
}}
setVisible(false);
}
package confer;
/**
*
* @author Elcot
*/
public class review extends javax.swing.JFrame {
/** Creates new form review */

public review() {
initComponents();
}
setVisible(false);
new review().setVisible(true);
}
String cname=jTextField1.getText();
98 ISO 9001:2008
String add=jTextField2.getText();
String refer=jTextField3.getText();
String con=jTextField3.getText();
try
{
Connection conn=DriverManager.getConnection("jdbc:odbc:conf");
String sql="insert into con values('"+cname+"','"+add+"','"+no+"','"+refer+"','"+con+"')";
setVisible(false);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "not Successfully Registered!!");
}
}
package confer;
public class thanks extends javax.swing.JFrame {
/** Creates new form thanks */

public thanks() {
initComponents();
}
setVisible(false);
}

System.exit(0);
}
BPO MANAGEMENT SYSTEM
Ex No: 13
Date:
AIM
99 ISO 9001:2008
To develop a project Business process outsourcing(BPO) management system Using ArgoUML
software and to implement the software in JAVA .

Generally outsourcing can be defined as an organization entering into a contract with another
organization to operate and managed one or more of its business processes. There are many
problems faced by the BPO one among them is meeting their targets and leaving the concern very often
and switch to another company.In this project we deal with the inbound system of the BPO.In inbound
system the agent calls the customer from his database to sell his product.
PROBLEM STATEMENT
In this BPO inbound system , the process undergoing is that the agent tries to sell his product so
that the agent gets the details of the customer from the database and pitches about his product and makes
the sales successful. The communication is done through the telephone. Telephone is the major
component used for this customer satisfaction service. The steps are as follows:
The agent login to the website and enters the username and password .It checks for authorization .
If the username and password is correct ,it allows the agent to get the details of the customer
from the database.
Now the agent makes the call to the customer and pitches about the product.
If the customer is satisfied ,agent sells the product else disconnects the call.
Agent proceeds with the another call.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
USE CASE DIAGRAM

The actors in this use case diagram are Process agent ,Customer and Database. The usecases are
the activities performed by actors.
PROCESS AGENT : The ultimate Goal of the process agent is to make sale. The operation performed
by him/her is he/she will first call the customer then pitches there product for sale. If the customer is
interested the agents mark it has a sale else disconnects the call and moves to another customer.
DATABASE : The database is neither a computer nor a memory where all the customers details will be
stored. It consists of the customer name, customer address, and customer phone number. Further details of
the customer can also be added in the future by the agent.
100 ISO 9001:2008

CUSTOMER : Customer plays a vital role in the BPO industry. Agent calls the customer from the
database. Once the call gets connected and the customer is happy with the product which is pitched by the
agent then he/she will show interest for buying the product else he/she will reject the product and
disconnect the call.
CLASS DIAGRAM

This class diagram has three classes process agent, customer and database.
Agent is the class name. Its attributes are username, password, name, phoneno and address. The
operations performed by the agent class are login, giving details to customer and selling the product.
Customer is the class name. Its attributes are name, phoneno, address . The operations performed are
attending the call,asks about the product.
Database is the class name. The operations performed are storing customer details, verifying login and
updating the customer details.
SEQUENCE DIAGRAM

Agent fetches the data from the database
database provides the details of the customer to agent and agent dials to the customer.
Customer responds to the agent and agent pitches his/her product.
If necessary customer buys else discards.
Agent updates the call history and proceeds with the another call.
DEPLOYMENT DIAGRAM
101 ISO 9001:2008

The processor in this deployment diagram is the BPO management system which is the main part
and the devices are the agent, customer and to sell the product to the customer are the main activities
performed in the system.
CODING AND FORMS
package javaapplication7;
/**
* Creates new form login
*/
public login() {
initComponents();
}
Agent a=new Agent();
a.login(s1,s2);
102 ISO 9001:2008

}
import java.sql.*;
public class Agent {
public String username;
public String password;
public String address;
public String name;
public String phneno;
public void login(String s1,String s2){
try
{
PreparedStatement pstm;
ResultSet rs;
String driver = "sun.jdbc.odbc.JdbcOdbcDriver";
Class.forName(driver);
// Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:bpoo");
String sq="select * from agentdetails where username = '" +s1+"'and password = '"+s2+"'" ;
//String s=rs.getString("username");
//System.out.println("error "+s);
//if(((rs.getString(1)).compareTo(s1)==0)&&((rs.getString(2)).compareTo(s2)==0))
//{
// new NewJFrame().setVisible(true);
//System.out.println("errorinmnkjkjk");
//}
int count = 0;
while(rs.next())
{
count ++;
}
if(count == 1)
{
new working().setVisible(true);
}
else
{
JOptionPane.showMessageDialog(null, "invalid password");
}}
catch(Exception spe)
{
System.out.println("error");
System.out.println(spe.getMessage()); }
103 ISO 9001:2008

public class working extends javax.swing.JFrame {
/**
* Creates new form working
*/
public working() {
initComponents();
}
try
{
ResultSet rs;
Connection connect=DriverManager.getConnection("jdbc:odbc:bpoo");
String sq="select * from customerdetails " ;
// System.out.println("check:"+rs.getInt("count"));
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"connection error") ;
} }
JOptionPane.showMessageDialog(null, "calling is in process");
}
Ex No: 14 STUDENT INFORMATION SYSTEM
Date:
104 ISO 9001:2008

Aim:
The aim of the project is to implement the Student Information system.This enables ease of
purchasing, searching and managing the student details online.
PROBLEM ANALYSIS
Student Information system gives an idea about how details about the student are maintained in
the particular websites. The student personal details, results and attendance are maintained here. . Further
some additional details of the current books that is available in the store are also given. Student
information system in this project is done in an authorized way. The password and user id has been set
here.
PROBLEM STATEMENT
Student details can be added.
Student details can be updated if needed details.
They can access their attendance details
They can verify or check their personnel as well as result details.
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
USE CASE DIAGRAM
CLASS DIAGRAM
105 ISO 9001:2008

SEQUENCE DIAGRAM
DEPLOYMENT DIAGRAM
CODING AND FORMS
106 ISO 9001:2008

public class welcom extends javax.swing.JFrame {
public welcom() {
initComponents();
new studentlogin().setVisible(true);
dispose();
}
new adminLogin1().setVisible(true);
dispose();
}
dispose();
}
public class adminLogin1 extends javax.swing.JFrame {
/**
* Creates new form adminLogin1
*/
public adminLogin1() {
initComponents();
}
107 ISO 9001:2008

String uname=jTextField1.getText();
String pwd=jPasswordField1.getText();
if(uname.matches("admin"))
{
if(pwd.matches("admin"))
{
new adminopening().setVisible(true);
}
else
{
JOptionPane.showMessageDialog(null, "Wrong Password");
}
}
else
{
JOptionPane.showMessageDialog(null, "Wrong Username");
}
dispose();
}
new welcom().setVisible(true);
dispose();
}
public class adminopening extends javax.swing.JFrame {

public adminopening() {
initComponents();
}
String sem=(String) jComboBox1.getSelectedItem();

if(sem=="V")
new V().setVisible(true);
else
new VI().setVisible(true);
dispose();
108 ISO 9001:2008

public class V extends javax.swing.JFrame {
/**
* Creates new form V
*/
public V() {
initComponents();
}

String reg=jTextField5.getText();
Integer mon=Integer.parseInt(jTextField1.getText());
Integer tue=Integer.parseInt(jTextField2.getText());
Integer wed=Integer.parseInt(jTextField3.getText());
Integer thur=Integer.parseInt(jTextField4.getText());
Integer fri=Integer.parseInt(jTextField6.getText());
int m1=(mon*100)/8;
int m2=(tue*100)/8;
int m3=(wed*100)/7;
int m4=(thur*100)/8;
int m5=(fri*100)/8;
System.out.println(m1);
try
{
Connection con= DriverManager.getConnection("jdbc:odbc:proj");
Statement st=con.createStatement();
String s="insert into V values('"+reg+"','"+m1+"','"+m2+"','"+m3+"','"+m4+"','"+m5+"')";
st.executeUpdate(s);
JOptionPane.showMessageDialog(null, "Updated Successfully");
new VI().setVisible(true);
dispose();
}
catch(Exception e)
{
}
}
109 ISO 9001:2008

new welcom().setVisible(true);
dispose();
}
public class studentlogin extends javax.swing.JFrame {
/**
* Creates new form studentlogin
*/
public studentlogin() {
initComponents();
}
String a=(String) jComboBox1.getSelectedItem();
String b=jTextField1.getText();
if(a.matches("V"))
{
new viewV (b).setVisible(true);
}
if(a.matches("VI"))
new viewVI (b).setVisible(true);
dispose();
}
110 ISO 9001:2008

public class viewV extends javax.swing.JFrame {
/**
* Creates new form viewV
*/
public viewV( String reg )
{
initComponents();
try
{
Connection c=DriverManager.getConnection("jdbc:odbc:proj");
Statement st=c.createStatement();
String s="select * from V where regno = '"+reg+"'";
ResultSet rs=st.executeQuery(s);
}
catch(Exception e)
{
System.out.println(e.getMessage());
}
}
package internal;
import java.sql.*;
public class V extends javax.swing.JFrame {
/**
* Creates new form Marks
*/
public V() {
initComponents();
}

//Integer reg=Integer.parseInt(jTextField10.getText());
111 ISO 9001:2008

Integer a=Integer.parseInt(jTextField1.getText());
Integer b=Integer.parseInt(jTextField2.getText());
Integer c=Integer.parseInt(jTextField3.getText());
Integer d=Integer.parseInt(jTextField4.getText());
Integer e=Integer.parseInt(jTextField5.getText());
Integer f=Integer.parseInt(jTextField6.getText());
Integer g=Integer.parseInt(jTextField7.getText());
Integer h=Integer.parseInt(jTextField8.getText());
Integer i=Integer.parseInt(jTextField9.getText());
String j=jTextField10.getText();
String k=(String) jComboBox1.getSelectedItem();
int a1=(a*5)/60;
int b1=(b*5)/60;
int c1=(c*5)/60;
int d1=(d*5)/60;
int e1=(e*5)/60;
int f1=(f*5)/60;
int g1=(g*5)/100;
int h1=(h*5)/100;
int i1=(i*5)/100;
try
{
Connection con=DriverManager.getConnection("jdbc:odbc:internal");
Statement st=con.createStatement();
ResultSet rs;
String s="insert into V values
('"+j+"','"+k+"','"+a+"','"+a1+"','"+b+"','"+b1+"','"+c+"','"+c1+"','"+d+"','"+d1+"','"+e+"','"+e1+"','"+f+"','"
+f1+"','"+g+"','"+g1+"','"+h+"','"+h1+"','"+i+"','"+i1+"')";
st.executeUpdate(s);
JOptionPane.showMessageDialog(null, "Inserted");
}
catch(Exception ex)
{
System.out.println(ex.getMessage());
}
new V().setVisible(true);
dispose();
}
new Welcome().setVisible(true);
dispose();
}
112 ISO 9001:2008

package internal;
import java.sql.*;
/**
*
* @author Abraham
*/
public class ViewV extends javax.swing.JFrame {
/**
* Creates new form ViewV
*/
public ViewV(String reg)
{
initComponents();
try
{
Connection c=DriverManager.getConnection("jdbc:odbc:internal");
String s="select * from V where RegNo = '"+reg+"'";
ResultSet rs=st.executeQuery(s);
}
catch(Exception e)
{
}
113 ISO 9001:2008

package internal;
public class StaffView extends javax.swing.JFrame {
/**
* Creates new form StaffView
*/
public StaffView() {
initComponents();
try
{
ResultSet rs;
Connection c=DriverManager.getConnection("jdbc:odbc:internal");
String s="select * from V";
rs=st.executeQuery(s);
String s1="Select * from VI";
rs=st.executeQuery(s1);
}
catch(Exception e)
{
}
114 ISO 9001:2008

Case Tools Lab

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Case Tools Lab

Hochgeladen von

Copyright:

Verfügbare Formate

CS6511 CASE TOOLS LABORATORY LTPC 0032

S.No Experiments Page No

2 Book bank management system

3 Exam registration system

4 Stock maintenance system

5 Online course reservation system

7 Software personnel management system

8 Credit card processing

9 E-book management system

11 Foreign trading system

12 Conference management system

13 Bpo management system

14 Student information system

S.No. SOFTWARE REQUIREMENTS SPECIFICATION

2.0 OVERALL DESCRIPTION

DOCUMENTATION OF USECASE DIAGRAM

DOCUMENTATION OF SEQUENCE DIAGRAM:

DOCUMENTATION OF COLLABORATION DIAGRAM

DOCUMENTATION OF ACTIVITY DIAGRAM

DOCUMENTATION OF DEPLOYMENT DIAGRAM

DOCUMENTATION OF PACKAGE DIAGRAM

public class select extends javax.swing.JFrame {

/** Creates new form select */

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {

public class user extends javax.swing.JFrame {

/** Creates new form user */

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {

/** Creates new form registre */

DOCUMENTATION OF USE CASE DIAGRAM

DOCUMENTATION OF CLASS DIAGRAM:

DOCUMENTATION OF ACTIVITY DIAGRAM

DOCUMENTATION OF DEPLOYMENT DIAGRAM

public class book extends javax.swing.JFrame {

public class login extends javax.swing.JFrame {

/** Creates new form login */

/** Creates new form bb */

public class verify extends javax.swing.JFrame {

/** Creates new form verify */

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {

private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {

DATE: 3 EXAM REGISTRATION SYSTEM

10. EXTERNAL INTERFACE REQUIREMANTS

DOCUMENTATION OF CLASS DIAGRAM .

DOCUMENTATION OF SEQUENCE DIAGRAM

DOCUMENTATION OF PACKAGE DIAGRAM

CODING AND FORMS

public class register extends javax.swing.JFrame {

public static void main(String args[]) {

public class student

public class login extends javax.swing.JFrame {

Ex. No: 4 STOCK MAINTENANCE SYSTEM

STATE CHART DIAGRAM

DOCUMENTATION OF ACTIVITY DIAGRAM

DOCUMENTATION OF COMPONENT DIAGRAM

private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {

private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {

private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {

Ex No: 5 ONLINE COURSE RESERVATION SYSTEM

DOCUMENTATION FOR USE CASE DIAGRAM

DOCUMENTATION OF SEQUECE DIAGRAM

String sqlquery1 = "Insert into register

DOCUMENTATION OF USE CASE DIAGRAM

DOCUMENTATION OF CLASS DIAGRAM

DOCUMENTATION OF SEQUENCE DIAGRAM