Nov. 6, 2003 CS 509 - WPI 1

CS 509Design of Software Systems

Lecture #10Thursday, Nov. 6, 2003

Nov. 6, 2003 CS 509 - WPI 2

Term Project administrationQuestionsQuiz #5Review of Chapter 10

Class Format for Today

Nov. 6, 2003 CS 509 - WPI 3

MC Project

Return Phase 4 (Test & Implementation Plan) documents

How is implementation going? Proceeding according to schedule?

Nov. 6, 2003 CS 509 - WPI 4

Questions?

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

Nov. 6, 2003 CS 509 - WPI 5

Quiz #5

Chapters 8 & 10You have 15 minutes.

Nov. 6, 2003 CS 509 - WPI 6

Chapter 10

Configuration Management

Nov. 6, 2003 CS 509 - WPI 7

Purpose of Config. Mgmt.

Controlling and monitoring change to work products

Automate the identification of versions

Why is this necessary?

Nov. 6, 2003 CS 509 - WPI 8

Terminology

Configuration Item / AggregateVersion / BaselinePromotion / ReleaseBranch / VariantRepository / WorkspaceChange RequestStatus Accounting / Auditing

Nov. 6, 2003 CS 509 - WPI 9

Config. Mgmt. Activities

Build Management Automated process for building a SW

system Why is this useful?

Process Management Allow for policy enforcement What policies might need to be

enforced?

Nov. 6, 2003 CS 509 - WPI 10

Version Identification Schemes

Code names, Digits in PiVersion numbers usually include:

Major version, Minor version, Revision Sometimes build number, service pack, etc.

Examples: Microsoft PowerPoint 2000, 9.0.2716 Microsoft Windows 2000, 5.0 (build 2195,

SP4) Opera Browser, 7.0 (build 2637) Java 2 Runtime Environment, 1.4.2 (build

b28)

Nov. 6, 2003 CS 509 - WPI 11

Config. Mgmt. Tools

RCS: Revision Control SystemCVS: Concurrent Version SystemPerforce, ClearCase, StarTeamUsually store deltas, most support

branching & mergingLocking vs. Sharing

Nov. 6, 2003 CS 509 - WPI 12

Config. Mgmt. Items

Most common is source code Why?

Other items include SW Eng. documents RAD, SDD, ODD, Test Plans, etc.

Why is CM useful for such documents?

Nov. 6, 2003 CS 509 - WPI 13

Braches and Variants

When is it appropriate to create a branch?

Why create multiple variants?

What problems do these items solve?

What new problems do these items create?

Nov. 6, 2003 CS 509 - WPI 14

Change Management Process

Request for changeAssess requestReject or Approve requestAssign responsibility for changeImplement changeValidate change

Nov. 6, 2003 CS 509 - WPI 15

For Next Time

Chapter 11Project Management