NAME :

REGISTER NUMBER:

Laboratory Record
20ITPW502 – OBJECT ORIENTED ANALYSIS AND
DESIGN WITH LABORATORY

B. TECH INFORMATION TECHNOLOGY

V Semester
ACADEMIC YEAR: 2024– 25

1
 Certificate
Register No:

Certified that this is the Bonafede Record of work done by

Mr/Ms_____________________________________________in
the B.Tech Degree Course INFORMATION TECHNOLOGY
in the 20ITPW502 OBJECT ORIENTED ANALYSIS AND
DESIGN LABORATORY during the academic year 2024-2025

Station :
Date :

STAFF INCHARGE HEAD OF THE DEPARTMENT

Submitted for Practical Examination held on ______________________at Sri Sai Ram

Engineering College, Chennai – 600 044.

INTERNAL EXAMINER EXTERNAL EXAMINER

2
 TABLE OF CONTENTS

PageNo
Ex.no Date Title of Experiment Signature

1. STUDY OF UML

2. PASSPORT AUTOMATION SYSTEM 15

3. BOOK BANK SYSTEM 23

4. ONLINE COURSE RESERVATION SYSTEM 28

5. E- TICKETING - RAILWAY RESERVATION 34

SYSTEM

6. CREDIT CARD PROCESSING SYSTEM 41

7. FOREIGN TRADING SYSTEM 46

CONFERENCE MANAGEMENT SYSTEM

8. 53

9. LIBRARY MANAGEMENT SYSTEM 57

10. STUDENT INFORMATION SYSTEM 65

11.
EXAM REGISTRATION SYSTEM 73

12. <<<Project Title>>

3
 STUDY OF UML
AIM

General Study of UML

DESCRIPTION

The heart of object-oriented problem solving is the construction of a model. The model abstracts the
essential details of the underlying problem from its usually complicated real world. Several modeling tools
are wrapped under the heading of the UML, which stands for Unified Modeling Language. The purpose of
this course is to present important highlights of the UML.

At the center of the UML are its nine kinds of modeling diagrams, which we describe here.

❖ Use case diagrams

❖ Class diagrams
❖ Object diagrams
❖ Sequence diagrams
❖ Collaboration diagrams
❖ State chart diagrams
❖ Activity diagrams
❖ Component diagrams
❖ Deployment diagrams

The UML is applicable to object-oriented problem solving. Anyone interested in learning UML must be
familiar with the underlying tenet of object-oriented problem solving -- it all begins with the construction of
a model. A model is an abstraction of the underlying problem. The domain is the actual world from which
the problem comes. Models consist of objects that interact by sending each other messages. Think of an
object as "alive." Objects have things they know (attributes) and things they can do (behaviors or
operations). The values of an object's attributes determine its state.

Classes are the "blueprints" for objects. A class wraps attributes (data) and behaviors
(methods or functions) into a single distinct entity. Objects are instances of classes.

AN INTRODUCTION TO UMLDIAGRAM

The Unified Modeling Language is a language for specifying, constructing, visualizing, and documenting
the artifacts of a software-intensive system. Analogous to the use of architectural blueprints in the
construction industry, UML provides a common language for describing software models, and it can be
used in conjunction with a wide range of software lifecycles and development processes.

1. USE CASE DIAGRAM

Use Case diagrams identify the functionality provided by the system (use cases), the users who interact with
the system (actors), and the association between the users and the functionality. Use Cases are used

4
in the Analysis phase of software development to articulate the high-level requirements of the system. The
primary goals of Use Case diagrams include:

❖ Providing a high-level view of what the system does

❖ Identifying the users ("actors") of the system
❖ Determining areas needing human-computer interfaces.
➢ GRAPHICAL NOTATION
The basic components of Use Case diagrams are the Actor, the Use Case, and the Association.
➢ ACTOR
An Actor, as mentioned, is a user of the system, and is depicted using a stick figure. The role of the user is
written beneath the icon. Actors are not limited to humans.
If a system communicates with another application, and expects input or delivers output, then that
application can also be considered an actor.

➢ USE CASE
A Use Case is functionality provided by the system, typically described as verb + object (e.g. Register
Car, Delete User). Use Cases are depicted with an ellipse. The name of the use case is written within the
ellipse.

➢ ASSOCIATION
Associations are used to link Actors with Use Cases, and indicate that an Actor participates in the Use
Case in some form. Associations are depicted by a line connecting the Actor and the Use Case.

The following image shows how these three basic elements work together to form a use case diagram.

Use case diagrams describe what a system does from the standpoint of an external observer. The
emphasis is on what a system does rather than how.

Use case diagrams are helpful in three areas.

5
• Determining features (requirements). New use cases often generate new
• Requirements as the system is analysed and the design takes shape.
• Communicating with clients. Their notational simplicity makes use case diagrams a good way
for developers to communicate with clients.
• Generating test cases. The collection of scenarios for a use case may suggest a suite of test cases
for those scenarios.

2. SEQUENCE DIAGRAM

Sequence diagrams document the interactions between classes to achieve a result, such as a use case.
Because UML is designed for object-oriented programming, these communications between classes are
known as messages. The Sequence diagram lists objects horizontally, and time vertically, and models these
messages over time.
➢ NOTATION
In a Sequence diagram, classes and actors are listed as columns, with vertical lifelines indicating the lifetime
of the object over time.
➢ OBJECT
Objects are instances of classes, and are arranged horizontally. The pictorial representation for an Object
is a class (a rectangle) with the name prefixed by the object name (optional) and a semi-colon.

➢ ACTOR
Actors can also communicate with objects, so they too can be listed as a column.
An Actor is modeled using the ubiquitous symbol, the stick figure.

➢ LIFELINE
The Lifeline identifies the existence of the object over time. The notation for a Lifeline is a vertical dotted
line extending from an object.

➢ ACTIVATION
Activations, modelled as rectangular boxes on the lifeline, indicate when the object is performing an
action.

