75752177 OOAD Lab Manual by N Gopinath SKPIT

S.K.P Institute of TechnologyTiruvannamalai – 606611.

DEPT : CSE

CS2357- OBJECT ORIENTED ANALYSIS AND DESIGN LAB MANUAL

(III Year CSE)

PREPARED BY

N.GOPINATHAP/CSE

1


DEPT : CSE

NAME :

REG.NO :

DEPT :

SEM :

SUB CODE/NAME :

2


DEPT : CSE

TABLE OF CONTENTS

S.NO DATE NAME OF THE EXPERIMENT MARKS SIGN

INTRODUCTION TO RATIONAL ROSE SOFTWARE

1 ATM SYSTEM

2 ONLINE RESERVATION SYSTEM

3 ONLINE QUIZ SYSTEM

4 STOCK MAINTENANCE SYSTEM

5 STUDENT MARK ANALYSIS SYSTEM

6 COURSE REGISTRATION SYSTEM

7 PAYROLL SYSTEM

8 EXPERT SYSTEM

9 LIBRARY MANAGEMENT SYSTEM

10 REAL TIME SCHEDULER

11 REMOTE PROCEDURE CALL

12 ONLINE PURCHASE SYSTEM

3


DEPT : CSE

BATCH SPLITUPS :

Batch - I Batch - II

Roll.NO REG NO Roll.NO REG NO

1 52909104001 21 52909104021

2 52909104002 22 52909104022

3 52909104003 23 52909104023

4 52909104004 24 52909104024

5 52909104005 25 52909104025

6 52909104006 26 52909104026

7 52909104007 27 52909104027

8 52909104008 28 52909104028

9 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 5290910401939 52909104302

20 52909104020

4


DEPT : CSE

Lab Plan for Tuesday Batch

5

DATES Roll.NO EXERCISE FOR BATCHES

20.12.2011 1to20 INTRODUCTION TO RATIONAL ROSE SOFTWARE

20.12.2011 1to20 ATM SYSTEM

27.12.2011 1to20 ONLINE RESERVATION SYSTEM

03.01.2012 1to20 ONLINE QUIZ SYSTEM

10.01.2012 1to20 STOCK MAINTENANCE SYSTEM

24.01.2012 1to20 STUDENT MARK ANALYSIS SYSTEM

31.01.2012 1to20 COURSE REGISTRATION SYSTEM

07.02.2012 1to20 PAYROLL SYSTEM

14.02.2012 1to20 EXPERT SYSTEM

14.02.2012 1to20 LIBRARY MANAGEMENT SYSTEM

21.02.2012 1to20 REAL TIME SCHEDULER

21.02.2012 1to20 REMOTE PROCEDURE CALL

28.02.2012 1to20 ONLINE PURCHASE SYSTEM


DEPT : CSE

Lab Plan for Friday Batch

RATIONAL ROSERATIONAL ROSE

6

DATES Roll.NO EXERCISE FOR BATCHES

23.12.2011 21to39 INTRODUCTION TO RATIONAL ROSE SOFTWARE

23.12.2011 21to39 ATM SYSTEM

30.12.2011 21to39 ONLINE RESERVATION SYSTEM

06.01.2012 21to39 ONLINE QUIZ SYSTEM

20.01.2012 21to39 STOCK MAINTENANCE SYSTEM

27.01.2012 21to39 STUDENT MARK ANALYSIS SYSTEM

03.02.2012 21to39 COURSE REGISTRATION SYSTEM

10.02.2012 21to39 PAYROLL SYSTEM

10.02.2012 21to39 EXPERT SYSTEM

17.02.2012 21to39 LIBRARY MANAGEMENT SYSTEM

24.02.2012 21to39 REAL TIME SCHEDULER

02.03.2012 21to39 REMOTE PROCEDURE CALL

09.03.2012 21to39 ONLINE PURCHASE SYSTEM


DEPT : CSE

RATIONAL ROSE SOFTWARE

ANALYSIS AND DESIGN

The application’s 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 model’s 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 model’s 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

7


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.

8


DEPT : CSE

9


DEPT : CSE

10


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 : 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

USE CASE DIAGRAM:

CLASS DIAGRAM

.

15


