INDEX

SL NO.

DATE

NAME OF THE EXPERIMENT

Railway Reservation

ATM

Course Registration

Library System

Quiz System

Online Bookshop

PAGE NO.

SIGNATURE

EXP NO:

DATE:

RAILWAY RESERVATION
Aim:

To Design the model for Railway Reservation.

Step 1: Problem Statement

1.
2.
3.
4.
5.
6.
7.
8.

The user has to reserve a ticket for a station through Railway reservation.
User will enquires all the details of the train.
User will enquire about the reservation ticket.
The user has to take the form and fill all the details in the registration form.
It performs to submit the form to administrator through enquiry.
Administrator will check the details of reservation.
It will have to perform the transaction.
User will have to pay the money to administrator on receiving of the ticket.

Step 2: Functional Requirements

1. User: Have complete access to reserve the ticket as detailed below.
Enquire: Enquires the information of train name, timings, ticket.
Receive: Receives the information through enquiry.
Ask: User will ask the reservation form.
Fill: The details of the train will be filled here.
Pay: The money will be paid to the operator.
2. Enquiry: The details of the train will be available.
Available Trains: The details of available trains will be shown.
Available Date: The date on which particular train available is shown.
Ask Time: At what time the train arrives and the departure time will asked by passenger.
3. Operator: Operates the transaction of reservation.
Issue: Issues the ticket for the particular train.
Take: Receives the money from the passenger.
4. Administrator: Maintains the information of trains.
Check: Checks the reservation form whether it is correct or not.
Update: Updates the information if any changes had been takes place.

ASCET

EXP NO:

DATE:

Step 3: Usecase Diagram

Identify the use cases for railway reservation.
Actors: User, Enquiry, Administrator.
Use cases: Enquiry Info, Receive Info, Take form, Submit form, Receive Ticket, Pay money, Perform
Transaction.
Enquiry Info: User will ask the enquiry about information of trains.
Receive Info: User will receive the information details.
Take form: User will take the registration form.
Submit form: User will fill and submits the form to operator.
Receive Ticket: User will receive the ticket from operator.
Pay money: User have to pay the money.
Perform Transaction: Administrator will perform the transaction and updating of available trains.

timings
train

ticket
enquiry info

receive info

check info

train Enquiry
Enquiry

U SER
enquiry abt resv .tkt

perform trains

take form
name

address
age

gender

train no

submit form

receive ticket

pay money

ASCET

give info

administrator

EXP NO:

DATE:

Step 4: Class Diagram

Steps to model the Class diagram:
1. First type the class name in the name field of the class.
2. Add Operations:
Add the attributes to attributes in the attributes field Operations in the operations field of the
class.
Add types to the attributes.
Add signatures to the operations/methods.

enquiry
trainname
trainno
time
1
user
name
age
gender
address
takeform()
submitform()
receivetkt() *
paymoney()

operator
trainno
trainname

*
*

availtrains()
availdate() 1
asktime()

1
issuetkt()
takemoney()

form
name
age
gender
date
time
bedthno
fillform()

ASCET

1 administrator
1..*

EXP NO:

DATE:

Step 5: Sequence Diagram

Steps to model the Sequence diagram:
1.

First placing the objects that participate in the interaction at the top of the diagram across the Xaxis.
2. Place the objects that initiate the interaction at left and increasing more subordinates to right.
3. Place the messages that these objects send and receive along the Y-axis in order of increasing
time from top to bottom.
4. Focus of control: It is a thin rectangle that shows the period of time during which an object is
performing an action.
:passenger

:enquiry

:form

:operator

:administrator

1: ask list of avail trains

2: give list

3: take form
4: fill form
5: check form

6: update info
7: pay money

8: issue tkt

ASCET

EXP NO:

DATE:

Step 6: Collaboration Diagram

Steps to model the Collaboration diagram:
1.
2.
3.
4.
5.

Place the object that participates in the interaction as the vertices in a graph.
Remember the links that connect these objects as arcs of the graph.
Finally, adorn the links with the messages that the object sends and receives.
Path: Path is needed to link the objects explicitly. For global, local parameters and self paths.
Sequence Number: It is used to indicate the time order of the message.

6: update info
5: check form
:operator
4: fill form
7: pay money
8: issue tkt
1: ask list of avail trains
:enquiry

:passenger
2: give list
3: take form

:form

ASCET

:administrator

EXP NO:

DATE:

Step 7: Activity Diagram

Steps to model the Activity Diagram:
To Model Workflow:
1. Establish a focus for workflow.
2. Identify pre-conditions at initial state and post-conditions at final state.
3. Beginning at the workflow, show transitions connecting activities in active state.
To Model Operation:
1. Collect the abstractions that are involved in operations.
2. Identify the pre-conditions branching as necessary to specify conditional paths and interactions.

