Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Engineering > chapter 9 > Flashcards

chapter 9 Flashcards

1
Q

What are some principles of system testing?

A
  1. faults exist but not detected.
    (code never ran; not long enough; not correct configurations).
  2. faults can be introduced b/c of incorrect requirements.
  3. design reviews. programmers and customers usually have no direct communications.
  4. faults detected sooner are easier and cheaper to fix.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is functional testing?

A

Does the integrated system perform as promised by req specifications.

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

What is performance testing?

A

are the non-functional reqs met?

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

What is acceptance testing?

A

is the system what the customer expects?

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

What is installation testing?

A

does the system run at the customer’s site(s)?

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

What is configuration management?

A
  1. versions or releases
  2. production or development
  3. deltas, separated files, conditionals ?
  4. change control ?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is regression testing?

A

as changes are made test the existing system.

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

What is build or integration plan?

A

large systems. candidates for phased dev. easier to build and test in small pieces.

a spin is a phase of the system.
spin 0 is the minimal system.

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

What are versions?

A

for different os

n

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

What are releases?

A

bug fixes and what not.

n.m

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

what is a delta?

A

like how git manages files.
stores the original file. then the changes in another file.
more efficient on storage.

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

what is change control?

A

pull requests.

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

who is a test team comprised of?

A

professional testers: write and run tests
analysts: created reqs
system designers: understand proposed solution.
config management specialists: help control fixes.
users: evaluate issues that arise.

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

what is a cause-and-effect graph?

A 
logical relationship (boolean) between inputs and outputs.
inputs = causes
outputs = effects
transformations = effects

uses gates. and, nor, not, etc.
page 26 for symbols.
~ = not

https://www.youtube.com/watch?v=iOT3BcfnUms&ab_channel=RANJIRAJ

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

for cause and effect graphs what do the symbols mean (I, S, A, P)

A 
I = involved
A = absent
P = present
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

what is a stress test?

A

evaluate a system to its limits over a short period of time.

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

what is a volume test?

A

are the defined fields large enough to handle the input data?

system shall be able to store 100k entries in the database.

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

what is configuration test?

A

testing code on multiple machines.

different machines may have different configurations of hardware and software.

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

what is compatibility test?

A

when system interfaces with different systems.

software supports win10 and ubuntu 20.04

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

what is regression test?

A

used during phased dev.

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

what is security testing?

A

uncovers vulnerabilities, threats, risks, and prevents attacks.
SQL Injection.

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

what is timing tests?

A

carried out with stress testing to ensure the system preforms within the required time constraints.

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

what is environment testing?

A

system’s ability to perform at the installation site.

mainly for technical systems that use sensors.

24
Q

what is quality testing?

A

evaluate the system’s reliability, availability, and maintainability.

25
Q

what are recovery tests?

A

responses to disasters. power failure, disk failure, etc.

26
Q

what are maintenance tests?

A

diagnostics tools and procedures to help find problems.

log files, and what not. installation progress…

27
Q

what is documentation testing?

A

proper documentation for the system is required.

28
Q

what is human factor testing?

A

ensuring the system has a robust user interface.
support color blind mode.
low learning curve.
nice layout of menus.

29
Q

what is software reliability?

A

operating software with no failures for a given interval.

30
Q

what is software availability?

A

operating successfully according to specs at a given time.

31
Q

what is software maintainability?

A

maintenance activity can be carried out within stated interval.

32
Q

define catastrophic (Different Level of Failure Severity)

A

death or system loss

33
Q

define critical (Different Level of Failure Severity)

A

severe injury or major system damage

34
Q

define marginal (Different Level of Failure Severity)

A

minor injury or minor system damage

35
Q

define minor (Different Level of Failure Severity)

A

causes no injury or system damage

36
Q

what is Type-1 uncertainty (Uncertainty Inherent from Failure Data)

A

how the system will be used.

cannot predict which faults will trigger the next failure.

37
Q

what is Type-2 uncertainty (Uncertainty Inherent from Failure Data)

A

lack of knowledge about the effect of fault removal.
don’t know if our fixes are complete and successful.
uncertain about the degree to which our correction increases the software’s reliability.

38
Q

what is mean time to failure (MTTF)

A

average inter-failure time.

as reliability increases, MTTF decreases.

39
Q

what is mean time to repair (MTTR)

A

average time to fix faulty software.

for maintenance we want to reduce MTTR.

40
Q

what is mean time between failure (MTBF)

A

MTTF + MTTR

how long the system is unavailable for use.

41
Q

What is the formula for reliability?
What is the formula for maintainability?
What is the formula for availability?

A 
R = MTTF / (1 + MTTF)
M = 1 / (1 + MTTR)
A = MTBF (1 + MTBF)
42
Q

what is reliability stability?

A

inter-failure times stay the same

43
Q

what is reliability growth?

A

inter-failure times increase. (gets further apart = good)

44
Q

functions.

  1. software will fail before time t.
  2. software will function properly until time t.
A
  1. integral f(t) dt

2. 1 - F(t)

45
Q

what is the goal of hardware reliability?

what is the goal of software reliability?

A 
hardware = stability
software = reliability growth
46
Q

what is The Jelinski-Moranda model?

A

failure rate is initially constant.
tracks the effects of removing faults.
no type-2 uncertainty.

47
Q

what is The Littlewood model?

A

more realistic than jelinski…

treats corrected fault’s contributions to reliability differently.

48
Q

what is benchmark testing (acceptance testing)?

A

typical running conditions for the system defined by customer.

performed with actual users.
testers are familiar with the requirements.

49
Q

what is pilot testing (acceptance testing)?

A

system installed on experimental basis.
users use the system as if it’s a permanent system.
tests everyday workings of the system.

less formal than benchmark testing.

50
Q

what is alpha testing (acceptance testing)?

A

test with users within the organization before releasing it to customers.

“pilot” the system before the customers run it.

51
Q

what is beta testing (acceptance testing)?

A

customer’s pilot test.

52
Q

what is parallel testing (acceptance testing)?

A

run new and old systems in parallel.

53
Q

what is test plan (test documentation)?

A

describe the system and plan for exercising all functions and characteristics

54
Q

what is test specifications (test documentation)?

A

details each test and defines criteria for evaluating each feature

55
Q

what is test description (test documentation)?

A

test data and procedures for each test

56
Q

what is test analysis (test documentation)?

A

result of each test

Software Engineering (10 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions