DEPT

: CSE

TABLE OF CONTENTS

S.NO

DATE

NAME OF THE EXPERIMENT

INTRODUCTION TO RATIONAL ROSE SOFTWARE

ATM SYSTEM

ONLINE RESERVATION SYSTEM

ONLINE QUIZ SYSTEM

STOCK MAINTENANCE SYSTEM

STUDENT MARK ANALYSIS SYSTEM

COURSE REGISTRATION SYSTEM

PAYROLL SYSTEM

EXPERT SYSTEM

LIBRARY MANAGEMENT SYSTEM

10

REAL TIME SCHEDULER

11

REMOTE PROCEDURE CALL

12

ONLINE PURCHASE SYSTEM

MARKS SIGN

DEPT

: CSE

RATIONAL ROSE SOFTWARE

ANALYSIS AND DESIGN
The applications method recommends the use of static and dynamic views of a logical model and a
physical model to capture the in-process products of object-oriented analysis and design. Using the notation,
the application enables you to create and refine these views within an overall model representing your
problem domain and software system.
This overall model contains classes, use cases, objects, packages, operations, component packages,
components, processors, devices and the relationships between them. Each of these model elements
possesses model properties that identify and characterize them. The notation provides graphical icons to
represent each kind of model element and relationship.
A model also contains diagrams and specifications, which provide a means of visualizing and
manipulating the models elements and their model properties. Since diagrams are used to illustrate multiple
views of a model, icons representing a model element can appear in none, one, or several of a models
diagrams. The application therefore enables you to control, which element, relationship, and property icons
appear on each diagram, using facilities provided by its application window. Within its application window,
it displays each diagram in a diagram window, and each specification in a specification window.
USE CASE VIEW

Contains the use case models, flow of events and supplementary documentation.
It is a contract between customer and developer.
It is essential for analysis, design and test activities.
It also contains activity diagrams.
It contains the use case diagrams.
It is the heart of the other views that represent the required behaviour of the system.

LOGICAL VIEW

It supports the functional requirements of the system.

It includes the use case realization, class diagram, interaction diagram, state chart and activity
diagram.

PROCESS VIEW

It addresses the performance, scalability and throughput of the system.

It includes the threads and the processes that found the system concurrency and synchronization
mechanism.
It is not necessary for single processing environment.

COMPONENT VIEW

DEPT

The component view addresses the ease of development management of software assets, reuse,
subcontracting and of the shelf components.
Describes the organization of static software, like source call data files components in terms of
packaging, layering and configuration management.

DEPLOYMENT VIEW

: CSE

It addresses the issue like deployment installation and performance.

The deployment view is used for distributed systems only.
It shows the various executables like a runtime components and computing modes.
It contains deployment diagrams.

DEPT

: CSE

DEPT

10

: CSE

DEPT

: CSE

EX NO:
DATE:

ATM SYSTEM
AIM:
To analyze, design and develop code for Automated Teller Machine system using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

Processor: x86-based processor.

Hard disk: 20 GB (min)
RAM: 128 MB (min)

SOFTWARE REQUIREMENTS

Rational Rose Enterprise edition

Visual Basic 6.0

11

DEPT

12

: CSE

DEPT

: CSE

MODULAR DESCRIPTION
VERIFICATION OF ATM CARD
For the verification of ATM card by the system, the user will enter the secret code. The pin number or
code number is verified with the database of the customers. If the code exactly is matched with database of
that of the customers then transaction can be performed. If the code does not match with the database of the
customer then the user is requested again to re-enter the pin number of the access card and is continued
further.
TRANSACTION
In this module, the necessary transaction to be performed by the user is displayed as option by the system.
The transaction options are withdrawal, deposit, balance enquiry, mini statement, pin change. The users can
withdraw the amount from their account if the amount is available in their account. The users can also
deposit the amount in their account either by cash or cheque. This module helps the users to check their
balance in their account through balance enquiry and also they can get the mini statement for recent
transaction done over their account. This module allows the users to change their pin number if they need.
DISPLAY AND RECEIPT
In this module, after the user performs the transaction process the system displays the balance amount
available in the account and the amount withdrawn by the user through receipt. The receipt will be provided
at the end of the transaction process.

