Review Session

1. Review Session • URS Results • Practice Workshop Feedback • Schedule for the week • Tuesday lecture – Practice Examples • Wednesday afternoon Project/Test Queries • Collect Test/URS/Workshop documents from IS Reception • Please check notice board to confirm results • Wednesday Wrap-up • Course Overview • Course Evaluation • Exam Preparation

2. URS Results • URS Documents were well prepared • Class Average 64% • Top Project – Rajesh Lalla and Lebohang Motloung • Feedback sheet with each project • Collect from IS Reception • Any queries – see me Wednesday afternoon

3. Workshop 7 Feedback: Bookworm.com

4. Use Case Diagram Approach • Need to focus on the big picture – the main business uses • Seller registers then lists books • Buyer purchases a book • And so on…… • Then think of the four types of “uses”: • Main business transactions • Maintenance requirements • Enquiries • Reporting • Finally add the detail • Extends and Includes

6. Class Diagram • Identify the main “things” in the Bookworm.com business environment • One good way is to follow the business workflow: • Sellers registers (opens an account) • Seller lists books • Buyer purchases books • No one solution • Payments can be attributes but better as classes (audit trail)

7. Bookworm.com Domain Class Diagram

8. Use Case Narrative

9. Use Case Narrative

10. Use Case Narrative

11. Systems Sequence Diagram

12. Use Case Diagram – ATM System Draw a use case diagram for an Automatic Teller Machine (ATM)System for a local bank. There will be other functions that could be performed by the ATM system but you must only document those described in the text.

13. Use Case Diagram – ATM System The ATM system will operate in the following way: • The bank customer will begin by placing their card in the card reader and entering their pin number. The ATM machine is able to authenticate the customer from a table of pin numbers held in the ATM. • Customers are able to make withdrawals, deposits and check their account balance. Customer often check their account balance during a withdrawal to determine how much they are able to withdraw. Customer account details are stored at the central banking system in Cape Town and all ATM’s are on-line to the central system 24 hours a day. The customer’s account balance is immediately updated after a deposit or withdrawal is made. • A bank maintenance officer regularly visits the ATM to refill the money dispenser and retrieve cheques that have been deposited.

14. Use Case Diagram – ATM System The ATM system will operate in the following way: • The bank customer will begin by placing their card in the card reader and entering their pin number. The ATM machine is able to authenticate the customer from a table of pin numbers held in the ATM. • Customers are able to make withdrawals, deposits and check their account balance. Customer often check their account balance during a withdrawal to determine how much they are able to withdraw. Customer account details are stored at the central banking system in Cape Town and all ATM’s are on-line to the central system 24 hours a day. The customer’s account balance is immediately updated after a deposit or withdrawal is made. • A bank maintenance officer regularly visits the ATM to refill the money dispenser and retrieve cheques that have been deposited.

16. ?

17. Domain Class Diagram You are currently computerizing the administrative systems for a Rondebosch medical practice. You are required to draw a domain class diagram to reflect the classes and the relationships required to support the Patient Administration System described below. On a patient’s first visit to the doctor, they fill in a form giving their personal details and medical aid number if they are a member of a medical aid scheme. Patients normally phone the receptionist to book an appointment with their doctor or one of the nurses depending on the treatment they require. Once the patent has seen the doctor or nurse, a bill is generated. The bill normally includes a consulting fee and any medicine purchased from the practice. This is the scope of the Administrative system. You are not required to model any other classes and relationships involved in out of scope activities such as the payment of the bill. Ensure all classes are labelled and associations between classes are drawn and labelled. Look for opportunities to use inheritance and aggregation in your model.

18. Domain Class Diagram You are currently computerizing the administrative systems for a Rondebosch medical practice. You are required to draw a domain class diagram to reflect the classes and the relationships required to support the Patient Administration System described below. On a patient’s first visit to the doctor, they fill in a form giving their personal details and medical aid number if they are a member of a medical aid scheme. Patients normally phone the receptionist to book an appointment with their doctor or one of the nurses depending on the treatment they require. Once the patent has seen the doctor or nurse, a bill is generated. The bill normally includes a consulting fee and any medicine purchased from the practice. This is the scope of the Administrative system. You are not required to model any other classes and relationships involved in out of scope activities such as the payment of the bill. Ensure all classes are labelled and associations between classes are drawn and labelled. Look for opportunities to use inheritance and aggregation in your model.