6
➢ MESSAGE
Messages, modelled as horizontal arrows between Activations, indicate the communications between
objects.

Below is a sequence diagram for making a hotel reservation. The object initiating the sequence of messages
is a Reservation window.

The Reservation window sends a makeReservation () message to a

HotelChain. The HotelChain then sends a makeReservation () message to a Hotel.

If the Hotel has available rooms, then it makes a Reservation and a Confirmation.

Each vertical dotted line is a lifeline, representing the time that an object exists. Each arrow is a message
call. An arrow goes from the sender to the top of the activation bar of the message on the receiver's lifeline.
The activation bar represents the duration of execution of the message.

3. ACTIVITY DIAGRAM

Activity diagrams are used to document workflows in a system, from the business level down to the
operational level. When looking at an activity diagram, elements from State diagrams are there. In fact, the
Activity diagram is a variation of the state diagram where the "states" represent operations, and the
transitions represent the activities that happen when the operation is complete. The general purpose of
Activity diagrams is to focus on flows driven by internal processing vs. external events.

7
 ACTIVITYSTATE

Activity states mark an action by an object. The notations for these states are rounded rectangles, the same
notation as found in State chart diagrams.

➢ TRANSITION
When an Activity State is completed, processing moves to another Activity State.
Transitions are used to mark this movement. Transitions are modeled using arrows.

➢ SWIM LANE
Swim lanes divide activities according to objects by arranging objects in column format and placing
activities by that object within that column. Objects are listed at the top of the column, and vertical bars
separate the columns to form the swim lanes.

➢ INITIAL STATE
The Initial State marks the entry point and the initial Activity State. The notation for the Initial State is the
same as in State chart diagrams, a solid circle. There can only be one Initial State on a diagram.

➢ FINAL STATE
Final States mark the end of the modeled workflow. There can be multiple Final States on a diagram, and
these states are modeled using a solid circle surrounded by another circle.

➢ SYNCHRONIZATION BAR
Activities often can be done in parallel. To split processing ("fork"), or to resume processing when multiple
activities have been completed ("join"), Synchronization Bars are used. These are modeled as solid
rectangles, with multiple transitions going in and/or out.

8
4. COMPONENT DIAGRAM

Component diagrams fall under the category of an implementation diagram, a kind of diagram that models
the implementation and deployment of the system. A Component Diagram, in particular, is usedto describe
the dependencies between various software components such as the dependency between executable files
and source files. This information is similar to that within make files, which describe source code
dependencies and can be used to properly compile an application.

➢ COMPONENT
A component represents a software entity in a system. Examples include source code files, programs,
documents, and resource files. A component is represented using a rectangular box, with two rectangles
protruding from the left side, as seen in the image to the right.

➢ DEPENDENCY
A Dependency is used to model the relationship between two components. The notation for a dependency
relationship is a dotted arrow, pointing from a component to the component it depends on.

5. CLASS DIAGRAM

A Class diagram gives an overview of a system by showing its classes and the relationships among them.
Class diagrams are static -- they display what interacts but not what happens when they do interact.

The class diagrams below model a customer order from a retail catalogue. The central class is the Order.
Associated with it is the Customer making the purchase and the Payment. A Payment is one of three
kinds: Cash, Check, or Credit. The order contains OrderDetails (line items), each with its associated
Item.
UML class notation is a rectangle divided into three parts: class name, attributes, and operations. Names of
abstract classes, such as Payment, are in italics. Relationships between classes are the connecting links.

Our class diagram has three kinds of relationships.

• Association -- a relationship between instances of the two classes. There is an associationbetween

two classes if an instance of one class must know about the other in order to perform its work. In a diagram,
an association is a link connecting two classes.
• Aggregation -- an association in which one class belongs to a collection. An aggregation has a
diamond end pointing to the part containing the whole. In our diagram, Order has a collection of
OrderDetails.

9
• Generalization -- An inheritance link indicating one class is a superclass of the other. A
generalization has a triangle pointing to the superclass. Payment is a superclass of Cash, Check, and
Credit.

An association has two ends. An end may have a role name to clarify the nature of the association. For
example, an Order Detail is a line item of each Order.
A navigability arrow on an association shows which direction the association can be traversed or queried.
An OrderDetail can be queried about its Item, but not the other way around. The arrow also lets you know
who "owns" the association's implementation; in this case, OrderDetail has an Item. Associations with no
navigability arrows are bidirectional.

The multiplicity of an association end is the number of possible instances of the class associated with a
single instance of the other end. Multiplicities are single numbers or ranges of numbers. In our example,
there can be only one Customer for each Order, but a Customer can have any number of Orders.

This table gives the most common multiplicities.

Multiplicities Meaning

0..1 zero or one instance. The notation n . . m indicates n tom instances.

0.. *or * no limit on the number of instances (including none).

1 exactly one instance

1.. * at least one instance

Every class diagram has classes, associations, and multiplicities. Navigability and roles are optional items
placed in a diagram to provide clarity.

10
6. PACKAGES AND OBJECT DIAGRAMS

To simplify complex class diagrams, you can group classes into packages. A package is a collection of
logically related UML elements. The diagram below is a business model in which the classes are grouped
into packages.

Packages appear as rectangles with small tabs at the top. The package name is on the tab or inside the
rectangle. The dotted arrows are dependencies. One package depends on another if changes in the other
could possibly force changes in the first.

Object diagrams show instances instead of classes. They are useful for explaining small pieces with
complicated relationships, especially recursive relationships.

This small class diagram shows that a university Department can contain lots of other Departments.

The object diagram below instantiates the class diagram, replacing it by a concrete example.

11
Each rectangle in the object diagram corresponds to a single instance. Instance names are underlined in
UML diagrams. Class or instance names may be omitted from object diagrams as long as the diagram
meaning is still clear.

7. COLLABORATION DIAGRAMS

