nov. 13, 2003cs 509 - wpi1 cs 509 design of software systems lecture #11 thursday, nov. 13, 2003

23
Nov. 13, 2003 CS 509 - WPI 1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Post on 21-Dec-2015

213 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 1

CS 509Design of Software Systems

Lecture #11Thursday, Nov. 13,

2003

Page 2: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 2

Term Project administrationReturn Quiz #5QuestionsReview of Chapter 11Project Management exercises

Class Format for Today

Page 3: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 3

MC Project & Quiz #5

Return Quiz #5 – solutions available on course web site.

How is implementation going? Proceeding according to schedule?

Page 4: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 4

Questions?

About Term ProjectFrom last week’s classFrom the readingAnything else?

Page 5: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 5

Chapter 11

Project Management

Page 6: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 6

Purpose of Management

Managers do not generate any work products of their own

Managers do not make technical decisions

Managers often do not have technical skills

What skills do they have/need?What is their purpose/function?

Page 7: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 7

Management Skills, Functions

Organizational skills – why are these needed?

People skills – such as?Time & resource management

skills, etc.

To ensure the delivery of a quality system on time and within budget

Page 8: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 8

Project Mgmt Terminology

TeamsRolesWork ProductsTasksSchedules

Page 9: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 9

Project Phases

Project Initiation Define scope and resources

Steady State Majority of development effort

Project Termination System is delivered and accepted

What activities are involved in each?

Page 10: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 10

Project Initiation

Problem statement definitionInitial top-level designTeam formationCommunication Infrastructure

setupInitial milestones planningProject kickoff

Page 11: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 11

Steady State

Project agreement definitionStatus monitoringRisk assessment & managementProject replanning

Page 12: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 12

Project Termination

Client acceptance testsInstallationPostmortem

Page 13: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 13

Project Communication

Needs to occur during all phases of project

Must be timely and accurateStructure of communication

Developers to team leaders Team leaders to project manager Project manager to higher-level

managementDifferent levels/types of communicationWhat can go wrong here?

Page 14: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 14

Team Communication

What is the definition/purpose of a liaison? Examples of where a liaison is

useful?What is a cross-functional team?

Examples?

Page 15: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 15

Team Associations

Reporting association Used for reporting status

Decision association Used for propagating decision

informationCommunication association

Used for exchanging info needed for decisions

Page 16: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 16

Hierarchical Organization

Cathedral modelBazaar model

What do these terms refer to?How does each model function?How do they differ?Movement from one to the other

Page 17: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 17

Project Roles

ManagementDevelopmentCross-functionalConsultantPromoter:

Power, knowledge, process

Page 18: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 18

Other Management Concepts

Work ProductsTasksSchedules

What are the relationships between these?

Page 19: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 19

Project Monitoring

Meetings Status, milestones, reviews,

inspections, demosMetrics

Defects to be resolved Source code metrics – such as?

Page 20: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 20

Risk Management

Identifying risks – managerial or technical How are they identified? Examples?

Prioritizing risks How likely, what impact?

Mitigating risks How to decrease likelihood and/or impact

Communicating risks

Page 21: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 21

Other Management Activities

Project agreement document Scope, duration, cost and

deliverablesClient acceptance testsInstallationPostmortem

Page 22: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 22

Project Management Exercises

From text book, page 453 Split into groups to discuss:

1. Exercise #42. Exercise #53. Exercise #74. Exercise #8

Present results to class

Page 23: Nov. 13, 2003CS 509 - WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003

Nov. 13, 2003 CS 509 - WPI 23

For Next Time

Chapter 12Software Life Cycle