Question: Needed accurate To ensure that the content renders…

Question: Needed accurate
To ensure that the content renders appropriately and consistently, you should view your pages in each of your two selected Web browsers and then verify that your code is error-free using the appropriate browser-specific development tool.
As the QA team lead, you are responsible for reviewing the Grading application project’s Configuration Management Plan.
You are reviewing to ensure that the CM practices and processes will be in place to manage the quality of the software throughout the Grading application software development.
Annotate at least five issues in comments of the document. Each comment should describe in detail your justification of the issue and recommendations for correcting the issue in the CM Plan.
Configuration Management Plan
A Plan for Software Configuration Management
3 June 2020

Prepared By
Project: Grading System
Division: Application Technologies
Table of Contents
1.0 Purpose 1
1.1 Roles and Responsibilities 1
2.0 Configuration Management Overview 1
2.1 Configuration Management Tools and Repositories 1
2.2 Baselines 2
2.3 Software Submittals and Receipts 2
2.3.1 Submittals 2 Release Package Submittal 2 Store Release Components 2
3.0 Configuration Identification 2
3.1 Configuration Items 2
4.0 Configuration Control 3
4.1 Change Control 3
4.1.1 Change Control Review Boards 3 Internal Configuration Control Board 3 ICCB Review Process 4
4.2 Change Tracking and Reporting 5
4.3 Version Control 5
4.3.1 Software Version and Release Identifiers 5
This Configuration Management Plan outlines configuration management methods and processes to be used for the Grading System application. Following of these processes is at each software developer’s discretion if they choose to participate or not.
Roles and Responsibilities
Table 1 describes configuration management responsibilities for the different project roles.
Table 1 – Roles and CM Responsibilities
Role CM Responsibilities
Program Manager (PM)
Ensures project CM is planned and implemented
Assigns CM responsibilities to specific resources under the PM’s control
Participate as a member of the Customer Configuration Control Board
Quality Assurance (QA)
Reviews and audits development activities based on defined processes, procedures, and guidelines
Reviews and audits development work products based on defined standards and guidelines
Certifies CM compliance with this plan and supporting procedures
Prepares and implements the CM Plan
Oversees the development and documentation of CM procedures
Develops and documents CM procedures
Coordinates with Product Development Team to define and maintain integrity of CIs
Develop and maintain Change Control Process
Establishes and maintains CM baselines
Performs CM audits
Executes Release and Delivery activities
Establishes the source code repository and sustains its integrity
Software Development Team
Develops and identifies CIs and supporting materials
Coordinates with CM to maintain integrity of CIs
Produces detailed design and coding
Performs unit testing and preliminary CI integration testing
All other project staff
Follows CM procedures
Participates in configuration audits on work products
Configuration Management Overview
Configuration management is a set of activities that is designed to:
Identify Configuration Items
Define mechanisms for managing different versions of the work products
Control changes that are imposed upon the work products
Configuration Management Tools and Repositories
Tools and repositories support the management and storage of software products and documentation as they progress through their development lifecycle.
Table 2 – CM Tools and Repositories
Tools CM Function Location
Microsoft Team Foundation Server (TFS) Source repository for code and documentation, change tracking, and test results; repository for documentation; repository for release packages Server

