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

Slides:



Advertisements
Similar presentations
Page 1 October 31, 2000 An Introduction to Large-Scale Software Development Steve Varnau Core HP-UX Operation October 31, 2000.
Advertisements

Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Configuration Management Main issues:  manage items during software life cycle  usually supported by powerful tools.
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
CS 5521 Configuration Management the problem Not a simple task! –Different versions of software usually is in the field during the life cycle –Different.
1 Software Configuration Management METU Computer Engineering CEng 492 Spring'2004.
Feb. 2, 2004CS WPI1 CS 509 Design of Software Systems Lecture #3 Monday, Feb. 2, 2004.
Nov. 13, 2003CS WPI1 CS 509 Design of Software Systems Lecture #11 Thursday, Nov. 13, 2003.
Oct. 9, 2003CS WPI1 CS 509 Design of Software Systems Lecture #6 Thursday, Oct. 9, 2003.
Chapter 13 Configuration Management
Sept. 11, 2003CS WPI1 CS 509 Design of Software Systems Lecture #2 Thursday, Sept. 11, 2003.
CS 501 : An Introduction to SCM & GForge An Introduction to SCM & GForge Lin Guo
Oct. 2, 2003CS WPI1 CS 509 Design of Software Systems Lecture #5 Thursday, Oct. 2, 2003.
CSC 395 – Software Engineering Lecture 25: SCM –or– Expecting Change From Everything But Vending Machines.
Software Configuration Management (SCM)
Chapter 13: Configuration Management
Oct. 30, 2003CS WPI1 CS 509 Design of Software Systems Lecture #9 Thursday, Oct. 30, 2003.
Configuration & Build Management
Configuration Management
Software Configuration Management CSC-532 Chandra Shekar Kandi Chandra Shekar Kandi.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering November 14, 2001 Software.
Software Configuration Management (SCM)
CSSE 375 Software Construction and Evolution: Configuration Management
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Software Project Configuration Management
SE-02 CONFIGURATION MANAGEMENT Today we talk about Software Configuration Management (SCM for short): - What? - Why? - How?
Software Configuration Management (SCM)
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Software Engineering Modern Approaches
More RUP and Configuration Management CS3300 Fall 2015.
Software Configuration Management
Software Configuration Management (SCM)
1 Lecture 19 Configuration Management Software Engineering.
Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?
1 Software Development Configuration management. \ 2 Software Configuration  Items that comprise all information produced as part of the software development.
Chapter 4: Software Configuration Management (SCM)
Software Configuration Management
1 Introduction to Software Configuration Management CprE 556 Electrical and Computer Engineering Department Iowa State University.
Software Quality Assurance
CEN 5011 Ninth Lecture (2 nd part) Nov. 24, 2004 Advance Software Engineering (CEN-5011) Fall 2004 Instructor: Masoud Sadjadi
Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 13, Configuration Management.
CSSE 375 Software Construction and Evolution: More SCM, and a loop back to Feathers! Shawn and Steve Left – On big systems, SCM is a well-defined process.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa Configuration management.
Software Project Management
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 29 Slide 1 Configuration management.
Principles of Computer Security: CompTIA Security + ® and Beyond, Third Edition © 2012 Principles of Computer Security: CompTIA Security+ ® and Beyond,
Configuration Management Main issues:  manage items during software life cycle  usually supported by powerful tools ©2008 John Wiley & Sons Ltd.
Management of Software Project CSM Software Configuration Management (SCM)
Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner ’ s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi,
Software Configuration Management n Art of coordinating SW development to minimize confusion n Software quality assurance (umbrella) activity n Set of.
Feb. 9, 2004CS WPI1 CS 509 Design of Software Systems Lecture #4 Monday, Feb. 9, 2004.
CS 350, slide set 11 M. Overstreet Old Dominion University Spring 2006.
Configuration Management
March 1, 2004CS WPI1 CS 509 Design of Software Systems Lecture #6 Monday, March 1, 2004.
Software Engineering Lecture 9: Configuration Management.
1 Week 9 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
Source Control Repositories for Enabling Team Working Doncho Minkov Telerik Corporation
Configuration & Build Management. Why Software Configuration Management ? The problem: Multiple people have to work on software that is changing More.
 Software Configuration Management is the process of controlling and monitoring change to work products.  Or  “It is the art of identifying, organizing.
School of Business Administration
Software Configuration Management (SCM)
Configuration Management
Software Configuration Management CSC-532
Software Project Configuration Management
Chapter 10, Software Configuration Management
Chapter 11: Software Configuration Management
Software Configuration Management
Configuration Management (managing change)
Chapter 11: Software Configuration Management
Software Configuration Management
Presentation transcript:

Nov. 6, 2003CS WPI1 CS 509 Design of Software Systems Lecture #10 Thursday, Nov. 6, 2003

Nov. 6, 2003CS WPI2 §Term Project administration §Questions §Quiz #5 §Review of Chapter 10 Class Format for Today

Nov. 6, 2003CS WPI3 MC Project §Return Phase 4 (Test & Implementation Plan) documents §How is implementation going? l Proceeding according to schedule?

Nov. 6, 2003CS WPI4 Questions? §About Term Project §From last week’s class §From the reading §Anything else?

Nov. 6, 2003CS WPI5 Quiz #5 Chapters 8 & 10 You have 15 minutes.

Nov. 6, 2003CS WPI6 Chapter 10 Configuration Management

Nov. 6, 2003CS WPI7 Purpose of Config. Mgmt. §Controlling and monitoring change to work products §Automate the identification of versions §Why is this necessary?

Nov. 6, 2003CS WPI8 Terminology §Configuration Item / Aggregate §Version / Baseline §Promotion / Release §Branch / Variant §Repository / Workspace §Change Request §Status Accounting / Auditing

Nov. 6, 2003CS WPI9 Config. Mgmt. Activities §Build Management l Automated process for building a SW system l Why is this useful? §Process Management l Allow for policy enforcement l What policies might need to be enforced?

Nov. 6, 2003CS WPI10 Version Identification Schemes §Code names, Digits in Pi §Version numbers usually include: l Major version, Minor version, Revision l Sometimes build number, service pack, etc. §Examples: l Microsoft PowerPoint 2000, l Microsoft Windows 2000, 5.0 (build 2195, SP4) l Opera Browser, 7.0 (build 2637) l Java 2 Runtime Environment, (build b28)

Nov. 6, 2003CS WPI11 Config. Mgmt. Tools §RCS: Revision Control System §CVS: Concurrent Version System §Perforce, ClearCase, StarTeam §Usually store deltas, most support branching & merging §Locking vs. Sharing

Nov. 6, 2003CS WPI12 Config. Mgmt. Items §Most common is source code l Why? §Other items include SW Eng. documents l RAD, SDD, ODD, Test Plans, etc. §Why is CM useful for such documents?

Nov. 6, 2003CS WPI13 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, 2003CS WPI14 Change Management Process §Request for change §Assess request §Reject or Approve request §Assign responsibility for change §Implement change §Validate change

Nov. 6, 2003CS WPI15 For Next Time Chapter 11 Project Management