Software Control Practices Flashcards

1
Q

is concerned with the policies, processes, and tools for managing changing software systems.

A

Configuration Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Is essential for team project to control changes made by different developers.

A

Configuration Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

4 Configuration Management Activities

A
  1. Version Management
  2. System Building
  3. Change Management
  4. Release Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

keeping track of multiple versions of system components and ensuring that changes made by others do not interfere with each other.

A

Version Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

4 Version Management Types:

A

o Multi-Version Development

o Codelines and Baseline

o Centralized Version Control

o Distributed Version Contral

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

the process of assembling program components, data and libraries, then compiling to create an executable system.

A

System Building

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

keeping track of requests for changes to the software from customer and developers.

A

Change Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

preparing software for external release and keeping track of the system version that have been released.

A

Release Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Two (2) Types of Releases:

A

o Major Release
o Minor Release

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

a release that delivers significant new functionality

A

Major Release

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

a release that repair bugs and fix customer problems.

A

Minor Release

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

10 COMMANDMENTS OF RELEASE ENGINEERING

A
  1. use a source code control system.
  2. use the right tools for the job
  3. write portable and low maintenance build files
  4. use a release process that is producible
  5. use unique build ID
  6. use a package manager
  7. design an upgrade process before releasing version 1.0
  8. provide a detailed log of what thou hath done to my machine
  9. provide a complete install/upgrade/patch/uninstall process
  10. Test Engineer: Though shalt apply these laws to thyself
How well did you know this?
1
Not at all
2
3
4
5
Perfectly