1 / 15

PaSOOS

PaSOOS. Programming of Large Object-Oriented Systems. PaSOOS. PaSOOS Three pieces Værktøjer og teknikker (ToolTech) Arkitektur, Patterns og Frameworks (APF ) Programmeringsprojekt (ProgProj) Audience Diploma Students Forthcoming Master Students. PaSOOS. ToolTech

shauna
Download Presentation

PaSOOS

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. PaSOOS Programming of Large Object-Oriented Systems Henrik Bærbak Christensen

  2. PaSOOS • PaSOOS • Three pieces • Værktøjer og teknikker (ToolTech) • Arkitektur, Patterns og Frameworks (APF) • Programmeringsprojekt (ProgProj) • Audience • Diploma Students • Forthcoming Master Students Henrik Bærbak Christensen

  3. PaSOOS • ToolTech • Focus on the supporting techniques for large systems • APF • Focus on the architecture and design of large systems (or at least some of it) • ProgProj • Try it out on a (small ) large system Henrik Bærbak Christensen

  4. Experience from Exam • Oral presentation  Henrik Bærbak Christensen

  5. Literature • Primary literature • Reliable and Flexible Software Explained (RFSE) •  Work in progress... •  Cheap! • Comments most welcome! • Compendium • Extracts from various books • Electronic material • Papers etc. posted on the web site. Henrik Bærbak Christensen

  6. RFSE Recurring Case: Pay Station Introduction to case study

  7. Case: Pay Station • Customer – Alphatown county: • The pay station must: • accept coins for payment • show time bought • print parking time receipts • US: 2 minutes cost 5 cent • handle buy and cancel • maintenance (empty it)

  8. Demo

  9. An initial design

  10. PayStation Interface

  11. Receipt and Exception

  12. Where we left it...

  13. TDD • Test-driven development of the pay station • The values • small steps, keep focus • The rhythm • quickly add test, red, add production code, green, refactor • Patterns • test list, test first, test • fake it till you make it (keep focus, small steps) + triangulate • isolated test, evident test, evident data • break, do over

  14. Next... • What I will do the next couple of weeks is to: • throw all sorts of new requirements at it • keep the production code ‘clean’ by refactoring • analyze my options carefully before committing to design • make it a pay station framework that is pretty configurable... • and derive a lot of design patterns as I go...

More Related