1

SRM VALLIAMMAI ENGINEERINGCOLLEGE

(An Autonomous Institution)
SRM Nagar, Kattankulathur-603203.

DEPARTMENT OF INFORMATION TECHNOLOGY

(Regulation 2023)

Lab Manual

IT3562 -OBJECT ORIENTED SOFTWARE ENGINEERING LAB

(V semester)
Prepared By
Dr.S.Sekar, Asso.Prof/IT

Mr.S.Suresh Kumar, Asst.Prof(Sr.G)/IT

 2

IT3562 -OBJECT ORIENTED SOFTWARE ENGINEERING LAB

OBJECTIVES:
 To design & implement complex software solutions using state of the art software solutions using
state of art software Engineering Techniques.
 To provide working knowledge of UML (Unified Modeling Languages) Sources control and
project Management.
 To provide working knowledge of the technologies essentially for incorporating in the project.
 To develop the project using any programming language
 To expertise for testing and document software.

LIST OF EXPERIMENTS:

1. Identify a software system that needs to be developed.

2. Document the Software Requirements Specification (SRS) for the identified system.
3. Identify use cases and develop the Use Case model.
4. Identify the conceptual classes and develop a Domain Model and also derive a Class
Diagram from that.
5. Using the identified scenarios, find the interaction between objects and represent them using
UML Sequence and Collaboration Diagrams
6. Draw relevant State Chart and Activity Diagrams for the same system.
7. Implement the system as per the detailed design
8. Test the software system for all the scenarios identified as per the use case diagram
9. Improve the reusability and maintainability of the software system by applying appropriate
design patterns.
10. Implement the modified system and test it for various scenarios

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. Airline/Railway reservation system
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
 3

OUTCOMES:
At the end of the course, students should be able to
 Identify and map basic software requirements in UML mapping
 Draw the UML diagrams for the given specification
 Use the technologies to create a code from design
 Develop the project using any programming language.
 Test the software system thoroughly for all scenarios and documents it.

SOFTWARE REQUIREMENTS

 Systems with ArgoUML that supports UML 1.4 and higher

PROGRAM EDUCATIONAL OBJECTIVES (PEOs)

1. To ensure graduates will be proficient in utilizing the fundamental knowledge of basic
sciences, mathematics and Information Technology for the applications relevant to various
streams of Engineering and Technology.
2. To enrich graduates with the core competencies necessary for applying knowledge of
computers and telecommunications equipment to store, retrieve, transmit, manipulate and
analyze data in the context of business enterprise.
3. To enable graduates to think logically, pursue lifelong learning and will have the capacity to
understand technical issues related to computing systems and to design optimal solutions.
4. To enable graduates to develop hardware and software systems by understanding the
importance of social, business and environmental needs in the human context.
5. To enable graduates to gain employment in organizations and establish themselves as
professionals by applying their technical skills to solve real world problems and meet the
diversified needs of industry, academia and research.

PROGRAM OUTCOMES (POs) ENGINEERING GRADUATES WILL BE ABLE TO:

1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering

fundamentals, and an engineering specialization to the solution of complex engineering
problems.
2. Problem analysis: Identify, formulate, review research literature, and analyze complex
engineering problems reaching substantiated conclusions using first principles of
mathematics, natural sciences, and engineering sciences.
 4

3. Design/development of solutions: Design solutions for complex engineering problems and

design system components or processes that meet the specified needs with appropriate
consideration for the public health and safety, and the cultural, societal, and environmental
considerations.
4. Conduct investigations of complex problems: Use research-based knowledge and research
methods including design of experiments, analysis and interpretation of data, and synthesis of
the information to provide valid conclusions.
5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and modern
engineering and IT tools including prediction and modelling to complex engineering activities
with an understanding of the limitations.
6. The engineer and society: Apply reasoning informed by the contextual knowledge to assess
societal, health, safety, legal and cultural issues and the consequent responsibilities relevant
to the professional engineering practice.
7. Environment and sustainability: Understand the impact of the professional engineering
solutions in societal and environmental contexts, and demonstrate the knowledge of, and need
for sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and
norms of the engineering practice.
9. Individual and team work: Function effectively as an individual, and as a member or leader
in diverse teams, and in multidisciplinary settings.
10. Communication: Communicate effectively on complex engineering activities with the
engineering community and with society at large, such as, being able to comprehend and write
effective reports and design documentation, make effective presentations, and give and
receive clear instructions.
11. Project management and finance: Demonstrate knowledge and understanding of the
engineering and management principles and apply these to one‘s own work, as a member and
leader in a team, to manage projects and in multidisciplinary environments.
12. Life-long learning: Recognize the need for, and have the preparation and ability to engage in
independent and life-long learning in the broadest context of technological change.

PROGRAM SPECIFIC OBJECTIVES (PSOs)

1. To create, select, and apply appropriate techniques, resources, modern engineering and IT
tools including prediction and modelling to complex engineering activities with an
understanding of the limitations.

2. To manage complex IT projects with consideration of the human, financial, ethical and
environmental factors and an understanding of risk management processes, and operational
and policy implications.
 5

COURSE OUTCOMES:
Course Name: IT3562 -OBJECT ORIENTED SOFTWARE ENGINEERING LAB
Year of study: 2025 –2026(ODD)

IT3562.1 Perform OO analysis and design for a given problem specification.

IT3562.2 Identify and map basic software requirements in UML mapping.
IT3562.3 Use the UML analysis and design diagrams.
IT3562.4 Improve the software quality using design patterns and to explain the rationale behind
applying specific design patterns.
IT3562.5 Create code from design.
CO-PO Matrix:

CO PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11
IT3562.1 2 1 1 - - - - - - - -
IT3562.2 2 2 1 - - - - - - - -
IT3562.3 2 2 1 - - - - - - - -
IT3562.4 2 2 2 - - - - - - - -
IT3562.5 2 2 1 - - - - - - - -

Justification:
Course Program
Value Justification
Outcome Outcome
Applying the basic engineering knowledge to perform the analysis of the problem
PO1 2
domain to get solution.
Identify the problem domain and perform analysis using UML and appropriate
IT3562.1 PO2 1
design diagram to find solution
Apply the knowledge,of engineering fundamentals, to the solution of complex
PO3 1
engineering problems using the UML analysis and design diagrams
Describing the Ideas and key features for UML Mapping. Identifying the approach
PO1 2
for mapping requirements to design solutions for complex problems.
Selection and application of appropriate techniques and tools for mapping the
IT3562.2 PO2 2
requirements
Apply the knowledge,of engineering fundamentals, to the solution of complex
PO3 1
engineering problems using the UML analysis and design diagrams
Identify the problem domain and perform analysis using UML and appropriate
PO1 2
design diagram to find solution.
IT3562.3 Identify and map basic software requirements in UML mapping using complex
PO2 2
problem domain
PO3 1 To solve complex problem Use the UML analysis and design diagrams
PO1 2 Deriving the appropriate pattern for designing the system
Improve the software quality using design patterns and to explain the rationale
IT3562.4 PO2 2
behind applying specific design patterns using various diagrams
PO5 2 Analyzing the design pattern and implementing the solution using modern tools.
 6

Apply the knowledge of mathematics, engineering fundamentals, to the solution of

PO1 2
complex engineering problems using the UML analysis and design diagrams
Design solutions for complex engineering problems and design system components
IT3562.5 PO2 2
using the UML design diagrams.
Identify, formulate, review research literature, and analyze complex engineering
PO3 1
problems to provide valid solutions.

CO PO1 PO2 PO3 PO4 PO5 PO6 PO7 PO8 PO9 PO10 PO11 PO12
IT3562 2 2 2 - - - - - - - - -

8. CO-PSO Matrix:

CO PSO1 PSO2 PSO3

IT3562.1 - 2 -
IT3562.2 - 2 -
IT3562.3 - 2 -
IT3562.4 - 2 -
IT3562.5 - 2 -

Justification:

Program
Course
Specific Value Justification
Outcome
Outcome
IT3562.1 PSO 2 2 Solutions of the existing system are used for problem solving and designing.

IT3562.2 PSO 2 2 Requirements are identified and mapped using UML diagrams.
IT3562.3 Developing the solutions for modern business environment usingdesign
PSO 2 2
diagrams and tools
IT3562.4 Implementing the solution using appropriate design pattern and defining the
PSO 4 2
test activities to ensure the product meets the requirements and needs.
IT3562.5
PSO 2 2 Developing code from design diagram for implementation.

CO PSO 1 PSO 2 PSO 3

IT3562 - 2 -
 7

ASSESSMENT METHOD

MARK SPLIT UP
AIM&PRE LAB VIVA QUESTIONS 20
OBSERVATION 30
CONDUCTION & EXECUTION 30
OUTPUT& RESULT 10
POST LAB VIVA QUESTIONS 10
TOTAL 100
 8

TABLE OF CONTENTS

EXP NO. NAME OF THE EXPERIMENT PAGE NO.

1. Passport Automation System 9

2. Book Bank Maintenance System 36

3. Conference Management System 45
4. Exam Registration System 53
5. Stock Maintenance System 62
6. Online Course Reservation System 70
7. Railway Reservation System 79
8. Software Personnel Management System 88
9. Credit Card Processing System 96
10. E-Book Management System 104
11. Recruitment System 112
12. Foreign Trading System 122
13. BPO Management System 133
14. Library Management System 141
15. Student Information System 149
16 *ATM 158
Additional Viva Voce Questions 162

*Topic beyond the syllabus

 9

Ex.No: 1a PASSPORT AUTOMATION SYSTEM

AIM:

To write the problem statement for the Passport automation system.

PROBLEM STATEMENT:

Passport Automation System is used to process the passport application form and dispatch

passport to the applicants. This system adopts a comprehensive approach to minimize the manual

work and schedule resources, time in an effective manner. The core of the system is to get the

online application form (with details such as personal information, address details, etc) filled by

the applicant whose testimonials are verified for its genuineness by the system with respect to

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 office. 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. The administrator will be provided with the option to display the current status of

the application to the applicant, which they can view in their online interface. The system also

provides the user with the facility to apply for the renewal of expired passports and to make

changes to current details in the passport.

RESULT:

Thus the problem statement for the Passport automation system has been done successfully.
 10

Ex.No: 1b SOFTWARE REQUIREMENT SPECIFICATION

AIM:

To write the software requirement specification for Passport Automation System.

1. 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 reduce the complexities involved in it to the maximum extent possible.

1.1Purpose:
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 it is a matter of national security, the system has to carefully
verify to satisfy it.

1.2 Scope:
This system provides an online interface for the applicant to submit the application form
filled with details. It also provides payment facilities for the user to pay online. The details given
by the applicant is cross-checked with already existing information in other databases. The system
also provides the user with options to check the status of his application, for renewal of expired
passports and make changes to existing information. The passport officer can update the status of
the application, view the verification report submitted by the police and access the information
submitted by the applicant for verification. The police can submit the verification report using this
system.

1.3 Definitions, Acronyms and Abbreviations

 Administrator/Passport Officer - refers to the authority who is vested with the privilege to
