SE-Training GmbH’s Post

📆 13 - 15 March | Systems Architecting (Intermediate level) Course | Zürich What will you learn? • What is systems architecture and how does it differ from the system design? • How does it relate to Systems and Holistic Thinking? • What makes a good architecture: how many architectures do we need? • What makes up a good architecture so important in the context of complex systems? • Why are Interfaces such a fundamental concept in Systems Architectures? • What is the relationship between the Operational Architecture and systems control? • Can/should we develop the architectures for a system and its Digital Twin together? • How does it help with decision making for an uncertain development environment? • Why is it important to develop variants and provide variation points and how do they relate to the interfaces? • What is a logical and repeatable methodology to develop architectures? • How can we model the architectures? Do we need MBSE? Do we need tools? • How can we ensure that the models are consistent and connected? • Where can one customise the architectures? • When is an agile approach permissible, when should you take extreme caution? • How do architectures help developing the system for safety, reliability, availability, maintainability, and inspectability? • Why is it important to separate the system’s (sometimes called “logical”) from the physical architectures? • How do all architecture map to the others? Why is mapping a powerful mechanism in developing for complexity? • What is the timing relationship between the various system (logical) architectures and the physical design? • What are the main skills of a senior Systems Architect? https://lnkd.in/eTBPmbxK #systemarchitecture #systemarchitect #systemdesign #systemdevelopment #systemsengineering

Building robust and very well segregated architectures facilitates the maintenance and implementation of new features. I recommend taking a look at the Abp Framework documentation Link:https://docs.abp.io

ADR (Architecture Decision Record) is a crucial document that captures significant architecture decisions, providing insights into their context and consequences. It brings clarity and transparency in decision-making processes. #softwarearchitecture #systemdesign #ADR #architecture

Some of my principles for system architecture 1. Focus on real benefits rather than the technology itself 2. Look at application services and APIs rather than resources and technologies 3. Choose the most mainstream and mature technology 4. Completeness is more important than performance 5. Develop and follow compliance standards, codes and best practices 6. Pay attention to architecture scalability and operability 7. Comprehensive closure of control logic 8. Don’t accommodate the technical debt of legacy systems 9. Don’t rely on your own experience, rely on data and learning 10. Be careful about X – Y questions and ask about the original requirements 11. Radical is better than conservative, innovation and practicality are not in conflict

Difference between requirements architecture and requirements model? > Requirements architecture refers to the high-level structure or framework that organizes and represents the requirements for a project or system. It defines the overall approach and principles governing how requirements are organized, categorized, and managed throughout the project lifecycle. > Requirements model is a representation or abstraction of the requirements for a project or system using graphical or textual notations. It provides a structured way to visualize, analyze, and communicate requirements to stakeholders and project teams.

Enterprise Continuum provides methods of classifying architecture and solution artifacts, both internal and external to the Architecture Repository as they evolve from generic Foundation Architectures to Organization Specific Architectures where generic Architectures are placed on the left side of the continuum. A Continuum is a continuous sequence in which adjacent elements are not that different from each other, but the extremes are quite distinct. The Enterprise Continuum contains two specializations, namely the Architecture and Solutions Continua: -       Architecture Repository is a place where we store Architecture Documents and Artifacts. The repository also contains all the reference materials as we go through ADM. The reference material includes All reference models, technical stuff, industry specific model and architecture specific to your enterprise. Enterprise continuum is used to classify the artifacts in the repository. Enterprise continuum documents are arranged from generic(left) to specific(right) -       The Solutions Continuum provides a consistent way to describe and understand the implementation of the assets defined in the Architecture Continuum

Everyone wants software architecture documentation until they realize it means constant updates and carefully crafted content and diagrams. #SoftwareArchitecture #SoftwareEngineering #Documentation

Event-driven architecture (EDA) is a software design approach emphasizing the production, detection, consumption, and reaction to events. In this architecture, events are state changes or updates within a system. 

We live in a world where the ability to design, communicate, and manage system architectures effectively is critical. Enter ISO/IEC/IEEE 42010:2022, the gold standard for architecting systems. This framework provides the principles and practices to ensure system architecture descriptions are consistent, relevant, and actionable, making it an indispensable tool for organisations across industries. In this article, you’ll clearly understand ISO/IEC/IEEE 42010:2022, the international standard for system architecture descriptions. Learn how it helps organisations design robust systems, communicate effectively with stakeholders, and manage architectural complexity. Whether you’re new to architecture frameworks or looking to refine your approach, this guide will equip you with practical insights. https://lnkd.in/dtpypfh8

I think IT architecture is more important than ever, as organisations struggle to do more with less, and get demonstrable business value from IT initiatives. The problem is, architecture done badly becomes the "department of no". Our approach is to do "just enough architecture, just in time" - a solid understanding of architecture principles is about enabling innovation, not blocking it, while also keeping systems, security and data safe. This course is a great entry point for people who want to learn architecture, and also for those who want a refresher - or some of the foundational understanding for work they are already doing.