Flow 1

Mon, 01 Jan 0001 00:00:00 +0000

Question

We’re talking about software engineering. (and architecture, whatever).

Please let’s find engineering (and/or architectural ) approaches which follow this scheme - where user needs, or JTBD, or other product thing serve as a base or frame to reason about system, provide required context to our view. I’m talking about this because many of the approaches - like C4 model - where we have just several diagrams, and there is no underlying guiding forces (not just architectural, but I’m talking about why something is even exist? like user send email, bla-bla, then system responds - what we’re solving here?)

Flow 2

Mon, 01 Jan 0001 00:00:00 +0000

Answer 1

Yes. The thing you are looking for is not really another architecture-view notation. It is closer to an intent-driven / goal-driven / scenario-driven architecture process, where architectural elements remain traceable back to the reason the system exists.

Goal Oriented Architecture on AI Engineering and Architecture

Flow 1

Question

Flow 2

Answer 1