Traceability & Auditability: Do you really know what went into production?

  1. create a defect for the developers to work against.  SBOM Artifacts would include the application source code, configuration files, requirements, test data, etc., and thus be visible to the RFC/ticket and SD as to true application impact, once the RFC has been completed and is ready for the CAB.
  2. Communication of Planned Changes to Customers - This interface provides the capability for complete visibility into the status of the RFC.  As an example, if the RFC has been assigned to a specific developer and the developer has checked-out the impacted code and its associated test files, one can rightly assume that the status is that the change is being tested. 
  3. Evaluate Proposed Changes for Capacity and Performance Impacts - MKS Integrity can automate the notification of the capacity planning and
    availability management teams whenever any RFC results in changes to
    configuration settings that are typically associated with application
    performance in a production environment. 
  4. Perform Impact Assessment of Proposed Changes - Impact analysis information, stored in the SCM repository, would consist of requirements information, code, configuration files, test cases, test data, design data, business process data, etc. 
  5. Provide Configuration Information to Problem Management to perform Level 1-2-3 Root Cause Diagnosis - The SCM repository, as part of its
    capability to adhere to the federated CMDB approach, would have the
    ability to provide application configuration information to the SD when
    problem management and root cause analysis is being performed.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.