Is the HMPPSSoftwareSystem interface good for our purposes? about hmpps-architecture-as-code HOT 2 OPEN

I like the current interface and the flexibility it gives me. People are (in my mind) at the same level and importance of software systems, and it reinforces this.

I can't say if we will ever create views for people. The overhead of adding an empty function is probably lower than keeping in mind which interface to use (we could have one for model items, relationships and views and compose them based on need).

The way it is can also help with contributions: it's explicit where parts have to go without having to build a mental model of what interface/class to use.

Should we rename it but keep the functions as-is? (For now?)

from hmpps-architecture-as-code.

Should we rename it but keep the functions as-is? (For now?)

I think that's the most sensible (read quickest, least impact) change. I agree that it's nice to treat people in the same way as systems, and we may end up wanting to generate views that revolve around them (?).

The cost of changing that later, or introducing a new interface, is pretty low too, so let's go with whatever feels right :)

from hmpps-architecture-as-code.