CASE TOOLS LAB

2010-2011 V SEMESTER Department of Information technology

N.P.R COLLEGE OF ENGINEERING AND TECHNOLOGY

Name of the Student: ___________________________________ Year/Sem Roll No : III/V : ___________________________________

CONTENTS

S.No
1. 2. 3. 4. 5.

Date

Name of the Experiment

Study of UML Student Mark Analyzing System Quiz System Online Ticket Reservation System Payroll System

Page no

Signature

6. 7. 8. 9. 10.

Course Registration System Expert Systems ATM Systems Stock Maintenance Remote Procedure Call Implementation.

EX N0 : 1 DATE :

STUDY OF UML
AIM: General study of UML DESCRIPTION:
The heart of object-oriented problem solving is the construction of a model. The model abstracts the essential details of the underlying problem from its usually complicated real world. Several modeling tools are wrapped under the heading of the UML, which stands for Unified Modeling Language. The purpose of this course is to present important highlights of the UML. At the center of the UML are its nine kinds of modeling diagrams, which we describe here.

Use case diagrams Class diagrams Object diagrams Sequence diagrams Collaboration diagrams State chart diagrams Activity diagrams Component diagrams Deployment diagrams
Some of the sections of this course contain links to pages with more detailed information. And every

section has short questions. Use them to test your understanding of the section topic. Why is UML important? Let's look at this question from the point of view of the construction trade. Architects design buildings. Builders use the designs to create buildings. The more complicated the building, the more critical the communication between architect and builder. Blueprints are the standard graphical language that both architects and builders must learn as part of their trade. Writing software is not unlike constructing a building. The more complicated the underlying system, the more critical the communication among everyone involved in creating and deploying the software. In the past decade, the UML has emerged as the software blueprint language for analysts, designers, and programmers alike. It is now part of the software trade. The UML gives everyone from business analyst to designer to programmer a common vocabulary to talk about software design.

The UML is applicable to object-oriented problem solving. Anyone interested in learning UML must be familiar with the underlying tenet of object-oriented problem solving -- it all begins with the construction of a model. A model is an abstraction of the underlying problem. The domain is the actual world from which the problem comes.Models consist of objects that interact by sending each other messages. Think of an object as "alive." Objects have things they know (attributes) and things they can do (behaviors or operations). The values of an object's attributes determine its state. Classes are the "blueprints" for objects. A class wraps attributes (data) and behaviors (methods or functions) into a single distinct entity. Objects are instances of classes.

Use case diagrams

Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is on what a system does rather than how. Use case diagrams are closely connected to scenarios. A scenario is an example of what happens when someone interacts with the system. Here is a scenario for a medical clinic. "A patient calls the clinic to make an appointment for a yearly checkup. The receptionist finds the nearest empty time slot in the appointment book and schedules the appointment for that time slot. " A use case is a summary of scenarios for a single task or goal. An actor is who or what initiates the events involved in that task. Actors are simply roles that people or objects play. The picture below is a Make Appointment use case for the medical clinic. The actor is a Patient. The connection between actor and use case is a communication association (or communication for short).

Actors are stick figures. Use cases are ovals. Communications are lines that link actors to use cases. A use case diagram is a collection of actors, use cases, and their communications. We've put Make Appointment as part of a diagram with four actors and four use cases. Notice that a single use case can have multiple actors.

. Use case diagrams are helpful in three areas.

determining features (requirements). New use cases often generate new requirements as the system is analyzed and the design takes shape. communicating with clients. Their notational simplicity makes use case diagrams a good way for developers to communicate with clients. generating test cases. The collection of scenarios for a use case may suggest a suite of test cases for those scenarios.

Class diagrams
A Class diagram gives an overview of a system by showing its classes and the relationships among them. Class diagrams are static -- they display what interacts but not what happens when they do interact. The class diagram below models a customer order from a retail catalog. The central class is the Order. Associated with it are the Customer making the purchase and the Payment. A Payment is one of three kinds: Cash, Check, or Credit. The order contains OrderDetails (line items), each with its associated Item.

