Software Configuration Management

Question 1

Three parts of configuration management

Answer 1

*Change control
*Version control
*build-making/generation

Question 2

Why software configuration management

Answer 2

Help maintain C&C (concurrency n control)
make you have
1. right versions
2. right requirements (traceability)
3. right software, docs, manuals (integrity)

Question 3

Software integrity

Answer 3

*Software with integrity is software that:
- is traceable through life-cycle phases
- works

Question 4

Configuration item

Answer 4

• A configuration item is a doc/codebit under configuration control
  can be broken down into smaller bits

Question 5

There’s a cycle, what’s the cycle

Answer 5

Identification: find stuff to make scis
Control: during sldc
Status Account: trace through sldc
Audit: make sure works w srs or etv

Question 6

Baseline

Answer 6

it’s a foundation that you build the rest of prod on

it’s agreed upon config shit during some review/inspection process

before it, we were free

after it, we’re locked into it, unless a formal change control procedure is launched

Question 7

Change control board

Answer 7

*Activities
- they help change direction of proj
- moderate change requests