RAGHU INSTITUTE OF TECHNOLOGY

Dakamarri (v), Bheemunipatnam (M)

Visakhapatnam Dist., Andhra Pradesh, PIN-531162
(Approved by AICTE, New Delhi, and Affiliated to Andhra University: Visakhapatnam (AP)

IV B. Tech., CSE I - Semester

FACULTY LABORATORY MANUAL

For

OBJECT ORIENTED SOFTWARE

ENGINEERING

Prepared by

M Purna Chandra Rao, Associate Professor

DEPARTMENT OF

COMPUTER SCIENCE AND ENGINEERING

RAGHU INSTITUTE OF TECHNOLOGY
(Affiliated to Andhra University: Visakhapatnam (AP))
Visakhapatnam-531162

CERTIFICATE

Name of the Laboratory : OBJECT ORIENTED SOFTWARE ENGINEERING

Name of the Faculty : M PURNA CHANDRA RAO

Department : CSE

Program : B.TECH

Year : IV

Semester :I

IQAC Members:

Name(s):

Signature(s):

HOD
INDEX

PROGRAM
SNO DESCRIPTION
NO.
1 1 LAB OBJECTIVE
2 2 UNIVERSITY / AU Syllabus
3 3 List of Programs
4 4 SCHEDULE/CYCLE CHART
5 5 Introduction to UML
Automated teller machine
6 6
E- seva
7 7
E-voting
8 8
Library management system
9 9
Online book shop
10 10
Railway reservation
11 11
LAB OBJECTIVE

1. Capture structure and behavior of architecture and behavior

2. Show how the elements of the system fit together.
3. Maintain consistency between design and implementation.
4. Promote unambiguous communication

COURSE OUTCOMES:

1. Identify and build an appropriate process model for a given project.

2. Analyze the principles at various phases of software development.
3. Translate a specification into a design, and identify the components to build The
architecture for a given problem, all using an appropriate software engineering
Methodology.
4. Define a project management plan and tabulate appropriate testing plans at different
levels during the development of the software.

CO TO PO MAPPING:

A C BD E F G H I J K L
Object Identify and build an appropriate process ✓ ✓
Oriented model for a given project.
Software Analyze the principles at various phases ✓ ✓
Engg. of software development.
Translate a specification into a design, ✓
and identify the components to build
The architecture for a given problem, all
using an appropriate software
engineering Methodology.
Define a project management plan and ✓
tabulate appropriate testing plans at
different levels during the development
of the software.
INTRODUCTION TO VISIO
The enterprise architect of version of Microsoft visual studio .net includes a copy of
Microsoft Visio for enterprise architects, for those who new to the product, Microsoft Visio is
a drawing package that allows selecting shapes from stents to draw and design different kinds
of diagrams such as flow charts, network diagrams and software diagrams.

Software applications developers can model the design and functionality with Visio
and unified modeling language (UML). Through Visio‟s model diagram template, Visio also
can perform reverse engineering on an implemented system.

The two-part article series explain how to model different UML diagrams with Visio
and how to transform these diagrams into code in a .net programming language.

The overview of several UML diagrams and examines their place in the development
cycle. I analyze a university system through UML diagrams. The system will allow user to
enroll in seminars and take courses. Courses are taught by professors. The system will also
store both students and professors information.
UML (UNIFIED MODELLING LANGUAGE)
UML stands for unified modeling language. UML is a language for specifying,
visualizing and documenting. This is the step while developing any product after analysis.
The goal is to produce a model of the entities involved in this project which later need to
built.
The purpose of the design phase is to plan a solution of the problem specified by the
requirement document. This phase is the first step of moving from the problem domain to the
system domain, i.e., starting with what is needed. The design of the system is perhaps the
most critical factor affects the quality of the software.

System design also called top-level design aims to identity models that should be in
the system, the specification of these modules and how they interact with each other.

Design Methodology:
Two basic modern strategies employed in software design are:
1. Top-down design
2. Bottom-up design
The top-down design is basically a decomposition process which focuses on the flow
of control. At later stages it concern itself with the code production. The first step is to study
the overall aspects of the tasks and to break into number modules, which are small enough
group to code in forward manner.
In a bottom-up designing one first identifies and investigates part of design that most
difficult and necessary designed decision are made the remainder of design is tailored to fit
around the design.
An UML system is represented using fire different views
Use-case view
Logical view
Implementation view
Process view
Deployment view

UMLDIAGRAMS:
The diagram contains the graphical elements arranged to illustrate a particular part or
aspect of the system. A system model having several diagrams of varying types of depending
for the model.
There are various kinds of diagrams used in software design:
 Use case diagram
 Class diagram
 Object diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
 Component diagram
 Deployment diagram
USE CASE DIAGRAM:
Usecase diagram identifies the functionality provided by the system, the users interact
with the system, the association between the users and their functionality. Usecases are used
in the analysis phase of software development.
Primarily goals of use case diagram include;
Providing a high-level view of what the system does
Identify users of the system
GraphicalNotation:
The basic components of usecase diagrams are the actors, the usecase and the
association.
Actor:
An actor is a user of the system. The role of the user is written beneath the icon.
Actors are not limited to humans.

Usecase:
A usecase is a functionality providing by the system, typically describes as verb
object. Usecases are depicted with an ellipse. The name of the usecase is written in within it.

Association:
Association is used to link actors with usecases and indicate that an actor participates
in usecase in some form. Association is depicted by a line connecting actor and usecase.

CLASS DIAGRAM:

Class diagrams identify the class structure of a system, including the properties and
methods of each class. If also depicted the various relationships that can exist between classes
such as inheritance relationship. The class diagram is one of the most widely used diagrams
for the UML specification.
Notation:
The elements on a class diagram are classes and the relationships between them.
Class:
A class is the basic building block in object-oriented programming. A class is
depicted using a rectangle divided into 3 sides.
Association:
An association is a generic relationship between two classes and is modeled by a line
collecting the two classes. This line can be qualified with the type of relationship.
Composition:
If a class cannot exist by itself, instead must be a member of another class, then that
class has a composition relationship with the containing class. A composition relationship is
indicated by a line filled with a diamond.

Dependency:
When a class uses another class, perhaps has variable or a parameter and so depends
on the class, a dependency relationship is formed.

Aggregation:
Aggregation indicates whole part relationship, and are known as “ has a”relationship.
An aggregation relationship is indicated by a line with a hallowen diamond.

Generalization:
A generalization relationship is the equivalentof an inheritance relationships in object-
oriented terms. It is indicated by an arrow head pointing to the base or parent class.

OBJECT DIAGRAM:

An object diagram is a variant of a class diagram and uses almost identical

identification. The difference between the two is that an object diagram shows a number of
object instances of classes, instead of actual class.
Object diagrams are not as important as class diagram but they can be used to
exemplify a complex class diagram by showing what the actual instances and the
relationships looks like.

SEQUENCE DIAGRAM:
It documents the interactions between classes to achieve a result, such as a use case.
The sequence diagram lists objects horizontally, time vertically, model these messages over
time.
Notation:
In a sequence diagram classes and actors are listed as columns. With vertical lifelines
indicating the life time of the object over time.
Object:
Objects are instance of classes that pictorial representation of an object is shown
below.

Life line:
The life line identifies the existence of the object overtime. The notation of a life line
is a vertical dotted line extends from an object.

Activation:
Activation are modeled as rectangular boxes on the life line, indicates when the object
is performing the action.

Message:
Messages modeled as horizontal arrows between activations, indicate communication
between the objects.

COLLABORATION DIAGRAM:
Collaboration diagram models the interaction between objects. This type of diagram is
a cross between an object diagram and a sequence diagram. The collaboration diagram uses
the free-form arrangement of objects as found in an object diagram.
Object:
Objects are instances of classes and are one of the entity types that can be involved in
communications. An object is shown as rectangular box, with the class name inside prefixed
with the object name.

Actor:
Actors can also communicate with objects, so they too can be listening on
collaboration diagrams.
Message:
Messages, modeled as arrows between objects, and labeled with a ordering number,
indicates communication between objects.

STATE CHART DIAGRAM:

State chart or state diagram is used to document the various models that a class can go
through, and events that cause a state transition. State diagram typically transitions with in a
single class.
State:
The state notation marks a node of the entity and is indicate using a rectangle with
rounded corners

Transition:
A transition marks the changing of the objects state, caused by an event.

Initial state:
The initial state is the state of an object before any transition.

Final state:
End state marks the destruction of the object where state we are modeling.

ACTIVITY DIAGRAM:
These are used to document works flows in a system from the business level down to
operational level. The general purpose of an activity diagram is to focus on the flows driven
by internal processing vs. external events.
Activity state:
Activity state marks on action by an object
Transition:
Where an activity state is completed, processing is moved to other activity state.
Transition are used to marks this movement.

Swim lane:
Swim lane divides activities according to objects by arranging objects in one column
format and placing activities by that object within that column.

Guard(label):
The guard is a conditional expression that when true indicates, the transition is taken.

To shows parallel behavior, use fork and join. The fork has one transition if and any
number of transitions exist. The join represents the end of the parallel behavior and has any
number of transitions entering, and only ne leaving.

COMPONENT DIAGRAM:
Component diagram are physical analysis of static structure diagram. They are used to
describe dependencies between software components. They often-represents architecture
level information.

Nodes:
These represent physical hardware.
Components:
These are physical building blocks of the system represents as a rectangle with tabs.
Interfaces:
These describe a group of operations used for created by components.
DEPLOYMENT DIAGRAM:
Deployment diagram are a different types of implementation diagram. They show the
physical configuration of hardware and software. They represent a static view of the systems
hardware. The software that is installed on that hardware and the middleware used to connect
the machines.
AUTOMATED TELLER MACHINE

ABSTRACT
Automated Teller Machines (ATMs) have gained prominence as a delivery channel
for banking transactions in India. Banks have been deploying ATMs to increase their reach.
The Primary Goal of this project is that we can withdrawl the money irrespective of the
timings of any bank. This system is mainly needed because the customer can visit ATM at
any time, to withdrawl, transfer and to know the balance of the account. To reduce the
complexity between customer and banker we have introduced ATM to do transactions.
This system contains information about various transactions of our bank account.
Customers can visit if interested to perform any of their transactions. We can do all
transactions from any type of account, savings and current using this system.
It provides flexible services to the customers so that there is no need to go to bank and
queing for hours to withdrawl even for small amount of money. Customers can take the mini
statement from the ATM rather go to bank and take it. Customers use ATMs to recharge their
mobile phone pre-paid connections, pay their utility bills, even mutual fund transactions.
PROBLEM STATEMENT
Design the software to support a computerized banking network including both
human cashiers and automated teller machine (ATM) to be shared by a consortium of banks.
Each bank provides its own computer to maintain its own accounts and process transactions
against them.
Cashier stations are owned by individual banks and communicate directly with their
own bank‟s computers. Human cashiers enter account and transaction data. Automatic teller
machines communicate with a central computer that clears transactions with the appropriate
banks. An automated teller machine accepts a cash card, interacts with the user,
communicates with the central system to carry out the transaction, and dispenses cash and
prints receipts.
The system requires appropriate record keeping and security provisions. The system
must handle concurrent accesses to the same account correctly. The banks will provide their
own software for their own computers.

Existing System:
The traditional system present is to withdrawl the money through bank. We have to
stand in the queue for hours even when we want to with drawl a small amount of money.
When we want cash suddenly and the bank is closed at that time, we can withdrawl the
money from ATM.

Disadvantages:
1. Time consuming process.
2. Not available 24 hours to do the transactions.

Proposed System:
1. The proposed system is ATM.
2. The system solves the problem of the existing system.
3. It provides the customer with the following benefits.

Features:
1. We can withdrawl the money at any time.
2. Time saving process.
3. Easier and flexible process.
4. Check the balance of the account at any time.
5. We can get the transactions details such as date and time.
6. We will get the status of the transactions immediately to your mobiles through messages.
7. Receipt will be provided to you with the details of the transactions you have done at that
moment.
USE CASE DIAGRAM:
A use case diagram is a set of scenarios that describes the interaction between user
and system. The use case is an external view of a system that represents some action the user
might perform in order to complete a task.

Cash installation

System shut down

System startup

Operator/Teller System status

Login
Change pin
Bank computer

Validation
Transaction

Customer

Withdrawl Deposit Transfer Check balance Mini statement

Account type

Savings Current

Fig: Use Case for ATM

SEQUENCE DIAGRAM:
The sequence diagram is very simple and has immediate visual appeal---this is it‟s
great strength. A sequence diagram is an alternative way to understand the overall flow of
control of a program. Instead of looking at the code and trying to find out the overall
sequence of behavior.

Operator ATM System Bank Computer

Switch on

Performs start up
Install cash
Get cash installation

Set cash installation

Cash installed

Fig: Sequence diagram for System start up

Operator ATM ATM Computer Bank Computer

system

save all settings

Saving performed
change done

shut down system

system is going to shut down
save all transactions
turn off the syystem
system shut down

Fig: Sequence diagram for System shut down

Customer Bank System
ATM

Insert card
Validate card
validate()

Card valid
Enter pin

Enter pin()
Validate pin
validate()
service()

Request deposit()
Insert cheque
Validate cheque()

Validation success
Enter account type

Enter savings or current account

Forward details
update()

notify()

Deposit succcessful()
Dispense card

Dispense receipt

Fig: Sequence diagram for Cash deposit

User ATM Bank Database
Insert card
Validate card

validate()
Card valid
Enter pin

Pin entered
Validate pin

validate()
Pin valid
Enter transaction

Transfer fund

Enter source aqccount no

Account no
Validate no

validate()
Account valid
Enter type of acc

Account type entered

Enter amount to transfer

Amount entered
Check amount
Amount checked
Amount sufficient
Enter destination acc no

Account no entered
Validate no
Validate
Account valid
Enter type of account

Type of account entered

Transfer

processing()
Transaction complete
Transaction successful

Fig: Sequence diagram for Transfer fund

User ATM Bank System

Start up()

Initiate start up

System ack()
Notify

Enter pin

Validate pin()
Validate
Notify

Valid pin

Install cash

Update()

Install cash

Cash update()

Updation

Display success()

Fig: Sequence diagram for Cash installation

User ATM Bank System Account

Insert card
valid()

valid()

Card is valid
Enter pin()
pin()
Verify pin() Check account
Account valid
Account is valid

service
Request withdrawl
amount()

Withwrawl amount

Withdrawl success

Display success

Take card

Card
Dispense cash()

Take cash

Fig: Sequence diagram for Withdrawl

COLLABORATION DIAGRAM:
It represents collaboration between the objects. It is nothing but a set of objects
related in a particular content and interaction.

2: Performs start up

1: Switch on
3: Install cash
Operator ATM
System
6: Cash installed

5: Set cash installation 4: Get cash installation

Bank
Computer

Fig: Collaboration diagram for System start up

2: Saving performed

1: save all settings

4: shut down system
Operator ATM ATM
system Computer
3: change done
8: system shut down

7: turn off the syystem 5: system is going to shut down

6: save all transactions

Bank
Computer

Fig: Collaboration diagram for System shut down

1: insert card
6: enter pin()
10: request deposit()
customer atm

5: enter pin
9: service()
14: enter amount type
15: enter savings or current account 4: card valid
19: deposit succcessful() 13: validation success
20: dispence card 18: notify()
21: dispence receipt

3: validate()
8: validate()
12: validate cheque() 2: validate card
17: update 7: validate pin
11: insert cheque
16: forward details

bank
system

Fig: Collaboration diagram for Deposit

1: Insert card
6: Pin entered
11: Transfer fund
User 13: Account no
18: Account type entered
20: Amount entered
25: Account no entered
30: Type of account entered
5: Enter pin
10: Enter transaction
12: Enter source aqccount no
17: Enter type of acc 4: Card valid
19: Enter amount to transfer 9: Pin valid
24: Enter destination acc no ATM
16: Account valid
29: Enter type of account 23: Amount sufficient
34: Transaction successful 28: Account valid
3: validate() 33: Transaction complete
8: validate()
15: validate()
22: Amount checked
27: Validate
32: processing()
2: Validate card
7: Validate pin
14: Validate no
21: Check amount
Bank 26: Validate no
Database 31: Transfer

Fig: Collaboration diagram for Transfer fund

11: Update()

1: Start up()
5: Enter pin
10: Install cash
User ATM

4: Notify
9: Valid pin
15: Display success()

3: System ack()
8: Notify
14: Updation

7: Validate
13: Cash update() 2: Initiate start up
6: Validate pin()
12: Install cash

Bank
System

Fig: Collaboration diagram for Cash installation

User Bank
System

1: Insert card
6: pin()
12: Request withdrawl
17: Take card
5: Enter pin()
11: service 2: valid() 4: Card is valid
16: Display success
18: Card 3: valid()
9: Account valid 20: Take cash 7: Verify pin()
8: Check account 13: amount()
14: Withwrawl amount

Account ATM
10: Account is valid
15: Withdrawl success
19: Dispense cash()

Fig: Collaboration diagram for Withdrawl

ACTIVITY DIAGRAM:
It is used to model an entire business process. It provides a flow of programs. It is
used to show internal state of an object but events may appear in them.

user

Insert Card

Enter Pin

Validate Pin

valid

Enter Type of
Account

invalid pin

Withdrawl Deposit Transfer Check Balance Mini Statement

Enter Amount Place cash Check bal

Enter Amount valid

to withdrawl
invalid amount

Amount
Dispense Cash

Take Reciept

Fig: Activity diagram for ATM

CLASSDIAGRAM:
Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model class structure and contents using design elements such
as classes, packages and objects.

Fig: Class diagram for ATM

COMPONENT DIAGRAM:
The component diagram contains components and dependencies. Components represent the
physical packaging of a module of code. The dependencies between the components show
how changes made to one component may affect the other components in the system.
Dependencies in a component diagram are represented by a dashed line between two or more
components. Component diagrams can also show the interfaces used by the components to
communicate to each other.

Bank
Computer

Client ATM
System

Account Transacti
ons

Current Savings
Account Account

Fig: Component diagram for ATM

DEPLOYMENT DIAGRAM:
A deployment diagram shows processors, devices and connections. Each model
contains a single deployment diagram which shows the connection between its processors
and devices and its allocation from processor to processor. Processor specifications, device
specifications and connection specifications enable you to display and modify the respective
properties

Bank Customer

Bank Computer Transaction

ATM System Accounts

Fig: Deployment diagram for ATM

Viva voice questions

1. What is UML?
Ans: UML stands for the Unified Modeling Language.
It is a graphical language for 1) visualizing, 2) constructing, and 3) documenting the
artifacts of a system.
It allows you to create a blue print of all the aspects of the system, before actually
physically implementing the system.