UML class notation is a rectangle divided into three parts: class name, attributes, and operations. Names of abstract classes, such as Payment, are in italics. Relationships between classes are the connecting links.

Our class diagram has three kinds of relationships.

association -- a relationship between instances of the two classes. There is an association between two classes if an instance of one class must know about the other in order to perform its work. In a diagram, an association is a link connecting two classes.

aggregation -- an association in which one class belongs to a collection. An aggregation has a diamond end pointing to the part containing the whole. In our diagram, Order has a collection of OrderDetails.

generalization -- an inheritance link indicating one class is a superclass of the other. A generalization has a triangle pointing to the superclass. Payment is a superclass of Cash, Check, and Credit.

An association has two ends. An end may have a role name to clarify the nature of the association. For example, an OrderDetail is a line item of each Order. A navigability arrow on an association shows which direction the association can be traversed or queried. An OrderDetail can be queried about its Item, but not the other way around. The arrow also lets you know who "owns" the association's implementation; in this case, OrderDetail has an Item. Associations with no navigability arrows are bi-directional. The multiplicity of an association end is the number of possible instances of the class associated with a single instance of the other end. Multiplicities are single numbers or ranges of numbers. In our example, there can be only one Customer for each Order, but a Customer can have any number of Orders. This table gives the most common multiplicities.

Multiplicities 0..1 0..* or * 1 1..*

Meaning zero or one instance. The notation n . . m indicates n to m instances. no limit on the number of instances (including none). exactly one instance at least one instance

Every class diagram has classes, associations, and multiplicities. Navigability and roles are optional items placed in a diagram to provide clarity.

Packages and object diagrams

To simplify complex class diagrams, you can group classes into packages. A package is a collection of logically related UML elements. The diagram below is a business model in which the classes are grouped into packages.

Packages appear as rectangles with small tabs at the top. The package name is on the tab or inside the rectangle. The dotted arrows are dependencies. One package depends on another if changes in the other could possibly force changes in the first. Object diagrams show instances instead of classes. They are useful for explaining small pieces with complicated relationships, especially recursive relationships. This small class diagram shows that a university Department can contain lots of other Departments.

The object diagram below instantiates the class diagram, replacing it by a concrete example.

Each rectangle in the object diagram corresponds to a single instance. Instance names are underlined in UML diagrams. Class or instance names may be omitted from object diagrams as long as the diagram meaning is still clear.

Sequence diagrams
Class and object diagrams are static model views. Interaction diagrams are dynamic. They describe how objects collaborate. A sequence diagram is an interaction diagram that details how operations are carried out -- what messages are sent and when. Sequence diagrams are organized according to time. The time progresses as you go down the page. The objects involved in the operation are listed from left to right according to when they take part in the message sequence. Below is a sequence diagram for making a hotel reservation. The object initiating the sequence of messages is a Reservation window.

The Reservation window sends a makeReservation() message to a HotelChain. The HotelChain then sends a makeReservation() message to a Hotel. If the Hotel has available rooms, then it makes a Reservation and a Confirmation. Each vertical dotted line is a lifeline, representing the time that an object exists. Each arrow is a message call. An arrow goes from the sender to the top of the activation bar of the message on the receiver's lifeline. The activation bar represents the duration of execution of the message.

In our diagram, the Hotel issues a self call to determine if a room is available. If so, then the Hotel creates a Reservation and a Confirmation. The asterisk on the self call means iteration (to make sure there is available room for each day of the stay in the hotel). The expression in square brackets, [ ], is a condition.

Collaboration diagrams
Collaboration diagrams are also interaction diagrams. They convey the same information as sequence diagrams, but they focus on object roles instead of the times that messages are sent. In a sequence diagram, object roles are the vertices and messages are the connecting links.

The object-role rectangles are labeled with either class or object names (or both). Class names are preceded by colons ( : ). Each message in a collaboration diagram has a sequence number. The top-level message is numbered 1. Messages at the same level (sent during the same call) have the same decimal prefix but suffixes of 1, 2, etc. according to when they occur.

