SSA
Study online at https://quizlet.com/_hust1x
1. Even if a formal specification does not exist, it is still correct to say every
system has an architecture.: True
2. 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 back-
log. 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.: False. Elect issues
from backlog to compose sprint
3. Defining a structured solution to meet all technical and operational require-
ments of a system while optimising its quality attributes.: Software Systems Architecture
4. During a standup, each development team member volunteers the status
of the activities under his or her responsibility (completed, next steps, and
roadblocks).: Agile daily coordination meetings
5. They have considerable impact on a system's quality.: Architectural decisions
6. It can be used to manage computational resources on supercomputers and
cloud environments.: DRMS. Distributed resource management system
7. 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).: True
8. A monitoring tool will be able to allocate resources on the distributed system
managed by the DRMS.: False. The monitoring does not do the actual allocation
9. 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.: False. User get's requested resources.
, SSA
Study online at https://quizlet.com/_hust1x
10. Some of the assignment requirements (DRMS) will be similar to the require-
ments of Internet bankings and other web systems, at least in terms of what
matters to build system architectures.: True
11. User Story: 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> .
12. DRMS: Distributed Resource Management System
13. Main Architectural Structures: 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)
14. There is no such thing as an inherently good or bad architectures: True
15. Architectures are either more or less fit for some purpose: True
16. Architectures can be evaluated but only in the context of
specific stated goals: True
17. System Requirements: Functional requirements, Quality Attribute Requirements, Constraints
18. Functional Requirements: • 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
19. Quality Attribute Requirements: • 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.
20. Constraints: • Design decisions that have already been made for you
• They cannot be changed, so architecture has to be built on top of the constraints
21. ASR: Architecturally Significant Requirements
22. Notations: Informal - general purpose diagrams (powerpoint, etc)
Semi-formal - standardised notation (UML)
Formal - precise, mathematically- based notation (ADLs - Architecture Description Languages)
23. 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
, SSA
Study online at https://quizlet.com/_hust1x
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.: True
24. 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.: False. it's not the only reason?
25. Agile establishes that there is value in processes, tools and contracts. How-
ever, 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 environ-
ment.: True
26. The quality attributes a system can achieve are determined by its architec-
ture, thus architects must understand this concept.: Technical Context
27. Architectures and systems must be built for a reason, thus architects must
understand this concept.: Business Context
28. They are the only ones with impact on the architecture.: ASRs
29. Recommended to take full advantage of an architecture.: Architecture Documentation
30. 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?: True. Reasons don't
have to be entirely relevant to business.
31. Quality Attributes (rare ones): Variability, Portability, development distributability, scalability, de-
ployability, mobility, monitorability, safety, conceptual integrity, marketability, quality-in-use (effectiveness, efficiency,
freedom-from-risk)
32. How can quality attribute requirements be properly specified: by building quality
attribute scenarios
33. Quality Attribute Scenarios force the architect to specify well defined,
testable and verifiable quality attributes: True
34. Conditions under which the stimulus occurs, e.g., system in normal opera-
tion or overload.: Environment
35. Artifact being stimulated, e.g. a collection of systems, a system, parts of a
system.: Artifact
36. QAS structure: SSEARR
Study online at https://quizlet.com/_hust1x
1. Even if a formal specification does not exist, it is still correct to say every
system has an architecture.: True
2. 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 back-
log. 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.: False. Elect issues
from backlog to compose sprint
3. Defining a structured solution to meet all technical and operational require-
ments of a system while optimising its quality attributes.: Software Systems Architecture
4. During a standup, each development team member volunteers the status
of the activities under his or her responsibility (completed, next steps, and
roadblocks).: Agile daily coordination meetings
5. They have considerable impact on a system's quality.: Architectural decisions
6. It can be used to manage computational resources on supercomputers and
cloud environments.: DRMS. Distributed resource management system
7. 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).: True
8. A monitoring tool will be able to allocate resources on the distributed system
managed by the DRMS.: False. The monitoring does not do the actual allocation
9. 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.: False. User get's requested resources.
, SSA
Study online at https://quizlet.com/_hust1x
10. Some of the assignment requirements (DRMS) will be similar to the require-
ments of Internet bankings and other web systems, at least in terms of what
matters to build system architectures.: True
11. User Story: 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> .
12. DRMS: Distributed Resource Management System
13. Main Architectural Structures: 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)
14. There is no such thing as an inherently good or bad architectures: True
15. Architectures are either more or less fit for some purpose: True
16. Architectures can be evaluated but only in the context of
specific stated goals: True
17. System Requirements: Functional requirements, Quality Attribute Requirements, Constraints
18. Functional Requirements: • 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
19. Quality Attribute Requirements: • 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.
20. Constraints: • Design decisions that have already been made for you
• They cannot be changed, so architecture has to be built on top of the constraints
21. ASR: Architecturally Significant Requirements
22. Notations: Informal - general purpose diagrams (powerpoint, etc)
Semi-formal - standardised notation (UML)
Formal - precise, mathematically- based notation (ADLs - Architecture Description Languages)
23. 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
, SSA
Study online at https://quizlet.com/_hust1x
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.: True
24. 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.: False. it's not the only reason?
25. Agile establishes that there is value in processes, tools and contracts. How-
ever, 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 environ-
ment.: True
26. The quality attributes a system can achieve are determined by its architec-
ture, thus architects must understand this concept.: Technical Context
27. Architectures and systems must be built for a reason, thus architects must
understand this concept.: Business Context
28. They are the only ones with impact on the architecture.: ASRs
29. Recommended to take full advantage of an architecture.: Architecture Documentation
30. 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?: True. Reasons don't
have to be entirely relevant to business.
31. Quality Attributes (rare ones): Variability, Portability, development distributability, scalability, de-
ployability, mobility, monitorability, safety, conceptual integrity, marketability, quality-in-use (effectiveness, efficiency,
freedom-from-risk)
32. How can quality attribute requirements be properly specified: by building quality
attribute scenarios
33. Quality Attribute Scenarios force the architect to specify well defined,
testable and verifiable quality attributes: True
34. Conditions under which the stimulus occurs, e.g., system in normal opera-
tion or overload.: Environment
35. Artifact being stimulated, e.g. a collection of systems, a system, parts of a
system.: Artifact
36. QAS structure: SSEARR