2. What are the different views that are considered when building an object oriented
software system?
Ans: Normally there are 5 views.
Use Case view – This view exposes the requirements of a system.
Design View – Capturing the vocabulary.
Process View – modeling the distribution of the systems processes and threads.
Implementation view – addressing the physical implementation of the system.
Deployment view – focus on the modeling the components required for deploying the
system.
3. What are the major three types of modeling used?
Ans: The 3 Major types of modeling are
Architectural,
Behavioral and
Structural.

4. Name 9 modeling diagrams that are frequently used?

Ans: 9 Modeling diagrams that are commonly used are
Use case diagram
Class Diagram
Object Diagram
Sequence Diagram
State chart Diagram
Collaboration Diagram
Activity Diagram
Component diagram
Deployment Diagram.

5. What is SDLC (Software Development Life Cycle)?

Ans: SDLC is a system including processes that are
Use case driven,
Architecture centric,
Iterative and
Incremental.
E- SEVA
Abstract

The case discusses E-Seva (Electronic Service), an e-government project

initiated by the state government of Andhra Pradesh (GoAP) in India. The E-
Seva project aimed at integrating and offering a wide range of government to
citizen (G2C) services at a single location. The case highlights the objectives of
the E-Seva project. It provides detailed information on the implementation of
the project, its IT architecture, and the hardware and software used. The case
describes the G2C services offered by the GoAP and the benefits reaped by the
citizens and the GoAP after the implementation of the project.

