SCM Architect
Previous Job
Previous
SCM Architect
Ref No.: 18-04362
Location: Warren, Michigan
Position Type:Direct Placement
Start Date: 05/04/2018
Title: Sofware Configuration Management Architect
Location: Warren, MI
Duration: Direct Hire
Start: Ideally ASAP

Salary: Open DOE


Purpose of Software Configuration Management
The purpose of Configuration Management (CM) is to manage and control system elements and configurations over the lifecycle. Configuration Management also manages consistency between a product and its associated configuration definition. Software Configuration Management (SCM) applies to both the software system and its interfaces. The purpose of interface management is to agree with interface partners on the exchange of data through communications among software systems and services. Software configurations are changed through a controlled release of a new version.
Configuration Management is a discipline that enables the entire software engineering lifecycle process. CM provides essential services to all the major processes of systems and software engineering as depicted in figure 1 below.

The successful implementation of the Configuration Management process:
  1. Items requiring configuration management are identified and managed.
  2. Configuration baselines are established.
  3. Changes to items under configuration management are controlled.
  4. Configuration status information is available.
  5. Required configuration audits are completed.
  6. System releases and deliveries are controlled and approved.
Description of Position
Those that are hired for this position could lead efforts or support efforts depending on their skill level and capabilities. There are seven (7) primary processes and two special instances of CM that this position supports.
  1. SCM Planning
  2. SCM Management
  3. SW Configuration Identification
  4. SW Configuration Change Control
  5. SW Configuration Status Accounting
  6. SW Configuration Auditing
  7. SW Configuration Release Management
  8. SW Interface Control (special)
  9. Supplier Configuration Item Control (special)
Responsibilities
A Configuration Manager at any level shall be responsible for:
· (Planning) Determining the scope of the Software Configuration Management (SCM) and technical activities (i.e. identify process outputs, project tasks
and deliverables, establish SCM schedules for project tasks including achievement criteria and required resources to accomplish SCM project tasks).
· (Planning) Developing and supporting the Software Configuration Management Plan (SCMP) for assigned projects. This includes interviewing the project team and management.
  • (Planning) Develop, maintain and update the Enterprise CM/DM plan, products and processes.
  • (Management) Implementing, monitoring, controlling and improving SCM services (i.e. determine status of SCM activities and tasks, ensure tasks are carried out within plans, schedules, budgets and satisfy technical objectives. Monitor risks and project metrics for indications of SCM issues.)
  • (Management) Managing the implementation of the SCMP. (i.e. monitor resource usage, progress, risks and identify variances. Update plans when necessary).
  • (Configuration Identification) Enforcing naming conventions.
· (Configuration Identification) Identifying the items that require control as Configuration Items (CIs) and apply appropriate naming conventions to them.
i. Determining the CIs that are to be managed.
ii. Planning for the collection, storage, retrieval and change control of baselined versions.
iii. Establishing and maintaining associations between versions of each
item
iv. Establishing versioned assemblies or collections of CI versions.
v. Establishing and maintaining associations between versions of assemblies or collections.
vi. Describing the product structure through the selection of CIs and identification of their interrelationships.
  • (Configuration Identification) Defining how baselines are established.
  • (Configuration Identification) Establishing/Enforcing the change control process.
  • (Configuration Identification) Establishing/Enforcing physical storage procedures.
  • (Change Control) Maintaining the integrity of the product in all of its states, from requirements to validated working product.
  • (Change Control) Verifying the implementation of approved changes.
  • (Configuration Status Accounting) Recording, retrieving and reporting critical information about assets under configuration control.
  • (Configuration Auditing) Objectively assessing the integrity of the products both from a functional perspective (how the different technical processes of product development – from requirements to testing – were performed) and from a physical perspective (how the as-is product was built and changes were applied).
  • (Interface Control) Managing the potential interfacing effects that hardware, system software, and support software as well as other projects and deliverables have on the project. Interface control activities coordinate changes to the project CIs with changes to interfacing items.
  • (Supplier Configuration Item Control) Managing the incorporation of items developed outside the project environment (e.g. by third parties) into the project CIs in order to support added accountabilities for organizational and legal relationships.
  • (Release Management) Assuring that the proper set of deliverables (including documentation and ancillary materials) are delivered to the designated receiving party in the designated form to the designated location.
  • (Process Improvement) Schedule, execute and resolve deficiencies with SCM processes.
Knowledge, Skills and Abilities
  • Creative Problem Solving Abilities
  • Skilled with the use of Linux (preferable).