Artifact Flashcards

1
Q

Software engineering

A

Idea of applying engineering principles to the building of big software products

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

Software crisis

A

Phenomenon whereby all too often software is delivered with faults,late,over/or not meeting all the users requirements

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

Positive testing

A

Testing that what you intended to change was changed in the desired way

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

Moving target problem

A

Occurs when requirements change while the software is still being developed

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

Scope creep

A

Succession of small almost tribal requests for additions to requirements

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

Regression fault

A

Occurs when a change in one part of the software product induces a fault in an apparently unrelated part of the software product

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

Regression test

A

Provides evidence that we have not unintentionally changed something that we did not intend to change

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

Millers law

A

At any one time a human is only able to concentrate on 7 chunks of information

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

Stepwise refinement

A

Breaking methods down into smaller methods so that you are not working on more than 7 components at a time

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

Software development

A

Process of developing software

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

Separation of concerns

A

It is broken down into components that overlap as little as possible with respect to their functionality

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

Divide and conquer

A

Break a large problem down into sub problems which are easier to solve

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

Brookes law

A

Adding a programmer to an already late project makes the project later

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

Inception phase

A

Initial version

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

Elaboration phase

A

Completed version

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

Construction phase

A

Final version

17
Q

Transition phase

A

Ready for deployment

18
Q

Data dictionary

A

Provides a centralized list of every data item defined in the software product. Helps with consistency and clarity as well as helping with avoiding duplication of the same data item. This then results in fewer faults

19
Q

Utility

A

Is the software easy to use?

20
Q

Reliability

A

Mean time between failures is long means it’s more reliable

21
Q

Robustness

A

A robust product has a wide range of operating conditions including some outside its specifications

22
Q

Performance

A

It is crucial to verify that a software product meets its time and space constraints

23
Q

Correctness

A

Satisfies output specification without regard for computing resources consumed when operated under permissible conditions

24
Q

Common for all reviews

A

Non execution based testing, centred around a meeting of key stakeholders, chaired by SQA representations, meeting is to identify faults not to fix faults in the document

25
Q

Participants for review meeting

A

SQA chair
Manager responsible for previous, current, and next workflow
Client representative
Another SQA member