13

DEPT

14

: CSE

DEPT

USE CASE DIAGRAM:

CLASS DIAGRAM

15

: CSE

DEPT

SEQUENCE DIAGRAM

16

: CSE

DEPT

COLLABORATION DIAGRAM

17

: CSE

DEPT

ACTIVITY DIAGRAM

COMPONENT DIAGRAM:

18

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the ATM SYSTEM. Thus the
outcome of the project is efficient. The ATM system caters the varied requirements of the user to perform
various options.

19

DEPT

20

: CSE

DEPT

21

: CSE

DEPT

: CSE

EX NO:
DATE:

ONLINE RESERVATION SYSTEM

AIM:
To analyze, design and develop code for online reservation system using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

22

DEPT

23

: CSE

DEPT

: CSE

MODULAR DESCRIPTION
RESERVATION MODULE:
This module allows the user to reserve tickets for a particular train on a particular date if there is a
vacancy. The user can know about the vacancy details of the train through the enquiry module.
CANCELLATION MODULE:
This module allows the user to cancel the tickets to a train for a particular date through the reservation
officer (System). This module permits the user to know the status of the reserved ticket before and after
cancellation.
All these modules together prove to be a flexible Online Reservation System and it provides
complete flexibility and reliability to the end users and it assures the desired performance.

24

DEPT

25

: CSE

DEPT

USE CASE DIAGRAM

CLASS DIAGRAM

26

: CSE

DEPT

SEQUENCE DIAGRAM
(Ticket reservation)

27

: CSE

DEPT

SEQUENCE DIAGRAM
(Ticket cancellation)

28

: CSE

DEPT

COLLABORATION DIAGRAM
(Ticket Reservation)

COLLABORATION DIAGRAM
(Ticket Cancellation)

29

: CSE

DEPT

ACTIVITY DIAGRAM

COMPONENT DIAGRAM

30

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the ONLINE RESERVATION
SYSTEM. Thus the outcome of the project is efficient. The ONLINE RESERVATION SYSTEM caters the
varied requirements of the user to perform various options.

31

DEPT

32

: CSE

DEPT

33

: CSE

DEPT

EX NO:
DATE:

ONLINE QUIZ SYSTEM

AIM:
To analyze, design and develop code for online quiz system using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

34

: CSE

DEPT

MODULAR DESCRIPTION

35

: CSE

DEPT

: CSE

REGISTRATION MODULE:
This module enables the end users to register themselves to the online quiz competition through two-way
communication between the coordinator and the participant. This is the most important module as it
maintains the details of the participants in the database and it is the preliminary stage of the online quiz
system.
DISPLAY MODULE:
This module provides the user with the fields i.e. the questions for which they have to answer and it displays
the answers of those questions when required by the coordinator.
EVALUATION MODULE:
This module evaluates the answers that are given by the users i.e. the participants with that of the
corresponding answers in the database. Either they are correct or wrong, in both the cases the scores of the
corresponding participant or team will be updated accordingly.
ANNOUNCEMENT MODULE:
This module is used to display the results of the quiz competition irrespective of the status of the result and it
also displays the scores acquired by each participant or team at the end of the quiz competition.
All these modules together prove to be a flexible Online Quiz System and it provides complete flexibility
and reliability to the end users and it assures of the desired performance.

36

DEPT

USE CASE DIAGRAM

37

: CSE

DEPT

CLASS DIAGRAM

SEQUENCE DIAGRAM
(Log in)

38

: CSE

DEPT

SEQUENCE DIAGRAM
(Quiz)

39

: CSE

DEPT

COLLABORATION DIAGRAM
(login)

COLLABORATION DIAGRAM
(Quiz)

40

: CSE

DEPT

ACTIVITY DIAGRAM

COMPONENT DIAGRAM

41

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the ONLINE QUIZ
SYSTEM. Thus the outcome of the project is efficient. The ONLINE QUIZ SYSTEM caters the varied
requirements of the user to perform various options.

42

DEPT

43

: CSE

DEPT

44

: CSE

DEPT

: CSE

EX NO:
DATE:

STOCK MAINTENANCE SYSTEM

AIM:
To analyze, design and develop code for Stock Maintenance System using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

Visual C++ 6.0

45

DEPT

46

: CSE

DEPT

: CSE

MODULAR DESCRIPTION
ORDER MODULE:
This module is necessary to get the request from the customer for any product and also this module
communicates with the stock module to determine the availability of stock.
STOCK MODULE:
This module is the one, which is necessary to add information about all the items that are to be stocked. This
module provides the stock availability and also data required for new orders.

47

DEPT

48

: CSE

DEPT

USE CASE DIAGRAM:

CLASS DIAGRAM:

49

: CSE

DEPT

SEQUENCE DIAGRAM

COLLABORATIOIN DIAGRAM:
(Login)

50

: CSE

DEPT

ACTIVITY DIAGRAM:

COMPONENT DIAGRAM:

51

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the STOCK MAINTENANCE
SYSTEM. Thus the outcome of the project is efficient. The STOCK MAINTENANCE SYSTEM caters the
varied requirements of the user to perform various options.

52

DEPT

53

: CSE

DEPT

54

: CSE

DEPT

: CSE

EX NO:
DATE:

STUDENT MARK ANALYSIS SYSTEM

AIM:
To analyze, design and develop code for Student Mark Analysis system using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

Visual Basic 6.0

55

DEPT

56

: CSE

DEPT

: CSE

MODULAR DESCRIPTION
RECORD MARKS MODULE:
This module enables the authenticated users to record the marks and thereby their respective grades in a
database. This is the most important module as it maintains the details of the marks scored by the students in
the database and it is the first and the foremost step in this system.
VIEW GRADES MODULE:
This module permits the respective users to view their grades as and when necessary after their identification
through their login name and password. This module proves to be the simplest as it does not allow the user
to modify or update any information except viewing them.
UPDATE MARKS MODULE:
This module enables the authenticated users to update the marks of the students after each and every test in
order to update the data to the present existing grades of the students. This module just allows the user to
modify or update the grades of the students alone but not their personal details. This module does not allow
any user just like that only authenticated users are allowed to update the necessary data after their
identification through their login name and password.

57

DEPT

58

: CSE

DEPT

USE CASE DIAGRAM:

CLASS DIAGRAM:

59

: CSE

DEPT

SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

60

: CSE

DEPT

ACTIVITY DIAGRAM:

COMPONENT DIAGRAM:

61

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the STUDENT MARK
ANALYSIS SYSTEM. Thus the outcome of the project is efficient. The STUDENT MARK ANALYSIS
SYSTEM caters the varied requirements of the user to perform various options.

62

DEPT

63

: CSE

DEPT

64

: CSE

DEPT

: CSE

EX N O:
DATE:

COURSE REGISTRATION SYSTEM

AIM:
To analyze, design and develop code for Course registration System using Rational Rose software.
.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

Visual C++ 6.0

65

DEPT

66

: CSE

DEPT

: CSE

MODULAR DESCRIPTION
REGISTRATION MODULE:
This module enables a student to select a course from a given set of courses. It is this module that acts as an
interface between the student and the registrar.
MAINTENANCE MODULE:
This module is necessary to store all the information about the student to the database. This module also has
the provision to retrieve the data from the database system.

67

DEPT

68

: CSE

DEPT

USE CASE DIAGRAM:

.
CLASS DIAGRAM:

69

: CSE

DEPT

SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

70

: CSE

DEPT

ACTIVITY DIAGRAM:

COMPONENT DIAGRAM

71

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the COURSE
REGISTRATION SYSTEM. Thus the outcome of the project is efficient. The COURSE REGISTRATION
SYSTEM caters the varied requirements of the user to perform various options.

72

DEPT

73

: CSE

DEPT

74

: CSE

DEPT

EX NO:
DATE:

PAY ROLL SYSTEM

AIM:
To analyze, design and develop code for Payroll System using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

75

: CSE

DEPT

76

: CSE

DEPT

: CSE

