ATM Project Abstract

All the business abstracts were reconciled or conflated into a single summary of scope that is consistent with
the sponsor’s mission statement. It also highlights those items mentioned in the Business Abstracts that are
out of scope. It must be clear to the stakeholders if and when they are not going to get what they expect.

The project abstract includes a context diagram, and for convenience to the reader, an equivalent stakeholder
relationship table for comparison purposes.

Automated Teller Machine Carolla Development, Inc.

Sample Project Application January, 2014

Project Increase customer access, bank profit, and security by implementing an

Mission automated teller (ATM) network that customers will accept as a suitable
alternative to regular tellers for their demand deposit transactions.

System Responsibilities

Objective 1 Customer Transactions: Enable processing of simple (deposit, withdrawal,

transfer, balance) transactions against demand deposit (checking, savings)
accounts. Each transaction must be individually verified against transaction
limits and account accessibility. Account balances must be updated at
transaction commit.

Objective 2 Security: Provide robust transaction security and customer authentication.

Customer need only be authenticated at beginning of ATM session. Cashier
needs to be authenticated for administrative transactions.

Objective 3 Administration: Cashier has special transactions to (1) load money and
initiate ATM software, (2) collect reconcilement report, and (3) to shut down
ATM system software.

Objective 4 Performance: Provide for nominal transaction volume to be 30% higher than
current volume, and peak volume to be 100% higher. Network should be
available 22 hours per day, 7 days a week. Hold cost per transaction, at
nominal transaction volume, at least 20% below that of regular teller
transactions.

Objective 5 Logging: Provide transaction logging which is consistent with current

transaction reporting.

Not Loan, mortgage, utility bill payments, credit card transactions (not demand
Included: deposits). Customer control of permissible transactions (account either
available or not). Complex security issues.
 Figure 3- 1. ATM Context Diagram

Actor Workflow Data In Data Out

Customer Demand Deposit Transactions authorization data, cash, receipt
cash, check, money
orders
Admin Add cash to machine; remove authorization data cashbox balance,
currency & reconcile machine deposits, reconcilement
report
Bank Data System Maintain customer data and updated customer transaction log
transaction records profiles & accounts

* Demand Deposit transactions is a banking term that means those transactions available to walk-in customers; i.e., deposits, withdrawals,
transfers, and inquiries.

NOTES

1. Mission Statement. The mission statement was taken verbatim from the project synopsis. The PM may
decide to share the entire synopsis with the stakeholders, but often that causes unnecessary discussion on
how the sponsor set up the project.

2. Not Included. Anything mentioned in the Business Abstracts but that is out of scope for one reason or
another, is listed in this section. The customer wanted bill payments and cash advances from credit cards,
but the sponsor choose to defer that until the core ATM system functionality was up and running. If a
stakeholder has a problem with that, that person can escalate to the sponsor and get it changed if the sponsor
is willing to pay for it.

3. Responsibility 4: The customer wanted access to the ATM 24/7, but the final access time was set to 22/7 to
allow some time for maintenance.