Statechart diagrams
Objects have behaviors and state. The state of an object depends on its current activity or condition. A statechart diagram shows the possible states of the object and the transitions that cause a change in state. Our example diagram models the login part of an online banking system. Logging in consists of entering a valid social security number and personal id number, then submitting the information for validation.

Logging in can be factored into four non-overlapping states: Getting SSN, Getting PIN, Validating, and Rejecting. From each state comes a complete set of transitions that determine the subsequent state.

States are rounded rectangles. Transitions are arrows from one state to another. Events or conditions that trigger transitions are written beside the arrows. Our diagram has two self-transition, one on Getting SSN and another on Getting PIN. The initial state (black circle) is a dummy to start the action. Final states are also dummy states that terminate the action. The action that occurs as a result of an event or condition is expressed in the form /action. While in its Validating state, the object does not wait for an outside event to trigger a transition. Instead, it performs an activity. The result of that activity determines its subsequent state.

Activity diagrams
An activity diagram is essentially a fancy flowchart. Activity diagrams and statechart diagrams are related. While a statechart diagram focuses attention on an object undergoing a process (or on a process as an object), an activity diagram focuses on the flow of activities involved in a single process. The activity diagram shows the how those activities depend on one another. For our example, we used the following process. "Withdraw money from a bank account through an ATM." The three involved classes (people, etc.) of the activity are Customer, ATM, and Bank. The process begins at the black start circle at the top and ends at the concentric white/black stop circles at the bottom. The activities are rounded rectangles.

10

Activity diagrams can be divided into object swimlanes that determine which object is responsible for which activity. A single transition comes out of each activity, connecting it to the next activity. A transition may branch into two or more mutually exclusive transitions. Guard expressions (inside [ ]) label the transitions coming out of a branch. A branch and its subsequent merge marking the end of the branch appear in the diagram as hollow diamonds. A transition may fork into two or more parallel activities. The fork and the subsequent join of the threads coming out of the fork appear in the diagram as solid bars.

Component and deployment diagrams

A component is a code module. Component diagrams are physical analogs of class diagram. Deployment diagrams show the physical configurations of software and hardware.

11

The following deployment diagram shows the relationships among software and hardware components involved in real estate transactions.

The physical hardware is made up of nodes. Each component belongs on a node. Components are shown as rectangles with two tabs at the upper left.

12

EX NO: 2 Date :

STUDENT MARK ANALYSIS SYSTEM

Aim: To create a UML diagram for MARK ANALYSIS system. Actors: 1. Student 2. Staff Use cases: 1. Number of subject 2. Marks 3. Total 4. Grade 5. Average Problem Statement: Student marks analyzing system has to be developed for analyzing the marks obtained by the students who scored in Semester Examination The System should provide the following functionalities 1. The System obtains the following information (No of Subjects, Marks, Total, Percentage, Grade, Marks obtained in each subject and No of students in each section) from the faculty and generates report. 2. The total, average and grade of each student should be calculated and ranked based on total and pass in all the subject appeared. If a student fails in at least in one subject then he/she should be given rank. 3. The Final report should display the top 3 persons in each subject along with rank, percentage, Class, Pass/Fail Status for each student. The report should also contain information about no of students passed, failed, list of students who got more than 60% in each subject and overall list of students who got >=60% and so on.

13

Use case diagram: Draw and drop the actors and use case from browser window into the diagram window. Associate the use cases and actors.

14

Class Diagram:

Activity diagram: The activity diagram describes the sequencing of activities, with support for both conditional and parallel behavior.

15

The various controls are placed into the diagram window to create activity diagram.

16

17

Sequence diagram :

Create a new package from the database and name it as a sequence diagram. From the toolbar, select the required tools and make corresponding connections.

S t a ff

M a rk s

F in d To ta l & A s s u m e G ra d e S t u de n t A ve ra g e

1 . N o o f S u b je c t s 2 . R e a d M a rk s 3 . F in d to t al & A vg 4 . F in d G ra d e 5 . S t o re

6 . S t ore M a rk s

18