Collaboration diagrams are also interaction diagrams. They convey the same information as sequence
diagrams, but they focus on object roles instead of the times that messages are sent. In a sequence
diagram, object roles are the vertices and messages are the connecting links.

The object-role rectangles are labeled with either class or object names (or both). Class names are
preceded by colons ( : ).

Each message in a collaboration diagram has a sequence number. The top-level message is numbered 1.
Messages at the same level (sent during the same call) have the same decimal prefix but suffixes of 1, 2,
etc. according to when they occur.

12
8. STATE CHART DIAGRAMS

Objects have behaviors and state. The state of an object depends on its current activity or condition. A
statechart diagram shows the possible states of the object and the transitions that cause a change in state.

Our example diagram models the login part of an online banking system. Logging in consists of entering a
valid social security number and personal id number, then submitting the information for validation.

Logging in can be factored into four non-overlapping states: Getting SSN, Getting PIN, Validating, and
Rejecting. From each state comes a complete set of transitions that determine the subsequent state.

States are rounded rectangles. Transitions are arrows from one state to another. Events or conditions that
trigger transitions are written beside the arrows. Our diagram has two self-transitions, one on Getting
SSN and another on Getting PIN.

The initial state (black circle) is a dummy to start the action. Final states are also dummy states that
terminate the action.

9. COMPONENT AND DEPLOYMENT DIAGRAMS

A component is a code module. Component diagrams are physical analogs of class diagram. Deployment
diagrams show the physical configurations of software and hardware.

The following deployment diagram shows the relationships among software and hardware components
involved in real estate transactions.

13
 The physical hardware is made up of nodes. Each component belongs on a node.
Components are shown as rectangles with two tabs at the upper left.

14
EXP.NO: 1 PASSPORT AUTOMATION SYSTEM
DATE:

AIM

To analyze, design and develop code for Passport Automation System using StarUML
software.

PROBLEM STATEMENT
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.

PROBLEM ANALYSIS
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 turnforwarded
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 also provides the
applicant the list of available dates for appointment to 'document verification' in the
administrator's office, from which they can select one. The system forwards the necessary
details to the police for its separate verification whose report is then presented to the
administrator. The administrator will be provided with an option to display the current
status of application to the applicant, which they can view in their online interface. After
all the necessary criteria have been met, the original information is added to the database
and the passport is sent to the applicant.

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.

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.

15
USER CHARACTERISTICS
• User - They are the person who desires 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.
• Database -It has all the privileges to add registration, delete registration and store,
display the user registration details.

TECHNOLOGIES USED
• React
• Firebase
TOOLS USED
Sublime text (text editor) and STAR UML (for developing UML Patterns).

SOFTWARE REQUIREMENTS
Front End Client -React js, Web Server - Firebase, Back End - Firestore.

HARDWARE REQUIREMENTS
128 MB RAM and Pentium III processor.

STRUCTURE OF DATABASE:
Create a table <Register> using phpmyadmin with the following attributes:
Table name: Register
S.NO FIELD TYPE SIZE

1. EmailID Varchar 15

2. Name Varchar 50

3. Password Varchar 15

4. Gender Varchar 10

5. Age Int 11

6. City Varchar 50

7. Year Int 11

8. Parent Name Varchar 30

Create a table <User> using php myadmin with the following

attributes:Table name: User

16
S.NO FIELD TYPE SIZE

1. Name Varchar 40

2. Email Varchar 10

3. Password Varchar 20

4. Created at Varchar 20

Create a table <Verify> using phpmyadmin with the following attributes:

Table name: Verify

S.NO FIELD TYPE SIZE

1. Adhaar URL Varchar 100

2. Birthcertificate URL Varchar 100

3. Pancard URL Varchar 100

UML DIAGRAMS

USE CASE DIAGRAM

The UML provides the use case diagram notation to illustrates the name of the use case
actors and relationship between them.

17
SEQUENCE DIAGRAM

● A sequence diagram illustrates in a kind of format in which each object interact via
messages. It is generalization between two or more specification diagram.
● Sequence diagram is an interaction over view diagram. It provides a big picture over
view of now a set of interaction is related in terms of logic and process flow.

COLLABORATION DIAGRAM

● It illustrates that object interaction in a graph or network format in which object can
be placed anywhere on the diagram.
● In collaboration diagram the relationship between applicant, system admin and
authority. The people must fill the application form according to detailed furnished. The
system admin verifies the all details and forward details to authority and passport is issued to
the applicant.

18
 CLASS DIAGRAM

● The UML include the class diagram, to illustrate and their association. They are used
for static object modelling

STATE CHART DIAGRAM

● It illustrates the intrusting events and state of an object and behaviors of an object is
reaction to an event. Transaction shows as allows labeled with theirs event. It is included with
initial pseudo state and final end state.
● The state chart diagram of passport automation system that the service of authority,
which is issues the passport received by the applicant and getting the passport.

19
ACTIVITY DIAGRAM

● Activity diagram shows sequential and parallel activities in a process. They are useful
for modelling business, workflows, the data flows and complex algorithm.
● A UML activity diagram offers rich notation to flows a sequential of activities. It may
be including parallel activities. It may be applied to any purpose, but it is popular for
visualization of business workflows and use case.

20
COMPONENT DIAGRAM

● A component represent a modular part of a system, that encapsulates it contents and

whose manifestation is replaced with in its environment. A component define its behaviours
in terms of provide and required interfaces.
● Here the three components are applicant, system admin and authority.
● The interface between people and system admin, from people to authority.

21
DEPLOYMENT DIAGRAM

● A deployment shows the assignment of concrete artifacts to computational nodes. It

shows the deployment of software elements to the physical architecture, and the
communication. Deployment diagrams are useful to communicate the physical and
deployment architecture.
● In the deployment diagram the object reference in component diagram is also
included the deployment diagram. In this authority and system admin, interface through the
people.
● It is the process of installing the program.