MODULAR DESCRIPTION
ADD MODULE:
This module enables the manager to add new employees. This module is the most important one as this is
the basic prerequisite for a payroll system.
VIEW MODULE:
This module permits the manager to view the details of all the employees and their salaries. This module
also allows an employee to view his/her salary information.
EDIT MODULE:
This module enables the manager to edit the salary details of any employee. This module also has the ability
to enable the manager to remove an employee from the firm.

77

DEPT

78

: CSE

DEPT

USE CASE DIAGRAM:

CLASS DIAGRAM:

79

: CSE

DEPT

SEQUENCE DIAGRAM:
(General view)

SEQUENCE DIAGRAM:
(Specified view)

80

: CSE

DEPT

COLLABORATION DIAGRAM:
(General view)

COLLABORATION DIAGRAM:
(Specified view)

81

: CSE

DEPT

ACTIVITY DIAGRAM:

.
COMPONENT DIAGRAM:

82

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the PAYROLL SYSTEM.
Thus the outcome of the project is efficient. The PAYROLL SYSTEM caters the varied requirements of the
user to perform various options.

83

DEPT

EXPERT SYSTEM

84

: CSE

DEPT

85

: CSE

DEPT

Ex.No:
DATE:

EXPERT SYSTEM

AIM:
To analyze, design and develop code for Expert System using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

86

: CSE

DEPT

87

: CSE

DEPT

: CSE

MODULE DESCRIPTION
MODULE 1:

The user logs into the system with the user login id and password.
The connection is made with the EQ database where a random set of 10 questions along with
their choices are selected.
The questions are selected in such a way that the same set is not repeated for the same login
id.

MODULE 2:

Here, ten questions are displayed.

As the user chooses an option it is stored in EQ marks format for evaluation.

MODULE 3:

The marks that are stored in EQ marks are transferred to EQ system.

EQ system calculates the sum and displays it as Emotional Quotient.

MODULE 4:

The EQ value is connected to the EQ database in which the characteristic matching the EQ
value is displayed.

MODULE 5:

Again, the EQ value is compared with the database for displaying the users drawbacks and
ways of improvement.

MODULE 6:

If the user is interested then provide an interface for entering personal details with EQ for
future reference.
The details are stored in the EQ database and can be accessed only through entering the
correct password.

88

DEPT

89

: CSE

DEPT

USECASE DIAGRAM

Creation

Log-in
Administrator

User
Answer questions

Wait for inference

View marks

Personal Details

Maintenance

CLASS DIAGRAM

EQ Questions
selectques
choices

EQ Marks
selectedchoices

transfers

valuatechoices()

calculates
EQ System
choicevalue
sum1()

90

: CSE

DEPT

SEQUENCE DIAGRAM

EQSystem

User Interface
login

EQDatabase

verify username and password

pose question

select answer

update marks on database

calculate result

give EQresult

display EQ

COLLABORATION DIAGRAM

2: verify usernameand password

User
Interface

EQDatabase

5: updatemarks on database
6: calculateresult
1: login
3: posequestion
8: display EQ

4: select answer
7: giveEQresult

EQSystem

91

: CSE

DEPT

ACTIVITY DIAGRAM

Start the
application
Enter the username
and password

Verify username
and password

Enter into
system

Read the
question

Enter personal
details

Select the
answers

Viewpast
records

Submit answers
Save your
current EQ
Viewthe result

Save settings

Log out

92

: CSE

DEPT

COMPONENT DIAGRAM

Server

User

Expert UI

Printer

DBMS
Server

DEPLOYMENT DIAGRAM

Server

DBMS
Server

Get details

Get question

Printer
UI

Print result

93

: CSE

DEPT

: CSE

RESULT:

This project was carried out in a sequential manner to design and implement the EXPERT SYSTEM. Thus
the outcome of the project is efficient. The EXPERT SYSTEM caters the varied requirements of the user to
perform various options.

94

DEPT

: CSE

LIBRARY MANAGEMENT SYSTEM

95

DEPT

96

: CSE

DEPT

: CSE

Ex.No:
DATE:

LIBRARY MANAGEMENGT SYSTEM

AIM:
To analyze, design and develop code for Library Management System using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

97

DEPT

98

: CSE

DEPT

MODULE DESCRIPTION
MODULE 1
Provide a user interface for getting the users login details.

