SSA Exam with all Correct & 100% Verified Answers |
Actual Complete Version |Already Graded A+
Even if a formal specification does not exist, it is still correct to say every system has an
architecture. ✔Correct Answer-True
Scrum is one of the most popular approaches for Agile project management.
The Scrum process starts by electing issues from the sprint to compose a backlog. The backlog
corresponds to an iteration and it should last a pre-defined period of time, where those issues
will be addressed by the project team. At the end of the sprint, unfinished issues are returned
to the sprint for prioritisation.
The status of each activity should be updated to the Scrum board. ✔Correct Answer-False.
Elect issues from backlog to compose sprint
Defining a structured solution to meet all technical and operational requirements of a system
while optimising its quality attributes. ✔Correct Answer-Software Systems Architecture
During a standup, each development team member volunteers the status of the activities under
his or her responsibility (completed, next steps, and roadblocks). ✔Correct Answer-Agile daily
coordination meetings
They have considerable impact on a system's quality. ✔Correct Answer-Architectural
decisions
It can be used to manage computational resources on supercomputers and cloud environments.
✔Correct Answer-DRMS. Distributed resource management system
Upon a user's request, the DRMS will allocate resources to the user, but only if such resources
are available, the resources are within the user's quota, and the user is allowed to work in that
particular environment (supercomputer or cloud). ✔Correct Answer-True
A monitoring tool will be able to allocate resources on the distributed system managed by the
DRMS. ✔Correct Answer-False. The monitoring does not do the actual allocation
When requesting resources to a DRMS, the user needs to specify exactly what he or she wants
in terms of infrastructure (e.g., memory, computing, and storage). In some cases, it is also
possible to specify other requirements such as operating system. All users will get exactly the
same resources regardless of the environment, making the DRMS task rather simplistic in terms
of resource allocation. ✔Correct Answer-False. User get's requested resources.
,Some of the assignment requirements (DRMS) will be similar to the requirements of Internet
bankings and other web systems, at least in terms of what matters to build system
architectures. ✔Correct Answer-True
User Story ✔Correct Answer-A user story represents a small piece of business value that a
team can deliver in an Agile iteration; must have only enough information to guide the
development; then it can be incremented over time.
As a <user type>, I want to <function> so that <benefit> .
DRMS ✔Correct Answer-Distributed Resource Management System
Main Architectural Structures ✔Correct Answer-Module - code
Runtime/Component and Connector (C&C) - Interaction of structures at runtime
Allocation - Mapping the structures to the system's environments: where software is created
and executed (dev-ops, integration and testing)
There is no such thing as an inherently good or bad architectures ✔Correct Answer-True
Architectures are either more or less fit for some purpose ✔Correct Answer-True
Architectures can be evaluated but only in the context of
specific stated goals ✔Correct Answer-True
System Requirements ✔Correct Answer-Functional requirements, Quality Attribute
Requirements, Constraints
Functional Requirements ✔Correct Answer-• State what the system must do or how it must
behave or react to run-time stimuli
• Functionality is the ability of a system to do the work for which it was intended
• Functionality does not determine architecture
Quality Attribute Requirements ✔Correct Answer-• Annotate (qualify) functional
requirements
• Qualification might be how fast the function must be performed, how resilient it must be to
erroneous input, how easy the function is to learn, etc.
Constraints ✔Correct Answer-• Design decisions that have already been made for you
• They cannot be changed, so architecture has to be built on top of the constraints
ASR ✔Correct Answer-Architecturally Significant Requirements
Notations ✔Correct Answer-Informal - general purpose diagrams (powerpoint, etc)
Semi-formal - standardised notation (UML)
, Formal - precise, mathematically- based notation (ADLs - Architecture Description Languages)
When creating user stories, it is important to name the user story and identify the user, the
action and the associated benefits. User stories also need to be validated, therefore adding
acceptance criteria in order to make sure the user story can indeed be moved to the "DONE"
column in the Scrum board is always welcome. ✔Correct Answer-True
The way an architecture is conceived will determine the quality attributes it can achieve. It's
relationship to quality attributes is the only reason why an architecture is important.
✔Correct Answer-False. it's not the only reason?
Agile establishes that there is value in processes, tools and contracts. However, individuals,
customer collaborations and responding to change are more important. Unfortunately, it is not
always possible to work without processes and contracts, so Agile teams must be ready to adapt
to the company environment. ✔Correct Answer-True
The quality attributes a system can achieve are determined by its architecture, thus architects
must understand this concept. ✔Correct Answer-Technical Context
Architectures and systems must be built for a reason, thus architects must understand this
concept. ✔Correct Answer-Business Context
They are the only ones with impact on the architecture. ✔Correct Answer-ASRs
Recommended to take full advantage of an architecture. ✔Correct Answer-Architecture
Documentation
As a purchaser on the website, I want the ability to pay with B-PAY so that I may better manage
my personal finances. Correct User Story? ✔Correct Answer-True. Reasons don't have to be
entirely relevant to business.
Quality Attributes (rare ones) ✔Correct Answer-Variability, Portability, development
distributability, scalability, deployability, mobility, monitorability, safety, conceptual integrity,
marketability, quality-in-use (effectiveness, efficiency, freedom-from-risk)
How can quality attribute requirements be properly specified ✔Correct Answer-by building
quality attribute scenarios
Quality Attribute Scenarios force the architect to specify well defined, testable and verifiable
quality attributes ✔Correct Answer-True
Conditions under which the stimulus occurs, e.g., system in normal operation or overload.
✔Correct Answer-Environment
Actual Complete Version |Already Graded A+
Even if a formal specification does not exist, it is still correct to say every system has an
architecture. ✔Correct Answer-True
Scrum is one of the most popular approaches for Agile project management.
The Scrum process starts by electing issues from the sprint to compose a backlog. The backlog
corresponds to an iteration and it should last a pre-defined period of time, where those issues
will be addressed by the project team. At the end of the sprint, unfinished issues are returned
to the sprint for prioritisation.
The status of each activity should be updated to the Scrum board. ✔Correct Answer-False.
Elect issues from backlog to compose sprint
Defining a structured solution to meet all technical and operational requirements of a system
while optimising its quality attributes. ✔Correct Answer-Software Systems Architecture
During a standup, each development team member volunteers the status of the activities under
his or her responsibility (completed, next steps, and roadblocks). ✔Correct Answer-Agile daily
coordination meetings
They have considerable impact on a system's quality. ✔Correct Answer-Architectural
decisions
It can be used to manage computational resources on supercomputers and cloud environments.
✔Correct Answer-DRMS. Distributed resource management system
Upon a user's request, the DRMS will allocate resources to the user, but only if such resources
are available, the resources are within the user's quota, and the user is allowed to work in that
particular environment (supercomputer or cloud). ✔Correct Answer-True
A monitoring tool will be able to allocate resources on the distributed system managed by the
DRMS. ✔Correct Answer-False. The monitoring does not do the actual allocation
When requesting resources to a DRMS, the user needs to specify exactly what he or she wants
in terms of infrastructure (e.g., memory, computing, and storage). In some cases, it is also
possible to specify other requirements such as operating system. All users will get exactly the
same resources regardless of the environment, making the DRMS task rather simplistic in terms
of resource allocation. ✔Correct Answer-False. User get's requested resources.
,Some of the assignment requirements (DRMS) will be similar to the requirements of Internet
bankings and other web systems, at least in terms of what matters to build system
architectures. ✔Correct Answer-True
User Story ✔Correct Answer-A user story represents a small piece of business value that a
team can deliver in an Agile iteration; must have only enough information to guide the
development; then it can be incremented over time.
As a <user type>, I want to <function> so that <benefit> .
DRMS ✔Correct Answer-Distributed Resource Management System
Main Architectural Structures ✔Correct Answer-Module - code
Runtime/Component and Connector (C&C) - Interaction of structures at runtime
Allocation - Mapping the structures to the system's environments: where software is created
and executed (dev-ops, integration and testing)
There is no such thing as an inherently good or bad architectures ✔Correct Answer-True
Architectures are either more or less fit for some purpose ✔Correct Answer-True
Architectures can be evaluated but only in the context of
specific stated goals ✔Correct Answer-True
System Requirements ✔Correct Answer-Functional requirements, Quality Attribute
Requirements, Constraints
Functional Requirements ✔Correct Answer-• State what the system must do or how it must
behave or react to run-time stimuli
• Functionality is the ability of a system to do the work for which it was intended
• Functionality does not determine architecture
Quality Attribute Requirements ✔Correct Answer-• Annotate (qualify) functional
requirements
• Qualification might be how fast the function must be performed, how resilient it must be to
erroneous input, how easy the function is to learn, etc.
Constraints ✔Correct Answer-• Design decisions that have already been made for you
• They cannot be changed, so architecture has to be built on top of the constraints
ASR ✔Correct Answer-Architecturally Significant Requirements
Notations ✔Correct Answer-Informal - general purpose diagrams (powerpoint, etc)
Semi-formal - standardised notation (UML)
, Formal - precise, mathematically- based notation (ADLs - Architecture Description Languages)
When creating user stories, it is important to name the user story and identify the user, the
action and the associated benefits. User stories also need to be validated, therefore adding
acceptance criteria in order to make sure the user story can indeed be moved to the "DONE"
column in the Scrum board is always welcome. ✔Correct Answer-True
The way an architecture is conceived will determine the quality attributes it can achieve. It's
relationship to quality attributes is the only reason why an architecture is important.
✔Correct Answer-False. it's not the only reason?
Agile establishes that there is value in processes, tools and contracts. However, individuals,
customer collaborations and responding to change are more important. Unfortunately, it is not
always possible to work without processes and contracts, so Agile teams must be ready to adapt
to the company environment. ✔Correct Answer-True
The quality attributes a system can achieve are determined by its architecture, thus architects
must understand this concept. ✔Correct Answer-Technical Context
Architectures and systems must be built for a reason, thus architects must understand this
concept. ✔Correct Answer-Business Context
They are the only ones with impact on the architecture. ✔Correct Answer-ASRs
Recommended to take full advantage of an architecture. ✔Correct Answer-Architecture
Documentation
As a purchaser on the website, I want the ability to pay with B-PAY so that I may better manage
my personal finances. Correct User Story? ✔Correct Answer-True. Reasons don't have to be
entirely relevant to business.
Quality Attributes (rare ones) ✔Correct Answer-Variability, Portability, development
distributability, scalability, deployability, mobility, monitorability, safety, conceptual integrity,
marketability, quality-in-use (effectiveness, efficiency, freedom-from-risk)
How can quality attribute requirements be properly specified ✔Correct Answer-by building
quality attribute scenarios
Quality Attribute Scenarios force the architect to specify well defined, testable and verifiable
quality attributes ✔Correct Answer-True
Conditions under which the stimulus occurs, e.g., system in normal operation or overload.
✔Correct Answer-Environment
