meeting -*- Outline -*- * summary and review ** what to read in the rest of the books Design patterns, esp. Decorator, Visitor Larman's: generalization (26), statecharts (ch 29), packages (30), architecture (32), issues/topics (part VI) Fowler's book gives a good perspective on UML notation and the process Reil gives some good design advice for OO design ** technical ideas Q: what technical ideas did we discuss? iterative development, layered architecture separation of UI from code (using controller, observer) requirements analysis, use cases (actors, goals), separation of use cases from UI non-functional vs. functional requirements system boundary domain model, associations, attributes contracts (pre- and postconditions) GRASP patterns/principles (info expert, creator, low coupling, high cohesion, controller, polymorphism, pure fabrication, indirection, protected variations) visibility GoF Design patterns: Adapter, Factory, Singleton, Strategy, Composite, Facade, Observer, Template Method, State, Command) ** intuitions Q: what intuitions did we discuss? importance of feedback risk (and addressing it early) design vs. analysis, design mimicing analysis as much as possible protected variations indirection to achieve flexibility (e.g., polymorphism) ** relationships/questions Q: what kind of questions did we ask? Low coupling? Highly Cohesive? ** limits Q: what are the limits of what we've studied so far? Doesn't deal with concurrency, components, domian knowledge, ...