qwertyuiopasdfghjklzxcvbnmqwerty

uiopasdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfghjklzx
System Analysis
cvbnmqwertyuiopasdfghjklzxcvbnmq
System Analysis Assignment 2
wertyuiopasdfghjklzxcvbnmqwertyui
9/17/2010

opasdfghjklzxcvbnmqwertyuiopasdfg
MIHIR Mehta

Student ID: 11452240

hjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfg
hjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopasdfg
hjklzxcvbnmrtyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmqwert
Page 1 of 7

yuiopasdfghjklzxcvbnmqwertyuiopas
pPage 1 of 7
Question 1
Activity Diagram (Selection of Object Oriented Approach)

Customer Automatic Coffee Machine

Welcome Message

Customer select coffee/muffin

Asking Cup size and Coffee

Type

Receiving Those Information

Display the Price

Insert appropriate amount

Dispenses the Coffee

If insert more amount

Return the Change

Page 2 of 7
Developing Use case Description:

Use case Name Planning to use an automatic coffee machine

Scenario Selling Coffee and Muffins

Trigging Event The Machine Dispenses the coffee

Brief Description Select the coffee or muffin and cup size, then coffee type,
insert appropriate amount, dispenses coffee, if more amount
insert, the machine returns change.

Actors Customer

Stockholders CSU Management

Pre Condition Customer and Coffee information

Post Condition Display The Price

Flow of Activity Actor System

1.Customer 1. Display welcome Message

2. Customer select coffee 2. Asking Cup size and coffee

or muffin type

3.Receiving those info 3. Display price

4.Insert appropriate amount 4. Dispenses the coffee

5.If insert more amount 5. Return the change

Exception Condition System does not return the change.

Question 2
Class Diagram

 A classification or class represents a collection of similar objects; so, object oriented

development uses a class diagram to show all of the classes of objects in the system.
For every class may be more specialised subclasses. Student in relationship to the
person, Student is subclass of the person. Person can be student or staff.

Page 3 of 7
 The object oriented approach involves classes of object, and many systems in the
organization use the same objects, these classes can be used frequently whenever they
required.

 Generalization in the problem domain model becomes inheritance in the design model
and programming language. Class diagram showing generalization between one
superclass and two subclasses. The notation is the same as in the problem domain. In
this case, we have used two separate arrows instead of one single arrow, but meaning is
identical. Each subclass inherits all of the attributes and methods of the parent order
class.

Question 3

 Name is an attribute that contains a new component at the bottom that specifies
the method of signature for the class in relation to video. The attribute has also
been enhance

 The constructor is the method that makes a new object for the class. We use a
create statement to follow more closely message names used in interaction
diagram. It also illustrates another constructor. The constructor must fill in the
information about the Video. Get Name is a constructor in relation to Video.
This usually requires access to a database to get values for the fields.

 This is a design class diagram that a summary of the final design that is used
directly when developing the programming code.

Question 4

Class Diagram

Football coach Team

Attribute Attribute
1 1.24
Attribute Attribute
Question 5

Page 4 of 7
  All use case is a person who uses the system that is called an actor. An actor is always
outside the automation boundary of the system but may be part of the manual system.

 Disable account is use case system processes that are used by two actors customer and
bank manager.

 This is a use case diagram that describes relation between actors and use case system.

 This is a use case diagram and describes the connecting lines between actors and use
cases indicate which actors invoke which use case. Customer and bank manager both
are an actor, and disable account and withdraw cash both are use case system. An
actor uses the use case outside the system. Use case is a kind of system process that is
used by an actor. The connecting line indicates which use case is include as a part of
the major use case.

Question 6
Class Diagram

Question 7

Page 5 of 7
 : SYSTEM

Customer

| |
| order welcome page |
| ------------------------------------------------------------------------------------------------- |
| |
| |
| Request new order () Select coffee or muffin |
| |
| |
| offering cup size and Coffee type |
| ------------------------------------------------------------------------------------------------- |
| |
| |
| Receiving info Page, ReviewOrder() |
| |
| |
| Display the Price, OrderSummary () |
| ------------------------------------------------------------------------------------------------|
| |
| |
| Insert appropriate amount, acceptOrder () |
| |
| |
| Dispenses coffee, orderProceed () |
| ---------------------------------------------------------------------------------------------- |
| |
| |
| If insert more amount |
| |
| |
| Return Change |
| ------------------------------------------------------------------------------------------------ |
| |

Question 8

Page 6 of 7
Member
Several

Make

Reservation Loan

Reserved
Many

Book Copy
Has

Combination

Author/ISBN

Page 7 of 7