RESULT:

Thus, the Passport Automation System application was successfully designed and codes
aregenerated and then it was executed successfully.

22
EX.NO: 2 BOOK BANK SYSTEM
DATE:
AIM
To analyze, design and develop code for Book Bank system using StarUML software.

PROBLEM STATEMENT

To create Book Bank Maintenance System software that will meet the needs of the customer
and help them in registering for the book bank, enquiry about the issue of book, return book
and available books.

OVERALL DESCRIPTION
The Book Bank Maintenance System is an integrated system that has four modules as part of
it. The four modules are,
1) Registration for the new user: In this module, the user can register as new user in
the database.
2) Issue Book: In this module, it shows the details of issued book to the existing user and it
shows the available book to the particular user.
3) Return Book: In this module, shows and modify the database and store the return book
from the user and shows the fine amount.

SOFTWARE REQUIRMENTS

● Microsoft Visual Basic 6.0

● StarUML
● Microsoft Access

HARDWARE REQUIRMENTS
● 1GB RAM
● Pentium IV Processor
● 100 GB HARDDISK

STRUCTURE OF DATABASE

Create a table using Microsoft access with the following attributes:

Table name: Add books

S.NO FIELD TYPE

SIZE
1. Book name Text 50
2. author Text 50
3. Publication Text 50
4. Category Text 50
5. Availability Int 2

23
 Table name: Student details
S.NO FIELD TYPE
SIZE
1. First name Text 50
2. Last name Text 50
3. Id no Int 2
4. Gender Text 50
5. Department Text 50
6. Batch Text 50
7. Phone no Text 50

USE CASE DIAGRAM

CLASS DIAGRAM

24
SEQUENCE DIAGRAM

COLLABORATION DIAGRAM

25
ACTIVITY DIAGRAM

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

26
PACKAGE DIAGRAM

RESULT

Thus, the project for Book bank management system was designed and codes are generated
and then it was executed successfully.

27
EX.NO: 3 ONLINE COURSE RESERVATION SYSTEM
DATE:

AIM
To analyze, design and develop code for Online Course Reservation System using
StarUML software.
PROBLEM STATEMENT

As the head of information systems for a college, you are tasked with developing a new student
registration system. The college would like a new client-server system to replace its much
older system developed around main frame technology. The new system will allow students
to register for courses and view report cards from PCs attached to the campus LAN.Professors
will be able to access the system to sign up to teach courses as well as record grades.
Students may request a course catalogue containing list of course offering for all college.
Information about each course, such as professor, department and prerequisites, will be
included to help students make informed decisions.
Once the registration process is completed for the student, the registration system sends
information to the billing system so that the student can be billed for the course.

OVERALL DESCRIPTION
The Online Course Reservation System is an integrated system that has four modules as part
of it. The four modules are,

1) Login for Student: Using this module student login to the system using his/her unique
username and password
2) Student Registration: In this module, the students register his/her details in the system.
The details are stored in students table in database
3) Form for Registration: In this module the user can apply for the course by giving the
details about the candidate and selecting the quota for the registration.
4) Enquiry about course: In this module the student can enquiry about the various courses
in all the colleges.

SOFTWAREREQUIRMENTS
• Microsoft Visual Basic 6.0
• StarUML
• Microsoft Access

HARDWARE REQUIRMENTS
• 8GB RAM
• Pentium IV Processor
• 100 GB HARDDISK

28
USE CASE DIAGRAM

CLASS DIAGRAM

29
SEQUENCE DIAGRAM

30
ACTIVITY DIAGRAM

31
COLLABORATION DIAGRAM

COMPONENT DIAGRAM

32
DEPLOYMENT DIAGRAM

PACKAGE DIAGRAM:

RESULT

Thus, the project Online course reservation System was designed and codes are generated and
then it was executed successfully.

33
EX.NO: 4 E-TICKETING-RAILWAY RESERVATION SYSTEM

DATE:

AIM
The aim of the project is to implement the online railway reservation. This system
enables e-ticketing in an automated and systematic manner.

PROBLEMSTATEMENT

Our project is carried out to develop software for online Railway Reservation System. The
software is coded in VB, which is the front end, and it has Back end, which contains
information about the reservation and the availability of seats in trains. It has various options
like reservation, cancellation and to view details about available seats. Our project mainly
simulates the role of a Railway ticket booking officer, in a computerized way.
The reservation option enables a person to reserve for a ticket at their home itself. All he/ she
has to do is to just login and enter the required details. After this the reservation database is
updated with the person details, train name and also the source and destination place.
The cancellation option enables the passenger to cancel the tickets that has been already
booked by him/her.
The availability option prompts the person to enter train number, train name and date of travel.
After this the availability database is accessed and available positions are produced.

OVERALL DESCRIPTION

The E-Ticketing System is an integrated system that has four modules as part of
it. The four modules are,

1) Viewing Train Details: To view the train details. Details can be viewed by giving the
train number or Source and Destination
2) Checking Availability of Tickets: To view number of tickets available in the train
3) Reservation of Tickets: To enable the users to reserve the tickets easily
4) Cancellation of Tickets: To enable the users to cancel the tickets by giving PNR No

34
USE CASE DIAGRAM

35
CLASS DIAGRAM:

36
SEQUENCE DIAGRAM:

37
COLLABORATION DIAGRAM

DEPLOYMENT DIAGRAM

38
ACTIVITY DIAGRAM

39
 COMPONENT DIAGRAM

RESULT:

Thus, the project for E-Ticketing System was designed and codes are generated and then itwas executed
successfully

40
 EX.NO: 5 CREDIT CARD PROCESSING SYSTEM
DATE:

AIM

To analyze, design and develop code for Credit Card Processing System using
StarUML software.

