Ashtin Dorsaint - Assignment - 1 - Computer Science 307

docx

School

Saint Leo University *

*We aren’t endorsed by this school

Course

430

Subject

Computer Science

Date

Jan 9, 2024

Type

docx

Pages

4

Uploaded by BarristerIceKudu28

Report
Ashtin Dorsaint Computer Science 307 - Assignment 1: Configuration Management Configuration Management Configuration Management is the practice of processing system changes systematically with the primary intent of updating system and maintaining integrity (Configuration Management | Definition, Plan & Process, 2017). In laymen’s terms, this is a practice of setting up your system in and maintaining the system with the idea of security. When conducting CM management, you would use CM tools to accomplish in order to manage revisions, track revision status, and document and verify each step throughout the process. When CM tools are used correctly it will result in: Improved performance, system compliance with established specifications and guidelines, lowered probability of errors, and enhanced online availability. (Configuration Management | Definition, Plan & Process, 2017). Five Components in Configuration Management The first component in configuration management is scope; The scope essentially establishes boundaries and guidelines applicable to the configuration change (Configuration Management | Definition, Plan & Process, 2017). The word scope has a lot of interchangeable definition depending on the context, but in short, the scope is lays down the roadmap of the product, in configuration management, we are looking at the rules for the configuration change. Second component is references, it is here to list of all of the publications, specifications, and requirements used to implementing a change (Configuration Management | Definition, Plan & Process, 2017). They are more being used like a tutorial on how to implement the change, these references are usually backed by a lot of evidence.
Third component is the Configuration Item (CI), these are essentially are the component or components that needed to be changed in the system, this can be any component in a system (Configuration Management | Definition, Plan & Process, 2017). When the change occurs, they are often issued a unique CI number for the component. Fourth component are baselines, they are essentially benchmarks that need to be surpassed in order a system to qualify, this is often used to compared between new and old hardware in order to update the baseline, the faster the new hardware, the higher of the new baseline. These are tested after the new configuration (Configuration Management | Definition, Plan & Process, 2017). The firth and last component are verification, this will determine the accuracy and completeness of the configuration data while exercising zero tolerance to protect the integrity of the CM database (Configuration Management | Definition, Plan & Process, 2017). This is the testing phase of CMP, this will look for any errors in the testing phase, any error that does arise will fail the verification. Five Setbacks without configuration management 1. A misconfigured system has a fault in the system, it can lead to a domino effect to other problems in the latest revision, rendering a test a complete failure, they will not be able to keep up with rapid changes with hardware and software, nor with the speed of the business (Configuration Management | Definition, Plan & Process, 2017). 2. Without Configuration management, it will be difficult for the company to keep up with integrity of software, this is important since, this records the entire life cycle of the
software development, and the change of configurations can be traced through each iteration (Project Schedule Configuration Management Policies, 2018). 3. Companies will have a hard time to determine a change control based on budget and resources, sometimes a competitor can have better product, and spontaneous changes can happen due to that. Services can also be disrupted heavily if not planned correctly, compromising availability of services and systems in the infrastructure (Project Schedule Configuration Management Policies, 2018). 4. Without the baselines, companies will never able to determine a performance increase when making change of configuration, for each change the goal is always be faster than the last revision whether it’s hardware or software. Baselines are often used to make the new software or hardware qualify for production. (Project Schedule Configuration Management Policies, 2018). 5. With the lack of performance testing, the lack errors and bugs will pile up, which it will lead to using a lot more resources than it was originally intended for the scope. More changes are needed to be made, more downtime needs to be requested, the budget will need to be higher, making it harder for the company to break even with the project. (Project Schedule Configuration Management Policies, 2018).
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Citations Configuration Management | Definition, Plan & Process. (2017, June 22). Retrieved from https://study.com/academy/lesson/what-is-configuration-management-definition-process- tools.html . Project Schedule Configuration Management Policies. (2018, February 14). Retrieved from https://study.com/academy/lesson/project-schedule-configuration-management-policies.html.