Verify login ID and if correct, provide access to the library database.

MODULE 2
Provide a search mechanism to search for a particular book.

Input the book name and the authors name.

MODULE 3
Get the book details from the database.

Display the book details on the screen.

MODULE 4
Allow the user to select the book for checking out.

Issue the book.

99

: CSE

DEPT

100

: CSE

DEPT

USE CASE DIAGRAM

Search book name

Select book name

Librarian

Student

Enter student login details

Issue the book

CLASS DIAGRAM

101

: CSE

DEPT

Software Entry

Data Entry

Querying

Name
Id no.
Book name
Author
DOI
DOR
Card no
Issue
Querying
Issue()
Return ()

DOI.
Renewal()
Issue()

SEQUENCE DIAGRAM

102

Return
Querying
Return()

: CSE

DEPT

Student

: CSE

library

Librarian

Administrator

Enter Login Details

Verify Authentication
Grant Permission/ Deny
Enter Login Details
Verify Authentication

Grant Permission/Deny
Enter Book name
Search the book

Enter author name

Check the book

Display results

COLLABORATION DIAGRAM

103

DEPT

: CSE

Librarian
Student

9: Enter author name

11: Issue the book
6: Grant Permission/Deny

1: Enter Login Details

3: Grant Permission/ Deny

4: Enter Login Details
7: Enter Book name

System

2: Verify Authentication
5: Verify Authentication
8: Search the book

ACTIVITY DIAGRAM

104

Administrator

DEPT

Enter login
name

Verify

Grant
permission

Enter book
name

Enter author
name

Display the
book

Check out the

book

105

: CSE

DEPT

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

Client
P roces s or

W eb S erver

106

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the LIBRARY
MANAGEMENT SYSTEM. Thus the outcome of the project is efficient. The LIBRARY
MANAGEMENT SYSTEM caters the varied requirements of the user to perform various options.

107

DEPT

REAL TIME SCHEDULER

108

: CSE

DEPT

Ex.No:

109

: CSE

DEPT

DATE:

REAL TIME SCHEDULER

AIM:
To analyze, design and develop code for Real Time Scheduler using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

110

: CSE

DEPT

111

: CSE

DEPT

MODULE DESCRIPTION
MODULE 1-GET USER DETAILS

Get the name, ID and Phone number of the user.

Get the password from the user.
Give options to either view the schedule of the user or to add a new schedule.

MODULE 2-VIEW SCHEDULE

In the view schedule window, display

o Appointment name
o Appointment time
o Appointment location

MODULE 3-ADD SCHEDULE

To add a schedule, the user must enter the name, time and location of the appointment.
The user should be alerted if the schedule is made after 5 PM.
If the user is busy at the selected time, he can reschedule.
The user can also delete an appointment using the delete option.

MODULE 4-RESCHEDULE

To reschedule, the user must first check whether he is free at the specified time or not.
If yes, he can proceed with the rescheduling process.
Otherwise, he must again check for an alternate time.

MODULE 5

The user must finally be informed that his schedule has been successfully created.

112

: CSE

DEPT

USE CASE DIAGRAM

113

: CSE

DEPT

V ie w S c h e d ule

A d d S c h e d u le

D e le t e S c h e d u le
P e rs o n _ D e ta ils

S y s te m
R e s c h ed u le

C h e c k A va ila b ilit y

CLASS DIAGRAM

P ers on
P ers on_N am e
P ers on_ID
P hone_N o
P as s w ord
V iew S c hedule()
E ditS c hedule()

m ak es

S c hedule
A c tivity
Tim e
Loc ation
D eleteS c hedule()
R es c hedule()

114

needs

A vailability
N ew_tim e
N ew_loc ation
C hec k A vailability ()

: CSE

DEPT

SEQUENCE DIAGRAM

Person

Appointment
Control

Appointment

View schedule

Add appointment

Check availability
If yes, create appointment

No

Reschedule
Confirm appointment

115

: CSE

DEPT

COLLABORATION DIAGRAM

1: View schedule
2: Add appointment
Person

Appointment Control

5: No

4: If yes, create appointment

3: Check availability
6: Reschedule
7: Confirm appointment

