D284 SOFTWARE
K
ENGINEERING EXAM 2021
C
QUESTIONS AND CORRECT
LO
VERIFIED ANSWERS 100%
YC
GUARANTEED PASS A+
GRADED
D
U
ST
,80/20-rule - ANS In the Dynamic Systems Development Method, the assumption that
80-percent of an application's features will take 20-percent of the project's total time to
implement. (The 80/20-rule often applies to other situations, too. For example, 80-percent of the
bugs are usually contained in 20-percent of the code.)
acceptance test - ANS A test to determine whether the finished application meets the
requirements. Normally, a user or other customer representative sits down the with application
and runs through all the use cases you identified during the requirements gathering phase to
K
make sure everything works as advertised.
activity diagram - ANS In UML, a diagram that represents work flows for activities. They
C
include several kinds of symbols connected with arrows to show the direction of the work flow.
adaptive development model - ANS A development model that enables you to change the
LO
project's goals if necessary during development.
administrator - ANS Someone who manages the development team's computers, network, and
other tools. Also called a system administrator.
YC
advisor user - ANS Any user who brings an important viewpoint to the project.
agile development - ANS A development model where you initially provide the fewest possible
features at the lowest fidelity to still have a useful application. Over time, you add more features
and improve existing features until all features have been implemented at full fidelity.
D
Agile Manifesto - ANS A set of four guiding principles for agile development. In brief the
principles are: (1) Individuals and interactions over processes and tools, (2) Working software
over comprehensive documentation, (3) Customer collaboration over contract negotiation, (4)
U
Responding to change over following a plan
Agile Unified Process (AUP) - ANS A simplified version of Rational Unified Process that
ST
includes agile methods such as test-driven development and agile modeling. In 2012 AUP was
superseded by Disciplined Agile Delivery.
algorithm - ANS A software recipe that explains how to solve a particular programming
problem.
ambassador user - ANS Someone who acts as a liaison between the users and the
developers.
anchoring - ANS A phenomenon where an early decision made by one person influences later
decisions by others.
, anomaly - ANS In a relational database, an error caused by a design flaw such as records
holding inconsistent values or being unable to delete a piece of data because it is necessary to
record some unrelated piece of information.
architect - ANS Someone who focuses on the application's overall high-level design.
artifact - ANS In a UML deployment diagram, a file, a script, an executable program or another
item that is deployed. In development models, something generated by the model such as a
requirements document, user story, or piece of code.
K
assertion - ANS A statement about the program and its data that is supposed to be true. If the
statement isn't true, the assertion throws an exception to tell you that something is wrong.
C
attribute - ANS Some feature of a project that you can measure such as the number of lines of
code, the number of defects, or the number of times the word "mess" appears in code
LO
comments. See also metric and indicator.
audit trail - ANS A record of actions taken by an application's users for security auditing
purposes.
YC
behavior diagram - ANS In UML, a diagram that shows the behavior of some entity. There are
three kinds of behavior diagrams: activity diagrams, use case diagrams, and state machine
diagrams.
Big Board - ANS A large board used by many agile models that is posted in a visible location
so that everyone can see the project's status at a glance. Also called an information radiator.
D
big O notation - ANS A system for studying the limiting behavior of algorithms as the size of the
problem grows large.
U
black-box test - ANS A test designed by someone who doesn't know how the code works
internally.
ST
brainstorming - ANS A group technique for discovering creative solutions to a problem.
bug - ANS A flaw in a program that causes it to produce an incorrect result or to behave
unexpectedly. Bugs are generally evil.
build engineer - ANS In Feature-Driven Development, someone who sets up and controls the
build process.
burndown chart - ANS In Scrum, a graph showing the amount of work remaining over time.
K
ENGINEERING EXAM 2021
C
QUESTIONS AND CORRECT
LO
VERIFIED ANSWERS 100%
YC
GUARANTEED PASS A+
GRADED
D
U
ST
,80/20-rule - ANS In the Dynamic Systems Development Method, the assumption that
80-percent of an application's features will take 20-percent of the project's total time to
implement. (The 80/20-rule often applies to other situations, too. For example, 80-percent of the
bugs are usually contained in 20-percent of the code.)
acceptance test - ANS A test to determine whether the finished application meets the
requirements. Normally, a user or other customer representative sits down the with application
and runs through all the use cases you identified during the requirements gathering phase to
K
make sure everything works as advertised.
activity diagram - ANS In UML, a diagram that represents work flows for activities. They
C
include several kinds of symbols connected with arrows to show the direction of the work flow.
adaptive development model - ANS A development model that enables you to change the
LO
project's goals if necessary during development.
administrator - ANS Someone who manages the development team's computers, network, and
other tools. Also called a system administrator.
YC
advisor user - ANS Any user who brings an important viewpoint to the project.
agile development - ANS A development model where you initially provide the fewest possible
features at the lowest fidelity to still have a useful application. Over time, you add more features
and improve existing features until all features have been implemented at full fidelity.
D
Agile Manifesto - ANS A set of four guiding principles for agile development. In brief the
principles are: (1) Individuals and interactions over processes and tools, (2) Working software
over comprehensive documentation, (3) Customer collaboration over contract negotiation, (4)
U
Responding to change over following a plan
Agile Unified Process (AUP) - ANS A simplified version of Rational Unified Process that
ST
includes agile methods such as test-driven development and agile modeling. In 2012 AUP was
superseded by Disciplined Agile Delivery.
algorithm - ANS A software recipe that explains how to solve a particular programming
problem.
ambassador user - ANS Someone who acts as a liaison between the users and the
developers.
anchoring - ANS A phenomenon where an early decision made by one person influences later
decisions by others.
, anomaly - ANS In a relational database, an error caused by a design flaw such as records
holding inconsistent values or being unable to delete a piece of data because it is necessary to
record some unrelated piece of information.
architect - ANS Someone who focuses on the application's overall high-level design.
artifact - ANS In a UML deployment diagram, a file, a script, an executable program or another
item that is deployed. In development models, something generated by the model such as a
requirements document, user story, or piece of code.
K
assertion - ANS A statement about the program and its data that is supposed to be true. If the
statement isn't true, the assertion throws an exception to tell you that something is wrong.
C
attribute - ANS Some feature of a project that you can measure such as the number of lines of
code, the number of defects, or the number of times the word "mess" appears in code
LO
comments. See also metric and indicator.
audit trail - ANS A record of actions taken by an application's users for security auditing
purposes.
YC
behavior diagram - ANS In UML, a diagram that shows the behavior of some entity. There are
three kinds of behavior diagrams: activity diagrams, use case diagrams, and state machine
diagrams.
Big Board - ANS A large board used by many agile models that is posted in a visible location
so that everyone can see the project's status at a glance. Also called an information radiator.
D
big O notation - ANS A system for studying the limiting behavior of algorithms as the size of the
problem grows large.
U
black-box test - ANS A test designed by someone who doesn't know how the code works
internally.
ST
brainstorming - ANS A group technique for discovering creative solutions to a problem.
bug - ANS A flaw in a program that causes it to produce an incorrect result or to behave
unexpectedly. Bugs are generally evil.
build engineer - ANS In Feature-Driven Development, someone who sets up and controls the
build process.
burndown chart - ANS In Scrum, a graph showing the amount of work remaining over time.
