Alex C
Quiz von , erstellt am more than 1 year ago

SE Ch 2 study guide

7
0
0
Alex C
Erstellt von Alex C vor mehr als 7 Jahre
Schließen

2 Introduction

Frage 1 von 28

1

(Select 4) Why is software special?

Wähle eine oder mehr der folgenden:

  • It is abstract, invisible, intangible.

  • It never wears out.

  • It is changing all the time.

  • It is not manufactured in the classical sense.

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

Erklärung

Frage 2 von 28

1

(Select 2) Which of the following are recognized process flow types?

Wähle eine oder mehr der folgenden:

  • Concurrent process flow

  • Iterative process flow

  • Linear process flow

  • Spiral process flow

Erklärung

Frage 3 von 28

1

Software processes can be constructed out of pre-existing software patterns to best meet the needs of a software project.

Wähle eins der folgenden:

  • WAHR
  • FALSCH

Erklärung

Frage 4 von 28

1

(Select 2) Which of these are standards for assessing software processes?

Wähle eine oder mehr der folgenden:

  • SEI

  • SPICE

  • ISO 9000

  • ISO 9001

Erklärung

Frage 5 von 28

1

The waterfall model of software development is

Wähle eine der folgenden:

  • A reasonable approach when requirements are well defined.

  • A good approach when a working program is required quickly.

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

  • An old fashioned model that is rarely used any more.

Erklärung

Frage 6 von 28

1

The incremental model of software development is

Wähle eine der folgenden:

  • A reasonable approach when requirements are well defined.

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

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

  • A revolutionary model that is not used for commercial products.

Erklärung

Frage 7 von 28

1

(Select 3) Evolutionary software process models

Wähle eine oder mehr der folgenden:

  • Are iterative in nature

  • Can easily accommodate product requirements changes

  • Do not generally produce throwaway systems

  • Build from the top down

Erklärung

Frage 8 von 28

1

The prototyping model of software development is

Wähle eine der folgenden:

  • A reasonable approach when requirements are well defined.

  • A useful approach when a customer cannot define requirements clearly.

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

  • A risky model that rarely produces a meaningful product.

Erklärung

Frage 9 von 28

1

The spiral model of software development

Wähle eine der folgenden:

  • Ends with the delivery of the software product

  • Is more chaotic than the incremental model

  • Includes project risks evaluation during each iteration

  • All of the above

Erklärung

Frage 10 von 28

1

(Select 2) The concurrent development model is

Wähle eine oder mehr der folgenden:

  • Another name for concurrent engineering.

  • Defines events that trigger engineering activity state transitions.

  • Only used for development of parallel or distributed systems.

  • Used whenever a large number of change requests are anticipated.

Erklärung

Frage 11 von 28

1

The component-based development model is

Wähle eine der folgenden:

  • Only appropriate for computer hardware design.

  • Not able to support the development of reusable components.

  • Dependent on object technologies for support.

  • Not cost effective by known quantifiable software metrics.

Erklärung

Frage 12 von 28

1

The formal methods model of software development makes use of mathematical methods to

Wähle eine der folgenden:

  • Define the specification for computer-based systems

  • Develop defect free computer-based systems

  • Verify the correctness of computer-based

  • All of the above

Erklärung

Frage 13 von 28

1

Which of these is not one of the phase names defined by the Unified Process model for software development?

Wähle eine der folgenden:

  • Inception phase

  • Elaboration phase

  • Construction phase

  • Validation phase

Erklärung

Frage 14 von 28

1

Which of these is not a characteristic of Personal Software Process?

Wähle eine der folgenden:

  • Emphasizes personal measurement of work product

  • Practitioner requires careful supervision by the project manager

  • Individual practitioner is responsible for estimating and scheduling

  • Practitioner is empower to control quality of software work products

Erklärung

Frage 15 von 28

1

(Select 2) Which of these are objectives of Team Software Process?

Wähle eine oder mehr der folgenden:

  • Accelerate software process improvement

  • Allow better time management by highly trained professionals

  • Build self-directed software teams

  • Show managers how to reduce costs and sustain quality

Erklärung

Frage 16 von 28

1

Process technology tools allow software organizations to compress schedules by skipping unimportant activities.

Wähle eins der folgenden:

  • WAHR
  • FALSCH

Erklärung

Frage 17 von 28

1

It is generally accepted that one cannot have weak software processes and create high quality end products.

Wähle eins der folgenden:

  • WAHR
  • FALSCH

Erklärung

Frage 18 von 28

1

What bridges the domain properties and requirements to the program on a computer?

Wähle eine der folgenden:

  • Specification

  • Qualification

  • Processing

  • The resurrection of Harambe

Erklärung

Frage 19 von 28

1

(Select 2 ) Why is software engineered?

Wähle eine oder mehr der folgenden:

  • To produce quality software

  • To satisfy stakeholders' needs and desires

  • To speed up development

  • To look smart to other people

Erklärung

Frage 20 von 28

1

(Select 3) What the three big software myths?

Wähle eine oder mehr der folgenden:

  • Mythical Man Month

  • Requirements can be a general statement of objectives without details

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

  • Adding engineers to a project near its completion slows productivity

Erklärung

Frage 21 von 28

1

What are the Software Engineering layers, staring from most basic?

Wähle eine der folgenden:

  • a quality focus, process model, methods, tools

  • methods, a quality focus, tools, process model

  • process model, methods, a quality focus, development

  • development, methods, process model, a quality focus

Erklärung

Frage 22 von 28

1

What is a process?

Wähle eine der folgenden:

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

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

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

  • A collection of shiny objects that distract you during your test

Erklärung

Frage 23 von 28

1

What are the 5 framework activities?

Wähle eine oder mehr der folgenden:

  • Communication

  • Planning

  • Modeling

  • Construction

  • Deployment

  • Development

  • Testing

  • Debugging

Erklärung

Frage 24 von 28

1

(Select 5) What are some umbrella activities?

Wähle eine oder mehr der folgenden:

  • Project tracking and control

  • Risk management

  • Quality assurance

  • Configuration management

  • Technical reviews

  • Coffee brewing

  • Deployment

Erklärung

Frage 25 von 28

1

(Select up to 2) What are some examples of the linear process flow?

Wähle eine oder mehr der folgenden:

  • Waterfall

  • V-Model

  • Spiral

  • Rapid Prototyping

  • Concurrent

Erklärung

Frage 26 von 28

1

(Select up to 2) What are some examples of the Iterative and evolutionary process flow?

Wähle eine oder mehr der folgenden:

  • Waterfall

  • V-Model

  • Spiral

  • Rapid Prototyping

  • Concurrent

Erklärung

Frage 27 von 28

1

What is an example of the parallel process flow?

Wähle eine der folgenden:

  • Waterfall

  • V-Model

  • Spiral

  • Rapid Prototyping

  • Concurrent

Erklärung

Frage 28 von 28

1

How do we produce quality software?

Wähle eine der folgenden:

  • By following a process

  • By letting Jacob fix our bugs

  • By speeding up development as much as possible

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

Erklärung

Vorherige
Nächste