Collaboration diagram: Press f5 on the sequence diagram the collaboration diagram is obtained. Save the diagram.

19

Component Diagram:

20

Deployment Diagram:

21

Result: Thus the UML Diagrams for Students Mark Analysis was created.

22

EX NO : 3 Date :

QUIZ SYSTEM
Aim: To create a uml diagram for QUIZ application. Actors: 1. Interviewer 2. Participant 3. Scorer Use cases: 1. Number of teams 2. Team name 3. Number of participants 4. Rules 5. Rounds 6. Question and Answers 7. Time 8. Marks 9. Results 10. Prize Problem Statement: Online Quiz System has to be developed for conducting Preliminary stage of a quiz. The System developed should contain the following features 1. The number of participants, Teams, team Name and Rounds are bound to follow Rules. 2. The duration for quiz is determined. Where the Scorer will have to take care of them. 3. The number of questions should be 40 chosen randomly from the database in 3 different areas namely i) Technical ii) logical reasoning and iii) General Knowledge. 4. The questions should be of objective type with multiple options. For each correct answer the participant will receive 1 Point and for wrong answer, the participant will be out of the quiz competition. 5. At the end of the quiz the users score along with information whether he has been selected or not has to be displayed. 6. Once a Student has answered a question, he cant change the answer later.

23

Use case diagram: Draw and drop the actors and use case from browser window into the diagram window. Associate the use cases and actors.

No of Teams

Team Name

No of Participant

No of Rounds

Rules

Prize

Interviewer

Particiapnt Questions Result

Answer

Marks

Scorer

24

Class Diagram:

25

Activity diagram: The activity diagram describes the sequencing of activities, with support for both conditional and parallel behavior. The various controls are placed into the diagram window to create activity diagram.

D scrib n o te m n o p rticip n n e e o f a s, o f a a t, o o ro n s, a d te mn m f ud n a a e

E te R u d n r on

A Qe n sk u stio s

G t A sw r e n e

N o C e A sw r h ck n e

If C rre o ct A ssig M rks n a

If N t C rre o o ct

C e E do R u d h ck n f o n

If Y s e D cla R su e re e lt

A a th P w rd e rize

26

Sequence diagram: Create a new package from the database and name it as a sequence diagram. From the toolbar, select the required tools and make corresponding connections.

Int ervie w er

P artic ipant

M ark s

R ounds

W inner

1. A s k Q ues tion 2.A ns w er t he Q ues tion

3. If A ns w er is C o rrec t provide M ark

4. If N ot C orrec t A s k N ex t Q ues t ion

5. If C he c k E nd of R ound 6.If Y es A nn ounc e W inner

7. If N o A s k N ex t Q ues tion

27

Collaboration diagram: Press f5 on the sequence diagram the coloration diagram is obtained. Save the diagram.

28

Component Diagram:

29

Deployment Diagram:

30

Result: Thus the UML Diagrams for Quiz Application was created.

31

EX NO : 4 Date : ONLINE TICKET RESERVATION Aim: To create a UML diagram for ONLINE TICKET RESERVATION system. Actors: 1. Passenger 2. System Use cases: 1. Enter the web site 2. Choose the destination 3. List of trains 4. User details 5. Choose the train 6. Number of seats 7. Credit card number 8. Ticket status 9. Confirmation 10. Exit Problem statement: Online ticket reservation system has to be developed for railway department. The System developed should contain following features 1. The System should provide information about arrival and departure of trains along with information about stations through which it passes. 2. Search about train passing through stations can be obtained either by means of train no, train name or specifying the source and destination stations. 3. While displaying information about train, it has to provide following informations a) Stations through which train passes along with arrival and departure time. b) Availability of seats in different classes along with waiting list and RAC information.

4. While reserving ticket online the system obtain following informations from the user a) Passenger name, Sex, Age, Address T.Authority no for tatkal reservation

32

