Looks like no one added any tags here yet for you.
The issue in software complexity that refers to the "relations and interactions" among these functions, components, and so on, is:
depth.
Important technical concerns in a large software development are:
estimation, planning, size and complexity
What is the maximum number of communications among a team of 25 people?
300
A method to simplify a complex problem is:
decomposition, modularization, incremental iteration
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
A technique to "lessen" the relationships, number of functionalities, amount of interactions, and so
decomposition and modularization
Large systems require software engineers to consider many aspects of development, including:
problem and design decomposition, technology and tool considerations, process and methodology
Important non-technical concerns in large software development are:
estimation and planning
What must we understand before jumping into implementing the solution?
problem description and the requirements
What is/are the main area(s) that needs to be coordinated in large software projects?
process, product, people
Software engineering must include the code and regulations that its members must uphold to be judged as a(n)
professional engineering practice
The definition of software engineering that points to a multi-person construction of multi-version software is from:
David Parnas
Breaking a project into smaller sub-projects is called:
decomposition
Which of the following is not listed as a reason for a project being cancelled?
Incomplete requirements and specifications
Requirement specification can be tested with:
hand-drawn screens and a prototype
Which activity involves collection of project information, analysis and evaluation of the collected data, and presentation and communication of the information?
monitoring
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.
The costliest errors made in a project are:
requirements
Acceptance testing is done by the client
True
Software process models define the:
tasks to be performed.
task's input and output.
task's preconditions and postconditions.
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.
Which model has the disadvantages of very little task overlap, a sequential process, and a single iteration?
waterfall
Which of the following could improve the waterfall model?
Develop multiple components
Overlap the development
Be more evolutionary
The need to develop multiple components, to overlap the development, and to be more evolutionary leads to the:
incremental and spiral model
Which model gave project managers a way to describe the actual status versus "almost complete"?
waterfall model
As a software product is developed using RUP, it may go through several iterations during which of the following?
Inception
Elaboration
Construction
Transition
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
Which of the following phase has an objective to establish all the major and critical requirements for the system?
Elaboration
The distinct tasks to develop software are:
requirements, design, code, test, integrate, and package
Programmers left alone will often think the single most important task in the development of software is:
coding
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.
One advantage of the waterfall process is:
it provides a clear way to track the stages of development for the project managers.
The RUP framework is driven by which of the following major concepts?
Use-case and requirements
Architecture centric
Iterative and incremental
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.
Entry criteria include a listing and a description of which of the following resources?
Artifacts
People
Tools
Activity definition
The characteristics of agile methods are:
short releases and iterations.
incremental design and user involvement.
minimal documentation and informal communication.
Agile methodology assumes that which of the following will change?
Requirements and environment
Examples of Agile methodologies include:
Extreme Programming and Kanban.
XP uses small software teams working in the same room to encourage:
communication.
Fundamental principles of Extreme Programming are:
None of these is correct
Which of the following decide on estimates, consequences, and processes during Extreme Programming planning?
Technical staff
Advantages of agile processes are:
Low process complexity
Low cost an overhead
Efficient handling of changes
Fast results
Usable systems
Scope/size; Criticality; People; Company culture; and Stability are:
Kind of projects
Kind of environments
Agile methodologies give importance to:
None of these is correct
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.
The set of statements that describe the user's needs and desires are the:
requirements.
Requirements are the "what" and design is the "how."
True
Incomplete requirement specification will always contribute to:
project development time.
project costs.
project failures.
Subject matter experts are used instead of users and customers when the software project:
is large and complex
The requirements engineering activities include review and validation, which are the testing of the requirements.
True
Analysis of the requirements consists of:
categorizing the requirements.
clustering the requirements.
prioritizing the requirements.
High-level requirements elicitation serves as the opportunity, needs, and justification for the software project in the client's business world.
True
Low-level requirements elicitation uncovers constraints for the software project to be developed.
False
All requirements must be enumerated uniquely. Why?
Traceable
Identifiable
Categorized
Defining the components of the system and how these components are related to each other is the:
architectural design phase.
An example of an architectural style is:
pipes-and-filters.
event-driven
client-server.
model-view-controller.
Two types of prototypes can be done in design. They are:
Low-fidelity, High-fidelity
Java API has the architectural style: _________________________.
Layered
Event-driven systems are modeled with _________________.
state modeling and state transition diagram
The phase that determines how the user's needs and desires will be achieved is the:
design phase.
Defining the components of the system and how these components are related to each other is part of the:
architectural design phase.
The view representing the run-time components (processes) and how they communicate with each other is:
process view.
The representation of a system's architecture structure is a:
view
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
The design example in section 7.4 uses which of the following architectural styles?
Model-view-controller
The design example in section 7.4 uses a DBMS, which is a:
database management system.
A phrase used to refer to "good design" could be:
easy to understand.
easy to change.
low complexity.
The characteristics of consistency and completeness are attributed to:
good design.
design-goodness.
general characteristics.
Which of the following characteristics ensures common terminology is used across the system's display screens, reports, database elements, and process logic?
Consistency
Current characterization of design attributes includes:
architectural design level.
detail design level.
coding level.
Popular terms describing good software are:
Easy to understand, change, reuse, test
Easy to integrate
Easy to code
The lowest and highest level of cohesion are:
Coincidental and Functional
Which of the following characteristics ensures common terminology is used across the system's display screens, reports, database elements, and process logic?
Consistency
Which of the following characteristics ensures that all the requirements are designed and that none are left out?
Completeness
Design reviews or inspections must focus on major characteristics like consistency and completeness.
True
The cyclomatic complexity measures the structural design complexity within the program and is used to assess how many test cases are needed.
True
A high Henry-Kafura number means a complex design structure.
True
User-Interface Design's goal is to reduce software defects.
False
UI design testing can be done with low fidelity interfaces made with paper boards and diagrams
True
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
We consider code indentation a very important issue affecting:
readability and maintainability.
Code reuse is done by sophisticated organization from design patterns to:
code templates.
Developing in the cloud offers which of the following advantages?
Flexibility and scalability
The implementation phase involves writing code as the only activity.
False
Good programmers reserve comments mainly for external references and statements of intent
True
Refactoring code will change the code's logic and behavior
False
A system implemented with code that can be matched to its design and to its requirement has the characteristic of performing correctly.
False
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
Readability, maintainability, correctness, completeness, performance, and traceability are six desirable characteristics of a good implementation
True
The main purpose of testing includes which of the following?
Finding faults
Assessing and ensuring quality
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
The severity of a defect measures the ______________ of that defect.
impact
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
Running all the branch coverage test cases would ensure total statement coverage.
True
In general, testing that covers all program statements will cover all logical paths
False
The white box testing technique requires the development of test cases from ______________.
Source code
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
Which of the following are techniques for detecting errors in programs and documents?
Testing, inspection, and review
The main levels of testing include:
Unit testing, functional testing and system testing
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.