PROBLEM STATEMENT
We envision a banking system that provides the customer holing a bank credit card can make
deposits, withdraws, check balances and perform transfer to and from their accounts. Credit
card processing will be attractive to banking customer because they allow access to their
accounts outside of regular business hours.
Participating Banks want to make sure the access to their customer account information is safe
and secure transaction information is accurate and reliable. Bank Customer-Want easy, low-
cost, remote access to their accounts, but want to be assuredthat their accounts aresecure and
not accessible to hackers or other their parties.
Bank must be able to handle multiple simultaneous transactions (and possible simultaneous
transaction to the same joint account). Bank owning a credit card must be able to determine the
cash on hand in the creditcard. The cash in the creditcard must be secure.

OVERALL DESCRIPTION
The Credit Card Processing System is an integrated system that has four modules as part of it.
The four modules are,
1) User Login: Using this module user login to the system using his/her unique username
and password
2) Withdraw: The purpose of this module to withdraw money from the account
3) Deposit: The purpose of this module to deposit money to the account
4) Balance Enquiry: Using this module the user can check his/her account balance and the
loan amount to pay if any.

SOFTWARE REQUIRMENTS

● Microsoft Visual Basic 6.0

● StarUML
● Microsoft Access

HARDWARE REQUIRMENTS

● 1GB RAM
● Pentium IV Processor
● 100 GB HARDDISK

STRUCTURE OF DATABASE

S.NO FIELD TYPE SIZE

1. creditcard text
2. password integer

41
S.NO FIELD TYPE SIZE
1. bankno integer

2. amount integer

ANALYSIS MODELING
The project can be explained diagrammatically using the following diagrams:

USE CASE DIAGRAM

CLASS DIAGRAM

42
SEQUENCE DIAGRAM

COLLABORATION DIAGRAM

43
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

44
 PACKAGE DIAGRAM

RESULT:

Thus, the project for Credit Card Processing System was designed and codes are generated and then it
was executed successfully.

45
EX NO: 6 FOREIGN TRADING SYSTEM
DATE:

AIM
To create a system to perform foreign trading system.

PROBLEM STATEMENT
The main activity of international marketing is the export-import procedure. This procedure
involves the actual and operational procedure of export and import trade. It also involves
documentation, procedures, rules and regulations imposed by both the exporting and
importing countries. These procedures include excise clearance, foreign exchange, etc.

INTRODUCTION
Foreign trading system is the interface between the exporter and buyer. It aims at improving
the efficiency in the production, export process and reduce the complexities involved in it to
the maximum possible extent.

PURPOSE
Considering the fact that the number of buyer 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. The system has been
carefully verified and validated in order to satisfy it.

SCOPE
The System provides an online interface to the buyer where they can fill in their personal
details and submit the necessary documents (may be by scanning). The authority concerned
with the production and shipment of goods can use this system to reduce his workload and
process the application in a speedy manner.

DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

Exporter – One who wishes to export the goods
Importer - One who wishes to obtain the goods
Regional authorities – Who provide service authority to individual and business firms
intending to export and/or import goods
IEC Number – Importer-Exporter Number
QC – Quality Control in order to ensure the quality of products

TECHNOLOGIES TO BE USED
• HTML
• JSP
• Java script
• Java

46
TOOLS TO BE USED

• Eclipse IDE (Integrated Development Environment)

• StarUML (for developing UML Patterns)
OVERALL DESCRIPTION:
It will describe major role of the system components and inter-connections.
PRODUCT PERSPECTIVE
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.
SOFTWARE INTERFACE
● Front End Client - The exporter online interface is built using JSP and
HTML.
● Web Server – Apache Tomcat Server (Oracle Corporation)
● Back End - Oracle 11g database
HARDWARE INTERFACE
● 1GB RAM
● Pentium IV Processor
● 100 GB HARDDISK
The server is directly connected to the client systems. The client systems have access to the
database in the server.

USE-CASE DIAGRAM
The book bank use cases are:
1. Preliminaries
2. Offer order
3. Production of goods
4. Shipment
5. Negotiation of documents

ACTORS INVOLVED
1. Exporter
2. Buyer

USECASE NAME: PRELIMINARIES

Individual and business firms intending to export and/or import goods and/or services should
obtain an Importer-Exporter Number from the regional licensing authorities.
USECASE NAME: OFFER ORDER
Offer is a proposal submitted by an exporter expressing his intention to export specific goods
at a specific price with specific terms and conditions. Exporter usually makes an offer in the
form of a „Proforma Invoice‟.
USECASE NAME: PRODUCTION OF GOODS
The exporting house after obtaining a confirmed order should produce the goods exactly as
specified in the invoice. If the exporting house does not have facilities, it has to procure the
products from others.

47
USECASE NAME: NEGOTIATION OF DOCUMENTS
The exporter submits the relevant documents to his buyer (banker) for getting the payment
for the goods exported.
● Production of goods
● Offer Order
● Shipment
● Buyer
● Negotiation of documents
● Exporter
● RegionalAuthorities
● Preliminaries

USE-CASE DIAGRAM

ACTIVITY DIAGRAM

48
CLASS DIAGRAM:
:

SEQUENCE DIAGRAM:

49
COLLABORATION DIAGRAM

DEPLOYMENT DIAGRAM
.

50
COMPONENT DIAGRAM

PACKAGE DIAGRAM

51
STATE CHART DIAGRAM

RESULT

Thus, the project for Foreign Trading System has been executed and codes are generated
andexecuted successfully.

52
EX NO: 7 CONFERENCE MANAGEMENT SYSTEM
DATE:
AIM
To analyze, design and code for CONFERENCE MANAGEMENT SYSTEM using StarUML
software.
PROBLEM STATEMENT
The conference management system is an online website in which the candidate can register
themselves, submit their paper and then attend the conference.

• The process of the candidate is to login the conference management system.