Appointment

ACTIVITY DIAGRAM

Enter details

ViewSchedule

Add
appointment

Available?

Yes

no
Reschedule
appointment

Confirm
schedule

116

: CSE

DEPT

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

Client
Processor

Web Server

117

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the REAL TIME
SCHEDULER. Thus the outcome of the project is efficient. The REAL TIME SCHEDULER caters the
varied requirements of the user to perform various options.

118

DEPT

: CSE

REMOTE PROCEDURE CALL

119

DEPT

120

: CSE

DEPT

Ex.No:
DATE:

REMOTE PROCEDURE CALL

AIM:
To analyze, design and develop code for Remote Procedure Call using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS

X86 based processor

RAM (128 MB min)
Hard Disc (40 GB)

SOFTWARE REQUIREMENTS

Rational Rose Software

121

: CSE

DEPT

122

: CSE

DEPT

: CSE

MODULE DESCRIPTION
MODULE 1

Create an account for each customer.

Customer has to log in using user name and password.

MODULE 2

Prepare the order.

Provide each customer with the shopping cart containing all the items that the customer wants to buy.
Give them access to all the details about different types of computers that is available in the store.

MODULE 3

Provide order form and let the customer to fill out payment and shipping details.
Store the order in database.
Review the order and check whether the items are available.
Email the order details to the customers email id.

MODULE 4

Send information to the warehouse to start shipping process.

Print the invoice.
Accept customer payment.

123

DEPT

124

: CSE

DEPT

: CSE

USE CASE DIAGRAM

Dis play s tandard c om puter config

B uild com puter c onfig

Order c onfigured c om puter

c us tom er
Request s alespers on c ontac t

Inform warehouse about order

warehouse
Upd ate orde r s tat us

P rint invo ic e

Verify and ac c ep t cus tom er

pay m ent

125

S alesperson

DEPT

CLASS

: CSE

DIAGRAM
Customer
name
address
ph no
email
get order()

Configuration
item type
item descp
Invoice
number
date
total

Order
od num
date
address
total
status
sales pname

SEQUENCE

Payment
payment method
date received
amt received

DIAGRAM

126

DEPT

Customer

Config window

Order

Order window

: CSE

Payment

Open new
Accept config

Prepare for order

Display order

Submit order
St ore order
Link customer
Link payment

COLLABORATION DIAGRAM

3: Prepare for orde r

Config
wi ndow

4: Display order
Order

Orde r
wi ndow
6: Store order

5: Submit order
1: Open new
2: Accep t c onfig

7: Link customer
Payment

Custome r

127

8: Link payment

DEPT

ACTIVITYDIAGRAM

Display current
config

Get order
request

Dispaly
purchase form
[time out]
[incomplete]
Get purchase
details

Store order
[OK]

Email order
details

COMPONENT DIAGRAM

Customer

Online
shopping

Order

128

: CSE

DEPT

DEPLOYMENT DIAGRAM

Client
Processor

Web Server

129

: CSE

DEPT

: CSE

RESULT:
This project was carried out in a sequential manner to design and implement the REMOTE PROCEDURE
CALL. Thus the outcome of the project is efficient. The REMOTE PROCEDURE CALL caters the varied
requirements of the user to perform various options.

Content Beyond Syllabus

ONLINE PURCHASE SYSTEM

1. ANALYSIS
1.1 Identifying the Actors
1.2 Identifying the Use Cases
2. REQUIREMENTS
2.1 System Requirements
2.2 Software Requirements
3. DESIGN
3.1 Use Case Diagram
3.2 Class Diagram
3.3 Sequence Diagram

130

DEPT

3.4 Collaboration Diagram

3.5 Activity Diagram
3.6 State Diagram

ONLINE PURCHASE USE CASE DIAGRAM

131

: CSE

DEPT

: CSE

OnlineP urch ase

Brow se Ca tlog

S e le ct Ite m

S oftw are
C ustomer

Re que st Ite m

Ask for P a ym e nt &

S hipping de ta ils

Issue De ta ils

Issue
Authoriz a tion

B anking
Che ck for
va lidity

De lie ve r Goods

