„The power of artificial intelligence is so incredible that it will change society in profound ways.“

(Bill Gates, founder of Microsoft)

What Are Our Guidelines for the Use of AI?

It’s the year 2024. The hype surrounding LLMs and ChatGPT started a year ago and is now having an initial impact on software development. AI chatbots can not only generate texts, draw photorealistic images, create music or answer questions — they can now also generate functioning programs in a programming language that even work. And through continuous learning, they are getting better and better at what they do. This is a powerful technology and so far there are hardly any regulations or legal guidelines for the use of these tools. So it’s time to start thinking about guard rails for the creation and use of this extremely powerful technology. Because one thing is clear: AI will be integrated into all kinds of products in the future and will therefore have a major impact on all our lives.

To really show the scale that will be upon us with the dawn of the AI age, I would like to quote here from a TED talk by Mustafa Suleyman:

“With that in mind, I offer the following metaphor today to help us grapple with what this moment [the widespread adoption of AI] really is. I think AI is best understood as something like a new digital species. Please don’t take this too literally, but I predict that we will see them as digital companions, new partners in our life journeys. Whether you believe we are on a 10‑, 20- or 30-year journey, I think this is the most accurate and fundamentally honest way to describe what is actually coming.”

And an important insight from him is: “We can only control what we can understand”. So what do we need to do to understand this?

“Nothing is as constant as change.”
(Heraclitus of Ephesus, 535–475 BC)

„A good software architect is like a werewolf: Afraid of silver bullets.“

(loosely based on Jochen Mader (codepitbull))

Welcome to the final part of the blog series
After we covered the basics of software architecture, agile development in general, and agile architectural approaches in the previous posts, in the final post of the series, we will look at the requirements agile projects bring for architectures.

Architectural Requirements in Agile Projects

Architectural requirements in agile projects are specific requirements or criteria that must be considered when developing the software architecture. They ensure that the resulting systems meet the desired quality characteristics, functionalities, and performance attributes. These requirements serve as guidelines for designing the architecture and influence technical decisions in the development process. In agile projects, architectural requirements should be agile and adaptable to respond to changing needs.

Architectural requirements can cover various aspects:

– Performance includes requirements for the system’s performance, scalability, and responsiveness under certain load conditions.
– Security refers to requirements for data protection, secure data transmission, access control, and the overall security of the system.
– Scalability relates to the system’s ability to adapt to increasing demands, whether in terms of the number of users, data volume, or transaction volume.
– Maintainability involves requirements that define how easily the system can be maintained, updated, and extended without negatively affecting functionality.
– Extensibility refers to how easily and seamlessly the system can be extended with new features or modules without affecting existing code.
– Interoperability concerns the system’s ability to communicate and interact seamlessly with other systems or services.
– Architectural Patterns and Styles can be defined as requirements to ensure that the architecture follows the desired design principles.
– Technological Requirements include specific technologies, frameworks, or platforms used in the project.
– Non-functional Requirements: These can include non-functional requirements such as usability, accessibility, and more.

In agile projects, architectural requirements are often developed in close collaboration with stakeholders and may change throughout the project. They serve as a guide for the continuous adaptation and development of the architecture to ensure that the final product meets the requirements and expectations.

Agile Concepts for Architectural Requirements

Agile concepts for architectural requirements emphasize flexibility, collaboration, and continuous adaptation of requirements. These concepts aim to ensure that architectural requirements are agile and can evolve in a constantly changing environment.

Here are some examples:

– User Stories for Architecture: Similar to functional requirements, architectural requirements can be formulated as user stories. These user stories describe the requirements from the perspective of a user or stakeholder role. They focus on the value the architecture provides to these users.
– Agile Architecture Documentation: Agile concepts prefer lightweight documentation that can be quickly adapted. Diagrams, sketches, whiteboard sketches, and brief descriptions can be used to document architecture principles and decisions.
– Emergent Architecture: Agile architects prefer developing emergent architecture, which evolves gradually from the requirements and functionality. This allows for flexible responses to changing requirements and conditions without extensive upfront planning.
– Risk-oriented Architectural Requirements: Agile architects identify and prioritize risks associated with the architecture. Requirements are set based on these risks, and corresponding strategies are developed to mitigate them.
– Continuous Adaptation: Architectural requirements are continuously reviewed and adjusted to ensure they remain current and relevant. This is done in close collaboration with stakeholders to ensure the architecture meets current needs.
– Just-in-Time Decisions: Agile teams make decisions “just-in-time” as the requirements and understanding of the system grow. This allows them to base decisions on up-to-date information.
– Collaborative Work: Architectural requirements are developed through collaborative work with the development team, product owners, and other stakeholders. This fosters shared understanding and ensures better implementation of the requirements.