manage the entire system. It can be a higher official in the Regional Passport Office of the
Ministry of External Affairs
 Applicant – one who applies for the passport
 PAS – Passport Automation System
 SRS – Software Requirements Specification
 LAN - Local Area Network
 GUI – Graphical User Interface

1.4 References

IEEE Software Requirements Specification format from http://www.ieee.org

 11

1.5 Overview:
SRS includes three chapters.
The 1st chapter is the Introduction specifying the purpose and scope of the PAS system.
The 2nd chapter is the Overall Description which includes the product perspective, product
functions, the user characteristics and the constraints.
The 3rd chapter is the Specific Requirements which includes the software product features,
the functional requirements, the product requirements for safety and performance, and the
system attributes.
2. Overall Description
2.1 Product Perspective
The PAS acts as an interface between the applicant and the passport officer. It tries
to make the interface as simple as possible at the same time not risking the security of data
stored. The processing of the application is automated and this reduces the time duration
in which the user receives the passport.
2.2 System Interfaces
The PAS will use a relational database as backend for data storage. The client
system should be able to share the data available in the database through the network
connection.
2.2.1 User Interfaces
The PAS will provide an easy to use GUI as part of the working environment for
the applicant and the passport officer to interact with the system.
2.2.2 Hardware Interfaces
A scanner is used to scan and upload the documents needed for verification.
2.2.3 Software Interfaces
The System uses ODBC drive version 6.0 to connect and control the database.
2.2.4 Communication Interfaces
LAN is used for communication among the client and server system.
2.2.5 Memory Constraints
A minimum of 64MB RAM is needed for the client system.
2.2.6 Operations
The applicant is required to fill and submit the application form and also scan and
upload documents needed for the verification process.
The police must verify the details forwarded by the system and submit the
verification report to the passport officer.
The passport officer must verify and approve the dispatch of passport for the
applicants based on the verification report submitted by the police. He must also update
the status of the application in each stage of the process.
2.3 Product Functions
 Secure registration of information by the applicants
 Display of passport application status
 12

 SMS and e-mail updates to the applicants from the passport office
 Passport officer can generate reports from the information and add eligible
application to the database
2.4 User Characteristics
Applicant – person who applies for the passport and submits information. He need
not be a person with special skills and training. He is the average common man.
Passport Officer – person with the privilege to update the application status,
approve the issue of passport and access the applicant information. He should have the
skills and necessary training to manage the database and the system.
Police – person who verifies the details on receiving intimation from the passport
officer. He should have basic computer knowledge to communicate via the PAS to submit
the verification report.
2.5 Constraints
 The applicant requires a computer with a scanner to upload documents for
verification
 Security is of much importance as there is always a chance of intrusion in the
web world
 Should support many users simultaneously
 Must display appropriate error messages while filling the application form
2.6 Assumptions and Dependencies
If the applicant is under 18 years of age, the details of the parents passport
information can be used to obtain the passport.
3. Specific Requirements
3.1 Functional Requirements
3.1.1 Apply
Input: The Applicant fills in the application form available in the online interface giving
the personal details and family information, and submits the application form.
Process: The details furnished by the applicant are stored in the database
Output: The database is updated with the new applicant details and appropriate message
is sent to the applicant
3.1.2 Check Status
Input: The applicant enters the application number and login password
Process: The applicant password is verified and if correct, the database table containing
the status information is searched with the application number provided by the user.
Output: The status message from the table is displayed for the applicant on the screen
3.1.3 Renewal
Input: The passport holder gives the passport number, passport holder’s name and the
expiry date for the validity.
Process: The given details are verified in reference with the existing information in the
database. If found to be valid, the passport is renewed and the database updated.
 13

Output: The renewed passport is dispatched to the user.

3.1.4 Update Status
Input: The passport officer gives the application number and the status for that application
Process: The database is updated with the new status message
Output: The updated database and the message to the applicant
3.1.5 Verification
Input: The details furnished by the applicant in the application form
Process: The details are cross checked with information in already existing databases
Output: The verification report
3.1.6 Online Payment
Input: The account details of the applicant
Process: The service of an external module provided by the bank is used to process the
payment.
Output: The updated status and message to the applicant
3.2 Performance Requirements
The system should have a very short response time while displaying forms and
messages.
As the system handles personal information and payment details, it should ensure privacy
to avoid malpractices.
The system should recover from crashes without any serious loss of data and should
always maintain a backup of important information.
3.3 Design Constraints
The user interface should be an easy to use GUI that contains forms with hints to
fill in the form in correct format and display error messages when not in required format.
The database should be accessible only to the passport officer.
The system should easily adapt to future changes and hence must be modular.
3.4 Software System Attributes
3.4.1 Reliability
To make the PAS system reliable, we must ensure that duplication is avoided
3.4.2 Availability
The system should be available to the applicant to check his status at any stage of
the process, once it has been submitted. It must support more than one user at a time.
3.4.3 Security
 To avoid unauthorized access, the applicant, passport officer and police must be given
unique login and password protected
 The police should be able to access the information only when notified by the passport
officer through the system
 All the documents uploaded by the applicant should be accessible only to the system
administrator
 A log of all user logins to the system must e maintained
 14

3.4.4 Maintainability
 The PAS system should be frequently updated with any changes that may have occurred
in the rules or application interface.
 For easy updation and maintenance, the system should be modular and the user interface
simple.
3.4.5 Portability
The PAS system should be supported by any operating system and should occupy
very less memory space.
3.5 Logical Database Requirements
Several tables are used in the database to store various information.
They are:
Register – used to store the details of users registered with the system. It contains the fields:
Name, Date of Birth, Username, and Password.
Personal – used to store the details filled in by the applicant in the application form. It
contains the fields: Name, Date of Birth, Sex, Address, City, State, Qualification,
Profession, Mother’s name, Father’s Name, Marital status, and Spouse’s Name.
Report - contains the verification reports submitted by the police for the reference of the
passport officer. It contains the field: Application number, Recommendation.
Renewal Requests – contains the information regarding the renewal requests submitted by
passport holders. It contains: Passport number, Passport holder’s name and Expiry date.
Status - contains the application status. It contains the fields: Application number, Status
and Passport number (if status is approved).
Pre lab Questions:

1. What Is A Software Requirements Specification?

2. What Is SrsIn Project?
3. What Is Requirement Specifications Of The System?
4. What Is Requirement Gathering?
5. How Many Types Of Software Requirements Are There? Specify Them.
Post Lab Questions:

1. What Are User Interface Requirements?

2. What AreThe Contents Of An Effective SRS Document?
3. What Are The Software Requirement Validations?
4. What are Functional and Non Functional Requirements?
5. What Is SRS In Software Engineering?

RESULT:

Thus the software requirement specification for Passport Automation System has been
done successfully

Ex.No:1c USECASE DIAGRAM

 15

AIM:
To draw use case diagram for Passport Automation System.

Introduction:
In the Unified Modeling Language (UML), a use case diagram can summarize the details of
your system's users (also known as actors) and their interactions with the system.
 Scenarios in which your system or application interacts with people, organizations, or
external systems
 Goals that your system or application helps those entities (known as actors) achieve
 The scope of your system

Registration
(from Use case)

Police
(from Actor)
Document Verification
(from Use case)

Address Verification
(from Use case)
Applicant
(from Actor) System
Administrator
Process Status (from Actor)
(from Use case)

Renewal
(from Use case)

Passport
officer
Dispatch (from Actor)

(from Use case)

Logout
(from Use case)
 16

Pre Lab Questions:

1. Define UML?
2. What is use case diagram?
3. What is use case?
4. List out the notations of use case diagram.
5. Write the differences of Use case diagram and use case.

Post Lab Questions:

1. What is actor in usecase diagrams?

2. Can you explain primary and secondary actors?
3. How does a simple usecase look like?
4. Can you explain ‘Extend’ and ‘Include’ in usecases?
5. Define modeling in UML and it advantages.

RESULT:

Thus the use case diagram for Passport Automation System has been drawn
successfully.
 17

Ex.No:1d CLASS DIAGRAM

AIM:
To draw class diagram for Passport Automation System.
Introduction:
A class diagram models the static structure of a system. It shows relationships between
classes, objects, attributes, and operations.

Overall Class Diagram

 18

Address Verification

Document Verification

Renewal
 19

Dispatch

Pre lab Questions:

1. What do class diagrams illustrate?
2. What are the notations and partitions of class diagram?
3. What three things does a UML class define?
4. What are the relationships that can be shown in the class diagram?
5. How a UML Use Case is Diagram different from a traditional flow chart?

Post Lab Questions:

1. How do we represent private, public and protected in class diagrams?
2. What does associations, aggregation and composition in a class diagram mean?
3. What are the four principal relationships classes participate in?
4. Which illustrates an “is a” relationship between instances of a class.
5. When is it necessary to use a static or dynamic view class diagram?

RESULT:
Thus the class diagram for Passport Automation System has been drawn successfully.
 20

Ex.No:1e ACTIVITY DIAGRAM

AIM:
To draw activity diagram for Passport Automation System
Introduction:
Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system. The control flow is
drawn from one operation to another.
Before drawing an activity diagram, we should identify the following elements −
 Activities
 Association
 Conditions
 Constraints
Activity diagram can be used for −
 Modeling work flow by using activities.
 Modeling business requirements.
 High level understanding of the system's functionalities.
 Investigating business requirements at a later stage.

Pre Lab Questions:

1. What the purpose of activity diagram?
2. Draw the activity flow of a system.
3. How the activity diagram is used in a system?
4. What are the benefits of activity diagram?
5. What is Conditional logic?

Post Lab Questions:

1. What are the components of activity diagram?
2. What is decision node?
3. State the differences of fork and join.
4. When the activity diagram cannot be used?
5. What are the pros and cons of activity diagram?
 21

Applicant Administrator Police Passport Officer

Start

Login

Renew/Chan New
ge

Application
Form

Attach
Document

Submit

Address Document
Verification Verification

View Status Update Report

Status

Dispatch

RESULT:
Thus the activity diagram for Passport Automation System has been drawn successfully.
 22

Ex.No:1f INTERACTION DIAGRAM

AIM:
To draw interaction diagram for Passport Automation System

SEQUENCE DIAGRAM
Introduction:
Sequence diagrams are sometimes called event diagrams or event scenarios. A sequence
diagram shows, as parallel vertical lines (lifelines), different processes or objects that live
simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in
which they occur.

SEQUENCE DIAGRAM FOR VERIFICATION AND DISPATCH:

Police Passport Applicant System

Officer

1: Request for age proof

2: Submit age proof

3: Request for address proof

4: Submit address proof

5: Notification of submission of proof

6: Request for verification report

7: Submit verification report

8: Verification report

9: Approve dispatch of passport

10: Notification of dispatch

 23

SEQUENCE DIAGRAM FOR FRESH APPLIER:

system

: new applier : RPO : cashier

1: 1.downloads form

2: submits form

3: rejects when incorrect

4: repply

5: verification over

6: updation

7: paycash

8: update amount paid

9: generator bills

Pre lab questions:

1. What is Interaction diagram?
2. What are the different interaction diagram notations does UML have?
3. What is a sequence diagram?
4. What is a lifeline?
5. What does a message mean?

Post Lab Questions:

1. What is an interaction fragment?
2. When is the operation executing, suspended and active?
3. What is break fragment?
4. What are the three different types of message arrows?
5. What are the heuristics which sequencing diagram follows?
 24

COLLABORATION DIAGRAM

Introduction:

A collaboration diagram, also called a communication diagram or interaction diagram, is

an illustration of the relationships and interactions among software objects in the Unified
Modeling Language (UML). A collaboration diagram often comes in the form of a visual chart
that resembles a flow chart.

COLLABORATION DIAGRAM FOR VERIFICATION AND DISPATCH:

Police
2: Submit age proof
4: Submit address proof

M
1: Request for age proof
3: Request for address proof
10: Notification of dispatch Applican
t
7: Submit verification report
6: Request for verification report

5: Notification of submission of proof

8: Verification report
Passport
System
Officer
9: Approve dispatch of passport
 25

Collaboration diagram for renewal:

: RPO
: cashier

3: verifies

2: submits 5: pay cash

4: update renewal

1: download form
6: generate bills

system
: passport
holder

Pre Lab Questions:

1. What is collaboration diagram?
2. What are the symbols used in collaboration diagram?
3. What are the notations used in collaboration diagram?
4. How the messages interact between the objects.
5. How the conditional statements are denoted by?

Post Lab Questions:

1. What is sequence number?
2. Is it possible to group the sequence number?
3. How the messages are represented by?
4. What is looping?
5. What are the advantages of collaboration diagram?

RESULT:
Thus the interaction diagram for Passport Automation System has been drawn
successfully.
 26

Ex.No:1g STATE CHART DIAGRAM

AIM:
To draw state chart diagram for Passport Automation System
Introduction:
State diagram describes the behavior of a single object in response to a series of events in
a system. This UML diagram models the dynamic flow of control from state to state of a particular
object within a system.

Application
Submission

Documents & certificates

submission &Processin

System Admin Checking

& redirection

verification by
passport officer

Generation
of reports

Pre Lab Questions:

1. How to draw a state chart Diagram?
2. Where to use state chart diagram?
3. What is a state?
4. What is an event?
5. What is composite state?

Post Lab Questions:

1. What is self-transition?
2. Give the notation for initial state and final state?
3. What is the difference between state chart diagram and sequence diagram?
4. What are the basic components of state chart diagram?
5. Can we use fork and join in state chart diagram? If yes, how to use?
RESULT:

Thus the state chart diagram for Passport Automation System has been drawn
successfully.
 27

Ex.No:1h PACKAGE DIAGRAM

AIM:
To draw package diagram for Passport Automation System.
Introduction:
Package diagram is used to simplify complex classdiagrams;we can group classes
into packages. Apackage is a collection of logically related UML elements. Packages appear as
rectangles with small tabs at the top.

USER INTERFACE

Web
Swing

DOMAIN LAYER

Registration Document
verification

Process status Address

verification

Renewal Dispatch

TECHNICAL SERVICES

Database Security

Error login

Pre lab Quesitions:

1. What are the three layers of package diagram?
2. How the public elements of a package are accessible?
3. How the packages can merge?
4. What is visibility?
5. Name the elements of package diagram.
Post lab Quesitions:
1. What is the difference between template and package template?
2. How the packages can merge?
3. How the packages can import?
4. What does ‘+’ symbol and ‘-‘symbol represents in package diagram.
5. What is the difference between public and private visibility?

RESULT:
Thus the package diagram for Passport Automation System has been drawn successfully.
 28

Ex.No:1i COMPONENT DIAGRAM

AIM:
To draw component diagram for Passport Automation System.
Introduction:
The purpose of a component diagram is to show the relationship between
different components in a system. The term "component" refers to a module of classes that
represent independent systems or subsystems with the ability to interface with the rest of the
system.

Registration

Document
Verification

Address Verification
Passport
Automation System

Process Status

Renewal/Change

Dispatch

Pre Lab Questions:

1. What is the purpose of component diagram?
2. How to draw a component diagram?
3. Where to use component diagrams?
4. What is meant by artifacts?
5. What are the benefits of component diagram?

Post Lab Questions:

1. Recollect the symbols and shapes used in component diagram.
2. What is an interface?
3. What is dependency?
4. How the relationship among the artifact can be represented?
5. What is the difference between libraries and folders?

RESULT:
Thus the component diagram for Passport Automation System has been drawn
successfully.
 29

Ex.No:1j DEPLOYMENT DIAGRAM

AIM:
To draw deployment diagram for Passport Automation System.
Introduction:
Deployment diagram is a structure diagram which shows architecture of the system
as deployment (distribution) of software artifacts to deployment targets. Artifacts represent
concrete elements in the physical world that are the result of a development process.

<<client>>
passprt.exe <<application server>>
application

<<container>>
HTTP

Registration.ear <<server>>
Document verification.ear JDBC database
Address verification.ear
Process status.ear
HTTP Renewal/change.ear
<<web server>> Dispatch.ear
JSP

Pre Lab Questions:

1. What is deployment diagram?
2. What are the limitations of your physical hardware?
3. Which distribution architecture are you using?
4. Do you have all the nodes you need? Do you know how they are all connected?
5. Do you know which components are going to be on which nodes?

Post Lab Questions:

1. What are the elements of deployment diagram?
2. What is the difference between software component and software component?
3. Name some of the deployment diagram applications.
4. How the database can be connected?
5. What are runtime processing nodes?

RESULT:
Thus the deployment diagram for Passport Automation System has been drawn
successfully.
 30

Ex.No :1k IMPLEMENTATION OF PASSPORT AUTOMATION SUSTEM

AIM:
To write a code for the passport automation system.

FORM1:
Private Sub Command1_Click()
If (Text1.Text = "vignesh" And Text2.Text = "1234") Then
MsgBox "valid"
Form1.Hide
Form2.Show
Else
MsgBox "invalid"
End If
End Sub
FORM2:
Private Sub Command1_Click()
Form2.Hide
Form3.Show
End Sub
Private Sub Command2_Click()
Form2.Hide
Form4.Show
End Sub
Private Sub Command3_Click()
Form2.Hide
Form5.Show
End Sub
Private Sub Command4_Click()
Form2.Hide
Form1.Show
End Sub
FORM3:
Private Sub Command1_Click()
If (Text2.Text < 30) Then
MsgBox "stillprocessing"
Else
If (Text2.Text > 30 And Text2.Text < 50) Then
MsgBox "police verification goin on"
Else
If (Text2.Text < 80) Then
MsgBox "police verification over"
 31

Else
MsgBox "invalid"
End If
End If
End If
End Sub
Private Sub Command2_Click()
Form3.Hide
Form2.Show
End Sub
FORM4:
Private Sub Command1_Click()
MsgBox "passport is renewed"
End Sub
Private Sub Command2_Click()
Form4.Hide
Form2.Show
End Sub
FORM5:
Private Sub Command1_Click()
MsgBox "updated successfully"
End Sub
Private Sub Command2_Click()
Form5.Hide
Form2.Show
End Sub
 32

GUI DESIGN:
33
34
 35

RESULT:

Thus the project to develop a Passport Automation System is done successfully.

 36

Ex.No:2 BOOK BANK

AIM:

The aim of the project is to develop and implement the software for Book bank

PROBLEM STATEMENT:
Book bank system is a place where books are managed and maintained efficiently.The
books can be collected by the students at every semester and returned at the end of every semester.
Students visit the book bank and enquire about the required schemes. The form is filled by the
student to join the book bank and there is provision for enrollment for new members by paying
deposit. Students are identified by their unique Id no and they use their card to borrow books from
the book bank. Membership card is issued to the students once they become the members.
Membership can be renewed periodically. On request the book banker checks the book bank on
the availability of the requested book by checking the database. If the book is available, the book
keeper issues the book to the students or else collects the book in the database. There are additional
offers provided for the user for concession.
USECASE DIAGRAM

Membership
(from usecase)
Cashier

(from actor)

payment
(from usecase)

student

(from actor)
login
(from usecase)

Manager
search
(from actor)
(from usecase)

borrow
(from usecase)

renew
(from usecase)

return
(from usecase)
 37

CLASS DIAGRAM

OVERALL CLASS DIAGRAM

MEMBERSHIP AND PAYMENT:

 38

SEARCH BOOK:

BORROW:

RENEWAL AND RETURN:

 39

ACTIVITY DIAGRAM

INTERACTION DIAGRAM
 40

MEMBERSHIP

: student : cashier : manager : database

1: fill membership form
2: checks details

3: authenticate 4: update details

5: validate
6: valid user

7: issue membership

8: pay deposit

9: issue receipt

10: update

RETURNS

: student : manager : database

1: show books to return 2: verify id and book details

3: display details

4: checks fine
5: Informs student

6: pays fine

7: issues receipt

8: returns books

BORROW
 41

: student : form : manager : database

1: login and authentication 2: check validity
3: returns status

4: valid user

5: fills book details

6: checks book details 7: check book availaibility
8: returns status
9: Available

10: Borrow book 11: update details

COLLABORATION DIAGRAM

MEMBERSHIP

2: checks details

1: fill membership form

8: pay deposit

9: issue receipt
: student : cashier

10: update
5: validate
7: issue membership
3: authenticate

4: update details

6: valid user
: manager : database

BORROW
 42

5: fills book details

: student : form
1: login and authentication
10: Borrow book 6: checks book details

2: check validity
4: valid user 7: check book availaibility
9: Available 11: update details

3: returns status : database

: manager 8: returns status

RETURNS

4: checks fine

1: show books to return

6: pays fine
8: returns books

5: Informs student
: student 7: issues receipt : manager
3: display details

2: verify id and book details

: database

STATE CHART DIAGRAM

 43

Issues
the form

Fills form

verificati
on

Choose
scheme

Make
payment

Issue
membership Id

PACKAGE DIAGRAM

user interface

web swing

domain layer
membership payment login

search borrow return

offers

NewPackage
database
security
login persistance

COMPONENT DIAGRAM
 44

member
ship

payment

renew

book bank
system search

borrow

return

offers

DEPLOYMENT DIAGRAM

<<device>>
<<client>> BOOK BANK MANAGEMENT SYSTEM
bookbankman
agements... <<server>>

HTTP <<application>>
Membership.ear Database Server
Payment.ear JDBC
login.ear
search.ear
<<webserver>>
HTTP/SOAP
borrow.ear
Return.ear
JSP

RESULT:
Thus the project to develop a Book Bank Maintenance System is done successfully.
Ex.No: 3 CONFERENCE MANAGEMENT SYSTEMS
 45

AIM:
To develop an application to manage Conference Management System that will enable
individuals to organize and manage their own conferences and events.

PROBLEM STATEMENT:
The Conference Management System is designed to manage paper submissions, reviewing
and conducting conferences. It is a web service that will enable companies or individuals to
organize and manage their own conferences and events. The main focus of the proposed system is
paper submission and reviewing. This system proposes the participants, organizers and reviewers
to do their work in their respective activities.
The main benefit of CMS is to reduce the time for receiving and reviewing papers. The
goal is to conduct conferences on selected paper. This includes registration of authors, paper
submission, reviewer assignments, group emailing, collecting ranks given by reviewers, collecting
final accepted paper. The project can be useful be conduct institutional/technical conferences. The
primary actor of the conference management system is the participants and the supporting actors
are review committee and the organizers. The participants fill the registration form and submit
their paper with the required details. The submitted paper is reviewed by the committee and the
result is notified to all through mail. The selected papers will be presented in the conference, the
judge will review it and the results will be published.
USECASE DIAGRAM

