Академический Документы
Профессиональный Документы
Культура Документы
DEPT
: CSE
CS2357- OBJECT ORIENTED ANALYSIS AND DESIGN LAB MANUAL (III Year CSE)
DEPT
: CSE
: : : : :
DEPT
: CSE
TABLE OF CONTENTS
S.NO
DATE
MARKS SIGN
1 2 3 4 5
6 7 8 9 10 11 12
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 REAL TIME SCHEDULER REMOTE PROCEDURE CALL ONLINE PURCHASE SYSTEM
DEPT
: CSE
Roll.NO
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
REG NO 52909104001 52909104002 52909104003 52909104004 52909104005 52909104006 52909104007 52909104008 52909104009 52909104010 52909104011 52909104012 52909104013 52909104014 52909104015 52909104016 52909104017 52909104018 52909104019 52909104020
Roll.NO
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
DEPT
: CSE
DATES
20.12.2011 20.12.2011 27.12.2011 03.01.2012 10.01.2012 24.01.2012 31.01.2012 07.02.2012 14.02.2012 14.02.2012 21.02.2012 21.02.2012 28.02.2012
Roll.NO 1to20 1to20 1to20 1to20 1to20 1to20 1to20 1to20 1to20 1to20 1to20 1to20 1to20
EXERCISE FOR BATCHES 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 REAL TIME SCHEDULER REMOTE PROCEDURE CALL ONLINE PURCHASE SYSTEM
DEPT
: CSE
DATES 23.12.2011 23.12.2011 30.12.2011 06.01.2012 20.01.2012 27.01.2012 03.02.2012 10.02.2012 10.02.2012 17.02.2012 24.02.2012 02.03.2012 09.03.2012
Roll.NO 21to39 21to39 21to39 21to39 21to39 21to39 21to39 21to39 21to39 21to39 21to39 21to39 21to39
EXERCISE FOR BATCHES 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 REAL TIME SCHEDULER REMOTE PROCEDURE CALL ONLINE PURCHASE SYSTEM
DEPT
: CSE
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
: CSE
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 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
: CSE
10
DEPT
: CSE
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)
11
DEPT
: CSE
12
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
: CSE
14
DEPT
: CSE
CLASS DIAGRAM
15
DEPT
: CSE
16
DEPT
: CSE
17
DEPT
: CSE
COMPONENT DIAGRAM:
18
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
: CSE
20
DEPT
: CSE
21
DEPT
: CSE
22
DEPT
: CSE
23
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
: CSE
25
DEPT
: CSE
CLASS DIAGRAM
26
DEPT
: CSE
27
DEPT
: CSE
28
DEPT
: CSE
29
DEPT
: CSE
COMPONENT DIAGRAM
30
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
: CSE
32
DEPT
: CSE
33
DEPT
: CSE
34
DEPT
: CSE
MODULAR DESCRIPTION
35
DEPT
: CSE
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
: CSE
37
DEPT
: CSE
CLASS DIAGRAM
38
DEPT
: CSE
39
DEPT
: CSE
40
DEPT
: CSE
ACTIVITY DIAGRAM
COMPONENT DIAGRAM
41
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
: CSE
43
DEPT
: CSE
44
DEPT
: CSE
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)
45
DEPT
: CSE
46
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
: CSE
48
DEPT
: CSE
CLASS DIAGRAM:
49
DEPT
: CSE
SEQUENCE DIAGRAM
50
DEPT
: CSE
COMPONENT DIAGRAM:
51
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
: CSE
53
DEPT
: CSE
54
DEPT
: CSE
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)
55
DEPT
: CSE
56
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
: CSE
58
DEPT
: CSE
CLASS DIAGRAM:
59
DEPT
: CSE
COLLABORATION DIAGRAM:
60
DEPT
: CSE
COMPONENT DIAGRAM:
61
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
: CSE
63
DEPT
: CSE
64
DEPT
: CSE
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)
65
DEPT
: CSE
66
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
: CSE
68
DEPT
: CSE
. CLASS DIAGRAM:
69
DEPT
: CSE
COLLABORATION DIAGRAM:
70
DEPT
: CSE
COMPONENT DIAGRAM
71
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
: CSE
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 X86 based processor RAM (128 MB min) Hard Disc (40 GB)
75
DEPT
: CSE
76
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
: CSE
78
DEPT
: CSE
CLASS DIAGRAM:
79
DEPT
: CSE
80
DEPT
: CSE
81
DEPT
: CSE
. COMPONENT DIAGRAM:
82
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
: CSE
EXPERT SYSTEM
84
DEPT
: 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 X86 based processor RAM (128 MB min) Hard Disc (40 GB)
86
DEPT
: CSE
87
DEPT
: CSE
MODULE DESCRIPTION MODULE 1: MODULE 2: MODULE 3: MODULE 4: MODULE 5: 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. Again, the EQ value is compared with the database for displaying the users drawbacks and ways of improvement. The EQ value is connected to the EQ database in which the characteristic matching the EQ value is displayed. The marks that are stored in EQ marks are transferred to EQ system. EQ system calculates the sum and displays it as Emotional Quotient. Here, ten questions are displayed. As the user chooses an option it is stored in EQ marks format for evaluation. 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.
88
DEPT
: CSE
89
DEPT
: CSE
Creation
View marks
Personal Details
Maintenance
CLASS DIAGRAM
EQ Marks selectedchoices valuatechoices()
transfers
90
DEPT
: CSE
E S Q yste m lo in g
U r In rfa se te ce
E D ta a Q a b se
v rify u rn m a p ssw rd e se a e nd a o
p se q e n o u stio
se ct a sw r le n e
u d te m rks o d ta a pa a n a b se
ca la re lt lcu te su
g e EQre lt iv su
d la E isp y Q
COLLABORATION DIAGRAM
2 v rify u e a ea d p s o : e s rn m n a sw rd U r se In r ce tefa E D ta a e Q a bs
E S te Q ys m
91
DEPT
: CSE
V rify u rn m e se a e a d p ssw rd n a o
E te in n r to syste m
E te p rso a n r e nl d ta e ils
R a th ed e qe n u stio S le th e ct e a sw rs n e
V wp st ie a re rd co s
S b it a sw rs um n e S v yo r ae u cu n E rre t Q V wth re lt ie e su
S v se g a e ttin s
L go t o u
92
DEPT
: CSE
COMPONENT DIAGRAM
Server
User
Expert UI
Printer
DBMS Server
DEPLOYMENT DIAGRAM
Server
Get details
DBMS Server
Get question
93
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
DEPT
: CSE
96
DEPT
: CSE
Ex.No: DATE:
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)
97
DEPT
: CSE
98
DEPT
: CSE
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
DEPT
: CSE
100
DEPT
: CSE
CLASS DIAGRAM
101
DEPT
: CSE
Software Entry
Data Entry Name Id no. Book name Author DOI DOR Card no Issue Querying DOI. Renewal() Issue()
Querying
Issue() Return ()
SEQUENCE DIAGRAM
102
DEPT
: CSE
Student
Librarian
library Administrator
Enter Login Details Verify Authentication Grant Permission/ Deny Enter Login Details Verify Authentication
COLLABORATION DIAGRAM
103
DEPT
: CSE
Librarian Student
9: Enter author name 11: Issue the book 1: Enter Login Details 6: Grant Permission/Deny
3: 4: Enter Login Details Grant Permission/ Deny 7: Enter Book name 2: Verify Authentication 5: Verify Authentication 8: Search the book
System
Administrator
ACTIVITY DIAGRAM
104
DEPT
: CSE
Verify
Grant permission
105
DEPT
: CSE
DEPLOYMENT DIAGRAM
Client P roces s or
W eb S erver
106
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
: CSE
108
DEPT
: CSE
Ex.No:
109
DEPT
: CSE
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)
110
DEPT
: CSE
111
DEPT
: CSE
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
DEPT
: CSE
DEPT
: CSE
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 R e s c h ed u le
S y s te m
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
needs
114
DEPT
: CSE
Person
Appointment Control
Appointment
View schedule
Add appointment
No
115
DEPT
: CSE
5: No
Appointment
ACTIVITY DIAGRAM
E te d ta n r e ils
V wS e u ie ch d le
Ad d a p in e t p o tm n
Ys e
Aa b ? v ila le
n o R sch d le e eu a p in e t p o tm n
Cn o firm sch d le eu
116
DEPT
: CSE
DEPLOYMENT DIAGRAM
Client Processor
Web Server
117
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
DEPT
: CSE
120
DEPT
: CSE
Ex.No: DATE:
121
DEPT
: CSE
122
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
: CSE
124
DEPT
: CSE
P rint invo ic e
125
DEPT
: CSE
CLASS
DIAGRAM
Customer name address ph no email get order() Inv oice num ber date total Order od num date address total status sales pname Configuration item type item descp
SEQUENCE
DIAGRAM
126
DEPT
: CSE
Payment
COLLABORATION DIAGRAM
8: Link payment
Custome r
127
DEPT
: CSE
Gto e e rd r re u st qe
S re o e to rd r
E a o e m il rd r d ta e ils
COMPONENT DIAGRAM
Customer
Online shopping
Order
128
DEPT
: CSE
DEPLOYMENT DIAGRAM
Client Processor
Web Server
129
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
DEPT
: CSE
131
DEPT
: CSE
Brow se Ca tlog
S e le ct Ite m
Issue De ta ils
B anking
Che ck for va lidity
De lie ve r Goods
D ealer
132
DEPT
: CSE
C u s to m e r
A tt r i b u te 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
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 1 () rd 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 1
C re d itC a r d
O p e r a ti o n s
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 vau b lic pl) 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.* b lic . u] ) 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 . .* ] )
Ite m O fP u rc h a s e
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 p u b lic P re ffe re d C u s t o m e r() mer 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
: CSE
: creditcard
validation
public void deleverItem () public void rejected() public void rem oveOrder()
134
DEPT
: CSE
: Customer
public void setAddrToShip() public void browsecatalog()
public void deleverItem () public void shipm entD etails() public void getAddrToShop() public void displaycatalog() public void getC reditR ating()
: Shoppingcart
public void rejected()
: creditcard
135
DEPT
: CSE
Browse Catlog
{ From OP_Activity }
Displaying Catlog
{ From OP_Activity }
Selecting Catlog
{ From OP_Activ...
Displaying ....
{ From OP_Activity }
Selecting &
{ From OP_Activit...
Requesting
{ From OP_Activity }
Validating credit
{ From OP_Activity }
Issuing payment
{ From OP_Activity }
Accepting delivery
{ From OP_Activity }
Unnamed
Delievering Item
{ From OP_Activity }
Authorized
{ From OP_Activity }
Rejected
{ From OP_Activity }
Unnamed
136
DEPT
: CSE
CHECKING
PROCESS DELIVERY
WAITING
CANCELLING
DISPATCH
EXIT
137
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