b) Credit Card No, Bank Name c) Class through passenger is going to travel i.e First class or Second class or AC d) Train no and Train name, Date of Journey and number of tickets to be booked. 5. Based on the availability of tickets the ticket has to be issued. The ticked issued should contain the following informations PNR NO, Train No, Date, K.M., no of adults and children, Ticket No, Class, Ticket No, Coach, Seat/Berth, Sex, Age, T.Authority, Concession, Reservation fee, Total Cash, Train Name, Departure time. 6. Before issuing ticket the amount from customer account has to be transferred to railway account. 7. Cancellation of booked tickets should be available

33

Use case diagram: Draw and drop the actors and use case from browser window into the diagram window. Associate the use cases and actors.

Enter the Web Site

Select the Destination

List of Trains System Passenger Select the Train

User Details Exit

No of Seats

Ticket Status

Credit Card No

Confirmation

34

Class Diagram:

35

Activity diagram: The activity diagram describes the sequencing of activities, with support for both conditional and parallel behavior. The various controls are placed into the diagram window to create activity diagram.

36

Sequence diagram:

Create a new package from the database and name it as a sequence diagram. From the toolbar, select the required tools and make corresponding connections.
System DB

Passenger 1. Login Web Site

2. Select the Destination 3. List of Trains

4. Give User Details

5. Give Train No & No...

6. Credit Card No

7. Give Status 8. Reserve Ticket

9.Confirmation 10. Issue Ticket

Collaboration diagram:

37

Press f5 on the sequence diagram the coloration diagram is obtained. Save the diagram.

38

Component Diagram:

DB

Store & Update

Computer

39

Deployment Diagram:

40

41

Result: Thus the UML Diagrams for Online Ticket Registration was created. EX NO: 5 Date : PAYROLL PROCESSING SYSTEM

Aim: To Create an UML Diagram for an PAYROLL PROCESSING SYSTEM. Actors: 1) User 2) Administrator. Use Case: 1) Login 2) Employee Details. 3) Salary details Problem Description: In payroll system, initially login details are taken into consideration from there salary, user name or password are analyzed through admin to the company database. The employee can easily take the required details that he/she wants to. When a specific details are analyzed, it gives a clear information to an employee like monthly salary after reduction, loan info etc., if any. Thus to ease the operation of the employee to his salary details and other requirements we perform the diagrammatical scenario to explain the concepts.

42

USECASE DIAGRAM:

Login

E m ploy ee details

Us er s alary details

adm istrator

M aintainenc e

EMPLOYEE CLASS DIAGRAM:

43

User check options analyze result check for error message Display the options window() Display the result() Display an error message()

Company DB Analyze Details Check for exact info Compare info.with DB Analyze Required Details() Check For Exact info() Take out Exact Details()

Option/Window Click Option Check Emp Details Display Emp Details Available/Not Available Choose an Option() If the Emp Details Available Display() If Emp-details Not available()

ACTIVITY DIAGRAM:

Display login form

Enter employee details

Store the given details in DB

44

EMPLOYEE SEQUENCE DIAGRAM

45

User

Option

CompanyDB

Window

