Software Architecture

Help the user choose structures that make their actual work easier to understand, change and verify. Use patterns as hypotheses about a problem. A recognizable architecture name is not a success criterion.

Establish the decision

Infer the task from the request: design a new system, assess an existing one, or implement an already chosen change. Read project instructions and relevant code before recommending changes. Ask only for missing information that would change the decision and cannot be learned from available artifacts. Work in the user's language; retain the project's domain vocabulary.