Software Engineering Final Exam Review

studied byStudied by 0 people
0.0(0)
Get a hint
Hint

The issue in software complexity that refers to the "relations and interactions" among these functions, components, and so on, is:

1 / 150

encourage image

There's no tags or description

Looks like no one added any tags here yet for you.

151 Terms

1

The issue in software complexity that refers to the "relations and interactions" among these functions, components, and so on, is:

depth.

New cards
2

Important technical concerns in a large software development are:

estimation, planning, size and complexity

New cards
3

What is the maximum number of communications among a team of 25 people?

300

New cards
4

A method to simplify a complex problem is:

decomposition, modularization, incremental iteration

New cards
5

What is the increase in the number of maximum communication paths when we grow from a six-person software team to an eight-person software team?

13

New cards
6

A technique to "lessen" the relationships, number of functionalities, amount of interactions, and so

decomposition and modularization

New cards
7

Large systems require software engineers to consider many aspects of development, including:

problem and design decomposition, technology and tool considerations, process and methodology

New cards
8

Important non-technical concerns in large software development are:

estimation and planning

New cards
9

What must we understand before jumping into implementing the solution?

problem description and the requirements

New cards
10

What is/are the main area(s) that needs to be coordinated in large software projects?

process, product, people

New cards
11

Software engineering must include the code and regulations that its members must uphold to be judged as a(n)

professional engineering practice

New cards
12

The definition of software engineering that points to a multi-person construction of multi-version software is from:

David Parnas

New cards
13

Breaking a project into smaller sub-projects is called:

decomposition

New cards
14

Which of the following is not listed as a reason for a project being cancelled?

Incomplete requirements and specifications

New cards
15

Requirement specification can be tested with:

hand-drawn screens and a prototype

New cards
16

Which activity involves collection of project information, analysis and evaluation of the collected data, and presentation and communication of the information?

monitoring

New cards
17

The definition of Software Engineering is:

The establishment and use of sound engineering principles in order to obtain economically software that is reliable and works on real machines.
That form of engineering that applies the principles of computer science and mathematics to achieving cost effective solutions to software problems.
The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software.

New cards
18

The costliest errors made in a project are:

requirements

New cards
19

Acceptance testing is done by the client

True

New cards
20

Software process models define the:

tasks to be performed.
task's input and output.
task's preconditions and postconditions.

New cards
21

Projects take a longer time with poor end products and, in worse situations, total project failure because of inconsistency in the:

tasks to be performed.
order to perform the tasks.

New cards
22

Which model has the disadvantages of very little task overlap, a sequential process, and a single iteration?

waterfall

New cards
23

Which of the following could improve the waterfall model?

Develop multiple components
Overlap the development
Be more evolutionary

New cards
24

The need to develop multiple components, to overlap the development, and to be more evolutionary leads to the:

incremental and spiral model

New cards
25

Which model gave project managers a way to describe the actual status versus "almost complete"?

waterfall model

New cards
26

As a software product is developed using RUP, it may go through several iterations during which of the following?

Inception
Elaboration
Construction
Transition

New cards
27

Which of the following phase has an objective to establish the critical use cases and the major scenarios that will drive the architecture and design?

Inception

New cards
28

Which of the following phase has an objective to establish all the major and critical requirements for the system?

Elaboration

New cards
29

The distinct tasks to develop software are:

requirements, design, code, test, integrate, and package

New cards
30

Programmers left alone will often think the single most important task in the development of software is:

coding

New cards
31

The disadvantage of the waterfall process for software development is:

very little overlapping of the tasks.
it is a single iteration.
sequential order of tasks.

New cards
32

One advantage of the waterfall process is:

it provides a clear way to track the stages of development for the project managers.

New cards
33

The RUP framework is driven by which of the following major concepts?

Use-case and requirements
Architecture centric
Iterative and incremental

New cards
34

You are working on requirement specification #22 and you define it to be "completed," which means:

all specifications have been reviewed by the customers and other stakeholders
all exceptions found during the requirement review are changed.
the modified specifications are accepted by all parties.

