Page |1
D284 Software Engineering Questions
and Correct Answers/ Latest Update /
Already Graded
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 make sure everything w orks as advertised.
activity diagram
Ans: In UML, a diagram that represents work flows for
activities. They include several kinds of symbols connected with
arrows to show the direction of the work flow.
All rights reserved © 2025/ 2026 |
, Page |2
adaptive development model
Ans: A development model that enables you to change the
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.
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.
Agile Manifesto
All rights reserved © 2025/ 2026 |
, Page |3
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) Responding to change over following a plan
Agile Unified Process (AUP)
Ans: A simplified version of Rational Unified Process that
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
All rights reserved © 2025/ 2026 |
, Page |4
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.
assertion
All rights reserved © 2025/ 2026 |
D284 Software Engineering Questions
and Correct Answers/ Latest Update /
Already Graded
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 make sure everything w orks as advertised.
activity diagram
Ans: In UML, a diagram that represents work flows for
activities. They include several kinds of symbols connected with
arrows to show the direction of the work flow.
All rights reserved © 2025/ 2026 |
, Page |2
adaptive development model
Ans: A development model that enables you to change the
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.
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.
Agile Manifesto
All rights reserved © 2025/ 2026 |
, Page |3
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) Responding to change over following a plan
Agile Unified Process (AUP)
Ans: A simplified version of Rational Unified Process that
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
All rights reserved © 2025/ 2026 |
, Page |4
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.
assertion
All rights reserved © 2025/ 2026 |