1.display the options window(

2.choose an option(

)
3.compare info with db( )

4.if the emp details available( ) 5.display the Details( )

6.if-emp-details not available( )

7.display an error message( )

EMPLOYEE COLLABORATION DIAGRAM:

46

2.choose an option( ) User 1.display the options window( ) 5.display the results( ) 7: display an error message( ) 4.if the emp details available( ) 6:.if-emp-details not available( ) 3:.compare info with db( )

option window

companydb

SALARY CLASS DIAGRAM:

47

User Option Window Enter Details View Details Display the options window() Enter the Details() View the Details()

Option Window Collect info. &Transfer Send info()

Company DB Chech For Details Display Details()

SALARY ACTIVITY DIAGRAM

Display Login Form

Enter Employee Name,ID Display Salary Details

SALARY SEQUENCE DIAGRAM: 48

User

Optionwindow

CompanyDB

1.Display the option window( ) 2.Enter the details( ) 3.Compare info with db( )

4.send info( ) 5.view the details( )

SALARY COLLOBORATION DIAGRAM:

49

LOGIN CLASS DIAGRAM: 50

User Enter Details Check For Message Login Completion() Check for valid/inlvalid()

LoginForm Info Details View Enter Info Check for info available() View to proceed further() Enter necessary Details()

Company DB Check for details Analyse them Check for exact details() Analyse the exact details()

Admin Controller Transform control Validate Connectivity Check for transformation() Check for connectivity between()

LOGIN ACTIVITY DIAGRAM

Display The Login Form Enter Uname & Password Yes No

Enter into Emp Details

Get Login

Go to Next Process

LOGIN SEQUENCE DIAGRAM: 51

User

Login Form

Admin Controller 1: Send Details

Company DB

2: Enter Login Details

3: Send Details

4: Transform To DB

5: if Password correct Validate

6: Login Completed 7: if Password Not Correct Access Denied

8: Display Error Message

LOGIN COLLABORATION DIAGRAM:

52

2: Enter Login Details User Login Form

6: Login Completed 8: Display Error Message

1: Send Details 3: Send Details 4: Transform To DB

Admin Controller 5: if Password correct Validate 7: if Password Not Correct Access Denied

Company DB

LOGIN COMPONENT DIAGRAM

53

Employee

Login Success/Unsuccessful

Display exact result

Emp id, Salary Allowance

Analyse DB for details

Admin Control

Authenticate

Check User Details

DEPLOYMENT DIAGRAM: 54

Admin Company Database Check for Authentication Transfer Control Take Exact Details

Analyze Output

Employee Uname/ pwd View Info Exact Request

55

Result: Thus the UML diagram for payroll processing system was designed successfully using Rational Rose Enterprise Edition. EX NO: 6

56

Date

: ON-LINE COURSE REGISRTRATION

Aim: To create a UML diagram of COURSE REGISTRATION system. Actors: 1. 2. 3. 4. Use cases: 1. 2. 3. 4. 5. 6. 7. 8. 9. Login id Registration form Update the grade of student Choose the subject Choose the courses Start registration Maintain student profile Close registration Maintain staff profile Student Staff Registrar Database

Problem Statement: 1. Develop a new student registration system for your college. 2. The college would like a new client-server system to replace its much older system developed around mainframe technology. 3. The database is an Ingres relational database running on a DEC VAX. and the college has invested in an open SQL interface that allows access to this database from the Unix servers. 4. The new system will allow students to select four course offerings for the coming semester. In addition, each student will indicate two alternative choices in case the student cannot be assigned to a primary selection. 5. Course offerings will have a maximum of twenty students and a minimum of five students. A course offering with fewer than five students will be canceled.Students must be able to access the system during this time to add or drop courses. Once the registration process is completed for a student, the registration system sends information to the billing system so the student can be billed for the semester.

57

6. If a course fills up during the actual registration process, the student must be notified of the change before submitting the schedule for processing. 7. At the end of the semester, the student will be able to access the system to view an electronic report card. Since student grades are sensitive information, the system must employ extra security measures to prevent unauthorized access.

58

Use case diagram: Draw and drop the actors and use case from browser window into the diagram window. Associate the use cases and actors.

59

Class Diagram:

60

Activity diagram: The activity diagram describes the sequencing of activities, with support for both conditional and parallel behavior. The various controls are placed into the diagram window to create activity diagram.

61

Sequence diagram:

Create a new package from the database and name it as a sequence diagram. From the toolbar, select the required tools and make corresponding connections.

62

Collaboration diagram: Press f5 on the sequence diagram the coloration diagram is obtained. Save the diagram.

63

Component Diagram:

SERVER

Store & Update

Front Panel

64

Deployment Diagram:

65

Result: Thus an UML Diagram for Online Course Registration is done.

66

EX NO: 7 Date : EXPERT SYSTEM

Aim: To Create an Uml Diagram for an EXPERT SYSTEM. Actors: 1) 2) Use case: 1) Fill Registration Form. 2) Login System. 3) Fill Query Form. 4) Prescribe Medicine. Problem Statement: An expert System has to be developed for prescribing medicines for given symptoms. The System should contain the following features 1. The user has to query the system by giving his name, age group, sex, symptoms, period (how long the user is having those symptoms). Based on these inputs, the system has to make a comparison with the symptoms in the database prescribing the medicine for the symptoms. 2. Only the Registered users can query the system. So there should be registration form and after registration the user has to be given username and password. If the user enters the correct password then the system has to redirect to query form. 3. In the query form, age group should be combo box and list of symptoms should be in the form of list box with options selecting multiple symptoms. While prescribing the medicine for the symptoms, corresponding disease, medicine name and medicine manufacturer name along with price has to be displayed. User Expert System