New cards
35

Entry criteria include a listing and a description of which of the following resources?

Artifacts
People
Tools
Activity definition

New cards
36

The characteristics of agile methods are:

short releases and iterations.
incremental design and user involvement.
minimal documentation and informal communication.

New cards
37

Agile methodology assumes that which of the following will change?

Requirements and environment

New cards
38

Examples of Agile methodologies include:

Extreme Programming and Kanban.

New cards
39

XP uses small software teams working in the same room to encourage:

communication.

New cards
40

Fundamental principles of Extreme Programming are:

None of these is correct

New cards
41

Which of the following decide on estimates, consequences, and processes during Extreme Programming planning?

Technical staff

New cards
42

Advantages of agile processes are:

Low process complexity
Low cost an overhead
Efficient handling of changes
Fast results
Usable systems

New cards
43

Scope/size; Criticality; People; Company culture; and Stability are:

Kind of projects
Kind of environments

New cards
44

Agile methodologies give importance to:

None of these is correct

New cards
45

A disadvantage of lengthy development times for a software engineering project can be the:

business that will use the project may exist for a year or two.
business that will use the project may change their focus.
business that will use the project may change their products.

New cards
46

The set of statements that describe the user's needs and desires are the:

requirements.

New cards
47

Requirements are the "what" and design is the "how."

True

New cards
48

Incomplete requirement specification will always contribute to:

project development time.
project costs.
project failures.

New cards
49

Subject matter experts are used instead of users and customers when the software project:

is large and complex

New cards
50

The requirements engineering activities include review and validation, which are the testing of the requirements.

True

New cards
51

Analysis of the requirements consists of:

categorizing the requirements.
clustering the requirements.
prioritizing the requirements.

New cards
52

High-level requirements elicitation serves as the opportunity, needs, and justification for the software project in the client's business world.

True

New cards
53

Low-level requirements elicitation uncovers constraints for the software project to be developed.

False

New cards
54

All requirements must be enumerated uniquely. Why?

Traceable
Identifiable
Categorized

New cards
55

Defining the components of the system and how these components are related to each other is the:

architectural design phase.

New cards
56

An example of an architectural style is:

pipes-and-filters.
event-driven
client-server.
model-view-controller.

New cards
57

Two types of prototypes can be done in design. They are:

Low-fidelity, High-fidelity

New cards
58

Java API has the architectural style: _________________________.

Layered

New cards
59

Event-driven systems are modeled with _________________.

state modeling and state transition diagram

New cards
60

The phase that determines how the user's needs and desires will be achieved is the:

design phase.

New cards
61

Defining the components of the system and how these components are related to each other is part of the:

architectural design phase.

New cards
62

The view representing the run-time components (processes) and how they communicate with each other is:

process view.

New cards
63

The representation of a system's architecture structure is a:

view

New cards
64

Software engineering design teams use which of the following, which are grounded in mathematical concepts of sets and relations, for their software projects?

Relational databases

New cards
65

The design example in section 7.4 uses which of the following architectural styles?

Model-view-controller

New cards
66

The design example in section 7.4 uses a DBMS, which is a:

database management system.

New cards
67

A phrase used to refer to "good design" could be:

easy to understand.
easy to change.
low complexity.

New cards
68

The characteristics of consistency and completeness are attributed to:

good design.
design-goodness.
general characteristics.

New cards
69

Which of the following characteristics ensures common terminology is used across the system's display screens, reports, database elements, and process logic?

Consistency

New cards
70

Current characterization of design attributes includes:

architectural design level.
detail design level.
coding level.

New cards
71

Popular terms describing good software are:

Easy to understand, change, reuse, test
Easy to integrate
Easy to code

New cards
72

The lowest and highest level of cohesion are:

Coincidental and Functional

New cards
73

Which of the following characteristics ensures common terminology is used across the system's display screens, reports, database elements, and process logic?

Consistency

New cards
74

Which of the following characteristics ensures that all the requirements are designed and that none are left out?

Completeness

New cards
75