advertisement
(from usecase)

registeration
(from usecase)
review comitee
(from actor)

review and selection

(from usecase)

intimation and confirmation

(from usecase)
organiser
participant (from actor)
(from actor)

paper presentation
(from usecase)

judge
notification of result
(from actor)
(from usecase)

CLASS DIAGRAM
 46

OVERALL CLASS DIAGRAM

PAPER PRESENTATION:

REVIEW AND SELECTION

 47

CONFIRMATION AND INTIMATION

RESULT NOTIFICATION

ACTIVITY DIAGRAM
 48

Student Oragniser Rev iew comittee Judge

Advertiseme
nt

not interested

interested
Verifies student details(only one
Register
registeration per student is allowed

not valid user

valid user

Issue ID Submit
paper

Review
paper

not selected

selected

Notify thorugh Notify through

mobile number emai-id

Presentation

Evaluate

Declare
result
Receive prize
and certificate

winner not a winner

Receive Prize Receive

and certificate certificate

INTERACTION DIAGRAM
 49

SEQUENCE DIAGRAM
1. REGISTERATION

: Participant : registeration form : Database

: Organiser
1: Fill
2: Check
3: Stored

4: validate

5: Reg accepted

6: Issue participant ID

2. PAPER PRESENTATION

: Participant : Paper Presentation : Database

: Judge : Organiser

1: Present paper

2: Evaluate

3: Comments on paper
4: Notify result

5: Store results

6: Notify results to participant

7: Collects certificates and prizes

 50

3. SUBMISSION AND REVIEW

: Organiser : Database
: Participant : Paper submission : review comitte

1: Submits paper

2: Review

3: Select papers
4: Store list

5: validate

6: OK

7: Calls for presentation

COLLABORATION DIAGRAM
1. REGISTRATION
1: Fill

: Participant : registeration form

4: validate 2: Check
6: Issue participant ID

5: Reg accepted

3: Stored
: Database : Organiser

2. SUBMISSION AND REVIEW

1: Submits paper 2: Review

: Participant : Paper submission : review comitte

5: validate
7: Calls for presentation 3: Select papers

4: Store list

6: OK
: Organiser : Database
 51

3. PAPER PRESENTATION
1: Present paper

: Participant : Paper Presentation

7: Collects certificates and prizes

6: Notify results to participant 2: Evaluate

3: Comments on paper

4: Notify result
: Organiser 5: Store results : Judge

: Database

STATE CHART DIAGRAM

Paper
presentation

Evaluation of
presentations

Comment to
participants

criteria for
selection

computation
of results

submission of
results to organiser

Result notification
to participants

Collection of
certificates
 52

PACKAGE DIAGRAM
User interface

swing web

Domain layer

Ad Registration paper
submission

review and paper result

selection presentation notification

Technical services

Database Security Error login

COMPONENT DIAGRAM
Advertise
ment

Registratio
n

Conference
managem...
Paper
submission

Review and
selection

Paper
presentation

DEPLOYMENT DIAGRAM
<<client>>

Conference.exe

<<client>> <<server>>
application server :database server
http

<<client
Participant
jdbc
database
register.ear
papersubmission.ear
<<web browser>> http review.ear
web results.ear

RESULT:
Thus the project to develop a Conference Management System is done successfully.
 53

Ex. No: 4 EXAM REGISTRATION SYSTEMS

AIM:

To develop a mini project for Exam Registration system.

PROBLEM STATEMENT:

Exam Registration system is the process of enrolling for exams. Enrolling students into the
general associate course examination is very difficult and important process. The main outcome is
to computerize everything related to registrations like GATE, CAT exams.
The student should download the registration form, read the rules and they have to fill up
the form. The payment for registration can be done wither through cheque or credit/debit.
Students have to submit the form to administrator. They view the form for confirmation and they
print the hall ticket. Unique ID is given to the student. The issuing of hall ticket to the student
involves certain procedure like verifying details, check for duplication and check the payment
which is done by the administration. The student can view the information like date, time on web
page. The registration number and other related information will be sent to the student through E-
mail by administrator.
USECASE DIAGRAM

Registration

Selection

Exam detail

Verification

Student admin
Payment

Print hallticket
 54

CLASS DIAGRAM
OVERALL CLASS DIAGRAM

Registration:

Selection:
 55

Exam details:

Verification:

Payment:

Issue hall ticket:

 56

ACTIVITY DIAGRAM

student admin

Register

Fill Details

Select Exam
Course

Submit

Verify Display
exam details

Payment

Credit/Debit Net Cash

Successful

Issue hall
ticket
 57

SEQUENCE DIAGRAM
SELECTION:

: student : form : system

: admin
1: login

2: enter name and password

3: type name and password

4: verify

5: login successful

6: request course details

7: provide details

8: selected course

9: submit

PAYMENT:

: student : system : admin : database

1: request payment details

2: select course

3: enter selected course

4: submit

5: verify

6: return status

7: details

8: display payment details

9: pay

10: email
 58

ISSSUE HALL TICKET:

: student : System : admin

1: Select course

2: submit

3: check eligibility

4: check payment

5: Details

6: issue hall ticket

COLLABORATION DIAGRAM

SELECTION:

1: login
3: type name and password

2: enter name and password

: student : form

6: request course details

7: provide details
8: selected course

: admin

4: verify
5: login successful
9: submit

: system
 59

PAYMENT:

1: request payment details

2: select course
3: enter selected course
9: pay

8: display payment details

: student 10: email : system

7: details

4: submit

5: verify

6: return status : database

: admin

ISSUE HALL TICKET:

1: Select course
: student

6: issue hall ticket

: System

5: Details

2: submit
3: check eligibility
4: check payment

: admin
 60

STATE CHART DIAGRAM

Select
exam

display exam
details

Check
eligibility

Make
payment

Confirmation

Issue
Hallticket

PACKAGE DIAGRAM

User interface

Swing Web

Domain Layer

Registration Selection Verification

Exam Details
Payment Hall ticket

Technical services

Database Security Error login

 61

COMPONENT DIAGRAM
Registration

Selection

Verification
Exam
Registration

Exam Details

Payment

Hall Ticket

DEPLOYMENT DIAGRAM

<<client>> <<server>>
exam registration <<server>>
database(os)
system.exe application service layer(OS)

http
.EJP container JDBC
registration.ear
selection.ear
verification.ear
display exam details.ear
payment.ear
http
<<web server>> issue hall ticket.ear
JSP

RESULT:
Thus the project to develop an Exam Registration System is done successfully.
 62

Ex. No: 5 STOCK MAINTENANCE SYSTEM

AIM:

The aim of the project is to develop and implement the software for stock maintenance
system .

PROBLEM STATEMENT:
Stock maintenance gives an idea about how products are maintained in the particular
concern. This is a database to store the details about stock inward and stock outward.
The manufacture is the producer of the item and it contains the necessary information of
the item such as price per item, date of manufacture, best before use, number of item available and
their company address.The shopkeeper is the one who is primary source for selling items in the
market. The customers get item from the shopkeeper and the database records all the transactions.
USECASE DIAGRAM

login
(from usecase)

product display
(from usecase)

customer
purchase detail
(from actor)
(from usecase)

biling/payment
(from usecase)

delivery
(from usecase)

stock verification
(from usecase)
stock manager
(from actor)

stock order
(from usecase)

stock supply
supplier
(from usecase)
(from actor)

stock updation
(from usecase)

CLASS DIAGRAM
 63

OVERALL CLASS DIAGRAM

PRODUCT DISPLAY
 64

BILLING /PAYMENT

STOCK ORDER
 65

STOCK SUPPLY

ACTIVITY DIAGRAM
customer stock manager supplier

login

display item

stock
product
verification
catalog

view details product stock shortage

discription order

purchase

no change order view order

payment

stock supply

update

verify
 66

SEQUENCE DIAGRAM
BILLING/PAYMENT

: stock manager : system

: customer
1: provide selected item
2: enter item

3: total

4: provides bill

5: payment

6: delivery

STOCK ORDER

: stock manager : form : system : supplier

1: verifies stock

2: provide details
3: login

4: enter username & password

5: type username and password

6: submit
7: validate

8: login successful

9: place order

10: total

11: pays amount

12: deliver stock

 67

STOCK UPDATE

: stockmanager : form : system : supplier : database

1: place order

2: deliver order

3: verify

4: pays
5: login
6: enter username &password
7: type username & password
8: submit
9: validate

10: login successful

11: request to update

12: enterdetails

13: provide details

14: update details
15: return status

16: updated succesful

COLLABRATION DIAGRAM

BILLING/PAYMENT
1: provide selected item
5: payment

4: provides bill
: customer 6: delivery : stock
manager

3: total

2: enter item

: system
 68

STOCK ORDER
7: validate

1: verifies stock

2: provide details
: stock 8: login successful : system
manager

9: place order 3: login

11: pays amount 5: type username and password
6: submit
10: total 4: enter username & password
12: deliver stock

: supplier
: form

STOCK UPDATE
9: validate

14: update details

15: return status

: system : database : supplier

10: login successful

12: enterdetails
1: place order
16: updated succesful
4: pays
8: submit
11: request to update
13: provide details 2: deliver order
3: verify

6: enter username &password

5: login
: form 7: type username & password : stockmanager

STATECHART DIAGRAM

view
product

select
product

billing

payment

delivery
 69

PACKAGE DIAGRAM

COMPONENT DIAGRAM
product
detail

purchase
detail

billing

stock maintenance
system

delivery

stock
verification

stock
supply

DEPLOYMENT DIAGRAM
<<client>>
<<server>>
stockmaintenance
database(os)
system.exe
<<server application>>
application service layer

HTTP :EJP container

JDBC
product detail.ear
purchase detail.ear
<<web server>> billing.ear
JSP delivery.ear
HTTP
stock verification.ear
stock supply.ear

RESULT:
Thus the project to develop a Stock Maintenance System is done successfully.
 70

Ex. No: 6 ONLINE COURSE RESERVATION SYSTEMS

AIM:
To implement software for online course reservation system.

PROBLEM STATEMENT:
The system should provide details of the college and should allow easy registration by
applicants for their admissions into the college by filling in the applications with their personal
details and the marks obtained by them along with their choice of courses in order of three.
Candidates with a cutoff of 75 and age between 18 and 25 will be sent intimation and will
be short listed as eligible candidates and their ranks will be published. The selected candidates will
be allotted seats according to their ranks, their choice of course and the number of seats vacant.
USECASE DIAGRAM

Registration
(from Use Case)

Login
(from Use Case)

View course
(from Use Case)

Eligible
(from Use Case)

Candidate Administrator
(from Actors) Availability (from Actors)
(from Use Case)

Submit Application
(from Use Case)

Verification
(from Use Case)

Payment
(from Use Case)

Confirmation
(from Use Case)

CLASS DIAGRAM
 71

OVERALL CLASS DIAGRAM

Registration:
 72

View course:

Eligibility:
 73

Availability:

Submit:

Verification:

Payment:
 74

Confirmation:

ACTIVITY DIAGRAM
Candidate Administrator

Register

Login

valid

no

yes

Show College
and course

Select
College
check
availability
Select
Course

verification and
confirm selection

Payment

Net Banking credit/debit

Verify

allotment and
confirm seat
 75

INTERACTION DIAGRAM

SEQUENCE DIAGRAM
Availability

: Student : System : Admin

1: view college and course

2: request to select college

3: select college
4: submit selected college

5: send details

6: request to select course

7: select course

8: submit selected course

9: send availability details

10: show availability details

Payment

: Student : Database : bank gateway

: Admin
1: show course and college
2: verify and seat selection

3: seat allocation

4: give payment details

5: submit payment details

6: pay amount

7: update

8: give acknowledgement

Seat confirmation

: Student : Admin : Database

1: request to view college and course

2: provide details
3: verify availability
4: check availability

5: shows availability

6: select college and course

7: update

8: acknowledgement

9: payment
10: verify details

11: seat confirmed

 76

COLLABORATION DIAGRAM
Availability
1: view college and course
3: select college
7: select course

2: request to select college : System

: Student 6: request to select course
10: show availability details

5: send details
9: send availability details
4: submit selected college
8: submit selected course

: Admin

Payment

: bank gateway
: Student

1: show course and college

4: give payment details
5: submit payment details
3: seat allocation 6: pay amount
8: give acknowledgement

: Admin 2: verify and seat selection

7: update : Database

Seat confirmation
1: request to view college and course
3: verify availability
6: select college and course
9: payment

2: provide details : Admin

: Student 8: acknowledgement

5: shows availability 4: check availability

11: seat confirmed 7: update
10: verify details

: Database
 77

STATECHART DIAGRAM

View
Course

Check
eligibility

Check Select Alternate

Availability course

yes

Select Course
and College

Payment

Confirm
Seat

PACKAGE DIAGRAM

UI layer

Swing Web

Domain layer

Register Login View Course

Eligible Availability Submit

Verification Payment Confirmation

Technical Layer

Database Error Login Security

 78

COMPONENT DIAGRAM
Register

Login

View
Course
Online course
reservation system
Eligible

Availability

Submit

Verification

Payment

Confirmation

DEPLOYMENT DIAGRAM

<<client>>
<<server>>

coursereservation .exe .EJP Container

<<server>>
HTML database server
display course
SQL OS=LINIX
check eligibility
check availability

<<webbrowser>>
seat allotment
HTML

JSP

RESULT:
Thus the project to develop an Online Course Reservation System is done successfully.
 79

Ex.No:7 RAILWAY RESERVATION SYSTEMS

AIM:

The aim of the project is to develop and implement the software for Railway
ReservationSystem.

PROBLEM STATEMENT:

Itis a system which provides an effective way to reserve ticket with remote access to the
issuing authority. It helps the user to book ticket without standing in queue and need not to go to
booking office. It manages all the information and data which are centrally stored. All the
reservation, cancellation, updation etc. are reflected to the centrally stored database. Its basic
process is to identify an authorized user and provide the user his/her required operation. Initially
the user should authenticate them by creating an identity so that the user can be identified.

It provides various operations like reservation, cancellation, status details etc. In

reservation, before reserving ticket, it shows the availability status also which is helpful to the user.
A major part of this system is the support of internet payment, which needs a secure way to transfer
the payment. At the end it provides the user with a e-ticket, which will be the authorized ticket
with which the user will travel.

USE CASE DIAGRAM

LogIn
(from Use Case)

Search Train
(from Use Case)

Train Details
(from Use Case)

Reservation
User (from Use Case) Database
(from Actor) Admin
(from Actor)

Payment
(from Use Case)

Cancellation
(from Use Case)

Refund
(from Use Case)
 80

CLASS DIAGRAM
OVERALL CLASS DIAGRAM

RESERVATION

PAYMENT
 81

CANCELLATION

REFUND
 82

ACTIVITY DIAGRAM

USER ADM IN

LogIn

Verify

Re-enter Username
& Password

Plan Train
Travel PNR

Search
Train Check
Details
Display
Train Details

Cancel
Ticket
Select Booking
Type
Deallocate
Check Seat Seat
Availability

Reservation Refund

Payment

Credit Debit
Card Card

Recieve
Payment

Payment Allocate
Acknowledgement Seat

Print
Ticket
 83

INTERACTION DIAGRAM
SEQUENCE DIAGRAM

SEARCH TRAIN

: User : Form : Admin : Database

1: Fill Login Form
2: Submit form
3: Verifies
4: Validate user
5: Allow user
6: Ask for Service

7: Input station details

8: Search related trains
9: Send Search Result
10: Display Search Result

RESERVATION

: User R : Admin R : Database R

1: Search Train

2: Train List

3: Request Train Details

4: Get Train Details

5: Train Details
6: Show Train Details

7: Verify Availability
8: Check Availability

9: Availability Info
10: Show Availability

11: Reserve Ticket

12: Make Payment
13: Update
14: Send Ticket
 84

PAYMENT

: User P : Admin P : Database P : Bank Gateway

1: Reserve Ticket
2: Verify Availability
3: Check Availability
4: Availability Data
5: Display Availability

6: Give Payment Details

7: Request Payment

8: Pay Amount
9: Update
10: Give ACK

COLLABORATION DIAGRAM
SEARCH TRAIN

1: Fill Login Form

: User : Form

7: Input station details

2: Submit form
6: Ask for Service
4: Validate user 10: Display Search Result

5: Allow user
9: Send Search Result

3: Verifies
: Database 8: Search related trains : Admin
 85

RESERVATION

: Database R

: User R
1: Search Train 4: Get Train Details
3: Request Train Details 8: Check Availability
7: Verify Availability 13: Update
11: Reserve Ticket
12: Make Payment 5: Train Details
9: Availability Info
2: Train List
6: Show Train Details
10: Show Availability
14: Send Ticket

: Admin R

PAYMENT

1: Reserve Ticket
2: Verify Availability
6: Give Payment Details

: User P 5: Display Availability : Admin P

10: Give ACK
8: Pay Amount
4: Availability Data
3: Check Availability
9: Update 7: Request Payment

: Database P
: Bank Gateway
 86

STATE CHART DIAGRAM

Fill Form

Get Source and

Destination Station

Train
Details

Check Alternate Train

Availability Details

Book
Ticket

Passernger
Details

Make
Payment

Reserve
Ticket

PACKAGE DIAGRAM
 87

COMPONENT DIAGRAM
LogIn

Search
Train

Train
Details

E-Ticketing Reservation
System

Payment

Cancellation

Refund

DEPLOYMENT DIAGRAM

E-Ticketing System

<<container>>

LogIn.ear
Search Train.ear
<<client>> Train Details.ear
e-ticketing.e Reservation.ear
xe http
Payment.ear
Cancellation.ear
Refund.ear

http

web browser

jdbc
jsp

<<server>>
database

RESULT:
Thus the project to develop an E-Ticketing System is done successfully.
 88

Ex.No:8 SOFTWARE PERSONNEL MANAGEMENT SYSTEM

AIM:

The aim of the project is to develop and implement the software for software personnel
management system.

PROBLEM STATEMENT:

In a simpler way, the application allows the HR department to manage its employee in a
better way. It will take very little time to find out all the details about an employee and his
contribution to the organization. It will also facilitate keeping track of all the records of employee
thereby making it easier for HR department.
It involves new system upgrades of software to send and capture information related to
payment and management of employee. He uses system to plan and analyze performance metrics
driven human resource functions including recruitment, attendance, compensation and benefits.
Software personnel management system should align for maximum operative efficiency with
financial accounting operations, customer relationship management, security and business of
organization.
USE CASE DIAGRAM

login
(from use case diag)

recruitement
(from use case diag)

training
(from use case diag)

view profile
(from use case diag)

work time
(from use case diag)
employee admin
(from actor) (from actor)

performance achievements
(from use case diag)

salary
(from use case diag)

update profile
(from use case diag)

logout
(from use case diag)
 89

CLASS DIAGRAM

OVERALL CLASS DIAGRAM

 90

INTERACTION DIAGRAM

RECRUITMENT

WORK TIME

TRAINING
 91

ACHIEVEMENTS

ACTIVITY DIAGRAM

Applicant HR Admin

login

not valid authenticate

re enter name
and password
valid

fills enrolement recruit

form

no
experiance

yes
attend
training
selected as
employee

yes
test

no

monitors

peformance and
achivements

work time achivements

record
achivements

logout update
salary
 92

SEQUENCE DIAGRAM
SALARY

: employee : log entry : acievements : hr : admin : sal

1: swipes card
2: records
3: monitored

4: info abt achievemnts

5: validates

6: given to hr

7: calculates sal based on log entry and achievemnts

8: notified

9: updates
10: shown to employee

RECRUITMENT
 93

: applicant : form : admin : test : HR : interview

1: fills
2: verified by

3: validates

4: attends

5: qualifies for

6: conducts

7: notifies

8: becomes employee

TRAINING

: hr : trainer : training : emp : report

1: selects
2: conducts
3: attends

4: report genration

5: report given to HR

COLLABORATION DIAGRAM
TRAINING
1: selects 2: conducts

: hr : trainer : training
3: attends

5: report given to HR 4: report genration

: emp : report
 94

RECRIUTMENT
8: becomes employee
7: notifies

5: qualifies for
: interview
: applicant
4: attends

6: conducts
: test
1: fills 3: validates

2: verified by

: admin : HR
: form
 95

SALARY CALCULATION

9: updates

: admin
10: shown to employe 8: notified

: employee : sal

4: inform abt achievemnts

5: validates

1: swipes card 7: calculates based on log entry and achieve...

2: records : acievements
6: given to

3: monitored

: log entry
: hr

STATE CHART DIAGRAM

 96

PACKAGE DIAGRAM

user interface

web swing

domain
recruitemnt worktime training

salary
performance n update profile
achievements

technical services

database
security error logging

COMPONENT DIAGRAM

recruitme
nt

work
time
software personnel
mgmt system
training

performance n
achievements

salary

update
profile

DEPLOYMENT DIAGRAM

<<client>>
s/w personnel mgmt.exe s/w mgmt sys
{OS.SOLARIS}

<<processor>>
.EJPCONTAINER
http
recruitmnt.ear <<DB server>>

training.ear
db
worktime.ear
jdbc {OS.SOLARIS
performance.ear
web browser salary.ear
http update.ear
JSP

RESULT:
Thus the project to develop aRailway Reservation System is done successfully.
 97

Ex.No:9 CREDIT CARD PROCESSING SYSTEMS

AIM:

The aim of the project is to develop and implement the software for credit card processing
system.

PROBLEM STATEMENT:
The credit card is used for the transaction of money between the users on the bank for the
credit card. The customer must have an account in the bank then the bank provides the credit card
for the customer with a unique card numbercalled personal identification number (PIN) this PIN
number contains the Security information.

During the purchase of goods, using the credit card, the customer canbuy the goods, and
the bank will pay the amount then after a certain period the amount due must be paid by the
user to the bank. Thus the credit card paid in the bank, transaction credit card also be used for
the online purchase of goods and only an authorized user can do the transaction after each
transaction the amount is to be updated regularly by the bank.

USECASE DIAGRAM

credit card request

(from use case)
bank
customer (from actors)

(from actors) credit card issue

(from use case)

login
(from use case)

server
(from actors)
purchase
(from use case)

payment
(from use case)

updation
(from use case)

bill payment
(from use case)
 98

CLASS DIAGRAM
OVERALL CLASS DIAGRAM
 99

Credit card request

Purchase

Payment
 100

Updation

ACTIVITY DIAGRAM

customer serv er bank

credit card
request

check details

produce correct
details wrong

correct

credit card
issue

received
credit card

login

wrong

enter correct correct

info

purchase

payment

cvv no. balance amount limit

bill payment

updation
 101

INTERACTION DIAGRAM

SEQUENCE DIAGRAM
Credit card request

: customer : form : bank : constraint set

1: fill the form
2: submit
3: checking

4: valid details

5: credit card issue

Updation

: server : database : customer : bank

1: does amount updation

2: viewed by customer
3: pays monthly bill payment

4: does updation

Payment

: customer : shop : server : gateway : database

1: enters

2: select item

3: billing desk

4: select mode of payment

5: credit card

6: card type

7: premium card
8: check valid card
9: verify card details

10: correct details

11: amount details for payment

12: bill signature

 102

COLLABORATION DIAGRAM

Credit card request

1: fill the form

: customer : form

5: credit card issue

2: submit
3: checking

4: valid details
: bank : constraint set

UPDATION
1: does amount updation

: server : database

4: does updation
2: viewed by customer

3: pays monthly bill payment

: customer : bank

PAYMENT

1: enters
2: select item
3: billing desk

: shop
: customer 5: credit card
7: premium card

4: select mode of payment

6: card type
11: amount details for payment
12: bill signature

8: check valid card : server

: gateway
9: verify card details

10: correct details

: database
 103

STATE CHART DIAGRAM

login

select
item

add selected
item to cart

verify and
view cart

enter bank
account

payment

PACKAGE DIAGRAM
 104

COMPONENT DIAGRAM

credit card
request

credit card
issue

credit card
processing
login

purchase

payment

updation

bill
payment

DEPLOYMENT DIAGRAM

<<client>> <<client>>
credit card.exe credit card processing
http <<container>>
<<dbserver>>

credit card request.ear bank database

credit card issue.ear jdbc
login.ear
<<webserver>> http purchase.ear
payment.ear
jsp updation.ear
bill payment.ear

RESULT:

Thus the project to develop a Credit Card Processing System is done successfully.
 105

Ex.No: 10 E-BOOKS MANAGEMENT SYSTEM

AIM:
The aim of the project is to develop and implement the software for E-Book management
system.

PROBLEM STATEMENT:

E-Book process is well organized on-line buying and selling of books. This process has
various issues in the basis of maintenance of database and updatingin sites.
The process of e-books is fully based on on-line and the process for this mainly interaction
between buyer and seller, buyer who enter the site for purchase of book will use search engine for
book to purchase, the search engine will mainly focused on the database process, it use to search
book for the buyer who mentioned the book name, author name, edition, publication details in the
sites, so that the search engine will show many books.
There will be payment option and user should decide whether he want which one. In case
of normal boo purchase if it is not available it is difficult for the customer and time wastage also,
but e-book avoids wastage of time and maintains the books, if we need any book, we should
register in the site.
E-BOOK ADVANTAGE:
Efficient use
Avoid time wastage
Provide necessary information.

USECASE DIAGRAM

Register
(from Usecase Di agram )

Login
(from Usecase Di agram )

Categories
(from Usecase Di agram )

Visitor
(from Actor) Search Book Admin
(from Usecase Di agram )
(from Actor)

Payment
(from Usecase Di agram )

Download
(from Usecase Di agram )

Email
(from Usecase Di agram )
 106

CLASS DIAGRAM

OVERALL CLASS DIAGRAM

 107

DOWNLOAD

LOGIN

PAYMENT
 108

REGISTRATION

ACTIVITY DIAGRAM

Customer Admin

Register

Issue ID

Login

Categories

Search

Display
Book Details

View Book

Download

Free Payment
Type

Debit Card
Credit Card

Receive
Payment

Payment
Acknowledge

Member Account
Updated

Download
Book
 109

SEQUENCE DIAGRAM
Categories

: Buyer : Admin
: Database

1: specify categories

2: search books for the category

3: Generate book list

4: Return book list

5: Display book list available

Payment

: Buyer
: Admin
: Authentication
system
1: Enter payment details

2: Proceeds authentication

3: Authorise

4: Details verified

5: Payment completed notification

Search

: Buyer : Search page : Database : Admin

1: Enter book details

2: Forward details
3: Search books

4: Find related books

5: return available books

6: Display available books

7: Choose book and select book

8: Make payment

9: Pay

10: Download
 110

COLLABORATION DIAGRAM
Categories

: Buyer

1: specify categories

5: Display book list available

3: Generate book list

2: search books for the category

4: Return book list

: Database
: Admin

Payment
1: Enter payment details

5: Payment completed notification

: Buyer : Admin

4: Details verified

2: Proceeds authentication
3: Authorise

: Authentication
system

Search
7: Choose book and select book
9: Pay
10: Download

6: Display available books

: Buyer 8: Make payment : Database

2: Forward details
5: return available books
1: Enter book details

3: Search books

4: Find related books

: Search page
: Admin
 111

STATECHART DIAGRAM

Select the
type of book

Type the author

name,title,ISBN no

Search

Book Not found Display error

Found message

Yes

Display book
details

PACKAGE DIAGRAM
 112

COMPONENT DIAGRAM

REGISTRATION

SEARCH

EBOOK MANAGEMENT
SYSTEM
PAYMENT

DOWNLOAD

DEPLOYMENT DIAGRAM
<<Client>>
Client.exe

<<Device>>
EBook Server

HTTP EJB Container

Login:ear
<<Server>>
Registration:ear SQL
Database
Search:ear
Payment:ear
HTTP
Download:ear
<<Web Server>>
JSP

RESULT:
Thus the project to develop an E-Book Management System is done successfully.
 113

Ex.No:11 RECRUITMENT SYSTEMS

AIM:

The aim of the project is to develop and implement the software for Recruitment system.

PROBLEM STATEMENT:

The recruitment system allows the job seekers to enroll their names through process of
registration. The employer also can get the list of available candidates and shortlist for their
company requirement.Once the applicant enrolls he receives an id, which helps him in further
corresponding.A fees amount is received from job seekers for enrollment.

This system makes the task of the job seeker easier rather than waiting in queue for
enrollment.This reduces the time consumption for both the job seeker and employer. After the
registration gets over, the applicant profile is verified and he attends aptitude and GD based on the
result the applicant attends a technical interview with HR, and the selected candidate receives the
offer letter.

USECASE DIAGRAM

company details
(from usecase)

applicant register
(from usecase)
(from actors)

company head
(from actors)
verification
(from usecase)

aptitude
(from usecase)

hr
gd (from actors)
(from usecase)

shortlisting
(from usecase)

hr interview
(from usecase)

intimate result
(from usecase)

confirmation
(from usecase)
 114

CLASS DIAGRAM
OVERALL CLASS DIAGRAM

COMPANY DETAILS
 115

REGISTRATION

APTITUDE TEST

HR INTERVIEW
 116

ACTIVITY DIAGRAM

applicant placement head HR

view company
details

register verify

aptitude test group

discussion

shortlist

intimation

HR interview

offer letter confirmation

 117

SEQUENCE DIAGRAM
REGISTRATION

: applicant : application form : admin : database

1: register
2: sends the filled form

3: checks

4: stores details

5: gets the selected candidate list

6: calls for interview

APTITUDE TEST

: applicant : aptitude test : admin : database

1: aptitude test

2: send for evaluation

3: check

4: store eligible list

5: eligible for group discussions

 118

CONFIRMATION

: admin : database
: applicant
1: get selected candidates list

2: search

3: show results

4: intimate confirmed result

COLLABORATION DIAGRAM
APTITUDE TEST

3: check

1: aptitude test 2: send for evaluation

: applicant : aptitude test : admin

5: eligible for group discussions

4: store eligible list

: database
 119

REGISTERATION
3: checks

6: calls for interview

: applicant : admin

2: sends the filled form

4: stores details
1: register 5: gets the selected candidate list

: application form : database

CONFIRMATION
2: search

1: get selected candidates list

3: show results
: admin : database

4: intimate confirmed result

: applicant

STATECHART DIAGRAM
 120

PACKAGE DIAGRAM

user interface

swing web

domain layer
company verification
details register

aptitude short listing

group
discussion

hr interview intimate confirmation

result

technical services

database security error logging

 121

COMPONENT DIAGRAM

COMPANY
DETAILS

REGISTER

RECRUITMENT
SYSTEM

VERIFICATIOn

APTITUDE

GD

SHORT
LISTING

HR
INTERVIEW

INTIMATE
RESULT

CONFIRMATion
 122

DEPLOYMENT DIAGRAM

<<client>>

recruit
http
recruitment system

EJS container
<<server>>

aptitude.ear SQL
gd.ear database server
shortlisting.ear
http hr interview.ear
confirmation.ear

<<web server>>

web

RESULT:
Thus the project to develop a Recruitment System is done successfully.
 123

Ex.No:12 FOREIGN TRADING SYSTEMS

AIM:

The aim of the project is to develop and implement the software forforeign trading system.

PROBLEM STATEMENT:

Foreign trading system involves details about the export and import of materials between
two or many countries. This project provides the complete information about various products
exported and imported across the world from the promoters to the buyers. The main objective of
this project is to ensure globalization and ensuring that the buyer all over the world gets the desired
product that helps in development of their globalization. Currency converter gives you accurate
and instant foreign currency conversions. In currency exchange money value of each country vary
every day. The change will be traced and updated by the system. Transportation of goods should
include quality verification also.

USECASE DIAGRAM

register
(from fts)

admin
(from fts)
log in
(from fts)

display product details

(from fts)

market status & agreement

(from fts)

customer place order dealer

(from fts) (from fts)
(from fts)

payment
(from fts)

money exchange
(from fts)

transportation & delivery

(from fts)

log out
(from fts)
 124

CLASS DIAGRAM

MARKET STATUS

PLACE ORDERS
 125

MONEY EXCHANGE
 126

PAYMENT
 127

ACTIVITY DIAGRAM

cust deal admin

register verify

login

authenticatio
n

view display products

products catalog

place orders

dealer
cust approval approval

agreement

order
approval

payment

net banking credit debit

money
exchange

money
receival

transportatio
n
delivery
 128

SEQUENCE DIAGRAM

DISPLAY ITEM

: customer
: display : data base
: dealer
1: request for product menu

2: send request

3: display product menu

4: enter specification
5: check

6: display product description

PLACE ORDER
 129

TRANSPORTATION AND DELIVERY

: customer : money exchange

: dealer
1: pays amount

2: converts into currency value

3: request for transportation

4: display transportation rate

5: agrees with rate

6: delivers the product

COLLABORATION DIAGRAM

DISPLAY ITEM

1: request for product menu

: customer : dealer

4: enter specification
2: send request
3: display product menu
6: display product description

5: check

: display : data base

 130

PLACE ORDER

3: register
6: view product
8: prepare agreement
10: approve agreement
11: place oredr
13: purchase product
15: payment

4: authorize
: customer 7: product details : admin
14: generate bills
1: register
5: update details
9: sign agreement

12: accept order 2: authorize

16: delivers product

: dealer

TRANSPORTATION AND DELIVERY

3: request for transportation

5: agrees with rate

4: display transportation rate

: customer 6: delivers the product : dealer

1: pays amount 2: converts into currency value

: money exchange
 131

STATE CHART DIAGRAM

 132

PACKAGE DIAGRAM

user interface

web swing

Domain layer

register login display product

details

place order market status & payment

agreement

money transportation logout

exchange & delivery

technical services

database error logging security

 133

COMPONENT DIAGRAM

product
details

place
order

foreign trading payment

system

money
exchange

transportatio
n&delivery

DEPLOYMENT DIAGRAM

<<client machine>>
...>>
foreign trading
system.exe <<application>>
application server

HTTP EJB CONTAINER

<<database>>
registration.ear
fts database
product desc.ear JDBC
agreement.ear

HTTP place order.ear

<<web browser>> payment.ear
web

RESULT:

Thus the project to develop a Foreign Trading System is done successfully.

 134

Ex.No:13 BPO MANAGEMENT SYSTEM

AIM:

The aim of the project is to develop a BPO management system and to implement the
software.

PROBLEM STATEMENT:

BPO focuses on hiring a third party company to do IT related services. A call center is an
office for receiving product queries and providing solutions by telephone.
A BPO is phone operated by a company to administer product support or information
queries from customers. Outgoing calls are made for assistance in resolving the queries in 3 ways
they are voiced, non-voiced communication. Voice based BPOs are those BPOs where you are
required to talk to the customers. Non-voiced based BPOs are BPOs which perform the outsourced
wok for their clients but do not need to interact with client’s customers. If the solutions are not
available directly then some assistance is needed to resolve the queries.

USECASE DIAGRAM

username
(from usecases)
admin
(from actors)
login
(from usecases) password
(from usecases)

query submission
(from usecases)

BPO agent
(from actors)

customer immediate response

(from usecases)
(from actors)

query processing
(from usecases) help associate
(from actors)

solution
(from usecases)

logout
(from usecases)
 135

CLASS DIAGRAM

OVERALL CLASS DIAGRAM:

 136

QUERY SUBMISSION:

IMMEDIATE RESPONSE:

QUERY PROCESSING:

SOLUTION:
 137

SEQUENCE DIAGRAM

QUERY SUBMISSION:

: customer : handler : query form : BPO agent

1: give query
2: fills
3: submited query

4: analyse query

5: gives solution

QUERY PROCESSING:

: handler : BPO agent : Help : customer

1: submit query Associate

2: get query assistance

3: process query

4: gives solution

5: forward solution

6: provide solution

SOLUTION:

: Help : handler : customer

Associate : BPO agent

1: Analyse query

2: give solution

3: forward solution

4: mail solution
 138

COLLABORATION DIAGRAM

QUERY SUBMISSION:

1: give query

: customer : handler

5: gives solution

4: analyse query 2: fills

3: submited query
: BPO agent : query form

QUERY PROCESSING:

: BPO agent : customer

5: forward solution
2: get query assistance 6: provide solution
4: gives solution
1: submit query

3: process query

: Help Associate : handler

 139

SOLUTION:

1: Analyse query

2: give solution

: Help Associate : BPO agent

3: forward solution

4: mail solution
: customer : handler

STATE CHART DIAGRAM

handler
submits query

BPO
agent

Identifies the
problem

find Asks help

solution associate for help

solution given to
customer
 140

PACKAGE DIAGRAM

USER INTERFACE

SWING WEB

DOMAIN
QUERY IMMEDIATE
QUERY
SUBMISSION IMMEDIATE
RESPONSE
SUBMISSION RESPONSE

QUERY
PROCESSING SOLUTION
QUERY SOLUTION
PROCESSING

TECHNICAL SERVICE

DATABASE ERROR LOGIN

SECURITY
 141

COMPONENT DIAGRAM

Query
Submission

Immediate
Response
BPO Management
System

Query
Processing

Solution

DEPLOYMENT DIAGRAM

<<client>>
BPOmanagem
entsys.exe <<server>>
Application Server{OS:Linux}

<<container>>
SOAP/HTTP <<server>>
Database
server{OS:Linux}
Query submission.ear JDBC
Immediate response.ear
Query processing.ear
<<Web browser>> HTTP Solution.ear
Web

RESULT:

Thus the project to develop a BPO Management System is done successfully.

 142

Ex.No:14 LIBRARY MANAGEMENT SYSTEMS

AIM:

To write the problem statement for the Library Management System.

PROBLEM STATEMENT:

Library Management system is to manage the book transaction and user details.At
first,users have to login the system and search for the required book for availability.If the book is
availableusers will take the book and request for book to the admin.Admin collects the details of
user and the book.Then the admin issues the book with the renewal date.Users have to return or
renew the book with in the given date.If the user failed to return the book the fine amount is
collected for the late submission corresponding to the variation in date.

USE CASE DIAGRAM

LIBRARY MANAGENENT SYSTEM

Login

Search/availability

Maintain Book Records

<<include>> ADMIN

<<include>>

<<include>>

Add book Remove book Update book

USER

LIBRARIAN

Borrow

Book Issue

Book Return

<<extend>>

Pay Fine
 143

CLASS DIAGRAM
OVERALL CLASS DIAGRAM:
 144

ACTIVITY DIAGRAM

User LMS Librarian Admin

Enter User name and Password

Login

Authentication

Valid user
Request Book Invalid User

Invalid

Search Book

Searching

By Author By Book
name Name

Book>0 [Book Available]

No books Issue Details
Book=0[No Stock]

Send details
Maintain book

Book Details

Update

Borrow Book Give Return

date of Book
Add Book Edit Book

Return
Update details
Return Book

Update the Book information

Update
 145

SEQUENCE DIAGRAM
OVERALL CLASS DIAGRAM

: LMS
: admin : librarian
: USER

login()

Authentication

Confirm login

Search book

get details

Requestm book

Check Availability

Issue Book

Update()

Add Book

Remove Book

Update Book

Retun Book

Check date

Pay Fine

INDIVIDUAL SEQUENCE DIAGRAM:

Login:

: login
: user

login

authenticate

valid user

authentication

invalid user
 146

Maintain/manage:

: LMS
: admin

Add Book

Added

Remove Book

Removed

Update book

Updated

Transaction:

: LMS
: user : librarian

search

getdata()

request book

check/availability

Check

details

issue book

update

return book

check date

late submission

pay fine
 147

COLLABORATION DIAGRAM
2: Authentication
14: Check date

: LMS

7: Check Availability
9: Update() : librarian

3: Confirm login
5: get details 15: Pay Fine
10: Add Book
11: Remove Book 8: Issue Book
12: Update Book 1: login()
4: Search book
6: Requestm book
13: Retun Book

: admin : USER

STATE CHART DIAGRAM

 148

PACKAGE DIAGRAM

<<Layer>>
User Interface

<<subsystem>> <<subsystem>>
Web Swing
(from User Interface) (from User Interface)

<<Layer>>
Domain Layer

<<subsystem>> <<subsystem>> <<subsystem>>

Login Search Borrow
(from Domain Layer) (from Domain Layer) (from Domain Layer)

<<subsystem>> <<subsystem>> <<subsystem>>

Book issue book Return Fine
(from Domain Layer) (from Domain Layer) (from Domain Layer)

<<layer>>
Techinical Service

<<subsystem>> <<subsystem>> <<subsystem>>

Database Error Login Security
(from Techinical Service) (from Techinical Service) (from Techinical Service)
 149

COMPONENT DIAGRAM

Books

Card Reader

Library Management
System Database

Library
Card

DEPLOYMENT DIAGRAM

Admin/librarian
<<Application Server>>
LMS

<<EJB Containers>>
Login.ear,Bookdetails,Userdetails.ear,
Bookstatus,ear,Update.ear

User

<<Database>>
SQL.exe

executive

RESULT:

Thus the project to develop a Library Management System is done successfully.

 150

Ex.No:15 STUDENT INFORMATION SYSTEM

AIM:
To identify the problem and to identify the project scope, objectives and infrastructure for
student information system

PROBLEM STATEMENT:
The main aim of the system is to improve the efficiency of maintaining student information
and to overcome the discrepancies involved in handling large volume of paper scripts.at the
beginning the details of all the students are collected. Initial stage of the system begins with the
login of the administrator. Administrator is the authorized person who can afford to add, remove
or edit student information. Administrator feeds the details of the student in the system. The
details of the student contain name, roll no, D.O.B., address, department,caste, attendancemark
percentage, extracurricular,other qualification,parent details.After getting necessary information
of the system the administrator can log out. Students can view their mark and attendance, curricular
information by logging into the system with their username password. After viewing their student
details can sign out from the system.
USE CASE DIAGRAM

LOGIN

ADMIN

UPDATE
<extend> <extend>

STUDENT
<extend>

PERSONAL PROFILE ACADEMICS

STAFF
EXTRA CURRICULAR ACTIVITIES

VIEW

<include>

PRINT
 151

CLASS DIAGRAM

OVERALL CLASS DIAGRAM:

INDIVIDUAL CLASS DIAGRAM

 152

View:
 153

ACTIVITY DIAGRAM
 154

INTERACTION DIAGRAM

SEQUENCE DIAGRAM

OVERALL:

LOGIN VIEW UPDATE

: STUDENT : STAFF : ADMIN

1.enter username& password

2.enter username& password

3.verify

4.valid user or invalid user

5.successful login

6.successful login

7.view information

8.search

9.display

10.edit inforamtion

11.save

12.search

13.display

14.edit details

15.save
 155

INDIVIDUAL SEQUENCE DIAGRAM:

LOGIN

LOGIN

: STAFF : ADMIN
: STUDENT

1.enter username& password

2.enter username& password

3.verify()

4.valid or inavalid user

5.successful login

6.successful login

VIEW:

VIEW

: STUDENT : STAFF : ADMIN

1.view details

2.search

3.display

4.search

5.display
 156

UPDATE:

VIEW

: STUDENT : STAFF : ADMIN

1.view details

2.search

3.display

4.search

5.display

COLLABORATION DIAGRAM

7: search
3: verify
4: successful login
view
: staff 8: display

login
2: enter username and password

9: edit details
1: enter username and password
10: save
6: view information
11: search
5: successful login
12: display

update

13: edit details

14: save

: student

: admin
 157

STATE CHART DIAGRAM

PACKAGE DIAGRAM

User interface it focus on UI

work such as
Swing creating
Web windows
(from User interface)
...) (from User interface)
...) capturing mouse
& keyboard
events

