SCM Plan Purpose
This SCM Plan is a model for software applications that require a disaster recovery ability.
Typical Software Configuration Management Plan Requirements
Software Application Builds
Repository Name |- Source Code Path |- DR |- Application Release |- Artifacts/Packages |- Documents |- 3rd-Party Dependency Software
SCM Plan Test
IIRC you won't be allowed to make an update. You need to do the following
Requirements: Tier 1 available within 24hrs of incident.
Require SCM standard delivery for each internally developed application
High Level SCM DR Plan
Source (Tier III)
Require SCM standard delivery for each internally developed application Possible layout inside each source code repository for DR applications Repository Name -> Source Code Path -> DR -> Application Release -> Artifacts/Packages -> Documents -> 3rd-Party Dependency Software
Software Configuration Management Plan Links
Software Configuration Management Table of Contents
Software Configuration Management Software Configuration Management are the practices and procedures for administering source code, producing software development builds, controlling change, and managing software configurations.
Software Configuration Management Software Configuration Mgmt is a software development support and control function. Specializing in software building, installation packaging, change control and configuration management.
Software Configuration Management Plan This document will cover source code administration, build environment standards and define the process by which new components will be added to builds, and a common understanding of how we will manage broken builds.
Software Configuration Management Systems Software Configuration Management Systems are the end-to-end tools and procedures that encompass the Software Configuration Management Systems. These are more than just software builds and version control tools. These are the processes you build that surround these tools.
Software Configuration Management Strategies Software Configuration Management Strategies can be difficult to define. Your SCM strategies can be as simple as providing excellent SCM service, but they can be more complex by introducing process improvement to your already existing service.
Software Configuration Management Best Practices Software Configuration Management Best Practices are designed and implemented to ensure software quality, integrity and reproducibility. Best Practices are methods and techniques that are proven to be the most effective way of ensuring repeatability of a processes.
General Best Practices Software Configuration Management Best Practices are designed and implemented to ensure software quality, integrity and reproducibility. Best Practices are methods and techniques that are proven to be the most effective way of ensuring repeatability of a processes.
SCM Plan This SCM Plan is a template model for software applications that require a disaster recovery plan.
SCM Books SCM Books is a collection of books and descriptions that can be a valuable resource and background for installation packaging, software builds, source control, software engineering or engineering in general
Genius Richard Feynman Genius Richard Feynman was written by James Gleick. Genius - The Life and Science of Richard Feynman a 20th century Physics.
Genius James Gleick Genius James Gleick - The Life and Sciences of Richard Feynman.
SCM Performance Goals SCM Performance Goals are set to help the SCM Engineer achieve high performance standards. The goals need to be clear, direct and ongoing feedback from management.
SCM Goals SCM Goals are a sample set of performance objectives that can be used as an example of typical Software Configuration Management Goals.
Forrester Reports This page contains a listing of Forrester Reports for SCM tools. Forrester is a leading company in discovering vendor tool directions and consumer trends. This is a listing of Forrester Reports of SCM tools.
Software Engineering The IEEE Computer Society defines Software Engineering as the application of a systematic, disciplined and quantifiable approach to the development, maintenance and operation of software.
SCM War Stories SCM War Stories are a collection of typical SCM anti-patterns that most experienced SCM Engineers have all lived through.
Circumventing Build Process Circumventing Build Process happens for many reasons. For example, it can happen because someone decides schedule is more important than software quality. Another example, might be that the person making the decision to circumvent the build process does not understand the implications of their decision.
Untested Software Untested software is an anti pattern due to a project that is behind schedule. A decision to proceed with the delivery to demonstrate progress of a project over the proper testing has taken place to ensure quality. Untested Software is a common Software Engineering Antipattern.
What is SCM What is SCM? SCM encapsulates the practices and procedures for administering source code, producing software development builds, controlling change, and managing software configurations. Specifically, SCM ensures the integrity, reliability and reproducibility of developing software products from planning to release.
Why Use SCM Why Use SCM? Software Configuration Management ensures software build repeatability and reproducibility. SCM enforces Source Code Administration Best Practices and proper Software Change Management practices are followed.
SCM Websites Software Configuration Management Websites a listing of top SCM sites and other interesting Websites. This page attempts to identify the truly unique Websites. Please visit them.
SCMWise Software Configuration Management SCMWise is dedicated to SCM. This site is a central repository for the collection of best practices, processes, methodologies and tools that surround SCM.
This is a collection of
Salary Surveys from
SCMWise Configuration Spec