DEPT : CSE

SEQUENCE DIAGRAM

16


DEPT : CSE

COLLABORATION DIAGRAM

17


DEPT : CSE

ACTIVITY DIAGRAM

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

EX NO:DATE:

ONLINE RESERVATION SYSTEM

AIM:

To analyze, design and develop code for online reservation system using Rational Rose software.

INFRASTRUCTURE:


• ¨X86 based processor

• ¨RAM (128 MB min)

• ¨Hard Disc (40 GB)


• Rational Rose Software

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

USE CASE DIAGRAM

.

CLASS DIAGRAM

26


DEPT : CSE

SEQUENCE DIAGRAM(Ticket reservation)

27


DEPT : CSE

SEQUENCE DIAGRAM(Ticket cancellation)

.

28


DEPT : CSE

COLLABORATION DIAGRAM(Ticket Reservation)

COLLABORATION DIAGRAM(Ticket Cancellation)

29


DEPT : CSE

ACTIVITY DIAGRAM

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

EX NO:

DATE:

ONLINE QUIZ SYSTEM

AIM:

To analyze, design and develop code for online quiz system using Rational Rose software.

INFRASTRUCTURE:






• ¨Rational Rose Software

34


DEPT : CSE

MODULAR DESCRIPTION

35


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 : CSE

USE CASE DIAGRAM

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

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

EX NO: DATE:

STOCK MAINTENANCE SYSTEM

AIM:

To analyze, design and develop code for Stock Maintenance System using Rational Rose software.

INFRASTRUCTURE:


• X86 based processor




• Rational Rose Software

• ¨Visual C++ 6.0

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

USE CASE DIAGRAM:

CLASS DIAGRAM:

49


DEPT : CSE

SEQUENCE DIAGRAM

COLLABORATIOIN DIAGRAM:(Login)

50


DEPT : CSE

ACTIVITY DIAGRAM:

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

EX NO:DATE:

STUDENT MARK ANALYSIS SYSTEM

AIM:

To analyze, design and develop code for Student Mark Analysis system using Rational Rose software.

INFRASTRUCTURE:







• ¨Visual Basic 6.0

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

USE CASE DIAGRAM:

CLASS DIAGRAM:

59


DEPT : CSE

SEQUENCE DIAGRAM:

COLLABORATION DIAGRAM:

60


DEPT : CSE

ACTIVITY DIAGRAM:

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

EX N O:DATE:

COURSE REGISTRATION SYSTEM

AIM:

To analyze, design and develop code for Course registration System using Rational Rose software.

.

INFRASTRUCTURE:







• ¨Visual C++ 6.0

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

USE CASE DIAGRAM:

.

CLASS DIAGRAM:

69


DEPT : CSE

SEQUENCE DIAGRAM:


70


DEPT : CSE

ACTIVITY DIAGRAM:

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:

PAY ROLL SYSTEM

AIM:

To analyze, design and develop code for Payroll System using Rational Rose software.

INFRASTRUCTURE:







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

USE CASE DIAGRAM:

CLASS DIAGRAM:

79


DEPT : CSE

SEQUENCE DIAGRAM:

(General view)

SEQUENCE DIAGRAM:

(Specified view)

80


DEPT : CSE


(General view)


(Specified view)

81


DEPT : CSE

ACTIVITY DIAGRAM:

.

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:







86


DEPT : CSE

87


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 : CSE

89


DEPT : CSE

USECASE DIAGRAM

Creation

Log-in

Answer questions

Wait for inference

View marks

Personal Details

Maintenance

UserAdministrator

CLASS DIAGRAM

EQ Questions

selectqueschoices

EQ Marks

selectedchoices

valuatechoices()

EQ System

choicevalue

sum1()

transfers

calculates

90


DEPT : CSE

SEQUENCE DIAGRAM

User Interface EQ DatabaseEQ System

login verify username and password

pose question

select answer

update marks on database

calculate result

give EQ result

display EQ


User Interface

EQ Database

EQ System

1: login

2: verify username and password

3: pose question4: select answer

5: update marks on database6: calculate result

7: give EQ result8: display EQ

91


DEPT : CSE

ACTIVITY DIAGRAM

Start the application

Enter the username and password

