1 / 15

CS 509 Design of Software Systems

CS 509 Design of Software Systems. Lecture #10 Thursday, Nov. 6, 2003. Class Format for Today. Term Project administration Questions Quiz #5 Review of Chapter 10. MC Project. Return Phase 4 (Test & Implementation Plan) documents How is implementation going?

jerome-paul
Download Presentation

CS 509 Design of Software Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS 509Design of Software Systems Lecture #10 Thursday, Nov. 6, 2003 CS 509 - WPI

  2. Class Format for Today • Term Project administration • Questions • Quiz #5 • Review of Chapter 10 CS 509 - WPI

  3. MC Project • Return Phase 4 (Test & Implementation Plan) documents • How is implementation going? • Proceeding according to schedule? CS 509 - WPI

  4. Questions? • About Term Project • From last week’s class • From the reading • Anything else? CS 509 - WPI

  5. Quiz #5 Chapters 8 & 10 You have 15 minutes. CS 509 - WPI

  6. Chapter 10 Configuration Management CS 509 - WPI

  7. Purpose of Config. Mgmt. • Controlling and monitoring change to work products • Automate the identification of versions • Why is this necessary? CS 509 - WPI

  8. Terminology • Configuration Item / Aggregate • Version / Baseline • Promotion / Release • Branch / Variant • Repository / Workspace • Change Request • Status Accounting / Auditing 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? CS 509 - WPI

  10. Version Identification Schemes • Code names, Digits in Pi • Version 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) CS 509 - WPI

  11. Config. Mgmt. Tools • RCS: Revision Control System • CVS: Concurrent Version System • Perforce, ClearCase, StarTeam • Usually store deltas, most support branching & merging • Locking vs. Sharing 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? 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? CS 509 - WPI

  14. Change Management Process • Request for change • Assess request • Reject or Approve request • Assign responsibility for change • Implement change • Validate change CS 509 - WPI

  15. For Next Time Chapter 11 Project Management CS 509 - WPI

More Related