Explain the process of software configuration management.

-

 Software Configuration Management (SCM)

  •  Software Configuration Management (SCM) refers to a process for maintaining computer systems, servers, and software in a desired, consistent state. 
  • Sometimes called software change management or IT automation, the idea is to have a system in place to track and compare changes made across a system throughout the development process and also identify who made these revisions.
  • The purpose is to make project management easier, minimize errors, increase traceability, and improve overall software quality. 
  • The software configuration management process is a series of steps designed to track and manage all the defects, resources, codes, documents, hardware, and budgets throughout a project.

  • SCM is an interdisciplinary process involving people at every level, including DevOps, developers, project managers/owners, SysAdmin, and testers. 


The 5 steps of an SCM plan

1. Planning and Identification

2. Version Control and Baseline

3. Change Control

4. Configuration Status Accounting

5. Audits and Reviews


1. Planning and Identification

  • The first step in the process is planning and identification. In this step, the goal is to plan for the development of the software project and identify the items within the scope. This is accomplished by having meetings and brainstorming sessions with your team to figure out the basic criteria for the rest of the project. 
  • Part of this process involves figuring out how the project will proceed and identifying the exit criteria. This way, your team will know how to recognize when all of the goals of the project have been met. 


2. Version Control and Baseline

  • The version control and baseline step ensure the continuous integrity of the product by identifying an accepted version of the software. This baseline is designated at a specific time in the SCM process and can only be altered through a formal procedure. 
  • The point of this step is to control the changes being made to the product. As the project develops, new baselines are established, resulting in several versions of the software.  


3. Change Control

  • Change control is the method used to ensure that any changes that are made are consistent with the rest of the project. Having these controls in place helps with quality assurance and the approval and release of new baseline(s). Change control is essential to the successful completion of the project. 
  • In this step, requests to change configurations are submitted to the team and approved or denied by the software configuration manager. The most common types of requests are to add or edit various configuration items or change user permissions.


4. Configuration Status Accounting

  • The next step is to ensure the project is developing according to the plan by testing and verifying according to the predetermined baselines. It involves looking at release notes and related documents to ensure the software meets all functional requirements. 
  • Configuration status accounting tracks each version released during the process, assessing what is new in each version and why the changes were necessary.


5. Audits and Reviews

  • The final step is a technical review of every stage in the software development life cycle. Audits and reviews look at the process, configurations, workflow, change requests, and everything that has gone into developing each baseline throughout the project’s development. 
  • The team performs multiple reviews of the application to verify its integrity and also put together essential accompanying documentation such as release notes, user manuals, and installation guides.


Comments

Post a Comment

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

-
Image
a) A Snowflake Shema is shown in figure below: b) The specific OLAP operations to be performed: 1. Roll-up on course from course_id to department. 2. Roll-up on a student from student_id to university. 3. Dice on course, student with department ="CS" and university = "biguniversity" 4. Drill-down on a student from the university to student_name. c) N = 4 dimensions The cube will contain 54 = 625 cuboids.
Read more

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

-
Image
  b) The specific OLAP operations to be performed are: 1. Roll-up on date from date id to year. 2. Roll-up on spectator from spectator id to status. 3. Roll-up on location from location id to location name. 4. Roll-up on the game from game id to all. 5. Dice with status= “students”, location name= “GM Place”, and year=2004
Read more

Discuss classification or taxonomy of virtualization at different levels.

-
Image
Taxonomy of virtualization Virtualization is mainly used to emulate the execution environment, storage, and networks. The execution environment is classified into two: – Process-level – implemented on top of an existing operating system.  – System-level – implemented directly on hardware and does not or minimum requirement of the existing operating system. OR,  Virtualization covers a wide range of emulation techniques that are applied to different areas of computing. A classification of these techniques helps us better understand their characteristics and use  V irtualization is mainly used to emulate  ● Execution Environments: To provide support for the execution of the programs eg. OS, and Application.  ○ Process Level: Implemented on top of an existing OS that has full control of the hardware  ○ System Level: Implemented directly on Hardware and do not require support from existing OS.  ● Storage: Storage vi...
Read more