Design reviews or inspections must focus on major characteristics like consistency and completeness.

True

New cards
76

The cyclomatic complexity measures the structural design complexity within the program and is used to assess how many test cases are needed.

True

New cards
77

A high Henry-Kafura number means a complex design structure.

True

New cards
78

User-Interface Design's goal is to reduce software defects.

False

New cards
79

UI design testing can be done with low fidelity interfaces made with paper boards and diagrams

True

New cards
80

To help get project X done faster, the detail design is done as part of the implementation. What are the issues for project X?

Less cohesive design and less organized design

New cards
81

We consider code indentation a very important issue affecting:

readability and maintainability.

New cards
82

Code reuse is done by sophisticated organization from design patterns to:

code templates.

New cards
83

Developing in the cloud offers which of the following advantages?

Flexibility and scalability

New cards
84

The implementation phase involves writing code as the only activity.

False

New cards
85

Good programmers reserve comments mainly for external references and statements of intent

True

New cards
86

Refactoring code will change the code's logic and behavior

False

New cards
87

A system implemented with code that can be matched to its design and to its requirement has the characteristic of performing correctly.

False

New cards
88

The most important issues for maintaining a good coding style are to be consistent and to try to highlight the meaning of your code.

True

New cards
89

Readability, maintainability, correctness, completeness, performance, and traceability are six desirable characteristics of a good implementation

True

New cards
90

The main purpose of testing includes which of the following?

Finding faults
Assessing and ensuring quality

New cards
91

Consider the situation where we have two input variables X and Y, where X can take on 7 valid values and Y can take on 10 valid values. If one wanted to test all the combinatorics of just the valid values of these two input variables, how many test cases need to be developed and executed?

70

New cards
92

The severity of a defect measures the ______________ of that defect.

impact

New cards
93

Of the two main perspectives on testing, Myers is a proponent of showing that a program works and is of good quality as opposed to showing that a program has defects and needs to be corrected before release.

False

New cards
94

Running all the branch coverage test cases would ensure total statement coverage.

True

New cards
95

In general, testing that covers all program statements will cover all logical paths

False

New cards
96

The white box testing technique requires the development of test cases from ______________.

Source code

New cards
97

We have seeded a software with 10 defects. If we desire an 80% defect discovery rate in our testing and have discovered 32 total defects through our testing, then _______ of those 32 defects found need to be from the non-seeded ones.

24

New cards
98

Which of the following are techniques for detecting errors in programs and documents?

Testing, inspection, and review

New cards
99

The main levels of testing include:

Unit testing, functional testing and system testing

New cards
100

The content of a code inspection report needs to include:

a list of problems found during the inspection.
the participants of the inspection.
severity levels of each of the problems found.
what material was inspected.

New cards

Explore top notes

note Note
studied byStudied by 12 people
... ago
5.0(1)
note Note
studied byStudied by 18 people
... ago
5.0(1)
note Note
studied byStudied by 8 people
... ago
5.0(1)
note Note
studied byStudied by 2 people
... ago
5.0(1)
note Note
studied byStudied by 18 people
... ago
5.0(1)
note Note
studied byStudied by 38 people
... ago
5.0(1)
note Note
studied byStudied by 13 people
... ago
5.0(1)
note Note
studied byStudied by 15 people
... ago
5.0(1)

Explore top flashcards

flashcards Flashcard (48)
studied byStudied by 15 people
... ago
5.0(1)
flashcards Flashcard (129)
studied byStudied by 39 people
... ago
5.0(1)
flashcards Flashcard (85)
studied byStudied by 24 people
... ago
5.0(1)
flashcards Flashcard (46)
studied byStudied by 32 people
... ago
5.0(1)
flashcards Flashcard (71)
studied byStudied by 169 people
... ago
4.0(1)
flashcards Flashcard (35)
studied byStudied by 2321 people
... ago
4.9(45)
flashcards Flashcard (20)
studied byStudied by 163 people
... ago
5.0(1)
flashcards Flashcard (50)
studied byStudied by 1 person
... ago
5.0(1)
robot