Verify username and password

Enter into system

Enter personal details

Save your current EQ

View past records

Read the question

Select the answers

Submit answers

View the result

Save settings

Log out

92


DEPT : CSE

COMPONENT DIAGRAM

Server

DBMS Server

User Expert UI Printer

DEPLOYMENT DIAGRAM

Server DBMS Server

Printer

UI

Get details

Get question

Print result

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

LIBRARY MANAGEMENT SYSTEM

95


DEPT : CSE

96


DEPT : CSE

Ex.No:

DATE:

LIBRARY MANAGEMENGT SYSTEM

AIM:

To analyze, design and develop code for Library Management System using Rational Rose software.

INFRASTRUCTURE:







97


DEPT : CSE

98


DEPT : CSE

MODULE DESCRIPTION

MODULE 1• Provide a user interface for getting the user’s 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 author’s 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

USE CASE DIAGRAM

Search book name

Select book name

Enter student login details

Issue the book

Student Librarian

CLASS DIAGRAM

101


DEPT : CSE

SEQUENCE DIAGRAM

102

Data Entry

NameId no.Book nameAuthorDOIDORCard no

Issue()Return ()

Software Entry

Issue Querying

DOI.

Renewal()Issue()

Querying

ReturnQuerying

Return()


DEPT : CSE


103

Student library

AdministratorLibrarian

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


DEPT : CSE

ACTIVITY DIAGRAM

104

SystemAdministrator

Student

Librarian

1: Enter Login Details

2: Verify Authentication

3: Grant Permission/ Deny4: Enter Login Details

5: Verify Authentication

6: Grant Permission/Deny

7: Enter Book name

8: Search the book

9: Enter author name11: Issue the book


DEPT : CSE

Enter login name

Verify

Grant permission

Enter book name

Enter author name

Display the book

Check out the book

105


DEPT : CSE

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

Client P roces sor

W eb Server

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

REAL TIME SCHEDULER

108


DEPT : CSE

Ex.No:

109


DEPT : CSE

DATE:

REAL TIME SCHEDULER

AIM:

To analyze, design and develop code for Real Time Scheduler using Rational Rose software.

INFRASTRUCTURE:







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 nameo Appointment timeo 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

USE CASE DIAGRAM

113


DEPT : CSE

V ie w S c h e d u le

A d d S c h e d u le

D e le t e S c h e d u le

R e s c h ed u le

S y s te m

C h e c k A va ila b i l it y

P e rs o n _ D e ta i ls

CLASS DIAGRAM

m ak es needs

A va ilab ilit y

New_t im eNew_loc a t ion

Chec k A vai lab ility ()

S c hedule

A c t ivityTim eLoc ation

De leteS c hedu le()Res c hedu le ()

P erson

P erson_Nam eP erson_IDP hone_NoP as s word

V iew S c hedule ()E d itS c hedule ()

114


DEPT : CSE

SEQUENCE DIAGRAM

Person Appointment Control

Appointment

View schedule

Check availability

Reschedule

Confirm appointment

Add appointment

If yes, create appointment

No

115


DEPT : CSE


Person Appointment Control

Appointment

1: View schedule

3: Check availability6: Reschedule

7: Confirm appointment

2: Add appointment

4: If yes, create appointment

5: No

ACTIVITY DIAGRAM

Enter details

View Schedule Add appointment

Available?

Reschedule appointment

no

Confirm schedule

Yes

116


DEPT : CSE

COMPONENT DIAGRAM

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

REMOTE PROCEDURE CALL

119


DEPT : CSE

120


DEPT : CSE

Ex.No:DATE:

REMOTE PROCEDURE CALL

AIM:

To analyze, design and develop code for Remote Procedure Call using Rational Rose software.

INFRASTRUCTURE:







121


DEPT : CSE

122


DEPT : CSE

MODULE DESCRIPTIONMODULE 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

USE CASE DIAGRAM

warehouse

Inform warehouse about order

Display s tandard computer config

Build com puter config

Order configured computer

Request salesperson contac t

cus tom er

Upd ate orde r s tat us

P r int invo ice

S alesperson

Verify and accep t cus tom er payment

125


DEPT : CSE

CLASS DIAGRAM

Configuration