Domain layer

Login View
(from Domain layer)
...) (from Domain layer)
...)
focus on
application login
such as
calculating a
sale total or tax.
Print Update
(from Domain layer)
...) (from Domain layer)
...)

Technical service

focus on
Database Security technicalservi
ces such as
(from Technical service)
...) (from Technical...)
service)
interfacing
with database
or error login
 158

COMPONENT DIAGRAM

System

Database

Student
information system
Printer

Modem

DEPLOYMENT DIAGRAM

<<CLIENT>>
Student
<<server>>
Staff Application Service

<<container>>
<<SERVER>>
EJB container JDBC Database server

HTML login
v iew
print
update
<<W EB>>
brow se web

RESULT:

Thus the project to develop a Student Information System is done successfully.

 159

Ex.No:16 ATM SYSTEMS

AIM:
To develop automated teller Machine (ATM) which is used to provide money everywhere
by adding addition feature to it.
PROBLEM STATEMENT:
The main objective of our project is to implement voice feature in all ATM machines, which will
reduce the user’s time to withdraw money.
 Design and develop the ATM system to monitor the system usage so that, we add additional
features to ATM called Voice recognition.
 It allows user to operate ATM by speaking to it.
 Speech is also a very natural way to interact and it is not necessary to select all option by
hands.
 This voice recognition allows user to withdraw money in short span of time.
 In older days, we used to go to banks to withdraw money, but using ATM we can get