En te r i n to th e
R e s e r va ti o n c o u n te r
En qu i r y th e
t r a i n i n fo
R e qu e s t fo r
R e s e r va ti o n fo r m
R e c e i ve & F i l l
t h e fo r m
S u bm i t i n to
o pe r a to r
Check
a va i l a bi l i ty
Tryfor
o th e r t r a i n
Allotseat
num
Paymo ne y
t o o pe r a to r
R e c e i ve th e
ticket
Ex i t

ASCET

EXP NO:

DATE:

Step 8: State Chart Diagram

Steps to model the State Chart Diagram:
1.
2.
3.
4.
5.

First select one state transition diagram.

Add states to the transition diagram.
Add documentation to states if needed.
Add activities to state chart diagram.
Add an entry action whenever we need in the state chart diagram, similarly exit action also
when needed.
6. Add transactions by dragging the transaction lines from source to target.
7. Add reflexive transaction whenever needed in the diagram.

Enter into res ervation

counter
Enquiry the
train info
Reques t for
reservation form
Receive &
fill the form
idle

s ubmit to the
operator
Try for
other train
n
o
yes
allot s eat
num
Pay money to
the operator
Receive
tick et

ASCET

try for
other train

EXP NO:

DATE:

Step 9: Component Diagram

Steps to model the Component Diagram:
1. It contains set of components and their relationships.
2. Graphically render as a set of vertices and arcs.
3. The different components in the component diagram are view, view controller and DB access.

Ticket.jav
a

Railway
station.exe

ticket.java

ticket.Jav
a

ASCET

EXP NO:

DATE:

Step 10: Deployment Diagram

Steps to model the Deployment Diagram:
1. It is a process of the nodes that lie on the system.
2. It contains nodes, interfaces and relationships.
3. Graphically render a set of vertices and arcs.

Administartor
( DB)

Customer client

Ticket

Result:-

ASCET

EXP NO:

DATE:

ATM
Aim: To develop a model for ATM.
Step 1: Problem Statement
1. The user has to draw the money from the ATM.
2. User will be logged through the pin card.
3. Administrator will have to maintain the transaction properly.
4. Administrator has to provide options to choose the type of transaction.
5. User will choose the required transaction.
6. User will enter the amount to be drawn.
7. The system will checks whether the user make the transaction.
8. Administrator will gives money to the user.
9. If the money will not be available, the administrator will cancel the transaction.
10. Finally the user will gets the receipt and exits the transaction.
Step 2: Functional Requirements
1. User: User will have to make the transaction, then the details below
Enter: User will enter the card into the system.
Enter pin: The user should have to enter the pin code.
Option: User has to choose an option to make a transaction.
Enter Amount: User enters the amount to be drawn.
2. Administrator: Administrator will make the transaction and returns money.
Check: The administrator will checks the pin code entered.
Check Bal: The administrator will checks the amount entered whether it is available or not.
Draw: It will give money to the user required.
Update: It will update the details after the transaction is completed.

ASCET

EXP NO:

DATE:

Step 3: Usecase Diagram

Identify the Use cases for ATM.
Actors: User, Administrator.
Use Cases: Enter card, Enter pin, Withdraw, Return, Exit.
Enter card: User enters the card into the system.
Enter pin: User will be asked to enter the pin code.
Withdraw: The amount required will be given by the user.
Return: Administrator will return the money.
Exit: User will exit the transaction.

enter card

enters

enter pin

enters
display options

checks
transaction

gives amt

USER

check for availability

receives
withdraw
received

returns money
acknowledges

comes out
return

issue

exit

ASCET

reads

Administrator

EXP NO:

DATE:

Step 4: Class Diagram

Steps to model the Class diagram:
1. First type the class name in the name field of the class.
2. Add Operations:
Add the attributes to attributes in the attributes field Operations in the operations field of the
class.
Add types to the attributes.
Add signatures to the operations/methods.

user
machine

name
pin
amt
enterCard() *
enterPin()
option()
enterAmt()

ASCET

Administrator

name

checkPin()
checkBal() *
withdraw()
deposit()

service num
acc num
1

valid()
checkPin()
updateBal()

EXP NO:

DATE:

Step 5: Sequence Diagram

Steps to model the Sequence diagram:
1. First placing the objects that participate in the interaction at the top of the diagram
across the X-axis.
2. Place the objects that initiate the interaction at left and increasing more subordinates
to right.
3. Place the messages that these objects send and receive along the Y-axis in order of
increasing time from top to bottom.
4. Focus of control: It is a thin rectangle that shows the period of time during which an
object is performing an action.

:U ser

:Adm inistrator

