Example: bachelor of science

configuration, change and release management …

configuration , change ,and ReleaseManagement Policiesand Procedures GuideTable of ContentsSection 1 Introducing configuration , change , and release of configuration , change , and release the change Request 2 of the configuration , change , and release management Policies and 3 of configuration , change , and release management You , change , and release management a and Approving a change the change for change Request a change a and Releasing a the out a change the configuration 38 Section 4 of configuration , change , and release management configuration , change , and release management a and and Approving a change a change change 47 Initial 47 Review a change a and Techniques for Risk and Constraint 61 Expected Monetary 61 Decision 62 Expert from Risk or Constraint and Contingency 63 Failure Mode Effects Analysis (FMEA).

Section 1 Introducing Configuration, Change, and Release Management 5 Section 1 Introducing Configuration, Change, and Release Management This section provides a brief introduction to policy and procedures for

Tags:

  Configuration, Management, Change, Change and release management, Release, And release management

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of configuration, change and release management …

1 configuration , change ,and ReleaseManagement Policiesand Procedures GuideTable of ContentsSection 1 Introducing configuration , change , and release of configuration , change , and release the change Request 2 of the configuration , change , and release management Policies and 3 of configuration , change , and release management You , change , and release management a and Approving a change the change for change Request a change a and Releasing a the out a change the configuration 38 Section 4 of configuration , change , and release management configuration , change , and release management a and and Approving a change a change change 47 Initial 47 Review a change a and Techniques for Risk and Constraint 61 Expected Monetary 61 Decision 62 Expert from Risk or Constraint and Contingency 63 Failure Mode Effects Analysis (FMEA).

2 And Releasing a the change the configuration , change , and release management 77 Section 1 Introducing configuration , change , and release Management5 Section 1 Introducing configuration , change , andRelease ManagementThis section provides a brief introduction to policy and procedures forconfiguration, change , and release management . By reading this introduction,you will gain a sense of how these policies and procedures apply to of configuration , change , and ReleaseManagementThe combined configuration , change , and release management approach providesa set of policies, processes and procedures for information systems. The policyis designed to preserve the integrity and stability of the information systems andto manage their life , change , and release management involves five processes toidentify, assess/approve, implement, test/ release , and account for all changes toan information system.

3 A commitment to this process will produce fullydocumented and managed changes to the systems on which the business is key topics of this section include: Objectives - A discussion of the processes, owners, and objectives Audience - A description of persons subject to the policies Usage - A flow chart depicting the overall processFigure illustrates the configuration , change , and release management processin the , change and release management Policies and Procedures Guide6 Figure configuration , change , and release management processIdentificationAssessment &ApprovalImplementationTest & ReleaseStatus , change , and release management are a set of related processesthat will achieve the following objectives:1. Maintain a detailed record of each system s configuration . This meanstracking down to the patch and revision level of individual software andhardware modules, components and Control changes to systems.

4 This includes a formal process for changerequests, assessment, approval, implementation, test and Ensure an audit trail. This includes change requests, approvals, test results,installation/deployment dates, and post installation quality assurance tests tosupport the system s operational baseline configuration Facilitate life cycle management and operational consistency. This isverified by auditing installed systems against baseline audience for this configuration , change , and release management processincludes most personnel. These customers fall in to five categories, each usingthe configuration , change , release management process for differing 1 Introducing configuration , change , and release Management7 Table lists the process owners and their particular usage of the configuration , change , and release management it AppliesSystem usersRequest a change or recommend an improvement tothe vendorsProvide a change to a vendor-supported system, suchas an upgrade, patch, maintenance release , or Technology personnelRecommend a change or to propose an improvementsuch as a shell script, NDS reconfiguration, improvedsystem configuration , increased capacity, Control ManagerManage the provider (such as hardwarevendor, third party service providers)Follow policy when making changes to baseline inconnection with providing service.

