I be coughing tho Flashcards

1
Q

requirements define the system from the

A

client’s pov

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

design defines the system from the

A

dev’s pov

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

implementation:

A

actual coding and testing

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

static verification:

A

techs of verification that do not include software execution. can be manual (code review) or use tools

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

dynamic verification

A

testing with trial data, debugging

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

white box testing

A

look at the code and try and make it fail.

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

coverage criteria

A

functional ,statement, edge

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

effectiveness

A

The accuracy and completeness with which users achieve certain goals. Measures: quality of solution, error rates

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

Efficiency

A

The relation between the effectiveness and the resources expended in achieving them
Measures: task completion time, learning time, number of clicks

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

Satisfaction

A

The users’ comfort with and positive attitudes towards the use of the system
• Measures: attitude rating scales

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

defect

A

implementation and design vulnerabilities. Deviation from requirements.

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

bugs

A

implementation level

Example: Buffer overflow.

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

flaws

A

are problems at a deeper level. They are instantiated in
the code and present or absent at design-level.
Example: Error-handling problems.

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

Failures

A

software fails to perform its required function

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

Risks

A

Risk = probability x impact (severity)

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

Vulnerabilities

A

are errors that an attacker can exploit.

17
Q

types of security practices:

A

abuse cases (anticipate abnormal behavior and defend), architectural risks (failure of web service to authenticate calling code mitigated by secure protocals and authentication), code reviews, pen testing, overall security operations (logging back ups).

18
Q

fault

A

the actual program or design error that caused the failure