:Machin e
1 : E nter card
2 : E nter pin code
3 : p in
4 : check pin
5 : correct
6 : d isp lay optio ns
7 : select transaction

8 : req uests transaction

9 : enter am ount
10 : amo unt
11 : check fo r availab le
12 : checks
13 : if available deb it am t
14 : give the amt
15 : received cash
16 : update bal
17 : send receip t
18 : take receipt & exit

ASCET

EXP NO:

DATE:

Step 6: Collaboration Diagram

Steps to model the Collaboration diagram:
1.
2.
3.
4.

Place the object that participates in the interaction as the vertices in a graph.
Remember the links that connect these objects as arcs of the graph.
Finally, adorn the links with the messages that the object sends and receives.
Path: Path is needed to link the objects explicitly. For global, local parameters and
self paths.
5. Sequence Number: It is used to indicate the time order of the message.

12: checks
16: update bal

:Administrator

5: correct
13: if available debit amt
14: give the amt

4: check pin
8: requests transaction
11: check for available

1: Enter card
3: pin
7: select transaction
10: amount

18: take receipt & exit

:User

ASCET

2: Enter pin code

6: display options
9: enter amount
15: received cash
17: send receipt

:Machine

EXP NO:

DATE:

Step 7: Activity Diagram

Steps to model the Activity Diagram:
To Model Workflow:
1. Establish a focus for workflow.
2. Identify pre-conditions at initial state and post-conditions at final state.
3. Beginning at the workflow, show transitions connecting activities in active state.
To Model Operation:
1. Collect the abstractions that are involved in operations.
2. Identify the pre-conditions branching as necessary to specify conditional paths and
interactions.

I n se r t
card
V e r i fy
card

y
E n te r
p a ssw o r d
Check PW

y
Select
tr a n sa c ti o n
P r o c e ssi n g
tr a n sa c ti o n
n o t c o n ti n u e
U p d a te
account
Print
receipt
Exit card

ASCET

c o n ti n u e

EXP NO:

DATE:

Step 8: State Chart Diagram

Steps to model the State Chart Diagram:
1.
2.
3.
4.
5.

First select one state transition diagram.

Add states to the transition diagram.
Add documentation to states if needed.
Add activities to state chart diagram.
Add an entry action whenever we need in the state chart diagram, similarly exit action
also when needed.
6. Add transactions by dragging the transaction lines from source to target.
7. Add reflexive transaction whenever needed in the diagram.

entry / read card exit / eject card

active
card insert

validate

idle
cancel
selecting
maintain
[continue]

maintain

processing

[ not continue]
printing

cancel

ASCET

EXP NO:

DATE:

Step 9: Component Diagram

Steps to model the Component Diagram:
1. It contains set of components and their relationships.
2. Graphically render as a set of vertices and arcs.
3. The different components in the component diagram are view, view controller and
DB access.

Atm.exe

Cash
dispense.exe

ASCET

EXP NO:

DATE:

Step 10: Deployment Diagram

Steps to model the Deployment Diagram:
1. It is a process of the nodes that lie on the system.
2. It contains nodes, interfaces and relationships.
3. Graphically render a set of vertices and arcs.

atm.exe

Result:-

ASCET

cash dispense

EXP NO:

DATE:

COURSE REGISTRATION
Aim: To develop a model for Course registration.
Step 1: Problem Statement
1. The person should choose a course for registration.
2. The person may be a student or a staff, should be logged in first.
3. It should have to provide all details of course in a view i.e., view the schedule to the
student.
4. It should submit grades to the registrar.
5. It should keep track of assigning the staff.
6. It should provide student information and the staff information.
7. If course will not be available then the person has to select another course.
8. After completion of the course, person has to pay the bill to the registrar.
Step 2: Functional Requirements
1. Registrar: Have complete access on the registration course.
Allotting Course: Registrar will allot the course for students.
Maintains: He have to maintain both the student and staff information.
Updation: When ever updation occurs in selection of a course, it will be updated.
Cancel: When the person choose a wrong course then the registration form will be
cancelled.
2. Member: The system must permit the members to perform the following:
Login: Permitted to login with a unique registered id.
Staff: Staff will be assigned by the registrar.
Selection: He will selects course to teach.
Student: Students have to register the course.
View schedule: Student will select a course in the view list.
Change: They may want to change for another course.
Submit: They have to submit the grades to the registrar.
Pay fee: The person have to pay the fee to the registrar

ASCET

EXP NO:

DATE:

Step 3: Usecase Diagram

Identify the use cases of course registration.
Actors: Person, Student, Staff, Registrar.
Use cases: Login, View schedule, Select course, Submit grades, Pay fee, Assign Staff,
student, staff information

login

viewSchedule

select course
person

Administrator
submit grades

pay fee

student

staff
assign staff

