“I bought this guide a few days ago to prepare for my interview with Oracle. Many of the questions they asked me were from this guide. I found this book absolutely great!”
ATM machine would “eat” your card if you give “three strikes” failure. This is what I hate the most. So I would add a feature so that a user could regain the card. For example, let user have way to add a secrete question and answer to that question.
I would eliminate the need for a physical card an opt for some kind of biometric id such as a retinal scan or somesuch.
I would orient the display to eliminate the opportunity for overlookers to view it - ie. make it horizontal like a table.
I would eliminate the masking of account information behind names such as ‘checking’, ’savings’, etc. and ensure that at least the balances are always displayed. This would help eliminate a good deal of ‘you don’t have enough funds’-type msgs.
Add an Undo capability where appropriate, i.e. for transfers/deposits. It would also negate any costs associated with the original transaction.
Remember the most common transactions done by the user and make them macros automatically.
I would add a way for the system to intermingle different languages during the transaction. This way, you could learn how to take out money in foreign languages while you were at the bank machine. Cool.
I guess you might be misleading by the question. To the best of my knowledge, ATM in computer network means Asynchronous Transfer Mode. It is a cell swtiching techology competing with Ethernet switching develop in the ealy 80s. ATM is a connection-oriented, packet-switched technology using virtual circuits. In order to re-design an ATM, you must understand what ATM is. Please review AAL5 (ATM Adaptation Layer 5) for info. For further info, please enter “ATM computer network” or appropriate words at yahoo.com or consult with any computer network books.
Just a reminder, two goal to design a packet switch (ATM) are the throughput of the swich and its scalability. It’s not an easy solution. Requires some research work and understanding of ATM. If you are looking for a networking position, good to know this before the interview.
First, it’s clear from the question “an ATM” that this is about a teller machine and not Async Tranfer. Second, you have to decide what your are optimizing *for*. Some possibilities are: security, user interface, user privacy, minimize datacom traffic, make ATM cheaper to build/program. Like all engineering, it’s a matter of balancing tradeofs. If we were optimizing for user interface, the first thing to do is to analyze what we’re doing to annoy current users and stop doing that (application of basic Hyppocratic oath “above all do no harm”). One basic UI problem I’ve noticed with many ATMs is that the keyboard is not near the screen. Users need to keep shifting eye focus. This change might make ATMs more expensive to build… so we’re back to making engineering tradeoffs.
ATM’s are designed to give you back your card after you have retrieved the money, hence why many people forget their card at the ATM, they already have what they came for. I would design an ATM that would not give you your money until you removed the card, so you would never forget it.
It is very clear to me this question IS about Async Transfer Mode. Because this is a section about I.T. not about banking or automated teller machines.
As stated before “If you are looking for a networking position, good to know this before the interview”.
no need to have ATM’s if every body has credit card and every shop excepts credit cards.just discard it rather than re-designing it.money should be replaced with digital electronics.all money should exist in computers only in terms of numbers,not as physical entity.that’s all.
ATM machine would “eat” your card if you give “three strikes” failure. This is what I hate the most. So I would add a feature so that a user could regain the card. For example, let user have way to add a secrete question and answer to that question.
I would eliminate the need for a physical card an opt for some kind of biometric id such as a retinal scan or somesuch.
I would orient the display to eliminate the opportunity for overlookers to view it - ie. make it horizontal like a table.
I would eliminate the masking of account information behind names such as ‘checking’, ’savings’, etc. and ensure that at least the balances are always displayed. This would help eliminate a good deal of ‘you don’t have enough funds’-type msgs.
Add an Undo capability where appropriate, i.e. for transfers/deposits. It would also negate any costs associated with the original transaction.
Remember the most common transactions done by the user and make them macros automatically.
I could go on forever!
I would add a way for the system to intermingle different languages during the transaction. This way, you could learn how to take out money in foreign languages while you were at the bank machine. Cool.
I guess you might be misleading by the question. To the best of my knowledge, ATM in computer network means Asynchronous Transfer Mode. It is a cell swtiching techology competing with Ethernet switching develop in the ealy 80s. ATM is a connection-oriented, packet-switched technology using virtual circuits. In order to re-design an ATM, you must understand what ATM is. Please review AAL5 (ATM Adaptation Layer 5) for info. For further info, please enter “ATM computer network” or appropriate words at yahoo.com or consult with any computer network books.
Just a reminder, two goal to design a packet switch (ATM) are the throughput of the swich and its scalability. It’s not an easy solution. Requires some research work and understanding of ATM. If you are looking for a networking position, good to know this before the interview.
Good luck.
First, it’s clear from the question “an ATM” that this is about a teller machine and not Async Tranfer.
Second, you have to decide what your are optimizing *for*.
Some possibilities are: security, user interface, user privacy, minimize datacom traffic, make ATM cheaper to build/program.
Like all engineering, it’s a matter of balancing tradeofs.
If we were optimizing for user interface, the first thing to do is to analyze what we’re doing to annoy current users and stop doing that (application of basic Hyppocratic oath “above all do no harm”). One basic UI problem I’ve noticed with many ATMs is that the keyboard is not near the screen. Users need to keep shifting eye focus. This change might make ATMs more expensive to build… so we’re back to making engineering tradeoffs.
I know i require SINGLES ( i live on vending Machines), so i would design it to give an option for the denomination
ATM’s are designed to give you back your card after you have retrieved the money, hence why many people forget their card at the ATM, they already have what they came for. I would design an ATM that would not give you your money until you removed the card, so you would never forget it.
It is very clear to me this question IS about Async Transfer Mode. Because this is a section about I.T. not about banking or automated teller machines.
As stated before “If you are looking for a networking position, good to know this before the interview”.
no need to have ATM’s if every body has credit card and every shop excepts credit cards.just discard it rather than re-designing it.money should be replaced with digital electronics.all money should exist in computers only in terms of numbers,not as physical entity.that’s all.
Leave an Answer/Comment