Software Configuration Management: Selecting the Right Tool Chetan Desai Software Project Management SWEN 5230 Dr. Boetticher.

Slides:



Advertisements
Similar presentations
Keys to Maximizing Component Reuse: Lessons and Case Studies OReilly Conference on Enterprise Java March 29, 2001 Presented by Gary Baney CTO, Flashline.com.
Advertisements

6th European Banking Supervisors XBRL Workshop Madrid 4, 5 October 2006 Version Control Pablo Santos Códice Software
Configuration Management
COMBASE: strategic content management system Soft Format, 2006.
Page 1 October 31, 2000 An Introduction to Large-Scale Software Development Steve Varnau Core HP-UX Operation October 31, 2000.
ECMDA workshop Thales ATM experience in using MDE ECMDA Workshop From code centric to model centric software engineering Bilbao 11 July 2006.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Chapter 7 CASE Tools and Joint and Rapid Application Development.
CoreGRID Workpackage 5 Virtual Institute on Grid Information and Monitoring Services Authorizing Grid Resource Access and Consumption Erik Elmroth, Michał.
Think. Learn. Succeed. Aura: An Architectural Framework for User Mobility in Ubiquitous Computing Environments Presented by: Ashirvad Naik April 20, 2010.
CATEGORIES OF INFORMATION There are three main categories of business information,and these are related to the purpose for which the information is utilized.
Capability Maturity Model (CMM) in SW design
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 1: Introduction to Windows Server 2003.
Chapter 9 Database Design
CS 501 : An Introduction to SCM & GForge An Introduction to SCM & GForge Lin Guo
Computers: Tools for an Information Age
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
Creating a Secured and Trusted Information Sphere in Different Markets Giuseppe Contino.
Information Systems Development and Acquisition Chapter 8 Jessup & Valacich Instructor: Ramesh Sankaranarayanan.
System Development Life Cycle (SDLC)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
Examine Quality Assurance/Quality Control Documentation
Configuration Management
Software Configuration Management
Complete and Integrated Lifecycle Management. Challenges 1.
Systems Analysis and Design: The Big Picture
Configuration Management, Logistics, and Universal CM Issues Larry Bauer Boeing Commercial Airplanes NDIA Conference Miami March 4-5, 2005
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Rational Unified Process Fundamentals Module 4: Disciplines II.
1 ©equinox limited 2005 What the hell is Configuration Management anyway? Martin White Equinox Software Architects August 2005.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
ITEC 3220M Using and Designing Database Systems
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
1 Chapter 9 Database Design. 2 2 In this chapter, you will learn: That successful database design must reflect the information system of which the database.
Feasibility Study.
1 SEG4912 University of Ottawa by Jason Kealey Software Engineering Capstone Project Tools and Technologies.
Auditing Information Systems (AIS)
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 7 CASE Tools and Joint and Rapid Application Development.
An Introduction to Software Engineering. Communication Systems.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
NT SECURITY Introduction Security features of an operating system revolve around the principles of “Availability,” “Integrity,” and Confidentiality. For.
1 Computing Challenges for the Square Kilometre Array Mathai Joseph & Harrick Vin Tata Research Development & Design Centre Pune, India CHEP Mumbai 16.
Business Productivity Infrastructure Optimization Campaign 1 Agenda: BPIO Partner Sales Readiness Workshop Day 3: Topic: Enterprise Content management.
About OlaTech We create web based custom software applications for businesses.
PPTTEST 12/26/ :41 1 IT Ron Williams Information Technology Management Project Management.
IBM Software Group ® Managing Reusable Assets Using Rational Suite Shimon Nir.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Jemerson Pedernal IT 2.1 FUNDAMENTALS OF DATABASE APPLICATIONS by PEDERNAL, JEMERSON G. [BS-Computer Science] Palawan State University Computer Network.
Basic Concepts Key Learning Points : The objectives of this chapter are as follows:  To provide an introduction to the basic Concepts of enterprise architectures,
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Salesforce.com Migration Assessment with Microsoft Services Assess whether your current CRM implementation is the right solution for your current and future.
Chapter 9 Database Planning, Design, and Administration Transparencies © Pearson Education Limited 1995, 2005.
This is a customer facing presentation that you can use to present the your assessment findings, recommendations, options, benefits and requirements. This.
Selecting the Right CRM System at AVEBE Refik Kocak CRM Partners (on behalf of AVEBE) CUSTOMER.
Configuration Management
PLM, Document and Workflow Management
Chapter 11: Software Configuration Management
CASE Tools and Joint and Rapid Application Development
Configuration Management
System Development Life Cycle (SDLC)
System Development Life Cycle (SDLC)
System Development Life Cycle (SDLC)
Chapter 11: Software Configuration Management
Presentation transcript:

Software Configuration Management: Selecting the Right Tool Chetan Desai Software Project Management SWEN 5230 Dr. Boetticher

What is SCM? History –CM Origins –SCM - Automation –Mature Discipline

Why do I need it? Reduce Costs Improve Productivity Encourage Reuse Reduce Deployment Defects Reduce Time-to-Market Integral Part of a Mature Organization [CMM]

But.. Adoption of SCM tools in the software development market is only 20% [Ovum Research] Lack of Awareness of the State-of-the-Art Problems with Tool Adoption –Behavioral Factors [WeigersK] –Political Factors –Inability to See Long-Term Benefits

Problem Definition Suitability for an organization “One size does not fit all” Large Investment, Resource Commitment, return-on- investment Select the most appropriate tool to obtain maximize return- on-investment (ROI) The total number of tools in the market today exceeds 50

Functionality (Requirements) Dart discusses functionality and requirements Does not address deployment Modified diagram Does not address entire industry spectrum No distinction made based on industry

Industry Spectrum Organization Factors - “How small is small?” –small who, what, when small, local, single-organization involvement with less volatile requirements –large communication control large, multi-organizational, multi-site and with volatile requirements Project Factors - Size, Complexity

Functionality and Industry Workspace –Simple (Workstation Directory), Intermediate (Hierarchical) –Workspace usage patterns –Small - Simple Workspace –Large - Intermediate Workspace (Enhances communication) Merging –Managing conflicts –Largely manual effort –Small - Parallel development not necessary –Large - Support tools, Automated merge

Functionality and Industry (continued) Communication –Local Area Connectivity Local network support –Wide Area Connectivity “Virtual Software Company” –Small - Local network support –Large - Wide area connectivity

Functionality and Industry (continued) Components –Uniquely identifiable components Applies to both - core function –Uniquely identifiable configurations Small - Labeling Large - Rules – Repository Small - File Based Repository Large - Database, structured storage (Efficient Retrieval)

Functionality and Industry (continued) Structure –System Model –Small - Parts List, Labels –Large - System Model Construction –Build Management –Small - make –Large - Integrated/Automated build management

Functionality and Industry (continued) Deployment –Installation –Parameterization –Instantiation –Reconfiguration

Functionality and Industry (continued) Process –Extent of Process Support - Little or None, Enforced, Custom Auditing –Change History –Trace Changes to Related Documents –Summary Charts and Reports

Functionality and Industry (continued) Accounting –Schedule Tracking –Gathering Metrics Controlling –Access Control Locks, Lists, Authentication –Small - Authentication governed by network –Large - Tool Authentication in Addition to Network Authentication

Taxonomy Onion Model Levels –1. Core functionality (simple version control) –2. Simple process introduction –3. Enforced process –4. Complex, Global Justification for Grouping

SCM Tool Survey SourceSafe –All Level 1 requirements implemented –Supports merging and parallel development –Level 1+ –$ for 10 users CS-RCS –All Level 1 requirements implemented –Supports merging and parallel development –Level 1+ –$ for 10 users

SCM Tool Survey (continued) Razor –Meets all Level 1 and Level 2 requirements –Does not meet any Level 3 requirements –Level 2 –$ for 10 users

Results CS-RCS, MS-VSS, Razor mapped to taxonomy Caveat: Level 1+ for CS-RCS, MS-VSS CS-RCS, MS-VSS –Low Operational Expertise –Developer-Oriented Razor –Basic Change Management Processes

Conclusions CM is a key element in the development and maintenance of a software product Investing in the most feature rich CM solution may not be the wisest solution General Taxonomy Presented - Guide Gradual Adoption

Future Work Practical Considerations Develop “Tie Breaking” Criteria Model Granularity Develop Questionnaire Usability, Performance, Platform, Technical Support Considerations Case Studies Needed to Valid Model and ROI

References Dart, S. Concepts in Configuration Management System (June 1992), On-line at Fruhauf, K. Software Configuration Management, State of the Art, State of the Practice (1999). Buckholz, G., Making CM Work for Software Development. IT Professional (September-October 2001), Wiegers, K.E. Lessons Learned from Tool Adoption Software Development Magazine (October 1999). On-line at Banachowski, S., Whitehead, J. An Observation of Fine Grain Usage Patterns for Two Configuration Management Tools (May 2001), Tenth International Workshop on Software Configuration Management.

Questions According to Ovum, what is the market penetration of SCM tool? –20% What are the core (fundamental) areas of SCM functionality according to this paper? –See “Onion Diagram” Level 1