D ealer

ONLINE PURCHASE CLASS DIAGRAM

132

DEPT

C u s to m e r

S h o p p in g C a r d

A tt r i b u te s

A ttr i b u te s

p riva t e
p riva t e
p riva t e
p riva t e
p riva t e

p u b lic flo a t s u b to t a l
p u b lic flo a t s a le s m o n e y
p u b lic flo a t t o ta lm o n e y
O p e r a ti o n s

p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic
p u b lic

: CSE

s t rin g a d d rt o s h ip
s t rin g n a m e
s t rin g a d d rt o b ill
s t rin g e m a ila d d
in t c re d it ra t in g

S h o p p in g C a rd ()
O p e r a ti o n s
flo a t g e t S u b t o t a l()
p u b lic C u s t o m e r()
vo id s e tS u b to t a l(flo a t va l )
p u b lic s t rin g g e t A d d rt o s h ip ()
flo a t g e t S a le s m o n e y ()
p u b lic vo id s e t A d d rto s h ip (s t rin g va l )
m C u s to m e r
vo id s e tS a le s m o n e y (flo a t va l )
p u b lic s t rin g g e t N a m e ()
flo a t g e t T o t a lm o n e y ()
1
*
p u b lic vo id s e t N a m e (s t rin g va l )
vo id s e tT o t a lm o n e y (flo a t va l )
p u b lic s t rin g g e t A d d rt o b ill()
vo id p la c e O rd e r()
p u b lic vo id s e t A d d rto b ill(s t rin g va l )
vo id re m o ve O rd e r()
p u b lic s t rin g g e t E m a ila d d ()
C u s to m e rvo id [ 0 . .* ] g e t C u s to m e r()
p u b lic vo id s e t E m a ila d d (s t rin g va l )
vo id s e tC u s to m e r(C u s to m e r va l[ 0 . .* ] )
p u b lic in t g e t C re d it ra t in g ()
C re d itC a rd vo id [0 . . * ] g e t C re d it C a rd ()
p u b lic vo id s e t C re d it ra t in g (in t va l )
m C u s to m e r
vo id s e tC re d it C a rd (C rd e it C a rd va l[ 0 . .* ] )
p u b lic vo id d is p la y C a t e g o ry ()
C u s to m e r[0 . .* ] g e t C u s t o m e r()
p u b lic vo id s e le c t Ite m ()
vo id s e tC u s to m e r(C u s to m e r va l[ 0 . .* ] )
p u b lic vo id d e lie ve rIte m ()
C re d itC a rd [ 0 .. *] g e tC re d itC a 1rd ()
p u b lic vo id re m o ve O rd e r()
vo id s e tC re d it C a rd (C re d it C a rd va l[ 0 . .* ] )
1
m C r e d itC a r d

C re d itC a r d

O p e r a ti o n s

Ite m O fP u rc h a s e

p u b lic
A ttr ib u te s
p u b lic
p riva te in t q u a n tit y
p u b lic
p riva te flo a t p ric e p e rit e m
p u b lic
O p e r a ti o n s
p u b lic
p u b lic It e m O fP u rc h a s e ()
p u b lic
p u b lic in t g e tQ u a n tity ()
p u b lic
p u b lic vo id s e t Q u a n tit y (in t va l )
p u b lic
p u b lic flo a t g e tP ric e p e rit e m ()
p u b lic
p u b lic vo id s e t P ric e p e rite m (flo a t va l p) u b lic
p u b lic C u s t o m e r fe t C u s t o m e r()
p u b lic
p u b lic vo id s e t C u s to m e r(C u s to m e r va
p ul b) lic
p u b lic P ro d u c t[ 0 . . * ] g e tP ro d u c t ()
p u b lic
p u b lic vo id s e t P ro d u c t(P ro d u c t va l[ 0p. .*u b] lic
)
p u b lic P ro d u c t[ 0 . . * ] g e tP ro d u c t ()
p u b lic
p u b lic vo id s e t P ro d u c t(P ro d u c t va l[ 0 . .* ] )

P r e ffe r e d C u s to m e r