5 , updating driverson systems, documenting IMAC (installs, moves, adds,changes) activities, configuration , change , and release management meta-process consists of aseries of processes that flow clockwise. Five of the six processes are sequential,starting with requirements or improvements identification and ending with statusaccounting. The sixth process, auditing, is an ongoing process to verify that thesystem configuration documentation accurately reflects the system s flow chart in figure illustrates the steps in the overall configuration , change , and release management , change and release management Policies and Procedures Guide8 Figure The configuration , change , and release management RequestReceive and AssignAssessScheduleTestPlanReleaseAppro valStatus AccountingSYSTEMA uditIdentificationAssessment & ApprovalImplementationTest & ReleaseStatus AccountingAuditTable describes the processes involved in configuration , change , and configuration , change , and release management and FormIdentificationUser initiates a change request.

6 Help DeskServices logs and validates a change request,notifies the initiator, and passes the request onto the configuration Control Request Form(Exhibit A)Assessmentand ApprovalThe configuration Control Manager assignspriorities, initiates a review, compiles thefindings, and forwards the findings to one ofthree on the requester, the ConfigurationControl Board, subject matter experts, or peerreview approves or denies the requests directedto Checklist(Exhibit B)Generic Checklist(Exhibit B)Section 1 Introducing configuration , change , and release Management9 ImplementationIf the change Request is approved, the projectis implemented. If the change Request isdenied, it is closed out and the initiators Checklist (ExhibitB); related to SampleQuality Assurance andTest Plan (Exhibit C)Test andReleaseProvides criteria for testing the system after achange has been implemented and releasingthe system back into Quality Assuranceand Test Plan(Exhibit C)StatusAccountingThis process documents the change that hasbeen Checklist(Exhibit B)AuditsThis process audits the configurationdocumentation against the actual Checklist(Exhibit B) the BaselineThe foundation of configuration and change management is baselineidentification.

7 release management is not directly affected by baselineidentification. A baseline is a reference point that describes the state of a systemat a given stage in its life system evolves through four distinct baselines, depending on the system sdevelopment stage. The first and second stages, functional and allocatedbaselines, are developed from functional specifications and designs. The thirdstage, product baseline, is developed from the final design or allocated final stage, the operational baseline, reflects the system after it has beenplaced into shows how the system baseline evolves during the system life cycle: configuration , change and release management Policies and Procedures Guide10 Figure Baseline evolution during system life baseline from functional specifications stipulate functions andcharacteristicsAlso known as Design Baseline.

8 Representsstandards and general technical specifications tobe employed in the system's products, standards and configuration thatcomprise the components (hardware, software andfirmware) configured for operations. Includesspecific hardware and software models, versionsand revisions and other configuration configuration control and change management processes and procedures setforth in this document apply to all baseline stages. release managementprocesses and procedures, on the other hand, apply only to the final two stages,the product and operational change Request ClassesA change request is the principal means of initiating any change to a requests are divided into three classes based on who submits the requestto the Help Desk. The classes are: End-user change requests - changes initiated by any system user orstakeholder.

9 Vendor-initiated requests - changes based on 1 Introducing configuration , change , and release Management11 IT changes - changes for internal technical improvements by last two changes are initiated by vendors and internal IT personnel and takethe form of upgrades, patches, maintenance releases, and field changes. For thesechanges, the process is more streamlined than the end-user change defines types of changes and who would typically initiate them:Table Profile of change ChangesXXXXXXF unctional improvement. An improvement in the way an information systemoperates. End user change requests for functional improvements are typically tocorrect a misalignment between how an information system supports their workand the supporting business processes. Vendor and IT initiated functionalimprovements usually focus on functional improvements related to capacity.

10 More of a specific resource, such as shared disk space, afaster communications connection, services. Range from telecommunications access to requiredfeatures. Examples include: workflow-enabled applications, networked faxservices, and departmental fixes. Always initiated by vendors and IT to correct deficiencies orinefficiencies in products, systems, subsystems and components. A technical fixfrom an end user s point of view falls under the purview of problem and incidentmanagement. Example technical fixes include improved shell scripts, patches,maintenance releases, Added features, such as the latest version of an application,improved user interface, additional functions, requirements. Any system, subsystem or component needed to fulfill anew requirement. Some examples include a warranty tracking system to meet aConfiguration, change and release management Policies and Procedures Guide12new customer service requirement, high-speed color laser printer in response to arequirement to develop marketing materials in-house, 2 Policies13 Section 2 PoliciesThis section defines the policies which underlies configuration , change , andrelease management processes.


Related search queries