In the last development session, one of the feedback was about making it easier to discover things.
I was thinking that maybe removing the system context diagrams and introducing topical landscape diagrams would help with that discovery process.
For example, instead of having MoJ SignOn context, HMPPS Auth context, we could have an "Authentication landscape" which could detail these lifecycle intentions [edit: in the original PR, we discussed how to expose intent that "MoJ SignOn" is essentially deprecated].
We could also expose the architecture decision records in the repo; the Structurizr API supports attaching markdown documents as ADR for each defined system.
In the last development session, one of the feedback was about making it easier to discover things.
I was thinking that maybe removing the system context diagrams and introducing topical landscape diagrams would help with that discovery process.
For example, instead of having MoJ SignOn context, HMPPS Auth context, we could have an "Authentication landscape" which could detail these lifecycle intentions [edit: in the original PR, we discussed how to expose intent that "MoJ SignOn" is essentially deprecated].
_Originally posted by @sldblog in https://github.com/ministryofjustice/hmpps-architecture-as-code/pull/45#discussion_r469267866_