Professional Documents
Culture Documents
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
6 E-ticketing
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.
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.
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.
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.
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.
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
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.
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.
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;
new user().setVisible(true);
}
new login().setVisible(true);
}
private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {
10
// TODO add your handling code here:
setVisible(false);
new login().setVisible(true);
}
private void jButton4ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new login().setVisible(true);
}
package pass;
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 {
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!");
}
}
private void jButton5ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(true);
new cancel().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.
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.
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.
17 ISO 9001:2008
DOCUMENTATION OF COMPONENT DIAGRAM
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.
18 ISO 9001:2008
DOCUMENTATION OF PACKAGE DIAGRAM
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
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new cancel().setVisible(true);
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
19 ISO 9001:2008
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new login().setVisible(true);
}
20 ISO 9001:2008
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
public class bb extends javax.swing.JFrame {
try
{
PreparedStatement psm=null;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection conn=DriverManager.getConnection("jdbc:odbc:bookbank");
String sql="insert into book values('"+name+"','"+author+"')";
Statement stm=conn.createStatement();
stm.executeUpdate(sql);
JOptionPane.showMessageDialog(null, "Successfully Registered!!");
setVisible(false);
new verify().setVisible(true);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, " Successfully Registered!!");
new verify().setVisible(true);
}
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new bb().setVisible(true);
}
21 ISO 9001:2008
import java.sql.Connection;
import java.sql.DriverManager;
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;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:bookbank");
String sq="select * from book" ;
Statement stmt=connect.createStatement();
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()); } }
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.
11. FUNCTIONAL REQUIREMENTS
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.
24 ISO 9001:2008
DOCUMENTATION OF USE CASE DIAGRAM
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.
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
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.
26 ISO 9001:2008
DOCUMENTATION OF COLLABORATION DIAGRAM
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.
DOCUMENTATION OF STATE CHART DIAGRAM
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
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
27 ISO 9001:2008
DOCUMENTATION OF ACTIVITY DIAGRAM
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 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.
DOCUMENTATION OF 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
DOCUMENTATION OF DEPLOYMENT DIAGRAM
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
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.
29 ISO 9001:2008
public class opening extends javax.swing.JFrame {
public opening() {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new register().setVisible(true);
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new login().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}
30 ISO 9001:2008
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
// 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);
/**
@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);
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
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+"')";
Statement stm=conn.createStatement();
stm.executeUpdate(sql);
JOptionPane.showMessageDialog(null, "sucessfully registerd") }
catch(Exception ex)
{
System.out.println(ex.getMessage());
JOptionPane.showMessageDialog(null, "error occured in connection");
}
}
}
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new login().setVisible(true);
}
});
}
DATABASE:
import java.sql.*;
import javax.swing.JOptionPane;
public class database
{
public database(String s1,String s2)
{
try{
PreparedStatement pstm;
ResultSet rs;
32 ISO 9001:2008
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:exam");
String sq="select * from userdetails where username = '" +s1+"'and password = '"+s2+"'" ;
Statement stmt=connect.createStatement();
rs=stmt.executeQuery(sq);
System.out.println("query executed");
int count = 0;
while(rs.next())
{
count ++;
}
if(count == 1)
{
new verify().setVisible(true);
}
else
{
JOptionPane.showMessageDialog(null, "INVALID PASSWORD");
}}
import javax.swing.JOptionPane;
import net.proteanit.sql.DbUtils;
import java.sql.*;
public class verify extends javax.swing.JFrame {
public verify() {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try
{
//String s=jTextField1.getText();
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:exam");
String sq="select * from studentdetails ";
Statement stmt=connect.createStatement();
rs=stmt.executeQuery(sq);
System.out.println("query executed");
// System.out.println("check:"+rs.getInt("count")
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
}
catch(Exception ex){
JOptionPane.showMessageDialog(null, "error occurs");} }
33 ISO 9001:2008
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new opening().setVisible(true); }
public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
new verify().setVisible(true); } }); }
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.
11. FUNCTIONAL REQUIREMENTS
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
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.
35 ISO 9001:2008
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are customer, vendor and Database. The use cases are the
activities performed by actors.
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
DOCUMENTATION OF CLASS DIAGRAM
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
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.
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.
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.
37 ISO 9001:2008
DOCUMENTATION OF COLLABORATION DIAGRAM
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.
.
DOCUMENTATION OF STATE CHART DIAGRAM
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
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.
38 ISO 9001:2008
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.
39 ISO 9001:2008
.
DOCUMENTATION OF DEPLOYMENT DIAGRAM
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
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.
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
DOCUMENTATION OF PACKAGE DIAGRAM
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.*;
import javax.swing.JOptionPane;
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");
} }
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
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");
}
}
package Sample;
import java.sql.*;
import javax.swing.JOptionPane;
public class Applicant extends javax.swing.JFrame {
public Connection con;
public Statement st;
/** Creates new form start */
public Applicant() {
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");
}
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
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 javax.swing.JOptionPane;
import net.proteanit.sql.DbUtils;
import java.lang.String.*;
/**
*
* @author Keerthana
*/
public class Status extends javax.swing.JFrame {
public Connection connect;
public Statement st;
String category;
/** Creates new form Status */
public Status(String c) {
initComponents();
category=c;
try
{
Class.forName("com.mysql.jdbc.Driver");
connect = DriverManager.getConnection("jdbc:mysql://localhost:3306/stock", "root", "");
st=connect.createStatement();
JOptionPane.showMessageDialog(null, "You are now connected...!!!");
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to connect");
}
43 ISO 9001:2008
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try{
String sqlquery1 = "Select * from details where category='"+category+"'";
ResultSet rs = st.executeQuery(sqlquery1);
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to display stock details");
}
}
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
CLASS DIAGRAM:
45 ISO 9001:2008
DOCUMENTATION OF CLASS DIAGRAM
-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
46 ISO 9001:2008
DOCUMENTATION OF DEPLOYMENT DIAGRAM
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();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new Applicant().setVisible(true);
}
47 ISO 9001:2008
package Sample;
import java.sql.*;
import javax.swing.JOptionPane;
public class Applicant extends javax.swing.JFrame {
public Connection con;
public Statement st;
/** Creates new form start */
public Applicant() {
initComponents();
try
{
Class.forName("com.mysql.jdbc.Driver");
con = DriverManager.getConnection("jdbc:mysql://localhost:3306/course", "root", "");
st=con.createStatement();
JOptionPane.showMessageDialog(null, "You are now connected...!!!");
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to connect");
}
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try{
String name = jTextField1.getText();
String fname = jTextField2.getText();
String dob = jTextField3.getText();
String addr = jTextArea1.getText();
String clgcode = jTextField7.getText();
String drg = jComboBox3.getSelectedItem().toString();
String yr = jTextField6.getText();
String email = jTextField4.getText();
String mob = jTextField5.getText();
String course = jComboBox1.getSelectedItem().toString();
String sch = jComboBox2.getSelectedItem().toString();
String payment="Unpaid";
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;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
import javax.swing.JOptionPane;
public class Register extends javax.swing.JFrame {
public Connection connect;
public Statement st;
/** Creates new form Register */
public Register() {
initComponents();
try
{
Class.forName("com.mysql.jdbc.Driver");
connect = DriverManager.getConnection("jdbc:mysql://localhost:3306/course", "root", "");
st=connect.createStatement();
JOptionPane.showMessageDialog(null, "You are now connected...!!!");
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to connect");
}
}
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
4 Collaboration diagram
6 Activity diagram
7 Deployment diagram
USECASE DIAGRAM:
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:
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:
ACTIVITY DIAGRAM:
52 ISO 9001:2008
The applicant appears for book ticket and search details from E-Ticketing DataBase.
DEPLOYMENT DIAGRAM:
FORMS:
53 ISO 9001:2008
public class login extends javax.swing.JFrame {
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here
String s1=jTextField1.getText();
String s2=jPasswordField1.getText();
if((s1.compareTo("admin")==0)&&(s2.compareTo("admin")==0))
{
new update().setVisible(true);
}
else{
customer s=new customer(s1,s2);
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
dispose();
}
import java.sql.*;
import javax.swing.table.TableModel;
//import org.apache.commons.dbutils.DbUtils;
import net.proteanit.sql.DbUtils;
public class NewJFrame extends javax.swing.JFrame {
54 ISO 9001:2008
/** Creates new form NewJFrame */
public NewJFrame() {
initComponents(); }
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try
{
String s=jTextField1.getText();
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:aero");
String sq="select * from planedetails where number = '" +s+"'" ;
Statement stmt=connect.createStatement();
rs=stmt.executeQuery(sq);
System.out.println("query executed");
// System.out.println("check:"+rs.getInt("count"));
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
}
catch(Exception e)
{System.out.println(e.getMessage()); } }
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
4 Collaboration diagram
5 State Chart diagram
6 Activity diagram
7 Component diagram
8 Deployment diagram
9 Package diagram
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
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
FORMS
package personnel;
/**
*
* @author Elcot
*/
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
public class login extends javax.swing.JFrame {
58 ISO 9001:2008
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
String s1=jTextField1.getText();
String s2=jPasswordField1.getText();
System.out.println(s1);
System.out.println(s2);
try {
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:pers");
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 employ().setVisible(true);
else
JOptionPane.showMessageDialog(null,"Wrong Password");
} catch (Exception e) {
JOptionPane.showMessageDialog(null, e.getMessage());
}
}
package personnel;
/**
*
* @author Elcot
*/
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
59 ISO 9001:2008
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
import net.proteanit.sql.DbUtils;
public class employ extends javax.swing.JFrame {
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:pers");
String sq="select id from empo" ;
Statement stmt=connect.createStatement();
rs=stmt.executeQuery(sq);
System.out.println("query executed");
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
} catch(Exception e)
{
System.out.println(e.getMessage()); } }
package personnel;
60 ISO 9001:2008
import java.sql.Connection;
import java.sql.DriverManager;
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 details extends javax.swing.JFrame {
/** Creates new form details */
public details() {
initComponents(); }
private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try {
String s=jTextField1.getText();
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:pers");
String sq="select * from empo where id = '" +s+"'" ;
Statement stmt=connect.createStatement();
rs=stmt.executeQuery(sq);
System.out.println("query executed");
jTable1.setModel(DbUtils.resultSetToTableModel(rs)); }
catch(Exception e) {
System.out.println(e.getMessage()); }}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new employ().setVisible(true); }
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new logout().setVisible(true);
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
4 Collaboration diagram
6 Activity diagram
7 Component diagram
8 Deployment diagram
9 Package diagram
62 ISO 9001:2008
DOCUMENTATION OF CLASS DIAGRAM
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:
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:
64 ISO 9001:2008
DOCUMENTATION OF DEPLOYMENT DIAGRAM
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
65 ISO 9001:2008
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
import javax.swing.JOptionPane;
/**
}
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
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+"'";
st.executeUpdate(sqlquery3);
String sqlquery1 = "Update register set payment='"+payment+"' where
itemname='"+itemname+"'";
st.executeUpdate(sqlquery1);
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");
}
new Thanks().setVisible(true);
}
import java.sql.*;
import javax.swing.JOptionPane;
import net.proteanit.sql.DbUtils;
import java.lang.String.*;
public class Status extends javax.swing.JFrame {
67 ISO 9001:2008
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
connect = DriverManager.getConnection("jdbc:odbc:credit");
st=connect.createStatement();
}
catch(Exception e)
{
}
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try{
String sqlquery1 = "Select * from details";
ResultSet rs = st.executeQuery(sqlquery1);
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to display stock details");
}
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try{
int price;
String payment="Unpaid";
String no = jTextField3.getText();
int qty = Integer.parseInt(jTextField1.getText());
String sqlquery1 = "Select * from details where itemno='"+no+"'";
ResultSet rs1 = st.executeQuery(sqlquery1);
while(rs1.next()){
String name =rs1.getString(2);
price=rs1.getInt(3);
price*=qty;
String sqlquery2 = "Insert into register
values('"+name+"','"+qty+"','"+price+"','"+payment+"')";
st.executeUpdate(sqlquery2);
setVisible(false);
JOptionPane.showMessageDialog( null, "purchased successfully");
}
}
catch(Exception e)
{
//JOptionPane.showMessageDialog(null, "Unable to check details");
}
}
private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
String reg = jTextField1.getText();
setVisible(false);
new Thanks().setVisible(true);
}
68 ISO 9001:2008
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new Status().setVisible(true);
}
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
4 Collaboration diagram
69 ISO 9001:2008
6 Activity diagram
7 Deployment diagram
70 ISO 9001:2008
Database is the class name. Its attribute is operation. The operations performed is store .
SEQUENCE DIAGRAM
ACTIVITY DIAGRAM
71 ISO 9001:2008
DOCUMENTATION OF ACTIVITY DIAGRAM
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
FORMS
72 ISO 9001:2008
public class book extends javax.swing.JFrame {
public book() {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new login().setVisible(true);
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new cancel().setVisible(true);
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
73 ISO 9001:2008
// TODO add your handling code here:
String s1=jTextField1.getText();
String s2=jPasswordField1.getText();
System.out.println(s1);
System.out.println(s2);
try
{
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:Database4");
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());
}
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new login().setVisible(true);
}
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
74 ISO 9001:2008
public class bb extends javax.swing.JFrame {
try
{
PreparedStatement psm=null;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection conn=DriverManager.getConnection("jdbc:odbc:Database4");
String sql="insert into book values('"+name+"','"+author+"')";
Statement stm=conn.createStatement();
stm.executeUpdate(sql);
JOptionPane.showMessageDialog(null, "Successfully Registered!!");
setVisible(false);
new verify().setVisible(true);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, " Successfully Registered!!");
new verify().setVisible(true);
}
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
75 ISO 9001:2008
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
import net.proteanit.sql.DbUtils;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:Database4");
String sq="select * from book" ;
Statement stmt=connect.createStatement();
rs=stmt.executeQuery(sq);
System.out.println("query executed");
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
} catch(Exception e)
{
System.out.println(e.getMessage()); } }
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
76 ISO 9001:2008
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
public class payment extends javax.swing.JFrame {
77 ISO 9001:2008
public class cancel extends javax.swing.JFrame {
78 ISO 9001:2008
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are applicant, recruiter and database. The use cases are the activities
performed by actors.
The actors in this use case diagram are Student,hr,admin .
The use cases in this use case diagram are
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
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.
COLLABORATION DIAGRAM
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
import java.sql.*;
import javax.swing.JOptionPane;
public class Login extends javax.swing.JFrame {
public Connection con;
public Statement st;
public Login() {
initComponents();
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
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+"'";
ResultSet rs = st.executeQuery(sqlquery1);
if(rs.next())
{
setVisible(false);
new Applicant().setVisible(true);
}
else{
JOptionPane.showMessageDialog(null, "Wrong username or password");
}
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "Unable to login");
}
}
import java.sql.*;
import javax.swing.JOptionPane;
public class Applicant extends javax.swing.JFrame {
82 ISO 9001:2008
String mob = jTextField4.getText();
String sqlquery1 = "Insert into register
values('"+name+"','"+qual+"','"+percent+"','"+exp+"','"+post+"','"+addr+"','"+email+"','"+mob+"')";
st.executeUpdate(sqlquery1);
JOptionPane.showMessageDialog(null, " successfully inserted");
setVisible(false);
new New(name).setVisible(true);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "insertion successful");
}
}
import java.sql.*;
import javax.swing.JOptionPane;
import net.proteanit.sql.DbUtils;
import java.lang.String.*;
}
}
83 ISO 9001:2008
private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try
{
String sqlquery1 = "Select * from details where name='"+n+"'";
ResultSet rs1 = st.executeQuery(sqlquery1);
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.*;
import javax.swing.JOptionPane;
84 ISO 9001:2008
public class Technical extends javax.swing.JFrame {
public Technical(String x) {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new Status(n).setVisible(true);
}
85 ISO 9001:2008
/** Creates new form Thanks */
public Thanks() {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new Login().setVisible(true);
}
.
86 ISO 9001:2008
DOCUMENTATION OF USE CASE DIAGRAM
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
87 ISO 9001:2008
DOCUMENTATION OF 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.
Vertical dimension-represent time.
Horizontal dimension-represent different objects.
COLLABORATION DIAGRAM
ACTIVITY DIAGRAM
88 ISO 9001:2008
DOCUMENTATION OF 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
DEPLOYMENT DIAGRAM
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.
FORMS
89 ISO 9001:2008
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
public class login extends javax.swing.JFrame {
/** Creates new form login */
public login() {
initComponents();
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
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();
ResultSet rs = st.executeQuery(sqlquery1);
if(rs.next()) {
setVisible(false);
new product().setVisible(true);
} else{
JOptionPane.showMessageDialog(null, "Wrong username or password");
}
} catch(Exception e) {
JOptionPane.showMessageDialog(null, "Unable to login");
}
}
90 ISO 9001:2008
/** Creates new form product */
public product() {
initComponents();
}
private void jButton4ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new details().setVisible(true);
import java.sql.Connection;
import java.sql.DriverManager;
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;
try
{
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:fore");
String sq="select * from pro" ;
Statement stmt=connect.createStatement();
91 ISO 9001:2008
rs=stmt.executeQuery(sq);
System.out.println("query executed");
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, e.getMessage());
}
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
public class purchase extends javax.swing.JFrame {
String name=jTextField1.getText();
String detail=jTextField2.getText();
String no=jTextField3.getText();
try
{
PreparedStatement psm=null;
92 ISO 9001:2008
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection conn=DriverManager.getConnection("jdbc:odbc:pro");
String sql="insert into pro values('"+name+"','"+detail+"','"+no+"')";
Statement stm=conn.createStatement();
stm.executeUpdate(sql);
JOptionPane.showMessageDialog(null, "Successfully Registered!!");
new pay().setVisible(true);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, " Successfully Registered!!");
}
}
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
4 Deployment diagram
93 ISO 9001:2008
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are candidate, reviewer and database. The use cases are the activities
performed by actors.
The actors in this use case diagram are Candidate , Reviewer , Databases .
The use cases in this use case diagram are
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.
SEQUENCE DIAGRAM
94 ISO 9001:2008
DOCUMENTATION OF SEQUENCE DIAGRAM
DEPLOYMENT DIAGRAM
95 ISO 9001:2008
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new thanks().setVisible(true);
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new login().setVisible(true);
}
package confer;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import javax.swing.JOptionPane;
public class login extends javax.swing.JFrame {
96 ISO 9001:2008
String sqlquery1 = "Select * from Login where Username='"+username+"'and
Password='"+password+"'";
Statement st=conn.createStatement();
ResultSet rs = st.executeQuery(sqlquery1);
if(!rs.next()) {
new paper().setVisible(true);
}
} catch(Exception e) {
JOptionPane.showMessageDialog(null, "Unable to login");
}
}
package confer;
/**
*
* @author Elcot
*/
import java.sql.Connection;
import java.sql.DriverManager;
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 paper extends javax.swing.JFrame {
97 ISO 9001:2008
JOptionPane.showMessageDialog(null, "Successfully Registered!!");
setVisible(false);
new review().setVisible(true);}
catch(Exception e) {
JOptionPane.showMessageDialog(null, " not Successfully registered");
}}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
setVisible(false);
new paper().setVisible(true);
}
package confer;
/**
*
* @author Elcot
*/
import java.sql.Connection;
import java.sql.DriverManager;
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 review extends javax.swing.JFrame {
98 ISO 9001:2008
String add=jTextField2.getText();
String no=jTextField3.getText();
String refer=jTextField3.getText();
String con=jTextField3.getText();
try
{
PreparedStatement psm=null;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection conn=DriverManager.getConnection("jdbc:odbc:conf");
String sql="insert into con values('"+cname+"','"+add+"','"+no+"','"+refer+"','"+con+"')";
Statement stm=conn.createStatement();
stm.executeUpdate(sql);
JOptionPane.showMessageDialog(null, "Successfully Registered!!");
setVisible(false);
new thanks().setVisible(true);
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null, "not Successfully Registered!!");
}
}
package confer;
99 ISO 9001:2008
To develop a project Business process outsourcing(BPO) management system Using ArgoUML
software and to implement the software in JAVA .
DEPLOYMENT DIAGRAM
package javaapplication7;
/**
* Creates new form login
*/
public login() {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
String s1=jTextField1.getText();
String s2=jPasswordField1.getText();
Agent a=new Agent();
a.login(s1,s2);
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
import javax.swing.JOptionPane;
import net.proteanit.sql.DbUtils;
public class working extends javax.swing.JFrame {
/**
* Creates new form working
*/
public working() {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
try
{
String s=jTextField1.getText();
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection connect=DriverManager.getConnection("jdbc:odbc:bpoo");
String sq="select * from customerdetails " ;
Statement stmt=connect.createStatement();
rs=stmt.executeQuery(sq);
System.out.println("query executed");
// System.out.println("check:"+rs.getInt("count"));
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
}
catch(Exception e)
{
JOptionPane.showMessageDialog(null,"connection error") ;
} }
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
JOptionPane.showMessageDialog(null, "calling is in process");
}
Ex No: 14 STUDENT INFORMATION SYSTEM
Date:
UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Sequence diagram
4 Deployment diagram
CLASS DIAGRAM
DEPLOYMENT DIAGRAM
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
import javax.swing.JOptionPane;
public class adminLogin1 extends javax.swing.JFrame {
/**
* Creates new form adminLogin1
*/
public adminLogin1() {
initComponents();
}
/**
* Creates new form V
*/
public V() {
initComponents();
}
/**
* Creates new form studentlogin
*/
public studentlogin() {
initComponents();
}
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
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();
}
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
import net.proteanit.sql.DbUtils;
package internal;
import java.sql.*;
import java.sql.DriverManager;
import javax.swing.JOptionPane;
public class V extends javax.swing.JFrame {
/**
* Creates new form Marks
*/
public V() {
initComponents();
}
}
catch(Exception ex)
{
System.out.println(ex.getMessage());
}
new V().setVisible(true);
dispose();
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
// TODO add your handling code here:
new Welcome().setVisible(true);
dispose();
}
import java.sql.*;
import java.sql.DriverManager;
import net.proteanit.sql.DbUtils;
/**
*
* @author Abraham
*/
public class ViewV extends javax.swing.JFrame {
/**
* Creates new form ViewV
*/
public ViewV(String reg)
{
initComponents();
try
{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection c=DriverManager.getConnection("jdbc:odbc:internal");
Statement st=c.createStatement();
String s="select * from V where RegNo = '"+reg+"'";
ResultSet rs=st.executeQuery(s);
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
}
catch(Exception e)
{
System.out.println(e.getMessage());
}
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
import net.proteanit.sql.DbUtils;
/**
* Creates new form StaffView
*/
public StaffView() {
initComponents();
try
{
ResultSet rs;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection c=DriverManager.getConnection("jdbc:odbc:internal");
Statement st=c.createStatement();
String s="select * from V";
rs=st.executeQuery(s);
jTable1.setModel(DbUtils.resultSetToTableModel(rs));
String s1="Select * from VI";
rs=st.executeQuery(s1);
jTable3.setModel(DbUtils.resultSetToTableModel(rs));
}
catch(Exception e)
{
System.out.println(e.getMessage());
}