In the E-seva there are many types of online bill payments (electric bill,
phone bill etc).and there is an online ticket reservation system. The electronic
bill presentment & payment application (EBPP) is a web based application
which helps billers and their customers settle their transitions online.
Problem Statement
E-seva is the online payments. In the e-seva there are many types of
online bill payments (electric bill, phone bill etc).and there is an online ticket
reservation system. The electronic bill presentment & payment application
(EBPP) is a web based application which helps billers and their customers settle
their transitions online.
Briefly speaking billers and issue bills (e-bill) Online and send them to
their customers electronically. The users can select to view and pay their e-bills
in multiple languages. The system will also keep tractions history between
billers and customers. EBPP system should be reasonably accessible to potential
user. And online ticket reservation system. Railways wishes to develop a
ticketing and reservation system .this must support advance booking of the
tickets, cancellation of tickets and change of class of a ticket. The system will
also have a web interface where their user can register themselves and purchase
ticket online... The system will also have a querying facility that allows user to
check train time –tables, Fares and availability of tickets.

Existing System:
As per previous contract, all the assets created by existing Service
Provider stands transferred to ESD at the end of the contract. These assets on
„as is where is‟ condition will be available for use free of charge to new service
provider during the entire contract period

Disadvantages:
1. Spoofing: In this practice, the attacker attempts to gain the access of the E-
Governance system by using fallacious identity either by stealth or by using
false IP address. Once the access is gained, the assailant abuses the E-
Governance system by elevation of the privileges.
2. Tampering of E-Governance system: As soon as the system is compromised
and privileges are raised, the classified information of the E-Governance
mechanism becomes very much susceptible to illegal adjustments.
3. Repudiation: Even the attacker can mount refutation attack during the E-
Governance transaction, which is the ability of the user to reject its
performed transaction.