• Then the candidate submits the paper through online.
• The receiver then reviews the paper.
• The reviewer sends an acknowledgement to the candidate whether the paper is selected or
rejected.
• All the selected papers are shown.
• In the acknowledgement sent by the reviewer, the details of the conference, date and time at
which each event is conducted and list of events that are to be conducted .
• When the candidate opens the conference system website, he gets to know about the events
conducted and can register to submit the papers through online.

USE_CASE DIAGRAM

53
CLASS DIAGRAM

COLLABORATION DIAGRAM

54
SEQUENCE DIAGRAM

COMPONENT DIAGRAM

55
ACTIVITY DIAGRAM

DEPLOYMENT DIAGRAM

RESULT

Thus the project for Conference Management System has been successfully executed and codes are
generated successfully.

56
EX NO: 8 LIBRARY MANAGEMENT SYSTEM
DATE:

AIM
To develop a project Library Management System Using StarUML software and to implement
the software in Visual Basic.

PROBLEM STATEMENT

The Mini project titled Library Management System is library management software for the
purpose of monitoring and controlling the transactions in a library. This library management
system gives us the complete information about the library and the daily transactions done in
a Library. We need to maintain the record of new s and retrieve the details of books available
in the library which mainly focuses on basic operations in a library like adding new member,
new books, and up new information, searching books and members and facility to borrow and
return books. It features a familiar and well thought-out, an attractive user interface, combined
with strong searching, insertion and reporting capabilities. The report generation facility of
library system helps to get a good idea of which are borrowed by the members, makes users
possible to generate hard copy.

The following are the brief description on the functions achieved through this project:
End-Users:

Librarian: To maintain and update the records and also to cater the needs of the users.

Reader: Need books to read and also places various requests to the librarian.

Vendor: To provide and meet the requirement of the prescribed books.

57
USE CASE DIAGRAM:

58
CLASS DIAGRAM

59
SEQUENCE DIAGRAM

60
STATE CHART DIAGRAM

61
ACTIVITY
DIAGRAM

62
COLLABORATION DIAGRAM

COMPONENT DIAGRAM

63
DEPLOYMENT DIAGRAM

RESULT

Thus, the project for Library Management System has been successfully executed and codes are
generated successfully.

64
EX NO: 9 STUDENT INFORMATION SYSTEM
DATE:

AIM
To develop a project Student Information System using StarUML software.

PROBLEM STATEMENT
The student information system is a software application for schools, colleges and
universities to manage student data. These systems are capable of holding students' profile
details, attendance records, test scores, assessment scores etc. A robust database and web server
is implemented where the information can be shared easily among the students and also being
kept so that it can be retrieved at any time by anybody who is in need of it. It will make the
information remain authentic without adding or removing anything.
The systems vary in size. The size of the system is usually proportionate to the size of
the school, college or university. This is because the number of students, and therefore
records in the system, will be higher in a larger school, college or university as they are likely
to have a large number of students.
PROBLEM ANALYSIS
Student Information System is used in the effective dispatch of displaying the details
of all the students. 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 enter,edit,
update, delete and display (with details such as name, student id etc.,) filled by the student as
well as the faculty. The database will be provided with fee details to display the exam details
to the student, which they can view in their online interface. After all the necessary criteria has
been met, the original information is added to the database.
They are also used to:
• Hold records of the students' attendance
• Track student schedules
• Handling inquiries from students
• Managing student health records
• Enrolling new students
• Maintaining discipline records
• Managing any other records relevant to students

INTRODUCTION
Student Information System (SIS) is a web-based application software designed to introduce
a conducive and structured information exchange environment for integrating students,
parents, teachers and the administration of a school or college. They are designed with

65
diverse application potentials ranging from simple management of students‟ records at school
to management of all student-related functions as well as administrative functions of a
university or a chain of educational establishments.
PURPOSE
• Improve the management of prospective and enrolled student‟s data.
• Increase communication between divisions.
• Maintain data of stakeholders when transferring records between departments
• Provide a unified resource location for relevant stakeholders, including alumni,
faculty, support staff, and donors
• Standardize data formats among divisions
• Ease the transfer of data to external institutions
• Reduce the time spent on maintaining and organizing student record
USER CHARACTERISTICS
Admin – The administrator can view the details and update or edit or delete according to the
need of the faculty or the student.
Student – Students view their profile details and can also edit the updated details.
Faculty – Faculty can view and edit their details and the details of the students for every
term.
Database – It has all the privileges to view, edit, update, delete and store the details of the
students.

SOFTWARE REQUIREMENTS
• StarUML
• MySQL
• PhpMyAdmin
• Text Editors like notepad, VisualStudioCode etc,
• Windows Xp and above

HARDWARE REQUIREMENTS
• 532 MHz and above processor
• Minimum 256 MB of RAM
• 100 MB data space for installation
• Other necessary input & output device
STRUCTURE OF DATABASE
Field Type Null
sid int (11) No
FirstName varchar (30) No
LastName varchar (30) No
StudentID varchar (30) No
StudentEmail varchar (30) No
StudentSecurityCode varchar (20) No

66
Department varchar (10) No
DateofBirth date No
YearofJoining varchar (50) No
YearofGraduation varchar (50) No
NatureofAdmission varchar (30) No
LanguagesKnown varchar (50) No
StudentPhoto varchar (50) No
FatherName varchar (30) No
FatherOccupation varchar (30) No
AnnualIncome varchar (20) No
ParentMobileNumber varchar (10) No
MotherName varchar (30) No
MotherOccupation varchar (30) No
BloodGroup varchar (10) No
HosteliteOrDayScholar varchar (10) No
StudentMobileNumber varchar (10) No
ResidentialAddress varchar (150) No
ParentPhoto varchar (50) No
USE CASE DIAGRAM

67
CLASS DIAGRAM

ACTIVITY DIAGRAM

68
SEQUENCE DIAGRAM

69
COLLABORATION DIAGRAM

COMPONENT DIAGRAM

70
DEPLOYMENT DIAGRAM

PACKAGE DIAGRAM