item typeitem descp

Customer

nameaddressph noemail

get order()

Payment

payment methoddate receivedamt received

Invoice

numberdatetotal

Order

od numdateaddresstotalstatussales pname

SEQUENCE DIAGRAM

126


DEPT : CSE

Customer Config window Order Order window Payment

Open new

Accept config Prepare for orderDisplay order

Submit order

Store order

Link customer

Link payment


Config window

Order Order window

Customer Payment

3: Prepare for order 4: Display order

6: Store order

8: Link payment

1: Open new2: Accep t c onfig

5: Submit order

7: Link customer

127


DEPT : CSE

ACTIVITYDIAGRAM

Display current config

Get order request

Dispaly purchase form

Get purchase details Store order

Email order details

[OK]

[incomplete]

[time out]

COMPONENT DIAGRAM

Online shopping

Customer

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.

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 : CSE

3.4 Collaboration Diagram

3.5 Activity Diagram

3.6 State Diagram

ONLINE PURCHASE USE CASE DIAGRAM

131


DEPT : CSE

OnlinePurchase

C ustomer

Softw are

Banking

D ealer

Che ck forva lidity

De lie ve r Goods

IssueAuthoriza tion

Issue De ta ils

Ask for Pa ym e nt &Shipping de ta ils

Se le ct Ite m

Brow se Ca tlog

Re que st Ite m

ONLINE PURCHASE CLASS DIAGRAM

132


DEPT : CSE

S h o p p in g C a r dA ttr i b u te s

p u b l ic flo a t s u b to t a lp u b l ic flo a t s a le s m o n e yp u b l ic flo a t t o t a lm o n e y

O p e r a t i o n s

p u b l ic S h o p p in g C a rd ( )p u b l ic flo a t g e t S u b t o t a l()p u b l ic vo id s e tS u b to t a l ( flo a t va l )p u b l ic flo a t g e t S a le s m o n e y ()p u b l ic vo id s e tS a le s m o n e y ( flo a t va l )p u b l ic flo a t g e t T o t a lm o n e y ( )p u b l ic vo id s e tT o t a lm o n e y (flo a t va l )p u b l ic vo id p la c e O rd e r( )p u b l ic vo id re m o ve O rd e r ()p u b l ic C u s to m e rvo id [ 0 . . * ] g e t C u s to m e r()p u b l ic vo id s e tC u s to m e r(C u s to m e r va l[ 0 . . * ] )p u b l ic C re d i tC a rd vo id [0 . . * ] g e t C re d it C a rd ()p u b l ic vo id s e tC re d i t C a rd (C rd e it C a rd va l[ 0 . . * ] )p u b l ic C u s to m e r [0 . . * ] g e t C u s t o m e r()p u b l ic vo id s e tC u s to m e r(C u s to m e r va l[ 0 . . * ] )p u b l ic C re d i tC a rd [ 0 . . * ] g e tC re d i tC a rd ( )p u b l ic vo id s e tC re d i t C a rd (C re d it C a rd va l[ 0 . . * ] )

C u s to m e rA tt r i b u te s

p r iva t e s t r in g a d d rt o s h ipp r iva t e s t r in g n a m ep riva t e s t r in g a d d rt o b i l lp r iva t e s t r in g e m a i la d dp r iva t e in t c re d it ra t in g

O p e r a t i o n s

p u b lic C u s t o m e r()p u b lic s t rin g g e t A d d rt o s h ip ( )p u b lic vo id s e t A d d r to s h ip (s t ri n g va l )p u b lic s t rin g g e t N a m e ()p u b lic vo id s e t N a m e (s t rin g va l )p u b lic s t rin g g e t A d d rt o b i l l ( )p u b lic vo id s e t A d d r to b i l l (s t ri n g va l )p u b lic s t rin g g e t E m a i la d d ( )p u b lic vo id s e t E m a i la d d (s t ri n g va l )p u b lic in t g e t C re d i t ra t in g ()p u b lic vo id s e t C re d i t ra t in g ( in t va l )p u b lic vo id d is p la y C a t e g o ry ()p u b lic vo id s e le c t It e m ()p u b lic vo id d e l ie ve rIt e m ()p u b lic vo id re m o ve O rd e r( )

