Domain Driven Development
In the past, I used to think that the value of creating business systems lies in efficiency and speed. However, I now believe that those are rather secondary effects. The main focus of systems engineering should be to create a new Stairs of harmony among the people involved in the business. And to do that, it is necessary to understand the various forces at work in the Domain. For example, in accounting, there is the complexity of financial reporting. The operational departments are tired of the monthly variance analysis. The management is anxious because they can't see the end result. They don't understand the situation of subsidiary companies. From these stairs, where should we aim to go next? What kind of harmony can we find among these forces? That is the challenge of systems engineering.
No matter where the new "stairs" are, IT is necessary to reach them. System engineers have more influence on the future of the domain than they think. However, most engineers do not commit to the future of the domain and think it is someone else's problem. It is unfortunate for both the domain and the engineers.
Recently, there was a discussion about the Art Museum Archive issue from the perspective of engineers. I found it very interesting and learned a lot from it. If such discussions arise in every domain that engineers are involved in, both Domain and Systems Engineering will become more creative and exciting worlds.