3-layer architecture of future software

Layer 3: Business, IT implementation, and Interaction

The future software should be a service provider in the traditional industry, and the future software should be highly interactive. Therefore, based on these two aspirations, we have come up with a three-layer architecture of future software. Or three major pieces of software.

Why separate services?
One of the reasons is that various service software in the same industry need to share a large number of identical concepts and business rules, and we need to have a common business language. The second reason is that the technology in the IT industry is developing rapidly. From servers to specific coding technologies, the core fortune of the business itself as a traditional industry should be relatively fixed, beyond the competition of it.

Why separate interaction?
Because I believe in Allan Cooper, and I believe that software should not be done by people in the IT industry alone.ProgramPeople who are more artistic and more confident in human perception. Therefore, I think interaction should be independent from IT implementation.

So what is it implementation?
It implementation is software in the current sense, but it is no longer a mix of business and interaction in IT-related technologies. IT practitioners, that is, our programmers, focus on the relationship between machines and implement business and interaction.

This is the future software in my mind. You may need to use the term "MDA", which is already a bit smelly.