CS%20509%20Design%20of%20Software%20Systems

1
CS 509Design of Software Systems

• Lecture 5
• Thursday, Oct. 2, 2003

2
Class Format for Today

• Term Project administration
• Return Quiz 2
• Questions
• Brief review of Chapter 3
• Communications Exercise
• Beginning Design Discussion Exercise

3
MC Project Quiz 2

• Turn in Phase 2 (Functional Specifications)
  document
• Hand out Phase 3 Assignment
• Return Quiz 2
• Solutions available on course web site

4
Questions?

• About Term Project
• From last weeks class
• From the reading
• Anything else?

5
Chapter 3

• Project Communication

6
Running a successful meeting

• What is the purpose of holding a meeting?
• What are the elements of a good meeting?
• What are the roles?
• What do you need to prepare?
• What should you take away?
• What are some common things that go wrong in
  meetings?

7
Meeting Purpose

• Enable a number of participants to
• Share ideas within a team
• Get input from outside the team
• Brainstorming - coming up with new ideas
• Schedule a project or phase of development
• Review status of work completed so far
• Bring up discuss current problems
• Negotiate resolve issues

8
Successful Meeting Elements

• Meeting facilitator - responsible for
• Organizing, scheduling
• Creating an agenda
• Keeping the meeting on track
• Minute taker - responsible for
• Taking notes to record discussion
• Capturing open issues
• Distributing minutes after the meeting

9
What participants should do

• Help facilitator to keep the meeting on track
• Everyone has the responsibility for making a
  meeting successful
• Prepare in advance
• If you have an agenda, know what you need to say
• Be a good listener
• When someone else is speaking, dont interrupt

10
What sometimes goes wrong?

• Scheduling difficulties, inappropriate attendance
• Facilitator isnt prepared and/or is disorganized
• Discussion gets too detailed or gets off track
• Obstructions to effective communication
• Interruptions, taking things out of context,
  defensiveness, finger pointing, etc.
• No effective follow-up
• No minutes, or nothing done with minutes

11
Communications Exercise

• Status Meeting
• (Role Playing)

12
Design Discussion

• Goals of Design phase
• How to begin?
• Top-down, divide conquer strategy
• Start with general statements, then refine
• High-level architecture vs. detailed classes
• Architecture design pattern
• Model-View-Controller

13
Design Exercise

• Choose a widely-understood system to begin to
  design
• Word Processor
• File System Explorer
• Internet Browser
• E-commerce (e.g., Amazon.com)
• Other ideas?

14
For Next Time

• Chapter 6
• System Design