67

Use Case Diagram:

Fills Registration form

user

Login system

expertsystem

Fill Query form

prescribe medicine

68

Class Diagram:

69

Activity Diagram

user

expertsystem

database

Fill the registration form Enters the Expert system [ yes ]

check the given details

update in the database

new user [ no ] [ login incorrect ]

Issues uername/password

login in the [ username/password ] system [ login correct ]

verify login information

Filling the query form

Provides query form

Submitting the query form [ syptoms matched ] view medicine details prescribing the medicines

compares with the database details

[ symptoms not matched ]

Symptoms not matched!!

70

Sequence Diagram

71

Collaboration Diagram:

72

Component Diagram:

Expert system Database

user

login interface

Prescribes medicine

Fills the Query form

Fills the Registration form

73

Deployment Diagram:

74

RESULT: Thus the Expert System was developed successfully.

75

EX NO: 8 Date : ATM APPLICATION Aim: To create an uml diagram of atm application. Actors: 1. Client 2. Administrator Usecases: 1. Insert card 2. Enter pin no 3. Invalid pin 4. Type of transaction 5. Deposit amount 6. Withdrawal amount 7. Transaction completed 8. Remove the card 9. Exit 10. Carryout transaction Problem Statement To develop an ATM System for HDFC Bank The system developed should contain the following features: 1. The Customer has to login into the system using Credit Card or Debit Card number and Pin Number. The system should check for validation. 2. The System queries the customer for the type of account either Savings Account or Current Account. After getting the type of account, the system shows the amount left. 3. The System then queries the customer for the required amount. The user enters the amount and gets the money.

76

Usecase diagram: Draw and drop the actors and usecase from browser window into the diagram window. Associate the usecases and actors.

In s e rt C a rd E n t e r P IN In va li d P IN A p p ro va l

D e p o s it A m o u n t T y p e o f T ra n s a c t io n C l ie n t A d m i n is t ra t o r

W it h d ra w A m o u n t R e m o ve t h e C a rd T ra n s a c t io n C o m p lt e d E x it

77

Class Diagram:

78

Activity diagram: The activity diagram describes the sequencing of activities, with support for both conditional and parallel behavior. The various controls are placed into the diagram window to create activity diagram.

Insert Card

Display Inv alid

Enter PIN No

Check PIN No Inv alid

Valid

Deposit Withdrawal Withdrawal Amount Check Type of T ransaction Deposit Amount

Approv al

Transaction Completed

Exit

79

Sequence diagram: Create a new package from the database and name it as a sequence diagram. From the toolbar, select the required tools and make corresponding connections

Client

ATM

Administrator

Bank

1. Insert Card

2. Enter PIN No 3. Send PIN No 4. Verify PIN No

5. Validate Message

6. Get Transaction Type

7. Get Amount 8. Send Amount 9. Update Account

10. Success 11. Transaction Completed

80

Collaboration diagram: Press f5 on the sequence diagram the coloration diagram is obtained. Save the diagram.

81

Component Diagram:

ATM Server

Update

Front Panel

82

Deployment Diagram:

83

Result: Thus the UML Diagrams for ATM Application was created.

84

