1. Feb. 2, 2004CS 509 - WPI1 CS 509 Design of Software Systems Lecture #3 Monday, Feb. 2, 2004

2. Feb. 2, 2004CS 509 - WPI2 §Term Project Administration §Return Quiz #1 §Questions §Brief review of Chapter 3: l Project Communication §In Class Exercise: l First Team Meeting Class Format for Today

3. Feb. 2, 2004CS 509 - WPI3 CTS Project & Quiz #1 §Return Phase 1 (Requirements) documents and Journals §How is Phase 2 going? §Return Quiz #1 l Solutions available soon on course web site

4. Feb. 2, 2004CS 509 - WPI4 Questions? §From last week’s class §From the reading §About the CTS Project §Anything else?

5. Feb. 2, 2004CS 509 - WPI5 Chapter 3 Project Communication

6. Feb. 2, 2004CS 509 - WPI6 Overview §Software engineering participants §Types of communication §Roles & Responsibilities §Anatomy of a meeting

7. Feb. 2, 2004CS 509 - WPI7 SW Engineering Participants §A collaborative activity involving l Domain experts, Analysts, Designers/Architects l Programmers, Managers, Technical Writers l QA Engineers, Graphic Designers, Users §No single person can understand or control all aspects of the system under development §Changes require participants to update their understanding of the system

8. Feb. 2, 2004CS 509 - WPI8 Types of Communication §Development & Client Review status meetings §Through documents: requirements, design, etc. §Handle crises and misunderstandings: l Phone calls, email messages, hallway conversations §Brainstorming sessions, design meetings §Bug fixing / Release management meetings §Postmortem reviews

9. Feb. 2, 2004CS 509 - WPI9 Roles & Responsibilities §See Table 3-1, page 87 §Cross-functional roles l API engineer, document editor l Configuration manager, tester §Consultant roles l Application & solution domain specialists l Client, end user

10. Feb. 2, 2004CS 509 - WPI10 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?

11. Feb. 2, 2004CS 509 - WPI11 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

12. Feb. 2, 2004CS 509 - WPI12 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

13. Feb. 2, 2004CS 509 - WPI13 What participants should do §Help facilitator to keep the meeting on track l Everyone is responsible 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

14. Feb. 2, 2004CS 509 - WPI14 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

15. Feb. 2, 2004CS 509 - WPI15 Communication Exercise Our First Team Meeting

16. Feb. 2, 2004CS 509 - WPI16 Meeting Agenda §Objective: l To produce comprehensive requirements for CTS §Tasks: l Come up with general outline for new document l Review individual documents for errors/omissions l Edit (cut & paste) into single document §Request for volunteer: l To record minutes

17. Feb. 2, 2004CS 509 - WPI17 For Next Time §Read Chapters 6 & 7: System Design §Reminders: l Phase 2 (Functional Specifications) Due l Quiz #2 on Chapters 3, 5, 6