stu info

staff info

ASCET

EXP NO:

DATE:

Step 4: Class Diagram

Steps to model the Class diagram:
1. First type the class name in the name field of the class.
2. Add Operations:
Add the attributes to attributes in the attributes field Operations in the operations field of
the class.
Add types to the attributes.
Add signatures to the operations/methods.

user
name
id
login()

student
name
address
phonenum

professor
name
address
phonenum

addcourse ()
removecourse () *

billing system
date
sendbill()
getPayment()

ASCET

select course ()
*

1
register
name
address
maintainstuinfo()
maintainproffinfo()
openreg()
closereg()
cancelreg()

EXP NO:

DATE:

Step 5: Sequence Diagram

Steps to model the Sequence diagram:
1. First placing the objects that participate in the interaction at the top of the diagram
across the X-axis.
2. Place the objects that initiate the interaction at left and increasing more subordinates
to right.
3. Place the messages that these objects send and receive along the Y-axis in order of
increasing time from top to bottom.
4. Focus of control: It is a thin rectangle that shows the period of time during which an
object is performing an action.
:Register

:login

:student

:professor

1: reg. login

2: maintain student info

3: maintain professor info
4: opening register
5: get the student list
6: view the list

7: cancel register if <3 students in a course

8: reg. is cancelled, choose another course

9: closing register

ASCET

:reg.controller

EXP NO:

DATE:

Step 6: Collaboration Diagram

Steps to model the Collaboration diagram:
1.
2.
3.
4.

Place the object that participates in the interaction as the vertices in a graph.
Remember the links that connect these objects as arcs of the graph.
Finally, adorn the links with the messages that the object sends and receives.
Path: Path is needed to link the objects explicitly. For global, local parameters and
self paths.
5. Sequence Number: It is used to indicate the time order of the message.

:professor
3: maintain professor info
1: reg. login
:Register

:login

4: opening register
5: get the student list
7: cancel register if <3 students in a course
9: closing register

2: maintain student info

6: view the list

:reg.controller

:student
8: reg. is cancelled, choose another course

ASCET

EXP NO:

DATE:

Step -7: Activity Diagram

Steps to model the Activity Diagram:
To Model Workflow:
1. Establish a focus for workflow.
2. Identify pre-conditions at initial state and post-conditions at final state.
3. Beginning at the workflow, show transitions connecting activities in active state.
To Model Operation:
1. Collect the abstractions that are involved in operations.
2. Identify the pre-conditions branching as necessary to specify conditional paths and
interactions.

Login
s ys te m
re que s t for
cours e de tails
D is play Cours e D e tails
& S che duling de tails
S e le cting
cours e
R e q . for
R e g . form

payme nt
office

R e gis trat
ion form
s pe cify
all de tails

pay fe e

s ubmit
form

s tore
form

update
vacancy

print
re ce ipt
As s ign
s taff

ASCET

EXP NO:

DATE:

Step-8: State Chart Diagram

Steps to model the State Chart Diagram:
1.
2.
3.
4.
5.

First select one state transition diagram.

Add states to the transition diagram.
Add documentation to states if needed.
Add activities to state chart diagram.
Add an entry action whenever we need in the state chart diagram, similarly exit action
also when needed.
6. Add transactions by dragging the transaction lines from source to target.
7. Add reflexive transaction whenever needed in the diagram.

active
request
for
display
login
select of
idle
Request
for
cancel

access all
payment

main

submissio
n&
update

print

assign

ASCET

EXP NO:

DATE:

Step 9: Component Diagram

Steps to model the Component Diagram:
1. It contains set of components and their relationships.
2. Graphically render as a set of vertices and arcs.
3. The different components in the component diagram are view, view controller and
DB access.

course
catalog.exe
Registration.exe

billing
system.exe

ASCET

EXP NO:

DATE:

Step 10: Deployment Diagram

Steps to model the Deployment Diagram:
1. It is a process of the nodes that lie on the system.
2. It contains nodes, interfaces and relationships.
3. Graphically render a set of vertices and arcs.

course
catalog.exe

billing
system.exe

Billing
system.exe

Result:-

ASCET

Registration.
exe

EXP NO:

DATE:

LIBRARY SYSTEM
Aim: To develop a model for Library System.
Step 1: Problem Statement
1. The statement must contain a Data base, Titles, and items in its inventory. Since, libraries
have multiple copies of popular books and magazines, the title name of book and author
must be stored.
2. The system permits members in restricted use.
3. It should permit the Librarian to have complete access.
4. It should keep track of the borrowed items of each member.
5. The system must have rates to be charged for over due items.
6. It should have the cost of every item.
7. It should have the capability to calculate and charge members for overdue items and cost of
damaged articles.
8. The system should restrict the members to borrowing only one item at a time.
9. It should permit deletion of discarded items.
10. It should permit renewal of items when required except for reserved items.

