1 / 5

Chapter 3: Case Studies

Chapter 3: Case Studies. 3.1. What is and is not Covered in the Case Study?. Traditional business software applications include UI elements, core application logic, database access and links to external software or hardware:

cachet
Download Presentation

Chapter 3: Case Studies

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. Chapter 3: Case Studies

  2. 3.1. What is and is not Covered in the Case Study? • Traditional business software applications include UI elements, core application logic, database access and links to external software or hardware: • To learn about OOA and D using UML we will focus on the core application logic layer; • These core skills can transfer to other layers and other application styles; • See Fig 3.1 for simple layer architecture scheme • Our focus is on OOA and D using the UML.

  3. Fig 3.1 Simple Layer Architecture Scheme

  4. 3.3 Case One: The NextGen POS System • A point-of-sale (POS) system: • A computerised application used to record sales and handle payment; • It includes hardware (Terminals, card readers etc.); • It interfaces to various external applications (inventory control, banking software etc.); • May support multiple and varied client-side interfaces (thin terminals, web browser, desktops etc.); • May be generic so that it can be sold to many clients (shop-chains) in various countries (which adds complexity);

  5. 3.4 Conclusion • Remember our focus is on learning to apply the UML for OOA and D within an iterative, evolutionary and agile process: • It is not about coding, graphics or UIs; • Questions Please

More Related