These agile concepts for architectural requirements help ensure that the architecture remains flexible, adaptable, and aligned with current needs, while also ensuring high quality and customer satisfaction.

Urgency as a Driver for Agile Architecture Work

Urgency as a driver for agile architecture work refers to the need to focus on specific aspects of the software architecture that must be prioritized due to their critical importance or potential impact on the project.

This approach is based on the idea that not all parts of the architecture are equally important, and it makes sense to focus first on those aspects that have an immediate and significant influence.

Urgency can have various reasons:

Risk Mitigation: If certain architectural aspects present a high risk to the project, they should be addressed early to minimize potential problems.
Critical Functionalities: If the architecture is directly related to critical system functions, it is urgent to prioritize these areas to ensure performance and reliability.
Performance and Scalability: If the system must perform well under expected load, it is essential to make architectural decisions that optimize performance and scalability.
Integration: If the system interacts with other external systems or services, it is urgent to carefully plan and implement the integration architecture.
Changes in Requirements: If the requirements change, it may be necessary to quickly adapt the architecture to ensure that the system meets current needs.

Agile architecture work, taking urgency into account, allows for a quick response to the most pressing concerns. This ensures that the project builds on a solid foundation. However, a balance is required to align urgency with the long-term goals of architecture and technical integrity.

Sources

• https://www.scrum.org/
• http://agilemanifesto.org/
• https://www.isaqb.org/
• https://de.wikipedia.org/wiki/Softwarearchitektur
• https://www.agile-academy.com/
• Mike Cohn: Agile Design: Intentional Yet Emergent.
• Stefan Toth: “Approach Patterns for Software Architecture: Combiniable Practices in Times of Agile and Lean”, 2nd edition, Hanser Verlag 2015

Agile Architectural Approach

This approach integrates agile principles and methods into the process of designing and developing software architectures. It aims to overcome traditional rigid and upfront planning approaches to architecture definition and instead promotes a flexible, adaptable, and incremental approach.
Within the agile architectural approach, architects and developers are encouraged to collaborate, continuously learn, and adapt to changing requirements.

Some characteristics of the agile architectural approach include:

– Continuous Adaptation: Instead of designing a complete architecture in advance, agile teams develop an initial architectural direction and adapt it over time as they learn more about the project and its requirements.

– Incremental Development: The architecture is developed gradually, evolving with each iteration and adjusting to the changing needs of the project.

– Close Collaboration: Architects work closely with the development team to ensure that architectural principles are integrated into the ongoing development process. In many agile approaches, architecture is considered from the start. This way, the architect can be assigned to a team and carry out their tasks within the team, ensuring that architectural principles are considered in the development process from day one.

– Clear Communication: Instead of extensive documentation, the agile architectural approach favors clear and understandable communication to share architectural decisions within the team.

– Fast Feedback: Through frequent deliveries of working software and prototypes, architects receive continuous feedback from stakeholders, users, and possibly customers during the review. During the sprint, individuals can be invited as needed. The Product Owner ensures that they provide feedback.

– Evolutionary Architecture: The architecture continually evolves to meet changing requirements. This allows a focus on what is essential and helps avoid unnecessary complexity.

– Risk Reduction: By identifying potential architectural problems early and being able to take countermeasures, risks are minimized.

Designing Architecture Iteratively and Agile – Risk-Driven Architectural Work

Risk-driven architectural work refers to an approach where the identification, assessment, and management of risks play a central role in the development and design of the software architecture. Rather than focusing solely on technical or functional aspects, this approach emphasizes evaluating and mitigating risks that could impact the success of the project.

The core idea behind risk-driven architectural work is to address critical risks first to ensure early on that the project is built on a solid foundation. This involves:

