Business Goals to Architecture Driver Mapping¶

Run the Business Goals to Architecture Driver Mapping MicroSim Fullscreen
Edit in the p5.js Editor

About This MicroSim¶

A five-level traceability hierarchy for a healthcare patient portal (Mission, Business Goals, Business Drivers, Architectural Drivers, and QA Scenarios), showing that architectural decisions are grounded in business context.

How to Use¶

Click any item to highlight its complete traceability chain upward and downward in gold. Hover a connecting arrow to read the "because... therefore..." reasoning link. Clear Highlight resets the view.

Iframe Embed Code¶

You can add this MicroSim to any web page by adding this to your HTML:

<iframe src="https://dmccreary.github.io/atam/sims/business-to-architecture-mapping/main.html"
        width="100%"
        scrolling="no"></iframe>

Lesson Plan¶

Grade Level¶

Undergraduate / Professional

Duration¶

10-15 minutes

Prerequisites¶

Familiarity with business goals and quality attribute scenarios.

Bloom's Taxonomy Level¶

Analyze (L4)

Learning Objective¶

Students can trace an architectural driver backward to its originating business goal and business driver, demonstrating that architectural decisions are grounded in organizational context.

Activities¶

Exploration (5 min): Students freely interact with the MicroSim to discover its behavior.
Guided Practice (5 min): Working from the learning objective above, students answer 2-3 focused questions posed by the instructor.
Discussion (5 min): Students share observations and connect them back to ATAM concepts.

Assessment¶

Ask students to pick a QA scenario and trace it all the way back to the mission statement.

References¶

Bass, L., Clements, P., & Kazman, R. (2021). Software Architecture in Practice (4th ed.). Addison-Wesley.
Kazman, R., Klein, M., & Clements, P. (2000). ATAM: Method for Architecture Evaluation (CMU/SEI-2000-TR-004).