Step 2: Functional Requirements

1. Librarian: Have complete access to the system as detailed.
Login: Permitted to login with a unique registered id.
Manage Items: Add new items to the DB. Delete the damaged items.
Manage Borrowers: Check on transactions of borrower and ensure charges for overdue,
damaged and lost items are paid.
2. Members: The system should permit members to perform the following:
Login: with their unique id that has already been registered with the system.
Browse: Have unrestricted access to view titles of all the items available in the library.
Search: The system must prompt the user to enter a title, author name, subject name or a key word.
he system finds matching names and displays them for the user to choose.
Check Out: Borrowers should be allowed to check up to four items of available titles at any time.
Reserve: If the search operation results in the required item being unavailable, the system allows the
borrower to reserve this item.
Removal of Reservation: Borrowers may remove any reservations they have made any time.

ASCET

EXP NO:

DATE:

Step 3: Usecase Diagram

Identify the use cases of library information system.
Use case actors: Library member, Librarian.
Use cases: Login, Browse, Search, Manage Borrower, Manage items, Manage Title, Remove
Reservation, Make Reservation, Check Item, and Return Item.
Librarian: Have complete access to the system as detailed.
Library Member: Can take issue of books based on restrictions.
Login: Permitted to login with their unique id.
Browse: Have unrestricted access to view titles of all the items available in the library.
Search: The system must prompt the user to enter a title, author name, subject name or a keyword.
Manage Items: Add new items to the DB, Delete the damaged items.
Manage Borrowers: Check on transactions of borrower and ensure charges for overdue items,
damaged, lost items are paid.
Check out: Borrowers should be allowed to check up to four items of available titles at any time.

enter id

enters

checks

checks id
valid

sends
searches book

asks
user

ASCET

issue

librarian

checks for avail

renewal

check for issue

return

check date

exit

modify fine

administrator

EXP NO:

DATE:

Step 4: Class Diagram

Steps to model the Class diagram:
1. First type the class name in the name field of the class.
2. Add Operations:
Add the attributes to attributes in the attributes field Operations in the operations field of the
class.
Add types to the attributes.
Add signatures to the operations/methods.

librarian
name
address

article
id
issuedate
returndate

newArticle()
removeArticle() *
returnArticle()

title
titleid
type
price
author
publication

ASCET

member
memberid
name
address
borrowinglimit
newMember()
removeMember()

student

newTitle()
removeTitle()

*
member borrow article

book title

borrow()
return()

magazine title

fine amount
fineAmt
paidDate

member pay fine

1
1

staff

payFine()
receipt()
collection()

EXP NO:

DATE:

Step 5: Sequence Diagram

Steps to model the Sequence diagram:
1. First placing the objects that participate in the interaction at the top of the diagram across
the X-axis.
2. Place the objects that initiate the interaction at left and increasing more subordinates to
right.
3. Place the messages that these objects send and receive along the Y-axis in order of
increasing time from top to bottom.
4. Focus of control: It is a thin rectangle that shows the period of time during which an object
is performing an action.

:member

:librarian

:stuissuereg

1: request book
2: validate fine borrowing limit
3: validate ok
4: find availability
5: available ok
6: update issue details
7: update issue details
8: update available copy
9: issue book
10: quit

ASCET

:title

:book

EXP NO:

DATE:

Step 6: Collaboration Diagram

Steps to model the Collaboration diagram:
1.
2.
3.
4.
5.

Place the object that participates in the interaction as the vertices in a graph.
Remember the links that connect these objects as arcs of the graph.
Finally, adorn the links with the messages that the object sends and receives.
Path: Path is needed to link the objects explicitly. For global, local parameters and self paths.
Sequence Number: It is used to indicate the time order of the message.

:title

4: find availability
8: update available copy
1: request book
10: quit
:member

5: available ok

:librarian

9: issue book

2: validate fine borrowing limit

7: update issue details
3: validate ok

6: update issue details

:book

ASCET

:stuissuereg

EXP NO:

DATE:

Step 7: Activity Diagram

Steps to model the Activity Diagram:
To Model Workflow:
1. Establish a focus for workflow.
2. Identify pre-conditions at initial state and post-conditions at final state.
3. Beginning at the workflow, show transitions connecting activities in active state. To
Model Operation:
1. Collect the abstractions that are involved in operations.
2. Identify the pre-conditions branching as necessary to specify conditional paths and
interactions.

Ente r pas s
book numbe r
invalid no
valid no
Ente r type
of is sue
borrow
re turn
update
iss ue de tails

ve rify is s ue
de tails

ve rify
re turn time

out of time
as s ign
time