money from anywhere and anytime.
The main scope of our project is to include Additional feature in ATM machine, which is voice
recognition, which is used to select the options through voice of user. Thus, through Voice
Recognition, it reduces customer’s effective time and blind people can also easily handle and even
physically disabled persons can also use ATM machine through Voice Recognition.

USE CASE DIAGRAM

 160

CLASS DIAGRAM

ACTIVITY DIAGRAM

Customer ATM Ba nk

Insert ATM Validate

card ATM card

Valid Invalid

Take card Eject card

Enter pin Authorization

Pin

Valid Pin Invalid Pin

Enter amount Check balance

Transaction Balance =amt

Take money Debit

from slot money

Show balance

Take the Terminate process eject card

card
 161

SEQUENCE DIAGRAM

c us tomer atm databas e

1: ins ert c ard

2: validat e c ard

3: valid c ard

4: enter pin

5: pin ent ered

6: verify pin

7: c orrec t pin

8: s elec t ac c ount ty pe

9: ac c ount t y pe s elec t ed

10: verify ac c ount ty pe

11: ac c ount t y pe verified

12: s elec t option

13: wit hdraw

14: enter amount

15: c heck balanc e

16: balanc e c hec k ed

17: reduc e amount

18: c hanged amonut

19: ret urn amount

