Brainscape's Knowledge GenomeTM

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


See full index

Software Engineering > Test 4 > Flashcards

Test 4 Flashcards

1
Q

____ Software quality is a concept

A

True

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

____ Software quality is not the result of good project management and solid engineering practice.

A

False

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

____ Software Quality has been defined as an effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it.

A

True

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

Quality of ___________________ - encompasses requirements, specifications, and the design of the system.

A

Design

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

Quality of ___________________ - is an issue focused primarily on implementation.

A

Conformance

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

Discuss the Software Quality Dilemma and what is meant by software being “good enough”.

A

So people in industry try to get to that magical middle groundwhere the product is good enoughnot to be rejected right away, such as during evaluation, but also not the object of so much perfectionism and so much work that it would take too long or cost too much to complete.

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

What is “Good Enough” Software ?

A

Good enough software delivers high quality functions and features that end-users desire, but at the same time it delivers other more obscure or specialized functions and features that contain known bugs.

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

____ Software reviews are a “filter” for the software process. That is, reviews are applied at various points during software engineering and serve to uncover errors and defects that can then be removed.

A

True

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

____ Software reviews will not “purify” software engineering work products, including requirements and design models, code, and testing data.

A

False

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

____ The Formal Technical Review is actually a class of reviews that includes walkthroughs and inspections.

A

True

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

Two types of reviews

A

Formal technical and informal

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

Is this typical of a review:

___ A mechanism for political or personal reprisal

A

Not typical

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

___ A software quality assurance mechanism

A

Typical

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

___ A technical assessment of a work meeting conducted by technical people for technical people

A

Typical

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

___ A meeting intended solely to impart information

A

Not Typical

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

____ A meeting conducted by technical people for technical people

A

Typical

17
Q

__ A project summary or progress assessment

A

Not Typical

18
Q

What is the difference between and error and a defect in software? (Define each)

A

Error—a quality problem found before the software is released to end users
Defect—a quality problem found only after the software has been released to end-users

19
Q

What are the 3 Review Meeting Results

A

Accept the product
Reject the product
Accept the product provisionally

20
Q

number 25 look at chart in chapter 20.

A

top is no effort bottom is effort.

21
Q

Parts of a informal review:

A
  1. a simple desk check of a software engineering work product with a colleague
  2. a casual meeting (involving more than 2 people) for the purpose of reviewing a work product
  3. the review-oriented aspects of pair programming
22
Q

Parts of a formal technical review:

A
  1. to uncover errors in function, logic, or implementation for any representation of the software
  2. to verify that the software under review meets its requirements
  3. to ensure that the software has been represented according to predefined standards
  4. to achieve software that is developed in a uniform manner
  5. to make projects more manageable
23
Q

____ Software Quality Assurance (often called quality management) is an umbrella activity that is applied throughout the software process

A

True

24
Q

___ Software safety is a software quality assurance activity that focuses on the identification and assessment of potential hazards that may affect software negatively and cause an entire system to fail.

A

True

25
Q

____ Testing is the process of exercising a program with the specific intent of finding errors prior to delivery to the end use

A

True

26
Q

____ Object oriented testing begins by evaluating the correctness and consistency of the analysis and design models.

A

True

27
Q

___ Class testing is equivalent to unit testing for conventional software.

A

True

28
Q

Verification

A

refers to the set of tasks that ensure that software correctly implements a specific function.
—–“Are we building the product right?”

29
Q

Validation

A

refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements. —–“Are we building the right product?”

30
Q

Who are the two testers of software?

A
  1. Developer

2. Independent tester

31
Q

Testing in the context of Software Engineering is a series of four steps. What are the 4 steps

A
  1. Unit testing
  2. Integration testing
  3. Validation testing
  4. Systems testing
32
Q

Top Down Integration –Depth-first integration

A

as new modules are integrated, some subset of tests is re-run

33
Q

Regression Testing

A

Regression testing is the re-execution of some subset of tests that have already been conducted to ensure that changes have not propagated unintended side effects

34
Q

In Smoke Testing, a build is:

A

includes all data files, libraries, reusable modules, and engineered components that are required to implement one or more product functions.

35
Q

In Smoke Testing, a build:

A

includes all data files, libraries, reusable modules, and engineered components that are required to implement one or more product functions.

36
Q

Object-Oriented Testing

A

Encapsulation drives definition of classes and objects

37
Q

Module interface

A

Test data flow first

38
Q

Boundary conditions

A

Test cases that exercise data structure, control flow, and data values just below, at, and just above maxima and minima are very likely to uncover errors.

39
Q

Error-handling paths

A

Make sure error messages are correct and accurately represent or describe error.

Software Engineering (5 decks)

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