Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

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

This course includes types of requirements, modeling of non functional, static and dynamic modelling, requirement elicitation and use case modeling. This lecture includes: Problem, Description, Entity, Class, Banking, System, String, Customer, Address

Typology: Slides

2011/2012

Uploaded on 08/07/2012

angana
angana 🇮🇳

4.4

(51)

159 documents

1 / 28

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
Object-Oriented Static Modeling of
the Banking System - II
Lecture # 32
docsity.com
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c

Partial preview of the text

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

1

Object-Oriented Static Modeling of

the Banking System - II

Lecture # 32

2

Problem Description

-^ 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.

4

Problem Description

-^ An ATM operator may start up and close down the ATM to replenishthe ATM cash dispenser and for routine maintenance. It is assumedthat functionality to open and close accounts and to create, update, anddelete customer and debit card records is provided by an existingsystem and is not part of this problem.•^ ‘Designing Concurrent, Distributed, and Real-Time Applications withUML’ by H. Gomaa, Addison-Wesley, 2000

5

Entity Classes in Banking System

7

Entity Classes in the Banking

System

DebitCard cardID: StringPIN: StringstartDate: DateexpirationDate: Datestatus: Integerlimit: Realtotal: Real

Account accountNumber: Stringbalance: Real

8

Entity Classes in the Banking

System

CheckingAccountlastDepositAmount: Real

SavingsAccount interest: Real

10

Entity Classes in the Banking

System

WithdrawalTransactionaccountNumber: Stringamount: RealBalance: Real

QueryTransactionaccountNumber: Stringamount: ReallastDepositAmount: Real

11

Entity Classes in the Banking

System

TransferTransaction fromaccountNumber: StringtoAccountNumber: Stringamount: Real

13

Entity Classes in the Banking

System

ATMCash cashAvailable: IntegerfiveHundreds: IntegeroneThousands: Integer

ATMCard cardID: StringstartDate: DateexpirationDate: Date

14

Interface Classes for External

Objects

16

User Interface Classes in the

Banking System

OperatorInterface

CustomerInterface

17

System and Subsystem Classes

19

A Bank Has Many ATMsBank

ATM

Has 1

20

An Operator Maintains an ATM

ATM

Operator

Maintains 1