of SCM during the Initiation phase is essential to assure the accuracy, traceability and integrity of a product throughout development.
SCM implementation methodology during the analysis phase
The next major set of activities following the Initiation phase is the Analysis phase; i.e. gathering, managing, and developing requirements. A stable process that stores narrative or descriptive requirements in the form of use cases, scenarios, stories, prototypes, documents, and high-level model artifacts should manage these activities. These critical work products are used to establish the requirement specifications, both business-related and system-related, that will determine and support the system's logical architecture. SCM processes, or methodology, in-place throughout the Analysis phase assures the availability of the latest versions of business functional requirements, business rules, and non-functional requirements.
SCM implementation methodology during the design phase
As requirements become clearer and more stable, the design of a product evolves from the logical architecture to the physical architecture. The transition of design maturity occurs during the Design phase and establishes a design specification that software engineers use to convert to code. SCM methodology should control and manage the key artifacts from these activities and the resulting strategic deliverables in order to provide a current, stable, and "clean" environment, and to ensure that the traceability of the user's needs are maintained throughout design activities.
SCM implementation methodology during the construction & integration phase
During the Construction and Integration phase, the source code and other critical components of the software product are produced, unit tests are conducted, and the unit test results are documented. System test specifications are created, including the system test cases and system test and migration procedures. System test cases are also used to verify traceability of system-level requirements. System documentation, including user manuals and operations and maintenance manuals, are produced. Data migration components are also produced. These and many other significant artifacts are created throughout the Construction and Integration phase, and only a well-defined and disciplined SCM methodology can assure the successful implementation of their production and placement into the designated target baseline release.
SCM implementation methodology during the system test & acceptance phase
The System Test and Acceptance phase is the stage that validates the system requirements as realized by the users or customer, and verifies the overall system functionality and performance as designed. Critical work products such as system test cases and system test results, updated system documentation, and in many cases a business continuity plan are completed during this phase. Traceability of system requirements is assured through system requirements mapping. The strategic role SCM ( methodologies) plays during this phase is to safeguard these artifacts, deliverables, and work products through version control and archiving processes, and assuring they are entered into the correct baseline release as planned.
SCM implementation methodology during the deployment phase
During the Deployment (sometimes called the Implementation) phase, the system is commissioned or otherwise placed into operation, and System documentation is distributed to the user community. The SCM process assures that only the components designated for the target release are available and entered into the baseline for delivery and deployment. This is the last phase of development activities - and SCM Implementation Methodologies have played a key role in assuring product integrity throughout the development lifecycle.
SCM implementation methodology during the production phase
Approximately 80% of a product's lifecycle is spent in production or the operations and maintenance domain. SCM can play a significant role during the Production phase by tracking defects, enhancements, and user feedback for system improvements, and at system replacement or disposal.
In this article, I have attempted to illustrate the SCM implementation