2 Introduction

Question

(Select 4) Why is software special?

Answer 1

It is abstract, invisible, intangible.

Answer 2

It never wears out.

Answer 3

It is changing all the time.

Answer 4

It is not manufactured in the classical sense.

Answer 5

It is manufactured using the same technologies used for other engineering artifacts.

Answer 6

Concurrent process flow

Answer 7

Iterative process flow

Answer 8

Linear process flow

Answer 9

Spiral process flow

Answer 10

A reasonable approach when requirements are well defined.

Answer 11

A good approach when a working program is required quickly.

Answer 12

The best approach to use for projects with large development teams.

Answer 13

An old fashioned model that is rarely used any more.

Answer 14

A reasonable approach when requirements are well defined.

Answer 15

A good approach when a working core product is required quickly.

Answer 16

The best approach to use for projects with large development teams.

Answer 17

A revolutionary model that is not used for commercial products.

Answer 18

Are iterative in nature

Answer 19

Can easily accommodate product requirements changes

Answer 20

Do not generally produce throwaway systems

Answer 21

Build from the top down

Answer 22

A reasonable approach when requirements are well defined.

Answer 23

A useful approach when a customer cannot define requirements clearly.

Answer 24

The best approach to use for projects with large development teams.

Answer 25

A risky model that rarely produces a meaningful product.

Answer 26

Ends with the delivery of the software product

Answer 27

Is more chaotic than the incremental model

Answer 28

Includes project risks evaluation during each iteration

Answer 29

All of the above

Answer 30

Another name for concurrent engineering.

Answer 31

Defines events that trigger engineering activity state transitions.

Answer 32

Only used for development of parallel or distributed systems.

Answer 33

Used whenever a large number of change requests are anticipated.

Answer 34

Only appropriate for computer hardware design.

Answer 35

Not able to support the development of reusable components.

Answer 36

Dependent on object technologies for support.

Answer 37

Not cost effective by known quantifiable software metrics.

Answer 38

Define the specification for computer-based systems

Answer 39

Develop defect free computer-based systems

Answer 40

Verify the correctness of computer-based

Answer 41

All of the above

Answer 42

Inception phase

Answer 43

Elaboration phase

Answer 44

Construction phase

Answer 45

Validation phase

Answer 46

Emphasizes personal measurement of work product

Answer 47

Practitioner requires careful supervision by the project manager

Answer 48

Individual practitioner is responsible for estimating and scheduling

Answer 49

Practitioner is empower to control quality of software work products

Answer 50

Accelerate software process improvement

Answer 51

Allow better time management by highly trained professionals

Answer 52

Build self-directed software teams

Answer 53

Show managers how to reduce costs and sustain quality

Answer 54

Specification

Answer 55

Qualification

Answer 56

Processing

Answer 57

The resurrection of Harambe

Answer 58

To produce quality software

Answer 59

To satisfy stakeholders' needs and desires

Answer 60

To speed up development

Answer 61

To look smart to other people

Answer 62

Mythical Man Month

Answer 63

Requirements can be a general statement of objectives without details

Answer 64

Until the program is running, there is no way to assess its quality

Answer 65

Adding engineers to a project near its completion slows productivity

Answer 66

a quality focus, process model, methods, tools

Answer 67

methods, a quality focus, tools, process model

Answer 68

process model, methods, a quality focus, development

Answer 69

development, methods, process model, a quality focus

Answer 70

A collection of activities, actions, and tasks that are performed when some work product is to be created

Answer 71

A collection of requirements that need to be met when some work product is to be created

Answer 72

A collection of specifications, steps, and requirements that make up a project's plan

Answer 73

A collection of shiny objects that distract you during your test

Answer 74

Communication

Answer 75

Construction

Answer 76

Deployment

Answer 77

Development

Answer 78

Project tracking and control

Answer 79

Risk management

Answer 80

Quality assurance

Answer 81

Configuration management

Answer 82

Technical reviews

Answer 83

Coffee brewing

Answer 84

Deployment

Answer 85

Rapid Prototyping

Answer 86

Concurrent

Answer 87

Rapid Prototyping

Answer 88

Concurrent

Answer 89

Rapid Prototyping

Answer 90

Concurrent

Answer 91

By following a process

Answer 92

By letting Jacob fix our bugs

Answer 93

By speeding up development as much as possible

Answer 94

By adding new developers near the end of a project to help finish it up

Próximo

2 Introduction

Descrição

Resumo de Recurso

Questão 1

Questão 2

Questão 3

Questão 4

Questão 5

Questão 6

Questão 7

Questão 8

Questão 9

Questão 10

Questão 11

Questão 12

Questão 13

Questão 14

Questão 15

Questão 16

Questão 17

Questão 18

Questão 19

Questão 20

Questão 21

Questão 22

Questão 23

Questão 24

Questão 25

Questão 26

Questão 27

Questão 28

Semelhante

	Criado por Alex C mais de 7 anos atrás