not firs t
Update
iss ue de tails
update article
availability

ASCET

EXP NO:

DATE:

Step 8: State Chart Diagram

Steps to model the State Chart Diagram:
1.
2.
3.
4.
5.

First select one state transition diagram.

Add states to the transition diagram.
Add documentation to states if needed.
Add activities to state chart diagram.
Add an entry action whenever we need in the state chart diagram, similarly exit action also
when needed.
6. Add transactions by dragging the transaction lines from source to target.
7. Add reflexive transaction whenever needed in the diagram.

validate
passbook

enter passbook num

receive type
of issue
borrow
return

idle

update issue details

of borrower

verify
return date
out of time
assign
fine

ASCET

verify issue
details of

update article
availability

EXP NO:

DATE:

Step 9: Component Diagram

Steps to model the Component Diagram:
1. It contains set of components and their relationships.
2. Graphically render as a set of vertices and arcs.
3. The different components in the component diagram are view, view controller and DB
access.

librarian.java

student issue
register

item.java

ASCET

EXP NO:

DATE:

Step 10: Deployment Diagram

Steps to model the Deployment Diagram:
1. It is a process of the nodes that lie on the system.
2. It contains nodes, interfaces and relationships.
3. Graphically render a set of vertices and arcs.

student / staff
kiosk

library manager

Result:-

ASCET

library (db)

EXP NO:

DATE:

QUIZ SYSTEM
Aim: To develop a model for Quiz system.
Step 1: Problem Statement
1.
2.
3.
4.
5.
6.
7.

The Participant will participate in Quiz.

The quiz will be conducted among the participants by the interviewer.
Interviewer will announce the rules for the participants.
Participants will answer the questions to appropriate.
Interviewers will checks the answer whether they will correct or not.
The scorer will calculate the score and gives to interviewer.
Finally interviewer will distribute the prizes for winners.

Step 2: Functional Requirements

1. Participant: Will participate in quiz competition details below
Enroll: Participant has to enroll their names in team number.
Answer: Participant will answer the questions asked by interviewer.
2. Interviewer: will ask the questions to Participants.
Rules: He will announce the rules for all the Participants.
Ask Que: Interviewer will aks the questions.
Check: He will checks the answers given by Participants.
Announce: He will announce the results to Participants.
Prizes: interviewer will distribute the prizes to winners.
3. Scorer: Will calculates the score.
4. Tell score: Scorer will tells the score to the interviewer.

ASCET

EXP NO:

DATE:

Step 3: Usecase Diagram

Identify the use cases of Quiz.
Actors: Participant, Interviewer, Scorer.
Usecases: Rules, Ask Questions, Answer, Checks, Prizes, Calculate score.
Rules: Rules will be announced by the interviewer.
Ask Que: The question will be asked by the interviewer.
Answer: Participant will answer the questions.
Check: Interviewer will check the answers.
Calculate score: The scorer will calculates the score.
Prizes: Prizes will be distributed to the winners by interviewer.

no of que
no of persons

time

team

prizes

rules
Accepts
Questioned

ask question

askscore

Questions
checks

Answers
R or W
participant

receives

answer
distributes

interviewer

annoscore
scorer

checks
total score
Prizes

ASCET

EXP NO:

DATE:

Step 4: Class Diagram

Steps to model the Class diagram:
1. First type the class name in the name field of the class.
2. Add Operations:
Add the attributes to attributes in the attributes field Operations in the operations field of the
class.
Add types to the attributes.
Add signatures to the operations/methods.

participant
name
teamNum
answ()

scorer
name
scoreAna()
*

1 interviewer
name
rules()
prizes()
askQue()
check()
total()
result()

ASCET

EXP NO:

DATE:

Step 5: Sequence Diagram

Steps to model the Sequence diagram:
1. First placing the objects that participate in the interaction at the top of the diagram across
the X-axis.
2. Place the objects that initiate the interaction at left and increasing more subordinates to
right.
3. Place the messages that these objects send and receive along the Y-axis in order of
increasing time from top to bottom.
4. Focus of control: It is a thin rectangle that shows the period of time during which an object
is performing an action.

:participant

:scorer

:interviewer

1: enter room
2: specify rules
3: ask que
4: ans que

5: check ans
6: assign marks
7: total
8: winners
9: announce results
10: distribute prizes

ASCET

EXP NO:

DATE:

Step 6: Collaboration Diagram

Steps to model the Collaboration diagram:
1.
2.
3.
4.
5.

Place the object that participates in the interaction as the vertices in a graph.
Remember the links that connect these objects as arcs of the graph.
Finally, adorn the links with the messages that the object sends and receives.
Path: Path is needed to link the objects explicitly. For global, local parameters and self paths.
Sequence Number: It is used to indicate the time order of the message.

5: check ans
6: assign marks

1: enter room

4: ans que
:interviewer

:participant
2: specify rules 3:
ask que
9: announce results
10: distribute prizes

8: winners7: total

:scorer

ASCET

EXP NO:

DATE:

Step 7: Activity Diagram

Steps to model the Activity Diagram:
To Model Workflow:
1. Establish a focus for workflow.
2. Identify pre-conditions at initial state and post-conditions at final state.
3. Beginning at the workflow, show transitions connecting activities in active state.
To Model Operation:
1. Collect the abstractions that are involved in operations.
2. Identify the pre-conditions branching as necessary to specify conditional paths and
interactions.

participant
e nte r room
s pe cify
rule s
As k
que s tion
G ive
ans we r
Che ck
Ans we r
wrong
right
as s ign
no mark s
mark s
End of round
or que s tions
announce
re s ults
distribute
prize s

ASCET

no

EXP NO:

DATE:

Step 8: State Chart Diagram

Steps to model the State Chart Diagram:
1.
2.
3.
4.
5.

First select one state transition diagram.

Add states to the transition diagram.
Add documentation to states if needed.
Add activities to state chart diagram.
Add an entry action whenever we need in the state chart diagram, similarly exit action also
when needed.
6. Add transactions by dragging the transaction lines from source to target.
7. Add reflexive transaction whenever needed in the diagram.

Enter
round
rules

Ask ques
idle
cancel

Get ans

yes

Check
Ans

Assign
Marks

check end
of round
Declare
Results
Award
prizes

ASCET

no

EXP NO:

DATE:

Step 9: Component Diagram

Steps to model the Component Diagram:
1. It contains set of components and their relationships.
2. Graphically render as a set of vertices and arcs.
3. The different components in the component diagram are view, view controller and DB
access.

Participant.
exe

Quiz.exe

interviewer
.exe

Scorer.exe

ASCET

EXP NO:

DATE:

Step 10: Deployment Diagram

Steps to model the Deployment Diagram:
1. It is a process of the nodes that lie on the system.
2. It contains nodes, interfaces and relationships.
3. Graphically render a set of vertices and arcs.

Interviewer.exe

Participation.ex
e

Scorer.exe

Result:-

ASCET

EXP NO:

DATE:

ONLINE BOOKSHOP
Aim:

To develop a model for Online book shopping.

Step 1: Problem Statement

1. The system must contain a Database such that maintains the transactions.
2. The user will log in by using the shopping card.
3. The administrator should maintain all the information about the books to be scheduled.
4. It should permit the user to have complete access.
5. It should update the items when ever the transaction had takes place.
6. The administrator should accept the credit card.
7. It will also keep track of shopping card.
8. The administrator should calculate the bill and give it to the user.
9. The customer should enter the valid pin.
10. Finally it will have to accept the money by giving books.

Step 2: Functional Requirements

1. User: Have complete access of the system as detailed below.
Browse: User will access to browse the product which he wants i.e. which book.
Register: User has to register all the details.
Place: Place the order form to the administrator.
View: User will view the shopping of books to purchase.
Pays: Customer will pay the bill by entering the credit card number.
Purchase: Finally the user purchases the book.
2. Administrator:
Displays: The books information will be displayed by the administrator.
Accept: Administrator will accept the order of the user.
Update: If any item selected then the availability of that item should be updated.
Calculate: Calculates the total amount and gives to the user.
Accept Credit card: Receiving bills through credit card also accepted.
Maintain: Administrator should maintains all the details and the bills.

ASCET

EXP NO:

DATE:

Step 3: Usecase Diagram

Identify the use cases of online book shopping.
Actors: Customer, administrator.
Use cases: Browse, Register, Place order, View shopping, Display, Accept order, Update items,
Calculate bill, Pay bill, Validate order, Accept credit card, Purchase new book.
Browse: Customer can search for the books through the browse option.
Register: Customer has to register the details of a book to place order.
Place order: order for a book will be placed.
View Shopping: Shopping can be viewed through the administrator.
Display: Displays the information of a particular book.
Accept order: Administrator will accept the order placed by the customer.
Update Items: If any change occurs to the books then they will be updated.
Calculate bill: The total amount to be paid by the customer will be calculated.
Validate order: It will checks whether the order is valid or not.
Pay bill: The bill should be paid to the administrator.
Accept Credit card: The administrator will accepts the credit card.
Purchase new book: A new book is purchased.

browse the product

register de tails

place order

vie w shopping

customer

display book info

administrator

acce pt orde r

update ite ms

< <include > >

cre ate /calculate

< <include > >

validate orde r

paybill
ente r cre dit card num
accept cre dit card

ASCET

purchase ne w book

EXP NO:

