SWE 201C: A+ QUESTIONS AND ANSWERS LATEST
UPDATE!
A constraint to only use Microsoft Project during the system development is a non-functional
requirement.
A. True.
B. False.
A
Looking at the difference between user requirements and system specifications in the ATM example,
we know that swiping the card and prompting for a PIN are requirements, while reading the card
details and a 4-digit PIN are specifications.
A. True.
B. False.
A
Partitioning of a large system into smaller subsystems helps the buy-or-build decision because we can
examine each subsystem and reason about possible buy-or-build options for each.
A. True.
B. False.
A
Software architecture concerns itself with both estimation and quality but not partitioning.
A. True.
B. False.
B
Software design is the process of transforming the stated problem into a ready-to-use
implementation.
A. False
B. True
A
Abstract solutions do not require extensive domain knowledge and effectively reduce the costs during
the software design phase.
A. False
B. True
, A
It is often advised that abstract solutions do not provide optimization details regarding the
implementation.
A. True
B. False
A
When it comes to software design, it is always best to follow a solution that is widely popular in the
industry
A. False
B. True
A
While a solution coming from software design does not include implementation details, there are still
common cases where pseudocode may be provided to correctly capture the sense of a complex
algorithm.
A. True
B. False
A
The goal in low coupling is to ensure that changes don't cross the boundaries of modules.
A. True
B. False
A
The goal in real-life software development is to aim for object and functional cohesion and anything
less than this should be justified.
A. True
B. False
A
True or False: inheritance strengthens cohesion.
A. True
B. False
B
UPDATE!
A constraint to only use Microsoft Project during the system development is a non-functional
requirement.
A. True.
B. False.
A
Looking at the difference between user requirements and system specifications in the ATM example,
we know that swiping the card and prompting for a PIN are requirements, while reading the card
details and a 4-digit PIN are specifications.
A. True.
B. False.
A
Partitioning of a large system into smaller subsystems helps the buy-or-build decision because we can
examine each subsystem and reason about possible buy-or-build options for each.
A. True.
B. False.
A
Software architecture concerns itself with both estimation and quality but not partitioning.
A. True.
B. False.
B
Software design is the process of transforming the stated problem into a ready-to-use
implementation.
A. False
B. True
A
Abstract solutions do not require extensive domain knowledge and effectively reduce the costs during
the software design phase.
A. False
B. True
, A
It is often advised that abstract solutions do not provide optimization details regarding the
implementation.
A. True
B. False
A
When it comes to software design, it is always best to follow a solution that is widely popular in the
industry
A. False
B. True
A
While a solution coming from software design does not include implementation details, there are still
common cases where pseudocode may be provided to correctly capture the sense of a complex
algorithm.
A. True
B. False
A
The goal in low coupling is to ensure that changes don't cross the boundaries of modules.
A. True
B. False
A
The goal in real-life software development is to aim for object and functional cohesion and anything
less than this should be justified.
A. True
B. False
A
True or False: inheritance strengthens cohesion.
A. True
B. False
B
