1 / 28

Withdrawal Transaction Use Case

Withdrawal Transaction Use Case. Primary Actor: Customer Pre-conditions: The customer must have a valid ATM card and PIN. Post-conditions: The customer receives the cash amount that he wanted to withdraw, with a receipt, if indicated.

landon
Download Presentation

Withdrawal Transaction Use Case

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Withdrawal Transaction Use Case Primary Actor: Customer Pre-conditions: The customer must have a valid ATM card and PIN. Post-conditions: The customer receives the cash amount that he wanted to withdraw, with a receipt, if indicated. The customer’s account balance is updated in the system. Normal flow of events: 1. The customer inserts ATM card into the ATM machine and enters PIN. 2. The system validates the ATM card and PIN . 3. The customer selects the ‘Cash Withdrawal’ option from the Options Menu. … Alternate flow of events: 1. The customer has entered invalid PIN; The system prompts the customer to enter a valid PIN. 2. If ATM card is not compatible-The system rejects the ATM card and displays an error message ….

  2. Review

  3. «local precondition» Have a license To motorway tollgate Go to the station with a friend Catch the ticket Buy the ticket Obliterate the ticket The friend goes home Exit to xxxxx tollgate Get luggage ready Go home with the car Study for 5 minutes Go to Heaven/ Hell ;) Go to Heaven/Hell ;) Fill up with fuel Pay the ticket Get off the train Go home with bus Catch the train Car crash Turn on the car [else] [on car] [the tank is full] [on train] The train derail When the train arrives to xxxxx [else] [xxxxx is a long way]

  4. Strategy Pattern

  5. Decorator Pattern

  6. UML Summary • UML: a graphical language for modeling and designing software • Semi-formal models using syntax and semantics • UML 2.0 standard • 3 stages of design before coding: business modeling (initiation), requirement analysis (what to do), architecture (how to do it) • UML as a family of languages: extensibility - UML for real-time systems, e.g., meta-class, constraints • Best open source UML tools: http://apps.open-libraries.com/best-OPEN-source-uml-tools/

  7. UML Diagrams Summary • Use Case Diagram: actor and use cases • 2 usage: mainly for requirement (sometimes business modeling), a communication between users, customers, designers • 4 elements: actor, system boundary, use cases, association • 4 rules to write good use case diagram: less ambiguity, complete, consistent, no design details - cross check with text requirement • 3 use case relations: include, extend, generalization/specialization • 4 key elements in use cases: name, actor, pre/post conditions, flow (main, alternative flows), sometimes relations with other use cases

  8. UML Diagrams Summary • Sequence diagram: object interactions • Requirement analysis – describe use cases, find more objects • 4 elements: objects (actor), lifetime, activation, messages

  9. UML Diagrams Summary • Class Diagram: class and class relations • Requirement and architecture design • 3 elements: name, attribute (optional), operation (optional) • 2 types of class relations: association (aggregation/composition), generalization/specialization – inheritance • Identify names in the requirement as classes

  10. UML Diagrams Summary • Activity diagram: capture an activity/action -- unit of executable functionality • Business modeling, requirement - both data and control flow, concurrent modeling • 2 types of elements • Activity nodes • Parameter nodes • Action nodes • Control nodes: decision/merge, join/fork, initial/final/flow final • Object nodes (pin): value pin, exceptional pin • Activity edges • Direct, Weight (optional) - the minimum number of tokens that must traverse the edge at the same time • Control /object edges

More Related