Proposed System:
E-seva is probably one of the best e-governance in India. It is a one –shop-stop
for a range of citizen‟s friendly system.
USE CASE DIAGRAM:
A use case diagram is a set of scenarios that describes the interaction between user
and system. The use case is an external view of a system that represents some action the user
might perform in order to complete a task.

telephone bill
house tax

water tax
electricity bill
login maintaining
pay bills
(from use ca...
database
(from use ca... (from use ca...

movie tickets
(from use ca...

consume
operator
r dba
(from actors)
...) (from actors)
...)
bus reservations (from actors)
...)
birth
death (from use ca...

certificates
competetive
passport
(from use ca...
exams

applications
(from use ca...

trade license vehicle license

licences
(from use ca...

Fig: Use case diagram for E-seva

Regester Biller <<include>>

UnRegester user Verify Information

<<include>>

Regester Customer

Biller Payment Engine

Customer MySql

Fig: Use case diagram for register

<<include>>
Issue Bill Enter e-bill
information

Biller

<<include>>
Update Trancation

MySql

<<include>>
Verify Customer
information

cancel Issue
e-bill screen

Fig: Use case diagram for issue bills

Cancel Pay bill
Action

Customer Payment Information

Valdiation

Payment engine
<<include>>

Enter Payment
Information
UpDate Trancation
Information

Fig: Use case diagram for pay bills

SEQUENCE DIAGRAM:
The sequence diagram is very simple and has immediate visual appeal---this is it‟s
great strength. A sequence diagram is an alternative way to understand the over all flow of
control of a program. Instead of looking at the code and trying to find out the over all
sequence of behavior.

Fig: Sequence diagram for register

Fig: Sequence diagram for issue bills

Fig: Sequence diagram for pay bills

Fig: Sequence diagram for view account information
Fig: Sequence diagram for update user information
system
: consumer : operator
1: requests for a ticket

2: specifies the details

3: enters the bus no.,date ,time

4: not available

5: the ticket is not available

6: valid

7: requests the amount

8: takes the amount

9: enquires the name

10: enters the name

11: issues the ticket

12: receivces the ticket

Fig: Sequence diagram for ticketing

COLLABORATION DIAGRAM:
It represents collaboration between the objects. It is nothing but a set of objects
related in a particular content and interaction.

: consumer

1: requests for a ticket

2: specifies the details
8: takes the amount

5: the ticket is not available

7: requests the amount
9: enquires the name
12: receivces the ticket

4: not available
6: valid
11: issues the ticket : operator

3: enters the bus no.,date ,time

10: enters the name
system

Fig: Collaboration diagram for E-seva

ACTIVITY DIAGRAM:
It is used to model an entire business process. It provides a flow of programs. It is
used to show internal state of an object but events may appear in them.

login

password not accepted

password accepted
select type of service
from menu

service selected

service not selected

more services

perform the
service

no more services
exit from the
service menu

Fig: Activity diagram for E-seva

CLASS DIAGRAM:
Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model class structure and contents using design elements such
as classes, packages and objects.
customer
(from Use Case View)
cname
servicetype

provide data()
receive receipt()

certificate 1,n licence

(from Use Case View) (from Use Case View)
name vehicleno
fname sercharge
mname cname
place interacts
date get details()
provide licenses()
get details() 1,n
receipt() 1,n

1,n OPERATOR
(from Use Case View)
issues id issues
password
1 1
+login()
+update()
reservation
bill 1 (from Use Case View)
(from Use Case View)
busno
billno seatno
amount give out reserve source
fine destination
date 1,n 1,n
get data()
pay bill() resticket()
reciept() get ticket()

movie ticket
(from Use Case View) application
seatno (from Use Case View)
sercharge 1,n 1,n
type
show
provide sercharge
tname reserve
provide app()
get details()
bookmovietickets()

Fig: Class diagram for E-seva

STATE TRANSITION DIAGRAM:
State chart diagrams are used to describe the behavior of the system. These statements
describes all possible states of an object as an event occurs.

idle state

login

per form
transaction

error in transaction maintena

nce
transaction successful

update
transaction

log out

Fig: State chart diagram for E-seva

COMPONENT DIAGRAM:
The component diagram contains components and dependencies. Components
represents the physical packaging of a module. The dependencies between the components
show how changes made to one component may affect the other components. Component
diagram can also show the interfaces used by the components to communicate each other.

Login Database Reservation

ticket

Customer Maintain
Bills Data base

Fig: Component diagram for E-seva

DEPLOYMENT DIAGRAM:
A deployment diagram shows processors, devices and connections. Each model
contains a single deployment diagrams which show the connection between the processors
and devices and its allocations from processor to processor. Processor specification, device
specifications enable you to display and modify the respective properties.

Fig: Deployment diagram for e-seva

Viva Voice Questions:

1. What are Relationships?
Ans: There are different kinds of relationships:
Dependencies,
Generalization and
Association.

Dependencies are relationships between two entities.

A change in specification of one thing may affect another thing.
Most commonly it is used to show that one class uses another class as an argument in the
signature of the operation.

Generalization is relationships specified in the class subclass scenario, it is shown when one
entity inherits from other.

Associations are structural relationships that are:

a room has walls,
Person works for a company.
Aggregation is a type of association where there is a has a relationship.
As in the following examples: A room has walls, or if there are two classes room and walls
then the relation ship is called a association and further
defined as an aggregation.

2. Static Diagrams (Also called Structural Diagram):

Ans: The following diagrams are static diagrams.
Class diagram,
Object diagram,
Component Diagram,
Deployment diagram

3. Dynamic Diagrams (Also called Behavioral Diagrams):

Ans: The following diagrams are dynamic diagrams.
Use Case Diagram,
Sequence Diagram,
Collaboration Diagram,
Activity diagram,
Statechart diagram.

4. What is an Use Case?

Ans: A use case specifies the behavior of a system or a part of a system.
Use cases are used to capture the behavior that need to be developed.
It involves the interaction of actors and the system.

5. What is an Use Case?

Ans: A use case specifies the behavior of a system or a part of a system.
Use cases are used to capture the behavior that need to be developed.
It involves the interaction of actors and the system.
E-VOTING

ABSTRACT
The Project is developed for the threat free and user oriented Online Voting System.
The Online Voting system is made for the people of the country residing around the world
and wants to vote for their representative. The election can be conducted in two ways the
paper ballot election and the automated ballot elections.

The automated ballot elections are called the electronic voting. The online voting
system is highly developed and the online polling system can be replaced by accurately and
directly voting online and immediate results. The online voting system is done by the internet
so it can be called the Internet Voting.
The electronic ballots are connected with the central ballot systems which directly
accept and get the updated record of all ballots. The central ballot system applies the Precinct
count method which calculates the all votes from the ballots present at polling centers. The
results are immediate.
PROBLEM STATEMENT
An electronic voting system via the Internet must fulfill the following five basic
requirements:
Only people eligible to vote should be able to vote.
It should be possible to use one‟s vote only once.
The system should ensure correct tallying of votes at all levels (voting district,
constituency and area).
Authentication:
At present, the election database contains the national civic registration number of
everyone who is included in the electoral register. In an Internet voting system, the electoral
register needs supplement with the voter‟s personal password or code, to permit reliable
identification.
Only one vote:
The system has information on all those who are eligible to vote, and when they do so
their votes are just as in the present-day manual procedure checked against the electronic
electoral register.
Ballot secrecy:
The system must not be technically feasible for any one to access the Ballot
information and should transmit it to the counting system.

Existing System:
The existing system is manual and the paper based voting which is voted on paper and
counted manually. The electronic tabulation brings new kind of voting system in which the
electronic cards with all candidates symbol is marked manually and this can be counted
electronically. The electronic voting systems are now different types known as the punch
card, mark sense and the digital pen voting systems.

Disadvantages:
1. Despite the particular advantages to electronic voting system, critics of electronic voting
argue about the security issue and the unequal access chance to the internet is the main
drawbacks to the system.
2. Inequality problem because for those people with low salary might not able to afford the
equipment for electronic voting.
3. Vulnerable tosecurity the security issue is the main drawback of the electronic voting
system.
4. The attacks might be happened from the webpage, network, to the extent of server‟s
database.
5. Virus The server can be easily protected from the attack of virus by using some specific
kinds of operating system. Data will be dangerous if virus attack.

Proposed System:
Once the ballot is released to the voter, along with the receipt bearing the unique ballot code,
the voter should be able to take the paper ballot over to a completely different machine.

Features:
1. Only one person can vote at a time.
2. Can check their status of a person whether vote was done or not.
3. There cannot be revoting at the same due to it is online.
USE CASE DIAGRAM:
A use case diagram is a set of scenarios that describes the interaction between user
and system. The use case is an external view of a system that represents some action the user
might perform in order to complete a task.

Fig: Use case for e-voting system

SEQUENCE DIAGRAM:
A Sequence diagram emphasizes on the time ordering of messages. It addresses the
dynamic view of the system.

: voter C-Verify : C-VProf : C-vinf :

C_Authenticate C_View_Profile C_Voting_info

1: Enter loginID

2: Not Valid

3: Valid

4: Caste Vote

Fig: Sequence diagram for authentication system

: administrator C-Binf : C_Ballot_info B-Vote : B_Voting

1: Ballot Report

2: Secure

3: Send Sucured Ballot

Fig: Sequence diagram for ballot secrecy

: voter C-Verify : C-Vprof :
C_Authenticate C_View_Profile

1: Enter LoginID

2: Not Valid

3: Valid

Fig: Sequence diagram for view profile

: administrator E-DBinf : B-UseDB : B_Use_Database

E_Database_info

1: Voter information

2: Create Database

3: Report

4: Voter Information

5: Get Database

6: Update

7: Save updates

Fig: Sequence diagram for data manipulation

: voter C-Verify : C-Vinf : : administrator
C_Authenticate C_Voting_info

1: Enter LoginID

2: Not Valid

3: Caste Vote

4: Send Ballot Report

Fig: Sequence diagram for voting system

: administrator B-Vote : B_Voting c-Res : C_Results C-ecm :

C_ECommission
1: Ballot report

2: Send Ballot Report

3: Count Results

4: Send Report

5: Declare Results

Fig: Sequence diagram for result

COLLABORATION DIAGRAM:
It represents collaboration between the objects. It is nothing but a set of objects
related in a particular content and interaction.

1: Enter loginID

2: Not Valid
: voter C-Verify :
C_Authenticate 4: Caste Vote

3: Valid

C-VProf : C-vinf :
C_View_Profile C_Voting_info

Fig: Collaboration diagram for authentication system

2: Secure

1: Ballot Report

: administrator C-Binf : C_Ballot_info

3: Send Sucured Ballot

B-Vote : B_Voting

Fig: Collaboration diagram for ballot secrecy

6: Update 2: Create Database

1: Voter information

3: Report
: administrator E-DBinf :
E_Database_info

4: Voter Information
5: Get Database 7: Save updates

B-UseDB : B_Use_Database

Fig: Collaboration diagram for data base manipulation

2: Create Profile

1: Voter Information

3: Report
: administrator E-DBinf :
E_Database_info

6: Report Update 5: Modify Profile

4: Send Profile

C-PModfy :
C_Profile_Modify

Fig: Collaboration diagram for profile manipulation

1: Enter LoginID

2: Not Valid
: voter C-Verify :
C_Authenticate

3: Caste Vote

4: Send Ballot Report

C-Vinf : : administrator
C_Voting_info

Fig: Collaboration diagram for voting system

1: Enter LoginID

2: Not Valid
: voter C-Verify :
C_Authenticate

3: Valid

C-Vprof :
C_View_Profile

Fig: Collaboration diagram for view profile

Fig: Collaboration diagram results
ACTIVITY DIAGRAM:
It is used to model an entire business process. It provides a flow of programs. It is
used to show internal state of an object but events may appear in them.

Fig: Activity diagram for e-voting

CLASS DIAGRAM:
Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model class structure and contents using design elements such
as classes, packages and objects.

Fig: class diagram for e-voting

STATE TRANSITION DIAGRAM:
State chart diagrams are used to describe the behavior of the system. These statements
describes all possible states of an object as an event occurs.

Fig: state chart diagram for e-voting

COMPONENT DIAGRAM:
The component diagram contains components and dependencies. Components
represents the physical packaging of a module. The dependencies between the components
show how changes made to one component may affect the other components. Component
diagram can also show the interfaces used by the components to communicate each other.

Fig: component diagram for e-voting

DEPLOYMENT DIAGRAM:
A deployment diagram shows processors, devices and connections. Each model
contains a single deployment diagrams which show the connection between the processors
and devices and its allocations from processor to processor. Processor specification, device
specifications enable you to display and modify the respective properties.

Fig: Deployment diagram for e-voting

Viva Voice Questions:

1. What is debugging?
Ans: Debugging is a methodological process of finding and reducing the number of bugs
or defects in a computer program.

2. What is spiral model?

Ans: The spiral model is a software development process combining elements of both
design and prototyping in stages, in an effort to combine advantages of top-down
and bottom-up concepts.
3. What is unit testing?
Ans: Unit testing is a method by which individual units of source code, sets of one or
more computer program modules together with associated control data, usage
procedures and operating procedures are tested to determine if they are fit for use.
4. What is module testing?
Ans: Module tests are typically dynamic white-box tests. This requires the execution of
the software or parts of the software. The software can be executed in the target
system, an emulator simulator or any other suitable test environment.
5. What is white box testing?
Ans: White-box testing is a method of testing software that tests internal structures or
workings of an application as opposed to its functionality.
LIBRARY MANAGEMENT SYSTEM

ABSTRACT
Personal library database management system software is designed to provide ease in
maintaining database of the list of different kinds of collections (books, journals, media, etc)
that are possessed by a person. It is a tedious job for a person to search through all the racks
and shelves to find a particular collection and if it is given to someone, then the person may
not be able to recollect properly to whom he has given .To overcome these overheads, a
flexible and simple database is maintained that updates, issues, retrieves, searches about a
particular thing in the collections. This software implements various modules, to maintain
user accounts to contact user, book table is another module to search for the required among
the collection and upgrading the new collection, finally transactions is concerned with issues
and returns from the user.
The basic idea behind this project is to clear the workload on the end-user and to
increase the feasibility to access the software by giving him the preferred details of his
collection at any point of time in a single go. This makes the end-user job much easier.In this
application, the software can be handled only by the end-user having all rights of using the
software. Every user should mention his requirements to the end-user whenever he is free.
Depending on the availability he performs the actions like issues, returns, and adding
new collection all just by making necessary modifications to the database. All features of the
software can be handled easily by its user friendly interface which simplifies the navigation
through the pages and hence makes it highly convenient.
PROBLEM STATEMENT
With the advent of sophisticated technology, computer has become main source for
storing important information and for performing certain jobs. Our project presents one
example of the basic application required to aid in the easy maintenance of a personal library
database which involves efficient management of the books.
The goal of this project is to establish the requirements for a new library Management
system. Librarians should be able to use this system to keep track of all books in the library.
It must enable us to catalog a wide range of information: author, title, ISBN number, editor,
type of book and status. It must contain information about login database: student login id,
staff login id, administration login id etc. The student account must contain a clear record
about each & every book, their library account number, information about the journals &
magazines that are available in the library, it must also maintains records about newspapers,
the record of books available for the reference etc. The staff account must enables the record
of the total number of books that are allocated for them & their account number etc
The administration account must maintain the record of new books that are available in
the library, the record of books that are under repair, finally the system should be able to
calculate any fee payable on an overdue books, there may be changes over a span of time.
This updated information must be accessed by the system.

Existing System:
The system in existence carries out the maintenance process manually by searching
the racks, shelves etc. The technique being employed in the manual system of a personal
library is if certain thing of our collection has given to someone we should remind ourselves
by writing it somewhere or just by remembering it.

Disadvantages:
1. Searching through the racks & shelves for the desired is tedious work.
2. Keeping track of what has lent to whom becomes critical when the no of users
increasing.
3. More vulnerable towards data loss.

Proposed System:
The proposed system is library management system. The system solves the problem of
the existing system. This software is used to maintain the user details, lists of the collection,
transactions followed by updating the database and such similar operations.

Features:
1. Highly feasible to use.
2. Searching a certain thing can be done just through one go.
3. Reduces the work load and makes user task simple.
4. Provides flexible access to the database.
USE CASE DIAGRAM:
A use case diagram is a set of scenarios that describes the interaction between user
and system. The use case is an external view of a system that represents some action the user
might perform in order to complete a task.

Fig: Use Case for Library Management

SEQUENCE DIAGRAM:
A Sequence diagram emphasizes on the time ordering of messages. It addresses the
dynamic view of the system.

Member Books Librarian Library Card

Login

Search books

Books available

Request book

Request library card

Give library card

Check account
Account not full

Issue book

Change book status

Fig: Sequence diagram for borrowing books

Member Books Librarian

Login
Search books

Books available

Request book

Grant book

Change status

Take card, do reading

Fig: Sequence diagram for Reading books

Member Librarian Library Card Books

Return book

Give card
Check card

due

Calculate fine
Give amount details

Pay fine
Update card

Change status

Fig: Sequence diagram for Returning books

COLLABORATION DIAGRAM:
It represents collaboration between the objects. It is nothing but a set of objects
related in a particular content and interaction.
7: Take card, do reading

1: Login
2: Search books
Member Books

3: Books available

4: Request book 6: Change status

5: Grant book

Librarian

Fig: Collaboration diagram for Reading books

5: Calculate fine

1: Return book
2: Give card
7: Pay fine
Member Librarian

6: Give amount details

4: due
9: Change status

3: Check card
8: Update card

Library Books
Card

Fig: Collaboration diagram for Returning books

1: Login
2: Search books
Member Books

3: Books available

10: Change book status

5: Request library card 4: Request book
9: Issue book 6: Give library card

7: Check account
Librarian Library
Card
8: Account not full

Fig: Collaboration diagram for Borrowing books

ACTIVITY DIAGRAM:
It is used to model an entire business process. It provides a flow of programs. It is
used to show internal state of an object but events may appear in them.

MEMBER LIBRIAN

return book go to counter if due Giv e details

y and return book of due

N pay cash

borrow book
inter lib loan
Y section
N N

check f or book in

do research
do research
Y done
N checkout
books
do news read news papers Y
Y
N

Fig: Activity diagram for Library Management

CLASS DIAGRAM:
Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model class structure and contents using design elements such
as classes, packages and objects.

Fig: Class diagram for Library management

STATE TRANSITION DIAGRAM:

State chart diagrams are used to describe the behavior of the system. These statements
describes all possible states of an object as an event occurs.

read
idle
do/ read

search
entry/ login
do/ select book

borrow
do/ check lib card
entry/ request for books
do/ change status
exit/ acquire book

return renewal
entry/ check due ...
date do/ renew book
do/ calculate due
exit/ pay amount

checking
do/ check books

Fig: State chart diagram for Library Management

COMPONENT DIAGRAM:
The component diagram contains components and dependencies. Components
represents the physical packaging of a module. The dependencies between the components
show how changes made to one component may affect the other components. Component
diagram can also show the interfaces used by the components to communicate each other.

Receipt
Generation

Validation
Member
Catalog
LMS
Database

Issues
Book
Catalog

Returns Fine
Collections

Fig: Component diagram for Library Management

DEPLOYMENT DIAGRAM:
A deployment diagram shows processors, devices and connections. Each model
contains a single deployment diagrams which show the connection between the processors
and devices and its allocations from processor to processor. Processor specification, device
specifications enable you to display and modify the respective properties.

Validation
Library card Bill printing
scanner system

Receipt
Library generation
Issues Database

Member
Fine catalog
collection Book
catalog Returns

Fig: Deployment diagram for Library Management

Viva Voice Questions:

1. Define alpha/beta testing?

Ans: Probably one term which you must be aware of as we often hears this software is in
Alpha phase and inBeta phase. Here Testing is done by representative set of
potential users for trial use. Please Note inhouse(alpha testing) external(beta
testing).
2. Define functional testing?
Ans: It checks that the functional specifications are correctly implemented. Can also
check if non-functional behavior is as per expectations.
3. What is SDLC?
Ans: A software cycle deals with various parts and phases from planning to testing and
deploying. All theseactivities are carried out in different ways, as per the needs.
Each way is known as a Software Development.
4. What are design patterns?
Ans: Design Patterns are simple and elegant solutions of commonly occuring problems in
software design.
Design Patterns make it easier to reuse successful designs and architectures of
expereinced andProfessional Designers.
There are three types of Patterns
1.Creational Concerned with creation of objects
2. Structural Concerned with composition of classes or objects
3. Behavioral characterize the ways in which classes and objects interact and
distribute responsibility.
5. what are software engineers needed?
Ans: Computer systems are pervasive and have a major impact on society. Software is a
critical component of all computer systems, including the "embedded systems" used
in communication networks, vehicles, consumerelectronics and medical devices.
Software engineers have the knowledge and skills needed to produce highquality,
effective software on which all these computer systems depend.

ONLINE BOOK SHOP

Abstract
The business to consumer aspect of electronic commerce is the most visible business
use of the World Wide Web. The Primary Goal of this project is to sell books through online
i.e., to develop book shopping system. This system is mainly needed because the customer
can visit the site at any time, search the book and place the order which will be delivered by
the dealer. To reduce the complexity between customer and dealer we have introduced
Electronic Commerce site to sell books online.
This system contains information about various books available in online bookshop.
Customers can browse through internet and if interested to purchase books through online
they can register.
We provide a cart which holds the items selected by the loyal customers. Cart is valid
up to three months from the date of selecting items. He can purchase the item in the cart by
placing an order at the time of selection of items.

PROBLEM STATEMENT
Online bookshop is a comprehensive bibliographic database providing online access
to books on various topics. The customer can reserve and purchase books. He can also get to
know the information about pricing and comparison shopping of each book with an online
shopping experience. The online bookshop should be user friendly in the sense that it has to
be easily to navigate. It should also provide for setting up an account and providing
membership. The process of searching can be done in a number of ways such as based on
name of the author, title of the book, price of the book, category of the book, name of the
publication and date of publication.
The user searches for the book online, selects it and approves the purchase of the
book. The approval of the purchase is done as follows. The online bookshop takes the credit
card number provide by the user and also the address of the user. If the credit card is known
to be valid the online bookshop approves the purchase and that book is marked as purchased
in the database.

Existing System:
The traditional system present to and buy the product in the shop. The customer has to
go to the bookshop directly for purchasing the books. If the book is not available presently,
then the customer place order if he is satisfied by the cost and delivery time.

Disadvantages:
1. No online payment pay-bill is provided.
2. Shipping is done when only after the payment is done.
3. Time consuming process.Manual process.

Proposed System:
The proposed system is online book shopping.The system solves the problem of the
existing system.It provides the customer with the following benefits.

Features:
1. Normal and Advanced search options.
2. Each book contents are listed.Each book contents are listed when book is selected.
3. Indexing is done according to Author name, Book Name, Year of Publishing Subject,
important topics.
4. Price allowance is givenwhen purchased three or more books.
5. Everyone who wishes to perform advanced search should register in order to reduces the impact
of robots, spiders and others on the server.
6. Soft copy is provided if the user/client wishes that too if he buys any books.

USE CASE DIAGRAM:

A use case diagram is a set of scenarios that describes the interaction between user
and system. The use case is an external view of a system that represents some action the user
might perform in order to complete a task.

Enter into Website

if new customer, perform

registration

if old customer, login

search books

Customer

create or update order

payment

Website registration

Shipping and Delivery

acknowledgment by hand

log out

Fig: use case for customer

Login

Maintain Website

Checking shipping details for each

order

Admin

Update Website

Update Database

Log Out

Fig: use case for administrator

Login

Add or Update Stock

Book Seller

Delivery

Log Out

Fig: use case for books seller

SEQUENCE DIAGRAM:
A Sequence diagram emphasizes on the time ordering of messages. It addresses the
dynamic view of the system.

Customer Website Database Banker Admin BookSeller

Homepage
enter the website

display webpage

if old customer,register else login

verify details in database

database verified
Success /failure login

select books required

open cart

display cart

add books into cart

create or update

enter credit/debit card details

verify credit/debit card details

card details verified

success card details

book seller login

admin login

maintain database

deliver books to customer

books are delivered to customer

update stock in database

stock updated

show updates in webpage

if books are not available in place, order

intimate book seller
log out

Fig:Seq
uence diagram for online book shop
COLLABORATION DIAGRAM:
It represents collaboration between the objects. It is nothing but a set of objects
related in a particular content and interaction.

1: enter the website

3: if old customer,register else login 5: database verified
6: Success /failure login 22: stock updated
7: select books required
8: open cart
10: add books into cart
11: create or update
Customer 12: enter credit/debit card details
26: log out Database
4: verify details in database

2: display webpage Website

9: display cart Homepage
24: if books are not available in place, order

21: seller
25: intimate book update stock in database
20: books are delivered to customer
15: success card details 17: admin login
18: maintain database
16: book seller login
23: show updates in webpage
13: verify credit/debit card details
14: card details verified

19: deliver books to customer BookSelle

r

Banker Admin

Fig: Collaboration diagram for online book shop

ACTIVITY DIAGRAM:
It is used to model an entire business process. It provides a flow of programs. It is
used to show internal state of an object but events may appear in them.

Login

invalid

valid

Database
Updating

Shipping

Log Out

.
Fig: Activity diagram for administrator

login

invalid

valid

Update the
stack

Deliver the
books

log out

Fig: Activity diagram for books seller

Enter into
website

Registration Login

valid
not valid
not valid

success

Search

Create Order

Ship order

Make Payment

credit card
details
invalid

valid

Deduct funds

Shipping

Log out

Fig: Activity diagram for customer

CLASS DIAGRAM:
Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model class structure and contents using design elements such
as classes, packages and objects.

Fig: Class diagram for online bookshop

STATE TRANSITION DIAGRAM:
State chart diagrams are used to describe the behavior of the system. These statements
describes all possible states of an object as an event occurs.

Registration Login

Search
Books

continue ordering
Ordering
Books

finished selection

Log Out Payment

Fig: State chart diagram for online bookshop

COMPONENT DIAGRAM:
The component diagram contains components and dependencies. Components
represents the physical packaging of a module. The dependencies between the components
show how changes made to one component may affect the other components. Component
diagram can also show the interfaces used by the components to communicate each other.

Component diagram represents clusters of logically related components. Component

packages are parallel to the role played by logical packages for class diagrams. They allow us
to partition the physical model of the system.

Homepage Registration Login Book

Details

Log Out Credit Card Make Create

Details Payment order

Fig: Component diagramm for online bookshop

DEPLOYMENT DIAGRAM:
A deployment diagram shows processors, devices and connections. Each model
contains a single deployment diagram which shows the connection between its processors
and devices and its allocation from processor to processor. Processor specifications, device
specifications and connection specifications enable you to display and modify the respective
properties

Admin System

BookSeller
System
Customer
System

DataBase
Bank System
System

Fig: Deployment diagram for online bookshop

Viva voice questions:

1. What are uses cases and class diagrams in SE?

Ans: Use cases are graphical representation of system parts and there interaction that is taking
place. Normally we depict the part of the systems who are involved in some activity as
actors. Class Diagrams are a part of designing process. After coming up with use cases
of the system, we take eachuse case and come up with the classes that we need to
perform that functionality. Each class will have Class Name, Attributes and Operations
associate with it. Some of the features of the classes are each class should have well
defined responsibilities These responsibilities should be cohesive i.e. the system as a
whole looks sensible and looks together.
2. What are test levels?
Ans: Unit testing, component testing, integration testing, system testing, acceptance system,
generic testing.
3. What is black box testing?
Ans: Black box testing is a method of software testing that tests the functionality of an
application as opposed to its internal structures or workings. This method of test can be
applied to all levels of software testing.
4. What is used case testing?
Ans: UCBT addresses phases where the tester is interested in exploring behavior that flows
through multiple use cases, which are typically the late function, system and solution
phases of the life cycle.
5. What is gray box testing?
Ans: Gray-box testing is a combination of white-box testing and black-box testing. The aim
of testing is to search for the defects if any due to improper structure or improper usage
of applications.
RAILWAY RESERVATION

ABSTRACT
Railway Reservation System is a complex online distributed transaction application
based on client server architecture. The salient features of the software include allowing user
from anywhere to do a booking for a journey in any train in any class from anywhere to
anywhere; handling reservation, modifications cancellation/refunds.
This project is all about the railway reservation online i.e., Software includes allowing
user from anywhere to do a booking for a journey in any train in any class from anywhere to
anywhere; handling reservation, modifications cancellation/refunds.
The online reservation system is basically derived from the GDS (global distribution
system) also known as CRS (computer reservation system). The online reservation system
has its database centrally located which is accessed through an Application Programming
Interface (API).
With the invent of online reservation system the traveler and the railway got the
freedom to book a seat anywhere at any time at their convenience. The traveler can book a
ticket at a click of a mouse saving the time and money for the travelling. It has also become a
hassle free transaction for both the railway and the traveler.
The online reservation system involves three main actors the database, online operator
and a database scheduler. The database scheduler updates the database, the online operator
accepts and confirms the booking and updates the database.
PROBLEM STATEMENT
The existing railway reservation system has many shortcoming associated with it. In
the existing system railway used to set train reservation levels higher than seating capacity to
compensate for passenger cancellation and no-shows accounting to overbooking in the agent
frequently to do so thus wasting time and money for all. In the existing system integration of
different railways on a single platforms was not met. With the advent of the online
reservation system these flaws can be overcome.

Existing system:
The traditional system present is to buy ticket from reservation counter in railway
station.We have to stand in the queue for hours even when we want to buy ticket. If we want
to reserve tickets suddenly, we can book tickets through online.

Disadvantages:
1. Time consuming process.
2. In transactions, it may take time.

Proposed system:
The new online reservation system maintains the database centrally giving the clients
the information required from anywhere in the world whenever required. This system
requires the use of API through which it interacts the data from a central database monitors
all the data exchanges that are made at the client side to it and updates it automatically.
Through online reservation system customer is able to book & purchase a ticket thus saving
time money for the customer and an railway/agent. As the information is stored centrally the
customer never loses his ticket as in the existing system.

Features:
1. We can reserve tickets at any time.
2. Time saving process.
3. Easier and flexible process.
4. Check the status of train at any time.
USE CASE DIAGRAM:
A use case diagram is a set of scenarios that describes the interaction between user
and system. The use case is an external view of a system that represents some action the user
might perform in order to complete a task.

Fig:- Use Case Diagram

SEQUENCE DIAGRAM:
A Sequence diagram emphasizes on the time ordering of messages. It addresses the
dynamic view of the system.

: APPLICATION FORM
TRAIN
: PASSENGER : CLERK
: ADMINISTRATOR

1: fills application form

2: submit the form

3: validate form

4: send details for reservation

5: check availability

6: selected train available

7: shows amaount

8: pay amount for reservation

9: pays amount TICKET

10: send details

11: <<create>>

12: issue ticket

13: get ticket

14: print ticket

15: gives ticket

Fig: Sequence diagram for reservation

TICKET TRAIN

: CLERK
: PASSENGER :
ADMINISTRATOR

1: give ticket details

2: validate

3: valid

4: confirm for cancel

5: confirmed

6: forwards details

7: cancel

8: <<destroy>>

9: update details

10: updation completed

11: returns amount details

12: collect amount

Fig: Sequence diagram for cancellation

TRAIN

: PASSENGER : CLERK

1: put query

2: forward query

3: gets result

4: displays answer

Fig: Sequence diagram for query

COLLABORATION DIAGRAM:

It represents collaboration between the objects. It is nothing but a set of objects

related in a particular content and interaction.

1: put query

4: displays answer : CLERK

: PASSENGER

3: gets result
2: forward query

TRAIN

Fig: collaboration diagram for query

: APPLICATION
FORM
1: fills application form

2: submit the form

9: pays amount
3: validate form

8: pay amount for reservation : CLERK

15: gives ticket
: PASSENGER

7: shows amaount 13: get ticket

12: issue ticket
14: print ticket

4: send details for reservation

10: send details
11: <<create>>
TICKET

:
ADMINISTRATOR6: selected train available TRAIN

5: check availability

Fig: collaboration diagram for reservation

1: give ticket details
5: confirmed

: PASSENGER
4: confirm for cancel
12: collect amount

3: valid
: CLERK

11: returns amount details

2: validate
TICKET
7: cancel

6: forwards details

8: <<destroy>> 9: update details

TRAIN
: 10: updation completed
ADMINISTRATOR

Fig: collaboration diagram for cancellation

ACTIVITY DIAGRAM:
It is used to model an entire business process. It provides a flow of programs. It is
used to show internal state of an object but events may appear in them.

PASSENGER CLERK ADMINISTRATOR

reservation
validate

[VALID]
check
[YES] availability
[INVALID]
fill application
prompt
modification
submit [AVAILABLE]
application
collect amount available

[NO] perform
modification

update
pays amount send details
for reservatiom

print ticket issue ticket

collect ticket

cancellation [UNAVAILABLE]

validate details
[YES]

give ticket
details
[INVALID]
[VALID]
[NO]
send details cancel ticket
for cancel

collect amount return amount

update details

put queries answering to

queries

get required
details

Fig: Activity diagram for railway reservation

CLASS DIAGRAM:

Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model class structure and contents using design elements such
as classes, packages and objects.

+1 APPLICATION FORM
+1
+1..* +1

PASSENGER +1
+1 +1
(from Use Case View) CLERK
(from Use Case View)
+1

+1

+1 +1
+1
+1 +1..*
TICKET ADMINISTRATOR TRAIN
(from Use Case View)

Fig: Class diagram for railway reservation

STATE CHART DIAGRAM:
State chart diagrams are used to describe the behavior of the system. These statements
describes all possible states of an object as an event occurs.

destroys ticket
print ticket

reservation
Idle
entry/ valid form cancellation
exit/ reserved
entry/ reserve
select query exit/ cancelled
answer reservation or cancel

for reserve
for cancel
query

entry/ valid query

exit/ invalid query validation

entry/ within 60 days or valid form

exit/ invalid details

Fig: state chart diagram for railway reservation

COMPONENT DIAGRAM:
The component diagram contains components and dependencies. Components
represents the physical packaging of a module. The dependencies between the components
show how changes made to one component may affect the other components. Component
diagram can also show the interfaces used by the components to communicate each other.

ADMINISTRATION
APPLICATION
SYSTEM
FORM

TRAIN
TICKET

Fig: component diagram for railway reservation

DEPLOYMENT DIAGRAM:

A deployment diagram shows processors, devices and connections. Each model

contains a single deployment diagrams which show the connection between the processors
and devices and its allocations from processor to processor. Processor specification, device
specifications enable you to display and modify the respective properties.

administrator
server
ticket

printer
train

Fig; Deployment diagram for railway reservation

Viva Voice Questions:

1. What is security testing?
Ans: Testing of security against unauthorized access, denial of service attacks.
2. What are types of test tools?
Ans: Test management tool, test specification tool, tools static testing, tools for dynamic
testing, tools for non functional test.
3. What is RAD?
Ans: Rapid application development is formally a parallel development of functions.
4. What is the difference between testing techniques and testing tools?
Ans: Testing technique: Is a process for ensuring that some aspects of the application
system or unit functions properly there may be few techniques but many tools.
Testing tools: Is a vehicle for performing a test process. The tool is a resource to the
tester but itself is insufficient to conduct testing.