Maintenance/Evolution Flashcards

1
Q

What is code maintenance?

A
  • Correcting errors which were not discovered in earlier stage of the life cycle
  • Updating the implementation for updating platforms
  • Enhancing the system services as new requirements are discovered
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the types of code changes you can have in the maintenance phase?

A

Fault repairs
Environmental adaptations
Functionality additions

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

Explain fault repairs

A

Fixing coding errors
Cost: cheap
Doesn’t involve much redesign

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

Explain environmental adpatation

A

Updates for new OS
Cost: A little more expensive than fault repairs
Doesn’t involve much redesign

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

Explain functionality additions

A

Meet business changes
Cost: Expensive, most common too!
Often involves redesign

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

Why is change expensive?

A

Poor original development practices

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

What are some poor original development practices?

A

Undocumented requirements
- Cant tell whats changed
Undocumented designs
- Cant understand plan
Low readability of code
- Cant figure out whats going on
Limited documentation

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

What is requirements change management?

A

The process of understanding and controlling change to requirements

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

What is the process of requirements change management?

A
  • Don’t start with code
  • Start by understanding the change and cost (big, small, easy, hard)
  • Decide whos paying
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are emergency changes in code?

A

Problems which occur that require fast or emergency changes
- Updating code takes priority over documentation

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

What are the dangers of emergency changes in code?

A
  • Multiple subsequent emergency repairs occur which mask the original emergency repairs
  • Code gets unmanageable/ unmaintainable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

When do we start code again?

A

Cost of change gets high
- Client notes it is costing a lot to have changes
- Software company realises code is getting hard to fix

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

How is maintenance different to software engineering?

A

Most SE involved the reuse or previous code
Evolution is another SE loop

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

Why is the maintenance of software important?

A
  • Code can easily adapt to changing needs
  • Minimising risks and costs
  • Enhancing customer satisfaction
How well did you know this?
1
Not at all
2
3
4
5
Perfectly