Architectural prototyping Flashcards
(25 cards)
Give the ISO-style definition of an architectural prototype.
A set of executable artefacts created to investigate architectural qualities related to stakeholder concerns for a system under development. :contentReference[oaicite:26]{index=26}
List the five characteristic “fingerprints” of an architectural prototype.
Learning tool, quality focus, minimal functionality, risk reduction, knowledge transfer. :contentReference[oaicite:27]{index=27}
Name the three main flavours of architectural prototype.
Exploratory, Experimental (measurement), Evolutionary (grow-into-product). :contentReference[oaicite:28]{index=28}
What is the primary purpose of exploratory prototypes?
To clarify requirements or compare broad architectural alternatives at low cost. :contentReference[oaicite:29]{index=29}
Describe the hypothesis-experiment-conclusion loop used in prototyping.
Formulate a hypothesis, build/run the prototype to gather data, interpret results and decide whether to adopt, revise, or discard the idea. :contentReference[oaicite:30]{index=30}
Which quality attributes are best suited to direct measurement with prototypes?
Performance, scalability, availability, and usability (when UI and backend can be separated). :contentReference[oaicite:31]{index=31}
Which attributes are hardest to validate solely through prototyping?
Security (many threats need formal analysis) and long-term modifiability (often inferred from code inspection rather than runtime). :contentReference[oaicite:32]{index=32}
How does an architectural backlog relate to prototypes?
Uncertainties and high-risk ASRs are logged as backlog items; prototypes are scheduled spikes to resolve or de-risk those items. :contentReference[oaicite:33]{index=33}
State the main difference between exploratory and experimental prototypes.
Exploratory clarifies direction; experimental gathers quantitative evidence under controlled load or fault scenarios. :contentReference[oaicite:34]{index=34}
Why are prototypes considered “measurement-based” evaluation techniques?
They produce empirical data (latency, throughput, fail-over time) rather than expert opinion, feeding into evaluation frameworks like ATAM. :contentReference[oaicite:35]{index=35}
Give one availability tactic that can be validated with a prototype.
Active redundancy with heartbeat monitoring can be mocked and fail-over time measured on the prototype cluster. :contentReference[oaicite:36]{index=36}
Summarise the Twitter SQL vs. Neo4J prototype experiment in one line.
A side-by-side spike showed graph DB read latency beat relational queries but buildability dropped; data informed migration planning. :contentReference[oaicite:37]{index=37}
What did the legacy enterprise DevOps prototype demonstrate?
A modern CI/CD pipeline reduced build time and improved testability, offering concrete evidence to overcome organisational resistance. :contentReference[oaicite:38]{index=38}
Why should prototype code track provenance and be disposable?
To avoid accidental production use of half-baked experiments and to keep architectural decisions auditable. :contentReference[oaicite:39]{index=39}
When does an evolutionary prototype become part of the final system?
When iterative refinement hardens the prototype until it meets production quality, effectively seeding the product codebase. :contentReference[oaicite:40]{index=40}
How can usability be tested with an architectural prototype?
By wiring UI screens to stubbed back-end services so UX researchers can observe user interaction early. :contentReference[oaicite:41]{index=41}
What risk does an architectural prototype explicitly target?
The most uncertain or most expensive design decision identified during analysis or synthesis. :contentReference[oaicite:42]{index=42}
Name two common tools or techniques for building prototypes.
Docker-compose for quick deployment topologies; Load-testing scripts (Locust, k6) for performance experiments. :contentReference[oaicite:43]{index=43}
How does prototyping complement scenario-based reviews like ATAM?
Prototype metrics give hard evidence for sensitivity points and trade-offs uncovered in workshop discussions. :contentReference[oaicite:44]{index=44}
Complete the sentence: “Prototype scope should be driven by …”
…the single stakeholder concern or ASR that poses the highest risk at the current project stage. :contentReference[oaicite:45]{index=45}
What’s the danger of keeping a prototype secret from the main team?
Knowledge stays siloed; lessons aren’t transferred; architectural decisions may be repeated or contradicted. :contentReference[oaicite:46]{index=46}
Give an example of a conditional criterion that decides prototype success.
“If average checkout latency under 2 000 concurrent users ≤ 500 ms, adopt caching layer; else reconsider data partitioning.” :contentReference[oaicite:47]{index=47}
List a non-technical benefit of architectural prototyping.
It promotes shared understanding and buy-in, reducing resistance when major architectural shifts are proposed. :contentReference[oaicite:48]{index=48}
Why might a prototype be discarded even if it ‘works’?
Code quality, scalability headroom, or licensing terms may make it cheaper to re-implement than to harden the throwaway spike. :contentReference[oaicite:49]{index=49}