Object Oriented Static Modeling Of The Banking System 1-Software Requirement-Lecture Slides, Slides of Software Project Management

Download Object Oriented Static Modeling Of The Banking System 1-Software Requirement-Lecture Slides and more Slides Software Project Management in PDF only on Docsity!

1

Object-Oriented Static Modeling of

the Banking System - I

Lecture # 31

2

Steps in Object-Oriented Analysis

• Identify classes within the problem

domain

• Define the attributes and methods of

these classes

• Define the behavior of those classes• Model the relationship between those

classes

4

Identification of Objects and Classes - 2• Identify specific roles played by

individuals

• Identify physical locations that need to

be known

• Identify organizations that humans

belong to

5

Identification of Objects and Classes - 3• Identify catalogs that have to record

quantities of repetitive, staticinformation about things

7

External Device I/O Objects - 1

• A concrete entity in the application domain

is an entity that exists in the real world andhas some physical attributes

• For every concrete entity in the real world

that is relevant to the application domain,there should be a corresponding softwareobject in the system

8

External Device I/O Objects - 2

• Each software object hides the details of the

interface to the real world entity that itreceives input from or provides outputs to.However, a software object models theevents experienced by the concrete entity towhich it corresponds. The eventsexperienced by the entity are inputs to thesystem, particularly to the software objectthat models the entity

10

User Role Objects - 1

• A user role object models a role played

in the application domain, typically bya user. A role is a sequence of relatedactions performed sequentially by auser

• If a user can play two or more

independent roles, then this may berepresented by a different object foreach role

11

User Role Objects - 2

• Examples
  • Machine Operator– Loan Officer

13

Control Objects - 2

• A control object receives incoming

events that cause state transitions

• It generates output events that control

other objects or functions

• In a real-time system, there are usually

one or more control objects

14

Control Objects - 3

• Examples
  • Elevator control

16

Data Abstraction Objects - 2

• Locations and organizations are

examples of objects that need to beremembered

• A data abstraction object is a passive

object

• The basis for a data abstraction object

is a data store

17

Algorithm Objects - 1

• An algorithm object encapsulates an

algorithm used in the problem domain

• This kind of object is more prevalent in

real-time domains

• Example
  • Scheduler object

19

Problem Description - 1

-^

A bank has several automated teller machines (ATMs), which aregeographically distributed and connected via a wide area network to acentral server. Each ATM machine has a card reader, a cash dispenser,a keyboard/display, and a receipt printer. By using the ATM machine,a customer can withdraw cash from either checking or savingsaccount, query the balance of an account, or transfer funds from oneaccount to another. A transaction is initiated when a customer insertsan ATM card into the card reader. Encoded on the magnetic strip onthe back of the ATM card are the card number, the start date, and theexpiration date. Assuming the card is recognized, the system validatesthe ATM card to determine that the expiration date has not passed, thatthe user-entered PIN (personal identification number) matches the PINmaintained by the system, and that the card is not lost or stolen. Thecustomer is allowed three attempts to enter the correct PIN; the card isconfiscated if the third attempt fails. Cards that have been reported lostor stolen are also confiscated.

20

Problem Description - 2

-^

If the PIN is validated satisfactorily, the customer is prompted for awithdrawal, query, or transfer transaction. Before withdrawaltransaction can be approved, the system determines that sufficientfunds exist in the requested account, that the maximum daily limit willnot be exceeded, and that there are sufficient funds available at thelocal cash dispenser. If the transaction is approved, the requestedamount of cash is dispensed, a receipt is printed containing informationabout the transaction, and the card is ejected. Before a transfertransaction can be approved, the system determines that the customerhas at least two accounts and that there are sufficient funds in theaccount to be debited. For approved query and transfer requests, areceipt is printed and card ejected. A customer may cancel atransaction at any time; the transaction is terminated and the card isejected. Customer records, account records, and debit card records areall maintained at the server.