Beruflich Dokumente
Kultur Dokumente
P Institute of Technology
Tiruvannamalai 606611.
DEPT
: CSE
PREPARED
BY
N.GOPINATH
AP/CSE
NAME
REG.NO
DEPT
SEM
SUB CODE/NAME
DEPT
: CSE
DEPT
: CSE
TABLE OF CONTENTS
S.NO
DATE
ATM SYSTEM
PAYROLL SYSTEM
EXPERT SYSTEM
10
11
12
MARKS SIGN
Roll.NO
REG NO
Roll.NO
Batch - II
REG NO
52909104001
21
52909104021
52909104002
22
52909104022
52909104003
23
52909104023
52909104004
24
52909104024
52909104005
25
52909104025
52909104006
26
52909104026
52909104007
27
52909104027
52909104008
28
52909104028
52909104009
29
52909104029
10
52909104010
30
52909104030
11
52909104011
31
52909104031
12
52909104012
32
52909104032
13
52909104013
33
52909104033
14
52909104014
34
52909104034
15
52909104015
35
52909104035
16
52909104016
36
52909104036
17
52909104017
37
52909104037
18
52909104018
38
52909104301
19
52909104019
20
52909104020
39
52909104302
DEPT
: CSE
DEPT
: CSE
DATES
Roll.NO
20.12.2011
1to20
20.12.2011
1to20
ATM SYSTEM
27.12.2011
1to20
03.01.2012
1to20
10.01.2012
1to20
24.01.2012
1to20
31.01.2012
1to20
07.02.2012
1to20
PAYROLL SYSTEM
14.02.2012
1to20
EXPERT SYSTEM
14.02.2012
1to20
21.02.2012
1to20
21.02.2012
1to20
28.02.2012
1to20
DEPT
: CSE
DATES
Roll.NO
23.12.2011
21to39
23.12.2011
21to39
ATM SYSTEM
30.12.2011
21to39
06.01.2012
21to39
20.01.2012
21to39
27.01.2012
21to39
03.02.2012
21to39
10.02.2012
21to39
PAYROLL SYSTEM
10.02.2012
21to39
EXPERT SYSTEM
17.02.2012
21to39
24.02.2012
21to39
02.03.2012
21to39
09.03.2012
21to39
DEPT
: CSE
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
PROCESS VIEW
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
DEPT
: CSE
10
DEPT
: 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
SOFTWARE REQUIREMENTS
11
12
DEPT
: 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
14
DEPT
: CSE
CLASS DIAGRAM
15
DEPT
: CSE
16
DEPT
: CSE
17
DEPT
: CSE
COMPONENT DIAGRAM:
18
DEPT
: 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
20
DEPT
: CSE
21
DEPT
: CSE
DEPT
: CSE
EX NO:
DATE:
SOFTWARE REQUIREMENTS
22
23
DEPT
: 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
25
DEPT
: CSE
CLASS DIAGRAM
26
DEPT
: CSE
27
DEPT
: CSE
28
DEPT
: CSE
COLLABORATION DIAGRAM
(Ticket Cancellation)
29
DEPT
: CSE
COMPONENT DIAGRAM
30
DEPT
: 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
32
DEPT
: CSE
33
DEPT
: CSE
DEPT
EX NO:
DATE:
SOFTWARE REQUIREMENTS
34
: CSE
MODULAR DESCRIPTION
35
DEPT
: 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
37
DEPT
: CSE
CLASS DIAGRAM
SEQUENCE DIAGRAM
(Log in)
38
DEPT
: CSE
SEQUENCE DIAGRAM
(Quiz)
39
DEPT
: CSE
COLLABORATION DIAGRAM
(login)
COLLABORATION DIAGRAM
(Quiz)
40
DEPT
: CSE
ACTIVITY DIAGRAM
COMPONENT DIAGRAM
41
DEPT
: 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
43
DEPT
: CSE
44
DEPT
: CSE
DEPT
: CSE
EX NO:
DATE:
AIM:
To analyze, design and develop code for Stock Maintenance System using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS
SOFTWARE REQUIREMENTS
45
46
DEPT
: 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
48
DEPT
: CSE
CLASS DIAGRAM:
49
DEPT
: CSE
SEQUENCE DIAGRAM
COLLABORATIOIN DIAGRAM:
(Login)
50
DEPT
: CSE
COMPONENT DIAGRAM:
51
DEPT
: 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
53
DEPT
: CSE
54
DEPT
: CSE
DEPT
: CSE
EX NO:
DATE:
AIM:
To analyze, design and develop code for Student Mark Analysis system using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS
SOFTWARE REQUIREMENTS
55
56
DEPT
: 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
58
DEPT
: CSE
CLASS DIAGRAM:
59
DEPT
: CSE
COLLABORATION DIAGRAM:
60
DEPT
: CSE
COMPONENT DIAGRAM:
61
DEPT
: 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
63
DEPT
: CSE
64
DEPT
: CSE
DEPT
: CSE
EX N O:
DATE:
AIM:
To analyze, design and develop code for Course registration System using Rational Rose software.
.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS
SOFTWARE REQUIREMENTS
65
66
DEPT
: 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
68
DEPT
: CSE
.
CLASS DIAGRAM:
69
DEPT
: CSE
COLLABORATION DIAGRAM:
70
DEPT
: CSE
COMPONENT DIAGRAM
71
DEPT
: 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
73
DEPT
: CSE
74
DEPT
: CSE
EX NO:
DATE:
AIM:
To analyze, design and develop code for Payroll System using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS
SOFTWARE REQUIREMENTS
75
DEPT
: CSE
76
DEPT
: 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
78
DEPT
: CSE
CLASS DIAGRAM:
79
DEPT
: CSE
SEQUENCE DIAGRAM:
(Specified view)
80
DEPT
: CSE
COLLABORATION DIAGRAM:
(Specified view)
81
DEPT
: CSE
.
COMPONENT DIAGRAM:
82
DEPT
: 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
85
DEPT
: CSE
Ex.No:
DATE:
EXPERT SYSTEM
AIM:
To analyze, design and develop code for Expert System using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS
SOFTWARE REQUIREMENTS
86
DEPT
: CSE
87
DEPT
: 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:
MODULE 3:
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
89
DEPT
: CSE
Creation
Log-in
Administrator
User
Answer questions
View marks
Personal Details
Maintenance
CLASS DIAGRAM
EQ Questions
selectques
choices
EQ Marks
selectedchoices
transfers
valuatechoices()
calculates
EQ System
choicevalue
sum1()
90
DEPT
: CSE
DEPT
SEQUENCE DIAGRAM
EQSystem
User Interface
login
EQDatabase
pose question
select answer
calculate result
give EQresult
display EQ
COLLABORATION DIAGRAM
EQDatabase
5: updatemarks on database
6: calculateresult
1: login
3: posequestion
8: display EQ
4: select answer
7: giveEQresult
EQSystem
91
: CSE
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
DEPT
: 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
95
96
DEPT
: CSE
DEPT
: CSE
Ex.No:
DATE:
AIM:
To analyze, design and develop code for Library Management System using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS
SOFTWARE REQUIREMENTS
97
98
DEPT
: CSE
MODULE DESCRIPTION
MODULE 1
Provide a user interface for getting the users login details.
MODULE 2
Provide a search mechanism to search for a particular book.
MODULE 3
Get the book details from the database.
MODULE 4
Allow the user to select the book for checking out.
99
DEPT
: CSE
100
DEPT
: CSE
DEPT
Student
CLASS DIAGRAM
101
: CSE
DEPT
Software Entry
Data Entry
Querying
Name
Id no.
Book name
Author
DOI
DOR
Card no
Issue()
Return ()
Issue
Querying
DOI.
Renewal()
Issue()
SEQUENCE DIAGRAM
102
Return
Querying
Return()
: CSE
Student
DEPT
: CSE
library
Librarian
Administrator
Grant Permission/Deny
Enter Book name
Search the book
COLLABORATION DIAGRAM
103
DEPT
: CSE
Librarian
Student
System
2: Verify Authentication
5: Verify Authentication
8: Search the book
ACTIVITY DIAGRAM
104
Administrator
Enter login
name
Verify
Grant
permission
Enter book
name
Enter author
name
Display the
book
105
DEPT
: CSE
DEPLOYMENT DIAGRAM
Client
P roces s or
W eb S erver
106
DEPT
: 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
108
: CSE
Ex.No:
109
DEPT
: CSE
DEPT
DATE:
AIM:
To analyze, design and develop code for Real Time Scheduler using Rational Rose software.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS
SOFTWARE REQUIREMENTS
110
: CSE
111
DEPT
: CSE
DEPT
MODULE DESCRIPTION
MODULE 1-GET USER DETAILS
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
: 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
Person
Appointment
Control
Appointment
View schedule
Add appointment
Check availability
If yes, create appointment
No
Reschedule
Confirm appointment
115
DEPT
: CSE
1: View schedule
2: Add appointment
Person
Appointment Control
5: No
3: Check availability
6: Reschedule
7: Confirm appointment
Appointment
ACTIVITY DIAGRAM
Enter details
ViewSchedule
Add
appointment
Available?
Yes
no
Reschedule
appointment
Confirm
schedule
116
DEPT
: CSE
DEPLOYMENT DIAGRAM
Client
Processor
Web Server
117
DEPT
: 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
119
120
DEPT
: CSE
DEPT
Ex.No:
DATE:
SOFTWARE REQUIREMENTS
121
: CSE
122
DEPT
: CSE
DEPT
: CSE
MODULE DESCRIPTION
MODULE 1
MODULE 2
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
123
124
DEPT
: CSE
DEPT
: CSE
c us tom er
Request s alespers on c ontac t
warehouse
Upd ate orde r s tat us
P rint invo ic e
125
S alesperson
CLASS
DEPT
: 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
Config window
Order
DEPT
Order window
: CSE
Payment
Open new
Accept config
Display order
Submit order
St ore order
Link customer
Link payment
COLLABORATION DIAGRAM
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
DEPLOYMENT DIAGRAM
Client
Processor
Web Server
129
DEPT
: 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.
130
131
DEPT
: CSE
DEPT
: CSE
Brow se Ca tlog
S e le ct Ite m
S oftw are
C ustomer
Re que st Ite m
Issue De ta ils
Issue
Authoriz a tion
B anking
Che ck for
va lidity
De lie ve r Goods
D ealer
132
: CSE
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
DEPT
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 ()
133
DEPT
: creditcard
: Customer
public void browsecatalog()
validation
134
: CSE
DEPT
: Customer
public void setAddrToShip()
public void browsecatalog()
: Shoppingcart
public void rejected()
: creditcard
135
: CSE
DEPT
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
CHECKING
PROCESS
DELIVERY
WAITING
DISPATCH
CANCELLING
EXIT
137
DEPT
: 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