20: depos it

21: enter amount

22: amount entered

23: verify amount

24: inc reas e amount

25: c hanc e balanc e

26: ret urn det ails

27: balanc e enquiry

28: ret rive balanc e

29: balanc e c hec k ed

30: ret urn balanc e details

31: c hange pin

32: verify old pin

33: old pin verified

34: enter new pin

35: new pin entered

36: updat e det ails

37: details updated

38: pin changed

39: ejec t c ard

40: rec eive the c ard

 162

STATECHART DIAGRAM

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

RESULT:

Thus the project to develop an ATM using Rational Rose is done successfully.
 163

ADDITIONAL VIVA – VOCE QUESTIONS

1. The method of design encompassing the process of object oriented decomposition and a notation for
depicting both logical and physical and as well as static and dynamic models of the system under design
is knownas:
A. Object- OrientedProgramming
B. Object- OrientedDesign
C. Object- OrientedAnalysis
D. None of thementioned

2. The Object Oriented Modeling for building systems takes the ———– as the basis.
A. Class
B. Object
C. Model
D. Modules

3. What is the programming style of the object oriented conceptualmodel?

A. Invariant relationships
B. Algorithms
C. Classes andobjects
D. Goals, often expressed in a predicatecalculus.

4. Abstraction isclassifiedinto types

