Shared by 
Unlock all 32 pages
Get it free by sharing your own notes, buy just this one, or become a member and unlock documents with your plan.
How to unlock this document
Choose the way that suits you. Each one gives you all 32 pages to read online and the PDF to download.
Share your notes, unlock for free
2 free unlocks for every 5 approved uploads
- Upload your own lecture notes, assignments, essays or past papers
- PDF, Word, PowerPoint and Excel files all work, and you can send many at once
- We check each upload; you get a notification when it is approved
- Spend a free unlock on this document or any other, and keep it for good
- Shared under your public username, never your email
Then upload your notes from your profile.
Buy this document
$32 one-time payment
- All 32 pages of this document, yours to keep
- Download the PDF and read it any time, also offline
- No subscription and nothing to cancel
- Find it again any time under My Profile → Library
You log in or create a free account first, then pay securely.
Become a member
Unlock documents from the whole library, which keeps growing
- Choose any documents you like, up to your plan’s unlocks
- Documents you unlock stay yours, even if you cancel later
- Your unlocks start again with every renewal
- Secure checkout by Dodo Payments
You log in or create a free account first, then pay securely.
Compare the plansAlready a member, or bought this before? Log in to open it
About this document
- Pages
- 32 pages
- Price
- $32 one-time, yours to keep
- Membership
- Included in every plan
- Format
- Subject
- Computer Science, Engineering
This document describes the process of software design for an ATM system, from requirements to maintenance. It details the analysis phase, including use cases and functional test cases. It is useful for understanding the software development process, particularly the analysis and design phases.
What's inside
- Software design process overview
- Analysis phase with use cases
- Functional test cases specification
- Overall design with CRC cards
- Detailed design and implementation
Who it is for: Students studying software engineering or computer science. (Undergraduate)
Share with classmates: WhatsApp Telegram X LinkedIn Facebook
Summary
Software design for an ATM system is described. Students learn about the process of analysis, design, and implementation.
System Requirements
An ATM system is described. The ATM will service one customer at a time. The ATM will communicate with the bank's computer over a communication link.
Analysis and Design
Use cases are identified and detailed. CRC cards are used to assign responsibilities to classes. State charts and interaction diagrams are used to develop the dynamic aspects of the design.
Detailed Design
Attributes and methods for each class are spelled out. A package diagram shows how the various classes are grouped into packages. Each class is implemented in Java.
Maintenance
Ideas for possible changes to the system are discussed. Changes to multiple documents, not just the code, are required.
Key terms
- Use Cases
- Scenarios that describe how users will perform tasks on the system.
- CRC Cards
- Cards that list the responsibilities and collaborators of each class.
- State Charts
- Diagrams that show the states of a system and the events that cause transitions between states.
- Interaction Diagrams
- Diagrams that show how objects interact with each other in a use case.
- Package Diagram
- A diagram that shows how classes are grouped into packages.
- Adaptive Maintenance
- Maintenance that involves changing the system to adapt to a new environment.
Questions this document helps with
- What are the requirements for an ATM system?
- How are use cases identified and detailed?
- What changes are needed for adaptive maintenance?
Summary written with AI from the document's text.
Ask the AI Teacher
Ask any question about this document or your course, and get a clear explanation.
Log in to ask Create a free account
Free accounts can ask 5 questions a day.