Ite m O fP u rc h a s eA ttr i b u te s

p r iva te in t q u a n t i t yp r iva te flo a t p r ic e p e r i t e m

O p e r a t i o n s

p u b lic It e m O fP u rc h a s e ()p u b lic in t g e tQ u a n t i t y ()p u b lic vo id s e t Q u a n t i t y (in t va l )p u b lic flo a t g e tP r ic e p e r i t e m ()p u b lic vo id s e t P r ic e p e r i t e m ( flo a t va l )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 vo id s e t C u s to m e r(C u s to m e r va l )p u b lic P ro d u c t [ 0 . . * ] g e tP ro d u c t ()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 u b lic P ro d u c t [ 0 . . * ] g e tP ro d u c t ()p u b lic vo id s e t P ro d u c t (P ro d u c t va l[ 0 . . * ] )

C re d itC a r dO p e r a t i o n s

p u b li c C re d i tC a rd ( )p u b li c in t g e tN u m b e r()p u b li c vo id s e tN u m b e r( in t va l )p u b li c d a te g e t E x p i ry d a t e ()p u b li c vo id s e tE x p iry d a te (d a t e va l )p u b li c b o o le a n g e t Is s u e ( )p u b li c vo id s e t Is s u e (b o o le a n va l )p u b li c vo id a u th o r iz e C h a rg e ()p u b li c P re ffe re d ( )p u b li c 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 li c vo id s e t It e m O fP u rc h a s e (It e m O fP u rc h a s e va l )p u b li c P re ffe re d C u s t o m e r [0 . . * ] g e tP re ffe r re d C u s to m e r( )p u b li c 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 u b li c 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()p u b li c 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 . . * ] )

P r e ffe r e d C u s to m e rA t tr i b u te s

p r iva t e in t d is c o u n t ra t e

O p e r a t i o n s

p u b lic P re ffe re d C u s t o m e r( )p u b lic in t g e t D is c o u n t ra t e ()p u b lic vo id s e t D is c o u n t ra te ( in t 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 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 u b lic C u s t o m e r g e t C u s to m e r1 ()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 )p u b lic C u s t o m e r g e t 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 )

P ro d u c tA ttr i b u te s

O p e r a ti o n s

p u b l ic P ro d u c t ()

1

*

m Pr o d u c t

1

m C u s to m e r

1*

m C r e d itC a r d 1

1

m C u s to m e r

m Pr e f f e r e d C u s to m e r

* 1

ONLINE PURCHASE SEQUENCE DIAGRAM

133


DEPT : CSE

: Customer

: Shoppingcart : creditcard

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 authorize()

public void getExpiryDate()

validation

public void setCrediting(int val )

public void setAddrToShip()

public void deleverItem()

public void rejected()

public void removeOrder()

134


DEPT : CSE

ONLINE PURCHASE COLLABORATION DIAGRAM

: Customer

: Shoppingcart

: creditcard

public void browsecatalog()

public void displaycatalog()public void selectItem()

public void getCreditRating()

public void getAddrToShop()

public void setCreditCard()

public void shipmentDetails()

public void setCrediting(int val )

public void setAddrToShip()

public void deleverItem()

public void removeOrder()

public void authorizedCharge()

public void authorize()

public void rejected()

public void getExpiryDate()

135


DEPT : CSE

ONLINE PURCHASE ACTIVITY DIAGRAM

OnlinePurchase

Customer Shoppingcart Creditcard

BrowseCatlog

{ From OP_Activity }

SelectingCatlog

{ From OP_Activ...

Selecting &

{ From OP_Activit...

Issuingpayment


DelieveringItem


DisplayingCatlog


Displaying ....


Requesting


Acceptingdelivery


Authorized


Rejected


Validatingcredit


Unnamed

Unnamed

Unnamed

136


DEPT : CSE

ONLINE PURCHASE STATECHART DIAGRAM

CHECKING

PROCESS

DELIVERY

DISPATCH

WAITING

CANCELLING

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

Date post:	23-Oct-2015
Category:	Documents
Upload:	karthik-keyan
View:	58 times
Download:	11 times

75752177 OOAD Lab Manual by N Gopinath SKPIT

Documents