A baseline is the collection and relationship of CIs that together comprise a product, component, subsystem, or system at a specific point in its lifecycle. Baselines will not be used often because the software development iterative cycle is too rapid and it will take too much time to manage the baselines as well.
Software Submittals and Receipts
Copies of the software submittals and receipts are maintained in the Configuration Management library.
Submittals Release Package Submittal
The details on preparing and submitting a software release package are as follows: Store Release Components
Get a copy of the release that was verified in Release Testing from:
TFS > Source Control > Project > Release > Version xxx
2. Check in the copy to:
TFS > Source Control > Project > CM Releases > Version xxx
The release package should consist of the software installation scripts, database scripts, test databases, and installation documentation.
Configuration Identification
Configuration identification includes the following:
Selection of Configuration Items (CIs)
Determination of types of configuration documentation required for the CIs
Assurance of unique identifiers for the following:
Technical documentation that describes the CIs
Documentation and software versions and/or releases
Internal and external interfaces
Establishment of configuration baselines
Configuration Items
A CI is an entity designated for configuration management and control. It may consist of individual elements or an aggregate of related work products treated as a single unit. CIs must be individually controlled because any change to one CI may affect others. The types of CIs currently tracked and controlled for a software project fall into one of the three following categories:
Each CI will be identified (by name or number) for control, tracking, and status accounting purposes. The same identification label can be used by multiple CIs as long as the CIs are located in different folders.
Configuration Control
Configuration Control is the formal process of managing changes to the system. It is focused on identifying changes to a baseline configuration of the software, database, or documentation and managing the manner in which proposed changes are processed from inception to ultimate disposition.
Change Control
Change Control is the main function of the Change Management Process. The Change Management Process is the systematic evaluation, coordination, development, approval/disapproval, and implementation of changes after the establishment of a baseline. Changes are managed from their inception to final resolution to ensure that a standard, repeatable process is maintained for handling proposed changes and to ensure that unauthorized changes are not introduced into a controlled baseline.
Change Control Review Boards
The Internal Configuration Control Board (ICCB) has been established to facilitate the change management process. Internal Configuration Control Board
An Internal Configuration Control Board (ICCB) purpose is to define the scope of a software release and approve and manage any proposed changes during the release lifecycle. The Inputs that may be used to help define the scope of the release are as follows:
Statement of Work
Internal problem reports or Bug Work Items
The ICCB is the final authority to approve changes to the scope of a release.
ICCB responsibilities include, but may not be limited to, the following:
Review, disposition, and prioritize changes
Ensure that the introduction of a proposed change will not have a negative impact on current operations
Approve resources for system maintenance and/or enhancements
Approve changes to a baseline, documentation, and overall system release
Table 6 shows the roles and responsibilities of the ICCB members.
ICCB Member Roles Responsibilities
Configuration Control Board Chairperson
Presides at each ICCB meeting or designates an alternate
Approves the ICCB agenda
Reviews each agenda item; gathers member recommendations; determines change impacts; assigns priorities and due dates; makes disposition determination
Targets change requests
Reviews and approves ICCB minutes prepared by the ICCB Designated Scribe
Acts as final authority for ICCB decisions
Program Manager
Represents program functional area(s)
Attends each ICCB meeting or sends an authorized representative
Reviews agenda items prior to meeting; determines impact of proposed actions; indicates recommendation to Chairperson
Analyzes proposed problem solutions prior to ICCB recommendation on the status of a system change
Recommends priorities and due dates
Monitors progress on items assigned by the Chairperson
Reviews ICCB minutes
Director / Deputy Director
Software Architect
Software Development Manager/Lead
ICCB Scribe
Coordinates meeting schedules and agendas with the Chairperson
Prepares and distributes ICCB agenda to ICCB members
Prepares and distributes change packages to the Chairperson and Members prior to each meeting
Presents each agenda item to ICCB at meeting
Records, publishes, and distributes ICCB minutes, upon approval from Chairperson, to members and the project community
Tracks and maintains the status of changes
Table 6 – ICCB Member Roles and Responsibilities ICCB Review Process
The typical process flow for coordinating and conducting the Internal Configuration Control Board is depicted in Figure 3. This typical process can be waived if the priority of the change request if high and the customer is very insistent.
Change Tracking and Reporting
CM will establish and maintain a change tracking reporting system to record all activity associated to any change from initiation to approval. The change is not tracked once the ICCB approved the change to be implemented.
Version Control
A version is an identified body of software system components that typically includes application software, one or more databases, and documentation. The totality of the software release is called a version. When a new version is released, CM will maintain copies of all superseded software versions for purposes of an audit trail or in the event that an older software version needs to be regenerated.
Software Version and Release Identifiers
Version and release numbers for executable files are structured in the following decimal format: for major, minor, revision, and build number
During initial development of a product, the development version will always begin as, with the build number being incremented as the product undergoes development. The Implementation Baseline submitted for Release Testing, however, will be numbered as In fact, the initial build number for any release will always be 1.
If a build fails to pass Release Testing, the build number will be incremented by 1. When a build passes Release Testing, the build number is zeroed out. If it is necessary to produce an interim release for a critical fix prior to the next scheduled release, the interim release will be assigned the next sequential revision number for the current release.
1. Build is submitted for Release Testing.
2. Build fails Release Testing and is replaced by build
3. Build passes Release Testing and becomes current release
4. Development effort begins on build for the next scheduled release.
5. A critical fix is needed for current release
6. Build is produced for the critical fix.
7. Build passes Release Testing and becomes release 6.0.4.
The fix implemented in 6.0.4 is also implemented in

Place this order or similar order and get an amazing discount. USE Discount code “GET20” for 20% discount