DATE:

Step 4: Class Diagram

Steps to model the Class diagram:
1. First type the class name in the name field of the class.
2. Add Operations:
Add the attributes to attributes in the attributes field Operations in the operations field of the
class.
Add types to the attributes.
Add signatures to the operations/methods.

online system
locate
date
time
validateCustomer()
bookDetails()
printReceipt()
validateOrder()

person
name
address
id
age
pinno

1
1

viewBooks()

1
*
bookstore
name
author
copies
cost
purchase()
newbook()
deletebook()

order
namebook
ety
bill
author

admin
updatebookdetails()
calculateBill()
placeBill()
collectBill()
mainteneceBill()

placeorder()
paybill()
*

*
atm
pinno
validatepin()

ASCET

customer
shoppingcard
creditcard

EXP NO:

DATE:

Step 5: Sequence Diagram

Steps to model the Sequence diagram:
1. First placing the objects that participate in the interaction at the top of the diagram across
the X-axis.
2. Place the objects that initiate the interaction at left and increasing more subordinates to
right.
3. Place the messages that these objects send and receive along the Y-axis in order of
increasing time from top to bottom.
4. Focus of control: It is a thin rectangle that shows the period of time during which an object
is performing an action.

:custome r

:databas e

:front pane l

:atm

:syste m
admin

1 : place shopping card

2 : validate custome r
3 : book de tails
4 : dis play books
5 : place orde r
6 : validate orde r
7 : place orde r
8 : calculate bill
9 : place bill
10 : dis play bill
11 : e nte r cre dit
12 : s e nd pin no & bill
13 : cre dit
14 : valid pin
15 : acce pt
16 : update books
17 : succe s sfull
18 : re ce ipt iss ue d
19 : clos e

ASCET

EXP NO:

DATE:

Step 6: Collaboration Diagram

Steps to model the Collaboration diagram:
1.
2.
3.
4.
5.

Place the object that participates in the interaction as the vertices in a graph.
Remember the links that connect these objects as arcs of the graph.
Finally, adorn the links with the messages that the object sends and receives.
Path: Path is needed to link the objects explicitly. For global, local parameters and self paths.
Sequence Number: It is used to indicate the time order of the message.

1: place shopping card

5: place order
11: enter credit
19: close

:custome
r

2: validate customer
6: validate order

:front
panel

:database
3: book details

18: receipt issued

10: display bill
4: display books
9: place bill
17: successfull

16: update books

12: send pin no & bill

7: place order
8: calculate bill

:system
admin

14: valid pin

13: credit
15: accept

ASCET

:atm

EXP NO:

DATE:

Step 7: Activity Diagram

Steps to model the Activity Diagram:
To Model Workflow:
1. Establish a focus for workflow.
2. Identify pre-conditions at initial state and post-conditions at final state.
3. Beginning at the workflow, show transitions connecting activities in active state.
To Model Operation:
1. Collect the abstractions that are involved in operations.
2. Identify the pre-conditions branching as necessary to specify conditional paths and
interactions.

S h o w s ho p p in g
d e ta ils
v a lid a te
C us to m e r

in v a lid

dis p la y
B o o k in fo
v a lid a te
c us to m e r
c a lc u la te
bill
p a y b ill

ASCET

E n te r C re d it
C a rd p in

U p d a te
A v a ila b ility

ATM
T ra n s a c tio n

P rin t
re c e ip t

EXP NO:

DATE:

Step 8: State Chart Diagram

Steps to model the State Chart Diagram:
1.
2.
3.
4.
5.

First select one state transition diagram.

Add states to the transition diagram.
Add documentation to states if needed.
Add activities to state chart diagram.
Add an entry action whenever we need in the state chart diagram, similarly exit action also
when needed.
6. Add transactions by dragging the transaction lines from source to target.
7. Add reflexive transaction whenever needed in the diagram.

activity
Ente r shopping
card
login

idle

validate
custome r
validate use r
take orde r from
custome r
R e que st
for bill

want to update
maintain

D isplay bill
to use r
ge t pinno
prompt for
cre dit card
proce ss cre dit
transactions
update book
availability
print re ce ipt for
the custome r

ASCET

EXP NO:

DATE:

Step 9: Component Diagram

Steps to model the Component Diagram:
1. It contains set of components and their relationships.
2. Graphically render as a set of vertices and arcs.
3. The different components in the component diagram are view, view controller and DB
access.

order.exe

ASCET

sales.exe

EXP NO:

DATE:

Step 10: Deployment Diagram

Steps to model the Deployment Diagram:
1. It is a process of the nodes that lie on the system.
2. It contains nodes, interfaces and relationships.
3. Graphically render a set of vertices and arcs.

Order client

Result:-

ASCET

sales server