1. Oct. 2, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #5 Thursday, Oct. 2, 2003

2. Oct. 2, 2003CS 509 - WPI2 §Term Project administration §Return Quiz #2 §Questions §Brief review of Chapter 3 §Communications Exercise §Beginning Design Discussion & Exercise Class Format for Today

3. Oct. 2, 2003CS 509 - WPI3 MC Project & Quiz #2 §Turn in Phase 2 (Functional Specifications) document §Hand out Phase 3 Assignment §Return Quiz #2 l Solutions available on course web site

4. Oct. 2, 2003CS 509 - WPI4 Questions? §About Term Project §From last week’s class §From the reading §Anything else?

5. Oct. 2, 2003CS 509 - WPI5 Chapter 3 Project Communication

6. Oct. 2, 2003CS 509 - WPI6 Running a successful meeting §What is the purpose of holding a meeting? §What are the elements of a good meeting? l What are the roles? l What do you need to prepare? l What should you take away? §What are some common things that go wrong in meetings?

7. Oct. 2, 2003CS 509 - WPI7 Meeting Purpose §Enable a number of participants to: l Share ideas within a team l Get input from outside the team l Brainstorming - coming up with new ideas l Schedule a project or phase of development l Review status of work completed so far l Bring up & discuss current problems l Negotiate & resolve issues

8. Oct. 2, 2003CS 509 - WPI8 Successful Meeting Elements §Meeting facilitator - responsible for: l Organizing, scheduling l Creating an agenda l Keeping the meeting on track §Minute taker - responsible for: l Taking notes to record discussion l Capturing open issues l Distributing minutes after the meeting

9. Oct. 2, 2003CS 509 - WPI9 What participants should do §Help facilitator to keep the meeting on track l Everyone has the responsibility for making a meeting successful §Prepare in advance l If you have an agenda, know what you need to say §Be a good listener l When someone else is speaking, don’t interrupt

10. Oct. 2, 2003CS 509 - WPI10 What sometimes goes wrong? §Scheduling difficulties, inappropriate attendance §Facilitator isn’t prepared and/or is disorganized §Discussion gets too detailed or gets off track §Obstructions to effective communication: l Interruptions, taking things out of context, defensiveness, finger pointing, etc. §No effective follow-up: l No minutes, or nothing done with minutes

11. Oct. 2, 2003CS 509 - WPI11 Communications Exercise Status Meeting (Role Playing)

12. Oct. 2, 2003CS 509 - WPI12 Design Discussion §Goals of Design phase §How to begin? l Top-down, divide & conquer strategy l Start with general statements, then refine §High-level architecture vs. detailed classes §Architecture design pattern: l Model-View-Controller

13. Oct. 2, 2003CS 509 - WPI13 Design Exercise §Choose a widely-understood system to begin to design l Word Processor l File System Explorer l Internet Browser l E-commerce (e.g., Amazon.com) l Other ideas?

14. Oct. 2, 2003CS 509 - WPI14 For Next Time Chapter 6 System Design