iSAQB defines a systematic approach to design a software system. In real-life projects, IT Architects encounter far different challenges, which will not correlate to the concrete structure described below. Activities of the referenced process are not executed in the described order, but based on stakeholder demand, requirements and influences. However, I do belive it’s usefull to know a red-line in this roughly defined discipline of IT.
You can find details for each discipline of this process within the next pages of this chapter.
2018-03-09%20Architecture%20Process.svg
Vision of a System
Even though any system starts with an idea. It’s the software architects responsibility to categorize this idea by type of use or type of control:
Type of Use
Interactive Online System / Operational System
- Business Processes
- Transactions based on current organizational data
- High availability and performance
Type of Control
Event Driven
- Control mechanism
Supporting System
- Calculations and Analysis
- Decision Support Systems
- Read-Only on copies of organizational data\r\n Longer runtimes
Procedural Control
- Implementation components
Background Processing System
- Offline- or Batchsystems
- Staggered pre- or postprocessing of data
Parallel Control / Concurrency
- Multiple, independent components
Embedded System
- Runs on specific, limited hardware and controls these
Declarative or rule-based Control
- Interpreter of rules
Realtime System
- Defined guaranty for delivery in time
- Time-critical operations