A. 4
B. 3
C. 2
D. 1

5. Which of the following views represents the interaction of the user with the software but tells nothing
about the internal working of the software?
A. Use case diagram
B. Activity diagram
C. Class diagram
D. All of the above

6. What are the notations for the Use case Diagrams?

A. Use case
B. Actor
C. Prototype
D. Use case and Actor

7. Which among the following can be heuristic for Use case diagram?
A. The product can be made actor
B. Never name actors with noun phrases
C. Name Use cases with verb phrases
D. All of the mentioned
 164

8. Which of the following are the valid relationships in Use Case Diagrams
A. Generalization
B. Include
C. Extend
D. All of the mentioned

9. Which of the following UML diagrams has a static view?

A. Collaboration
B. Use case
C. State chart
D. Activity

10. The essential characteristics of an object that distinguish it from all other kinds of objects and thus
provide crisply defined conceptual boundaries, relative to the perspective of the viewer is called
A. Encapsulation
B. Modularity
C. Hierarchy
D. Abstraction

11. Which is a model static data structure?

A. Object diagrams
B. Class diagrams
C. Activity diagrams
D. Interaction diagrams

12. Where the class diagrams are not convenient?

A. simple interactions model
B. the vocabulary of a system model
C. simple collaborations model
D. logical database schema model

13. An association may be

A. unary
B. binary
C. ternary or n-ary
D. All of the above

14. Which of the following specifies how many instances of one class may relate to a single instance of an
associated class?
A. Multiplicity
B. Association
C. Degree
D. None of the above

15. The attribute(s) is/are associated with the association is called

A. Link attribute
 165

B. Derived attribute
C. Multi-valued attribute
D. None

16. Which of the following is a name that uniquely identifies one end of an association?
A. Label name of the link
B. Role name
C. Link attribute name
D. None

17. The role name is a

A. Derived attribute
B. Link attribute
C. Attribute
D. All of the above

18. Which of the following is the “part-whole” or “a-part-of” relationship in which objects representing the
component of something are associated with an object representing the entire assembly?
A. Generalization
B. Specialization
C. Aggregation
D. None

19. Aggregations are drawn like associations, using a small hollow ———— indicating the assembly end
of the relationship.
A. Diamond
B. Box
C. Circle
D. Triangle

20. Inheritance is a ———- relationship between two classes.

A. “is-a”
B. Part of
C. Both a and b
D. None

21. Which things are dynamic parts of UML models?

A. Structural things
B. Behavioral things
C. Grouping things
D. Annotational things

22. Interaction Diagram is a combined term for

A. Sequence Diagram + Collaboration Diagram
B. Activity Diagram + State Chart Diagram
C. Deployment Diagram + Collaboration Diagram
 166

D. None of the mentioned

23. If you are working on real-time process control applications or systems that involve concurrent
processing, you would use a
A. Activity diagram
B. Sequence diagram
C. State chart diagram
D. Object diagram

24. Forward Engineering is possible for an Activity Diagram especially if the context of the diagram is
________
A. an operation
B. a workflow
C. a class
D. a use case

25. Realization of a use case is specified by ________

A. a collaboration
B. a component
C. a node
D. an activity

26. Which of these is correct?

A. Artifacts instances and types have same names
B. Artifact names and instances are underlines
C. All of the mentioned
D. None of the mentioned

27. What refers to the value associated with a specific attribute of an object and to any actions or side?
A.Object
B. State
C.Interface
D. None of the mentioned

28. How many diagrams are here in Unified Modelling Language?

A.six
B. seven
C.eight
D. nine

29. Which of the following determines the state diagram?

A.The UML notation for specifying finite automata is the state diagram
B. In state diagrams, states are represented by rounded rectangles
C.Both A and B
D. None of the mentioned
 167

30. Which of the statements state the name compartment?

A.The first compartment is the name compartment
B. It contains the state name; State names are optional and may be path names
C.The name compartment can never be omitted
D. The first compartment is the name compartment, It contains the state name; State names are
optional and may be path names

31. _____ provides guidance for assigning responsibilities to classes and to a limited extent, determining
the classes that will be in a design in an object oriented system.

A. GRASP
B. IPR
C. DBMS
D. SOA

32. GRASP defines ______ basic object oriented design principles or basic building blocks in design

A. 3
B. 5
C. 8
D. 9

33. The basic object oriented design principles of GRASP include

A. Information expert
B. Controller
C. Indirection
D. All of the above

34. In object oriented design, a ________ is a named description of a problem and solutions that can be
applied to new contexts. It has given a category of problem, guide the assignment of responsibilities to
objects.

A. Design pattern
B. Pattern
C. Both (a) and (b)
D. None of the above

35. In software engineering, _______ is a general repeatable solution to a commonly occurring problem in
software design. It is not a finished that can be transformed directly into code.

A. Design pattern
B. Pattern
C. Both (a) and (b)
D. Either (a) or (b)
 168

36. The UML defines a __________ as “a contract or obligation of a classifier”. They are related to the
obligations of an object in terms of its behavior.

A. Responsibility
B. Pattern
C. Object
D. Interconnection

37. Doing responsibilities of ab object include:

A. Doing something itself

B. Initiating action in other objects
C. Controlling and coordinating activities in other objects
D. All of the above

38. Knowing responsibilities of an object include

A. Private encapsulated data

B. Related data
C. Things it can derive or calculate
D. All of the above

39. Why are patterns important?

A. Capture expert design knowledge

B. Capture design accessible to both novices and other experts
C. Both (a) and (b)
D. None of the above

40. What benefits does pattern provide?

A. Novice designers can benefit from learning solution patterns that experts use, without needing
design experience
B. Expert designers can benefit from studying patterns too: they can broaden their repertoire of
patterns and deepen their understanding of the patterns they already know
C. Both (a) and (b)
D. None of the above

41. ___________ is the process of finding out where something went wrong and correcting the code to
eliminate the errors or bugs that cause unexpected results.

A. Debugging
B. Coding
C. Documentation
D. Review
 169

42. ________ result from incorrectly constructed code, such as an incorrectly typed keyword or some
necessary punctuation omitted.

A. Logical error
B. Language/Syntax error
C. Runtime error
D. None of the above

43. _________ occur and are detected as the program is running, when a statement attempts an operation
that is impossible to carry out.

A. Syntax error
B. Logical error
C. Runtime error
D. All of the above

44. __________ occur when code doesn’t perform the way you intended. The code might be syntactically
valid and run without performing any invalid operations and yet produce incorrect results.

A. Logic errors
B. Syntax errors
C. Both (a) and (b)
D. None of the above

45. Quality assurance testing consists of

A. Error based testing

B. Scenario based testing
C. Both (a) and (b)
D. Either (a) or (b)

46. __________ technique search a given class’s method for particular clues of interests, then describe how
these clues should be tested.

A. Error based testing

B. Scenario based testing
C. Unit testing
D. Sanity testing

47. __________ concentrates on what the user does, not what the product does.

A. Scenario-based testing
B. Usage based testing
C. Error based testing
D. Either (a) or (b)
 170

48. The extent of testing a system is controlled by

A. Risks involved
B. Limitations on resources
C. Deadlines
D. All of the above

49. The concept of the _________ is used to represent a system whose inside workings are not available
for inspection.

A. White box testing

B. Black box testing
C. Grey box testing
D. Beta testing

50. ________ assumes that the specific logic is important and must be tested to guarantee the system’s
proper functioning.

A. Black box testing

B. White box testing
C. Sanity testing
D. Integration testing