In the context of software architecture, the common definitions often focus on the structural aspects of system design. Here’s how the chosen answers align with the iSAQB® guidelines on software architecture:
Building Blocks (B): A fundamental concept in software architecture, building blocks refer to the modular units from which the system is constructed. These can include modules, classes, or components, all of which are vital for defining the structure and behavior of the system.
Relationships (D): Relationships in software architecture define how different components or building blocks interact with each other. These interactions are essential for understanding data flow, dependencies, and communication patterns within the system.
Components (E): Components are larger than building blocks and encompass them, representing significant units of functionality within the system. Each component usually encapsulates a portion of the system's overall functionality and interacts with other components via interfaces.
Interfaces (G): Interfaces define the points of interaction between components or building blocks. They are critical for ensuring that components can function independently yet interact seamlessly when required.
Questions # 12:
Which of the following principles apply to testing? (Choose two.)
Options:
A.
In general, exhaustive testing is not possible.
B.
Where many errors exist, more errors are usually hidden.
C.
Sufficient testing will show that a program is free of errors.
D.
Error-free test runs also mean: the software is usable.
The principles that apply to testing include:A. In general, exhaustive testing is not possible. - It is widely recognized in software testing that it is not feasible to test every possible input or state of a software application due to the vast number of variations and combinations, especially in complex systems.B. Where many errors exist, more errors are usually hidden. - This principle, often referred to as the pesticide paradox in software testing, suggests that discovering numerous bugs in a specific area of the software often indicates the presence of additional, less obvious bugs.