– Risk Identification: Architects analyze and identify potential risks related to requirements, technology, scalability, performance, security, and other relevant factors.

– Risk Assessment: Identified risks are assessed to determine which ones pose the greatest threat to the success of the project.

– Risk Prioritization: Based on the assessment, risks are prioritized by urgency and impact. Those with higher priority are addressed first.

– Development of Risk Mitigation Strategies: For the identified and prioritized risks, strategies are developed to mitigate or prevent them. This can be done through technical solutions, architectural adjustments, or alternative approaches.

– Prototyping and Validation: In some cases, it may be necessary to create prototypes or proof-of-concepts to verify the effectiveness of the chosen risk mitigation strategies.

– Iterative Adjustment: During the development process, risk assessments are continuously reviewed and updated to ensure new risks are identified and addressed.

By considering and addressing risks from the outset, architects can detect and mitigate potential problems early. This reduces the likelihood of errors and delays. This approach ensures that the software architecture is solid, stable, and meets the project’s requirements.

Roles of Architects in Agile Projects

In agile projects, different role models for architects can exist depending on the size of the team, the type of project, and the specific requirements.

Here are some common role models for architects in agile projects:

– Agile Architect: This role is responsible for designing the software architecture with a focus on flexibility, collaboration, and adaptability. The agile architect works closely with development teams and product owners to ensure that the architecture reflects agile values and principles.

– Architect as Part of the Development Team: In smaller agile teams, the architect may be part of the development team and actively participate in coding and implementing features. This allows for close collaboration and continuous alignment of the architecture with the development work.

– Technology Advisor: An architect may serve as a technology advisor, helping the team select appropriate technologies, frameworks, and tools. They ensure that the chosen technologies meet the project’s requirements and integrate well into the architecture.

– Architecture Coach: This role involves coaching the team on best practices, architectural patterns, and principles. The architecture coach promotes understanding of architecture practices and helps the team make better technical decisions.

– Quality and Maintainability Evangelist: Architects can take responsibility for ensuring that the developed software is of high quality, maintainable, and scalable. They set standards for code quality and work with the team to ensure these standards are met.

– Architecture Strategist: This role takes a long-term view of the architecture and helps define a vision for the technical development of the product. They consider technological trends, organizational goals, and future requirements to ensure the architecture remains successful in the long run.

It is important to note that role models for architects in agile projects can vary. In any case, collaboration between architects, the development team, product owners, and other relevant stakeholders is crucial. This ensures that the architecture meets the needs of customers, users, and stakeholders, and is implemented in an agile manner.

Ways to Involve Stakeholders in Agile Architecture Work

Involving stakeholders in agile architecture work is crucial to ensure that the developed software meets the needs and expectations of all relevant parties. Here are three ways to engage stakeholders in agile architecture work:

– Regular Feedback and Reviews: By holding regular meetings or reviews, stakeholders have the opportunity to view the results of the sprint and provide feedback. This can take the form of demos, presentations, or discussions. The team can experiment with how the review should be structured, and stakeholders can communicate their requirements, expectations, and concerns, leading to continuous adaptation and improvement of the architecture.

– Involvement in Planning and Prioritization: By inviting stakeholders to participate in planning sessions where upcoming tasks and priorities are discussed, they have the chance to share their perspectives and ensure that the architecture work considers the aspects most important to them. In a Scrum framework, the entire stakeholder group typically does not participate in planning sessions. The Product Owner (PO) represents the voice of the customer and user, and they must prioritize which backlog stories are to be planned together with the development team.

– User Stories and Requirements: Collaborate with stakeholders to create or revise user stories and requirements that will inform the development of the architecture. These user stories can serve as a foundation for the architectural work, ensuring that the architecture meets the desired features and characteristics.

The key element in all of these approaches is open communication and close collaboration with stakeholders. This helps avoid misunderstandings, respond early to feedback, and ensure that the architecture meets the needs and expectations of everyone involved.

Sources

• https://www.scrum.org/
• http://agilemanifesto.org/
• https://www.isaqb.org/
• https://de.wikipedia.org/wiki/Softwarearchitektur
• https://www.agile-academy.com/
• Mike Cohn: Agile Design: Intentional Yet Emergent.