71
STATECHART DIAGRAM

RESULT
Thus, the project for Student Information System was designed and codes are generated and
then it was executed successfully.
72
EX.NO: 10 EXAM REGISTRATION SYSTEM
DATE:

AIM
To analyze and design an Exam registration system using StarUML software.

PROBLEM STATEMENT

To design an Exam registration system that has been developed to meet the need of the
student and helps them to register themselves for the exam and get the details about the
exam by enquiring it. The student can able to register for the exam, process their examform,
they can able to modify the database.

PROBLEM ANALYSIS
Exam registration system is used in the effective dispatch of registration form to all of
the students. 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, student id etc.,) filled by the student.This
forms the first and foremost step in the processing of exam application.The database will
be provided with fees details to display the exam details to the student, which they can view
in their online interface. After all the necessary criteria has been met, the original
information is added to the database.

INTRODUCTION
Exam registration system is an interface between the student and the database
responsible for the registration of exam. It aims at improving the efficiency in the issue of
registering the exam and reduces the complexities involved in it to the maximum possible
extent.

PURPOSE
If the entire process of „Exam registration' is done in a manual manner then it would
takes several days for registering the exam. Considering the fact that the number of students
appearing in exam is increasing every year, an automated system becomesessential to meet
the demand. So, this system uses several programming and database techniques to elucidate
the work involved in this process.

USER CHARACTERISTICS
• Student - They are the people who desire to register the exam and submit the
information to the database.

• Database - It has all the privileges to add registration,delete registration and store ,
display the exam and student details.

• Admin - The person who has privileges to verify student details.

73
SOFTWARE REQUIREMENTS
● ·Eclipse IDE
● ·Java
● ·StarUML
● ·MySQL

HARDWARE REQUIREMENTS
● ·128MB RAM
● ·Pentium III Processor

STRUCTURE OF DATABASE :
Create a table <student> using phpmyadmin with the following attributes:

Table name: Student

S.NO FIELD TYPE SIZE

1. Student ID Varchar 15

2. Name Varchar 50

3. Password Varchar 15

4. Gender Varchar 10

5. Age Int 11

6. Department Varchar 50

7. Year Int 11

8. Email Varchar 30

Create a table <exam> using phpmyadmin with the following attributes:

Table name: exam

S.NO FIELD TYPE SIZE

1. Exam name Varchar 40

2. Exam code Varchar 10

3. Department Varchar 20

4. Fees Int 11

74
Create a table <registerexam> using phpmyadmin with the following attributes:
Table name: Register exam

S.NO FIELD TYPE SIZE

1. Exam code Varchar 10

2. Student ID Varchar 15

3. Paid fees Tinyint 1

4. Fees Int 11

USE CASE DIAGRAM

ACTORS
The actors used in this system are
1. Student:The person who registers the exam.
2. Database: Maintains the student details and exam details.
3.Admin:The person who verify the students.

The use cases used in this system are

1. Login: The student enters email-id and password to login and retrieve the information.
2. View Exam Details: The student views the details about the exam which contains subject
name, subjectcode, department allowed and exam fees.
3. Register: The new student can register by using his/her details and register,enquiry about
the exam.
4. Register for Exam: Student can register for required exams.
5.Acknowledgement: After new student registration and Exam registration
acknowledgement message shown to the student.

75
CLASS DIAGRAM
The Exam registration system class diagram consists of three classes:
1. Student: The person who registers the exam.
2. Exam Database: All student and exam datas are stored as tables.
3. Register: The student registers for required exam using exam code.

76
SEQUENCE DIAGRAM

77
COLLABORATION DIAGRAM

ACTIVITY DIAGRAM

78
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

79
PACKAGE DIAGRAM

80
STATECHART DIAGRAM:

GENERATED CODE
Enquiry about exam details:

ExamDetails.java

import javax.swing.*;
import javax.swing.table.DefaultTableModel;
import java.awt.*;
import java.awt.event.ActionEvent;