EX NO: 9 Date : STOCK MAINTENANCE Aim: To create a UML diagram for the stock maintenance system. Actors: 1. Producer 2. Dealer 3. Retailer . Use case: 1. Purchase 2. Company name 3. Price 4. Item ordered 5. Total price 6. Sales 7. Company Name 8. Price of the item 9. Item ordered 10. Total price Problem Statement Inventory system is a real time application used in the merchants day to day systems. This is the database to store transactions that takes place between the manufacturer, dealer and retailer. That includes stock inwards and stock outwards with reference to the dealer. Here we assume ourselves as a dealer and proceed with the transaction. The manufacturer is the producer of items and it contains the necessary information of the item price. The dealer is the secondary source of an item from the manufacturer by requesting the required item with its corresponding company name and the number of item required. The dealer is only responsible for the distribution of the item to the retailer in the town/city. The shopkeeper/retailer is the one who is the main source of selling the items in the market. The customer gets the item from the shopkeeper and not directly from the manufacturer or dealer. Stock is a database used in our system in which records or transactions that takes place between manufacturer, dealer and retailer.

85

Use Case:

86

Class Diagram

Manufacturer Menu/Item Name Company name Date of Item Address Contact No Price Mention an item name() give company name() give manufacturing date() give address() put price()

Dealer 1 Dealer Name Date_item Received contact no no of item ordered No of Item sold Display dealer name() Item Received() Put contact no() get price() no of item required() indicate item sold()

retailer 1 Shop Keeper name address contact no price no of items ordered Display Shopkeeper() Display address() Get Contact no() Display price() Indicate item ordered()

87

Activity Diagram:

88

Sequence Diagram

89

Collaboration Diagram

Component Diagram

90

S tock Maintanance syste m m aintains database inform s order

stockinterf ace custo m er vend or

order for m aterial

finished good s

91

Deployment Diagram

92

RESULT: Thus the UML Diagrams for Stock Maintenance Application was created.

93

EX NO: 10 Date:

Remote procedure call

Aim: To draw a UML diagram for the Remote procedure call Actors: 1. Client 2. Server Use Case: 1. Request 2. Response Problem Statements: This system is used to access the remote computer, the user identifies the location of a procedure stores in a remote system. The user request is accepted and the remote procedure is executed. The response will also be executed at the same time when the request command is executed.

94

Use case diagram

95

Class diagram

96

Activity diagram for request module

u rn m se a e

n o

p ssw rd a o

is p d co ct w rre ye s g e u se e iv r rv r a d IP a d ss n d re

n o

p rt o n me u br

is se e rv r co n cte ne d ye s se rch g a in fo file r s

is re u d files q ire ye e xist n o re u d file q ire n t fo n o ud

tra sfo a n o n rm tio f re u ste file qe d s T n rm tio ra sfo a n co p te m le d

97

Activity diagram for response

requisition from client for connection no Is connection accepted yes connection accepted connection rejected

searching for the request file yes requested file exist

is file exist no file not found

requisition from client to transfer the requested file

is request accepted no request rejected

yes

transfering the requested files to client

file transfered

process completed

98

Sequence for the Request:

c lie n t

unam e

pwd

a d m in

ip a d d re s s

p o rt n o

s e rve r

1 : c li e n t in te ra c t io n w it h s y s te m

2: unam e

3: pwd

4 : p w d /u s e rn a m e is c o rre c t

5 : s e rve r ip a d d re s s

6 : s e rve r p o rt n o

7 : c lie n t re q u e s t in g fo r s o u rc e c o n n e c tio n 8 : s e rve r c o n n e c t e d

99

Sequence for the response:

server

client

files

Transfer

1: requistion for the connection

2: server connected

3: searching for files

4: file exist

5: requistion for transfer the file 6: start transfering

7: files transfered

8: connection aborted

100

Collaboration diagram for the request:

server uname

pwd

2: uname 3: pwd 8: server connected 1: client interaction with system 7: client requesting for source connection admin

client

4: pwd/username is correct

6: server port no 5: server ip address ip address port no

101

Collaboration for the response:

102

Component diagram for the request:

client

uname pwd

data transfer

IP and port no

files

server

103

Component diagram for the response:

client

server

check ip and port no

data transfer

file search

104

Deployment diagram:

Response Request uname pwd enable conn... IP addr

port no server IP addr server port no file transfer

search file

file transfer

105

RESULT: Thus the UML Diagrams for Remote Procedure Call was created

106

107