C re d itC a rd ()
A ttr i b u te s
in t g e tN u m b e r()
p riva t e in t d is c o u n t ra t e
vo id s e tN u m b e r(in t va l )
O p e r a ti o n s
d a te g e t E x p iry d a t e ()
m Pr e f f e r e d C u s to pm ue br lic P re ffe re d C u s t o m e r()
vo id s e tE x p iry d a te (d a t e va l )
p u b lic in t g e t D is c o u n t ra t e ()
b o o le a n g e t Is s u e ()
p u b lic vo id s e t D is c o u n t ra te (in t va l )
1
vo id s e tIs s u e (b o o le a n va l )
*
p u b lic C u s t o m e r g e t C u s to m e r()
vo id a u th o riz e C h a rg e ()
p u b lic vo id s e t C u s t o m e r(C u s to m e r va l )
P re ffe re d ()
p u b lic C u s t o m e r g e t C u s to m e r1 ()
It e m O fP u rc h a s e g e t It e m O fP u rc h a s e ()
p u b lic vo id s e t C u s o t m e r1 (C u s t o m e r va l )
vo id s e tIt e m O fP u rc h a s e (Ite m O fP u rc h a s e va l )
p u b lic C u s t o m e r g e t C u s to m e r()
P re ffe re d C u s t o m e r[0 . . *] g e tP re ffe rre d C u s to m e r()
p u b lic vo id s e t C u s t o m e r(C u s to m e r va l )
vo id s e tP re ffe rre d C u s t o m e r(P re ffe re d C u s t o m e r va l[ 0 .. *] )
P re ffe re d C u s t o m e r[0 . . *] g e tP re ffe re d C u s t o m e r()
vo id s e tP re ffe re d C u s t o m e r(P re ffe re d C u s t o m e r va l[0 . .* ] )

m Pr o d u c t
1

P ro d u c t
A ttr i b u te s
O p e r a ti o n s

p u b lic P ro d u c t ()

ONLINE PURCHASE SEQUENCE DIAGRAM

133

DEPT

: Shoppingcart

: creditcard

: Customer
public void browsecatalog()

public void displaycatalog()

public void selectItem()

public void getCreditRating()

public void getAddrToShop()

public void setCreditCard()

public void shipmentDetails()

public void authorizedCharge()

public void getExpiryDate()

validation

public void authorize()

public void setCrediting(int val )

public void setAddrToShip()

public void deleverItem()

public void rejected()
public void removeOrder()

134

: CSE

DEPT

ONLINE PURCHASE COLLABORATION DIAGRAM

: Customer
public void setAddrToShip()
public void browsecatalog()

public void deleverItem()

public void getCreditRating()

public void shipmentDetails()

public void getAddrToShop()

public void displaycatalog()

public void selectItem()

public void removeOrder()

public void setCreditCard()

public void setCrediting(int val )

: Shoppingcart
public void rejected()

public void authorize()

public void authorizedCharge()

: creditcard

public void getExpiryDate()

135

: CSE

DEPT

ONLINE PURCHASE ACTIVITY DIAGRAM

OnlinePurchase
Customer

Shoppingcart

Creditcard

Unnamed

Browse
Catlog

Displaying
Catlog

{ From OP_Activity }

{ From OP_Activity }

Selecting
Catlog

Displaying ....

{ From OP_Activ...

{ From OP_Activity }

Selecting &

Requesting

Validating
credit

{ From OP_Activit...

{ From OP_Activity }

{ From OP_Activity }

Issuing
payment

Accepting
delivery

{ From OP_Activity }

{ From OP_Activity }

Unnamed

Delievering
Item

Authorized

{ From OP_Activity }

{ From OP_Activity }

Rejected
{ From OP_Activity }
Unnamed

136

: CSE

DEPT

ONLINE PURCHASE STATECHART DIAGRAM

CHECKING

PROCESS
DELIVERY

WAITING

DISPATCH

CANCELLING

EXIT

137

: CSE

DEPT

: CSE

RESULT:This project was carried out in a sequential manner to design and implement the ONLINE PURCHASE
SYSTEM. Thus the outcome of the project is efficient. The ONLINE PURCHASE SYSTEM caters the
varied requirements of the user to perform various options.

138