81
import java.awt.event.ActionListener;
import java.sql.*;
public class ExamDetails implements ActionListener {
JFrame frame;
JLabelheaderLabel=new JLabel("ENQUIRY EXAM");
JLabelcodeLabel=new JLabel("Exam Code/Subject Code");
JTextFieldcodeField=new JTextField();
JButtonsearchButton=new JButton("SEARCH");
JButtonexitButton=new JButton("EXIT");
ExamDetails(){
createWindow();
setLocationAndSize();
addComponentsToFrame();
actionEvent();
}
public void createWindow()
{
frame=new JFrame();
frame.setTitle("Exam Details");
frame.setBounds(40,40,500,300);
frame.getContentPane().setBackground(Color.white);
frame.getContentPane().setLayout(null);
frame.setVisible(true);
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.setResizable(false);
}
public void setLocationAndSize()
{
headerLabel.setBounds(190,20,200,70);
codeLabel.setBounds(60,100,180,35);
codeField.setBounds(230,107,180,25);
searchButton.setBounds(100,170,100,35);
exitButton.setBounds(280,170,80,35);
}
public void addComponentsToFrame()
{
frame.add(headerLabel);
frame.add(codeLabel);
frame.add(codeField);
frame.add(searchButton);
frame.add(exitButton);
}
public void actionEvent()
{
exitButton.addActionListener(this);
searchButton.addActionListener(this);

82
}
@Override
public void actionPerformed(ActionEvent e) {
if(e.getSource()==exitButton) {
frame.dispose();
new ExamInfo();
}
if(e.getSource()==searchButton) {
try {
String examname,deptname,examfees;
String code = codeField.getText();
Connection connection = DriverManager.getConnection("jdbc
:mysql://localhost:3306/examregistrat ion" ,"root","");
PreparedStatementPstatement=connection.prepareStatement("select * from exam where
examcode='"+code+"'");
ResultSetrs = Pstatement.executeQuery();
if(rs.next()) {
examname = rs.getString("examname");
deptname = rs.getString("dept");
examfees = rs.getString("fees");
new SubjectDetails(code,examname,deptname,examfees);
}
else {
JOptionPane.showMessageDialog(null,"Invalid Exam Code");
}}catch (SQLException e1) {
e1.printStackTrace();
}
}} }

SubjectDetails.java
import java.awt.Color;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import javax.swing.JButton;
import javax.swing.JFrame;
import javax.swing.JLabel;
public class SubjectDetails implements ActionListener{
public String code="";
JFrame frame1;
JLabel headerLabel1 = null,subcode=null,subname=null,dept=null,fees=null;
String examname,deptname,examfees;
JButtonokButton=new JButton("OK");
SubjectDetails(String code,Stringexamname,Stringdeptname,Stringexamfees){
this.code=code;
this.examfees=examfees;
this.deptname = deptname;

83
this.examfees=examfees;
headerLabel1=new JLabel("SUBJECT DETAILS");
subcode = new JLabel("SUBJECT CODE : "+code);
subname = new JLabel("SUBJECT NAME : "+examname);
dept = new JLabel("DEPARTMENT ALLOWED : "+deptname);
fees = new JLabel("EXAM FEES (In Rupees) : "+examfees);
createWindow();
setLocationAndSize();
addComponentsToFrame();
actionEvent();
}
public void createWindow()
{
frame1=new JFrame();
frame1.setTitle("Subject Details");
frame1.setBounds(40,40,450,400);
frame1.getContentPane().setBackground(Color.white);
frame1.getContentPane().setLayout(null);
frame1.setVisible(true);
frame1.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame1.setResizable(false);
}
public void setLocationAndSize()
{
headerLabel1.setBounds(180,10,300,70);
subcode.setBounds(90,70,300,35);
subname.setBounds(90,120,300,35);
dept.setBounds(90,170,300,35);
fees.setBounds(90,220,300,35);
okButton.setBounds(120, 270, 180, 35);
}
public void addComponentsToFrame()
{
frame1.add(headerLabel1);
frame1.add(subcode);
frame1.add(subname);
frame1.add(dept);
frame1.add(fees);
frame1.add(okButton);
}
public void actionEvent()
{
okButton.addActionListener(this);
}
@Override
public void actionPerformed(ActionEvent e) {

84
// TODO Auto-generated method stub
if(e.getSource()==okButton) {
frame1.dispose();
}
}
}

Register for an exam:

RegisterExam.java

import java.awt.Color;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import javax.swing.JButton;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.JOptionPane;
import javax.swing.JTextField;
public class RegisterExam implements ActionListener{
JFrame frame;
JLabelheaderLabel=new JLabel("REGISTER FOR AN EXAM");
JLabelstudLabel=new JLabel("STUDENT ID");
JLabelcodeLabel=new JLabel("EXAM CODE");

85
JTextFieldstudField=new JTextField();
JTextFieldcodeField=new JTextField();
JButtonregisterButton=new JButton("REGISTER");
JButtonexitButton=new JButton("EXIT");
RegisterExam(){
createWindow();
setLocationAndSize();
addComponentsToFrame();
actionEvent();
}
public void createWindow()
{
frame=new JFrame();
frame.setTitle("Register Exam");
frame.setBounds(40,40,400,300);
frame.getContentPane().setBackground(Color.white);
frame.getContentPane().setLayout(null);
frame.setVisible(true);
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.setResizable(false);
}
public void setLocationAndSize()
{
headerLabel.setBounds(100,10,200,70);
studLabel.setBounds(20,60,100,70);
codeLabel.setBounds(20,110,100,70);
studField.setBounds(180,83,165,23);
codeField.setBounds(180,133,165,23);
registerButton.setBounds(70,200,100,35);
exitButton.setBounds(220,200,100,35);
}
public void addComponentsToFrame()
{
frame.add(headerLabel);
frame.add(studLabel);
frame.add(codeLabel);
frame.add(studField);
frame.add(codeField);
frame.add(registerButton);
frame.add(exitButton);
}
public void actionEvent()
{
registerButton.addActionListener(this);
exitButton.addActionListener(this);
}

86
@Override
public void actionPerformed(ActionEvent e) {
// TODO Auto-generated method stub
if(e.getSource()==exitButton) {
frame.dispose();
new ExamInfo();
}
if(e.getSource()==registerButton) {
String studid = studField.getText();
String code = codeField.getText();
int examfees = 0;
try {
Connection connection
=DriverManager.getConnection("jdbc:mysql://localhost:3306/examregistration","root","
Root");
PreparedStatementPstatement=connection.prepareStatement("select * from exam where
examcode='"+code+"'");
ResultSetrs = Pstatement.executeQuery();
if(rs.next()) {
examfees = rs.getInt("fees");
PreparedStatement Pstatement2=connection.prepareStatement("select * from
registerexam where examcode='"+code+"' and studid='"+studField.getText()+"'");
ResultSet rs1 = Pstatement2.executeQuery();
if(rs1.next()) {
JOptionPane.showMessageDialog(null,"You have already registered for this exam!");
studField.setText("");
codeField.setText("");
}
else {
PreparedStatement Pstatement1=connection.prepareStatement("insert into registerexam
values(?,?,?,?)");
Pstatement1.setString(1,code);
Pstatement1.setString(2,studid);
Pstatement1.setBoolean(3,false);
Pstatement1.setInt(4,examfees);
Pstatement1.executeUpdate();
JOptionPane.showMessageDialog(null,"Registered Successfully");
studField.setText("");
codeField.setText("");
}
}
else {
JOptionPane.showMessageDialog(null,"Invalid Exam Code");
studField.setText("");
codeField.setText("");
}

87
}catch (SQLException e1) {
e1.printStackTrace();
}
}
}}

RESULT

Thus, the project Exam registration system was designed and codes are generated and then it
was executed successfully.
88