3 ms·

This reads like GPT-2 generated business platitudes. "Data is reasonably structured to allow automated processing.". "Data is made available as quickly as nece

This reads like GPT-2 generated business platitudes. "Data is reasonably structured to allow automated processing.". "Data is made available as quickly as necessary to preserve the value of the data."

dgb23 6y ago
From skimming the document I don't get what "Architecture" even means. What do business processes have to do with architecture? I always assumed the term describes a category of software engineering practices. In all of the software things I've participated in, the main driver for any tool, application, library etc. was always data and data flow. Data comes from some place and then gets processed and displayed or consumed. And from these requirements a higher level view, an architecture so to speak, emerges. As someone who works in small teams, I have never even heard of most of the tools mentioned in this document. The business focused language is very repelling as well. I'm not sure whether I'm too simple minded and incompetent or just live in a completely different world.
- johnorourke 6y ago
  Business processes have everything to do with architecture. You've said it yourself: "Data comes from some place and then gets processed and displayed or consumed." If you don't factor in who that data comes from and why, and who's consuming it and why, then you don't have all the information you need to be a good architect.
  - dgb23 6y ago
    With business processes I rather meant things related to strategic decision making and so on and not domain modelling and I/O processes. Those are obviously related to engineering. But the advice under the business category is rather generic and strategic, what to buy, what to focus on etc. I don't see how any of that is related to domain modelling, I/O etc. Also I'm not an architect, I'm a programmer. I literally don't understand what an architect is as stated above, especially not when looking at this document.

dgb23 6y ago

From skimming the document I don't get what "Architecture" even means. What do business processes have to do with architecture? I always assumed the term describes a category of software engineering practices. In all of the software things I've participated in, the main driver for any tool, application, library etc. was always data and data flow. Data comes from some place and then gets processed and displayed or consumed. And from these requirements a higher level view, an architecture so to speak, emerges. As someone who works in small teams, I have never even heard of most of the tools mentioned in this document. The business focused language is very repelling as well. I'm not sure whether I'm too simple minded and incompetent or just live in a completely different world.

johnorourke 6y ago
Business processes have everything to do with architecture. You've said it yourself: "Data comes from some place and then gets processed and displayed or consumed." If you don't factor in who that data comes from and why, and who's consuming it and why, then you don't have all the information you need to be a good architect.
- dgb23 6y ago
  With business processes I rather meant things related to strategic decision making and so on and not domain modelling and I/O processes. Those are obviously related to engineering. But the advice under the business category is rather generic and strategic, what to buy, what to focus on etc. I don't see how any of that is related to domain modelling, I/O etc. Also I'm not an architect, I'm a programmer. I literally don't understand what an architect is as stated above, especially not when looking at this document.