Configuration management and version control in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is configuration management?

Configuration management is the process of organizing and controlling changes in software, hardware, or systems to maintain consistency and traceability over time.

beginner

What is version control?

Version control is a system that records changes to files or code over time, allowing you to track history, revert to previous versions, and collaborate with others.

beginner

Why is version control important in software development?

Version control helps teams work together without overwriting each other's work, keeps a history of changes, and makes it easy to fix mistakes by going back to earlier versions.

beginner

What is a repository in version control?

A repository is a storage location where all the files, history, and changes of a project are kept. It acts like a folder that tracks every change made.

intermediate

How does configuration management support software quality?

By controlling changes and keeping track of different versions, configuration management ensures software is consistent, reliable, and easier to test and maintain.

What does version control primarily help with?

A Writing documentation

B Designing user interfaces

C Testing software performance

D Tracking changes and collaborating on files

Version control systems track changes and help multiple people work on files without conflicts.

Which of the following is a popular version control system?

A Git

B Photoshop

C Excel

D Slack

Git is a widely used version control system for managing code changes.

Configuration management helps ensure software is:

A Consistent and reliable

B Faster to run

C More colorful

D Easier to uninstall

Configuration management controls changes to keep software consistent and reliable.

What is a 'commit' in version control?

A Creating a new user

B Deleting a file

C Saving a snapshot of changes

D Running a program

A commit saves a snapshot of your changes to the version control system.

Which term describes a storage location for all project files and history?

A Compiler

B Repository

C Debugger

D Server

A repository stores all files and their change history in version control.

Explain in your own words what configuration management is and why it matters.

Think about how keeping track of changes helps teams avoid mistakes.

Describe how version control helps a team work together on a software project.

Imagine multiple people editing the same document at once.

Practice

1. What is the main purpose of version control in software development?

easy

A. To write code faster

B. To test software automatically

C. To design user interfaces

D. To track and manage changes to code over time

Solution

1. Step 1: Understand version control basics

   Version control systems keep a history of changes made to code files.

2. Step 2: Identify the main goal

   The main goal is to track and manage changes so developers can collaborate and revert if needed.

3. Final Answer:

   To track and manage changes to code over time -> Option D

4. Quick Check:

   Version control = track changes [OK]

Hint: Version control means saving code changes safely [OK]

Common Mistakes:

• Confusing version control with coding speed
• Thinking it is for UI design
• Assuming it automates testing

2. Which of the following is the correct Git command to save your changes to the local repository?

easy

A. git commit

B. git clone

C. git push

D. git pull

Solution

1. Step 1: Understand Git commands

   git commit saves changes to the local repository with a message.

2. Step 2: Differentiate commands

   git push sends commits to a remote repository, git clone copies a repo, git pull fetches updates.

3. Final Answer:

   git commit -> Option A

4. Quick Check:

   Save changes locally = git commit [OK]

Hint: Commit means save locally, push means send remotely [OK]

Common Mistakes:

• Using git push to save locally
• Confusing git clone with commit
• Thinking git pull saves changes

3. Consider this Git command sequence:
git add file.txt
git commit -m "Update file"
git push origin main
What is the result of running these commands?

medium

A. The file.txt changes are sent to the remote repository branch named main

B. The file.txt changes are saved locally but not sent to the remote repository

C. The file.txt is deleted from the repository

D. The repository is cloned to your computer

Solution

1. Step 1: Analyze each command

   git add stages file.txt changes, git commit saves them locally with a message, git push sends them to remote branch main.

2. Step 2: Understand the final effect

   After these commands, the changes in file.txt are updated in the remote repository on branch main.

3. Final Answer:

   The file.txt changes are sent to the remote repository branch named main -> Option A

4. Quick Check:

   git push origin main = send changes to main branch [OK]

Hint: Push sends committed changes to remote branch [OK]

Common Mistakes:

• Thinking git push only saves locally
• Confusing git add with deleting files
• Assuming cloning happens here

4. A developer runs git commit -m "Fix bug" but gets an error saying "nothing to commit, working tree clean." What is the most likely cause?

medium

A. The repository is corrupted

B. The commit message is missing

C. No changes were staged with git add

D. The remote repository is unreachable

Solution

1. Step 1: Understand the error message

   "nothing to commit, working tree clean" means no changes are ready to be saved.

2. Step 2: Identify the cause

   Changes must be staged with git add before committing; without staging, commit has nothing to save.

3. Final Answer:

   No changes were staged with git add -> Option C

4. Quick Check:

   Commit error = no staged changes [OK]

Hint: Always git add before git commit [OK]

Common Mistakes:

• Assuming commit message is missing
• Thinking repository is corrupted
• Blaming remote repository issues

5. You want to create a new branch in Git to work on a feature without affecting the main code. Which sequence of commands correctly achieves this and switches to the new branch?

hard

A. git clone feature
git add .

B. git branch feature
git checkout feature

C. git push origin feature
git commit -m "Start feature"

D. git checkout main
git branch feature

Solution

1. Step 1: Understand branch creation and switching

   git branch feature creates a new branch named feature; git checkout feature switches to it.

2. Step 2: Evaluate options

   git branch feature git checkout feature correctly creates and switches to the new branch. git checkout main git branch feature creates branch but does not switch.

3. Final Answer:

   git branch feature git checkout feature -> Option B

4. Quick Check:

   Create and switch branch = branch + checkout [OK]

Hint: Create branch then checkout to switch [OK]

Common Mistakes:

• Not switching to the new branch after creation
• Using git push before committing
• Confusing clone with branch creation