[et_pb_section fb_built=”1″ fullwidth=”on” _builder_version=”4.16″ _module_preset=”default” global_colors_info=”{}”][et_pb_fullwidth_header title=”AGILA – Agile software architecture” subhead=”Part 3″ content_max_width_tablet=”” content_max_width_phone=”100%” content_max_width_last_edited=”on|desktop” _builder_version=”4.27.2″ _module_preset=”default” title_font=”|600|||||||” title_text_align=”left” title_font_size=”60px” subhead_font=”|600|||||||” subhead_font_size=”19px” background_enable_color=”off” background_image=”https:\/\/www.itech-progress.com\/wp-content\/uploads\/2020\/08\/AGILA_heller.jpg” height=”306px” custom_padding=”113px||298px|||” hover_enabled=”0″ title_font_size_tablet=”30px” title_font_size_phone=”27px” title_font_size_last_edited=”on|desktop” global_colors_info=”{}” sticky_enabled=”0″][\/et_pb_fullwidth_header][\/et_pb_section][et_pb_section fb_built=”1″ _builder_version=”4.17.3″ _module_preset=”default” custom_padding=”56px||6px|||” global_colors_info=”{}”][et_pb_row _builder_version=”4.17.3″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.20.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text content_tablet=”<\/p>\n<\/p>\n
Welcome to our new blog series, Requirements for Software Architects!
In this three-part series, learn about the significance of your customers' requirements, the different roles of Agile Requirement Engineering, and modern techniques.<\/p>\n
” content_phone=”<\/p>\n
What is it, really?<\/strong><\/p>\n In February 2001, 17 software developers met. From their perspective, existing practices lacked flexibility and customer proximity. The Agile Manifesto emerged, transforming the ways of working in software development in a similar way that ChatGPT is doing today. The core of agile methods is customer proximity, quick feedback loops, and continuous changes based on the feedback received. Agile approaches place people at the center of work\u2014not only on the customer side but also within the team.<\/p>\n ” content_last_edited=”on|phone” _builder_version=”4.27.2″ _module_preset=”default” custom_margin=”109px||||false|false” custom_margin_tablet=”109px||||false|false” custom_margin_phone=”0px||||false|false” custom_margin_last_edited=”on|phone” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n Welcome to the final part of the blog series<\/strong> [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.2″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n Architectural Requirements in Agile Projects<\/strong><\/p>\n 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.<\/p>\n Architectural requirements can cover various aspects:<\/p>\n – Performance<\/span> includes requirements for the system\u2019s performance, scalability, and responsiveness under certain load conditions. 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.<\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/www.itech-progress.com\/wp-content\/uploads\/2024\/11\/1677611813350.png” align=”center” _builder_version=”4.27.2″ _module_preset=”default” width=”59%” width_tablet=”59%” width_phone=”100%” width_last_edited=”on|desktop” border_radii=”on|10px|10px|10px|10px” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.2″ _module_preset=”default” custom_padding=”||0px|||” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n Agile Concepts for Architectural Requirements<\/strong><\/p>\n 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.<\/p>\n Here are some examples:<\/p>\n – User Stories for Architecture<\/span>: 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. 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.<\/p>\n [\/et_pb_text][et_pb_text _builder_version=”4.27.2″ _module_preset=”default” custom_padding=”43px|||||” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n Urgency as a Driver for Agile Architecture Work<\/strong><\/p>\n 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.<\/p>\n 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.<\/p>\n Urgency can have various reasons:<\/p>\n Risk Mitigation<\/span>: If certain architectural aspects present a high risk to the project, they should be addressed early to minimize potential problems. 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.<\/p>\n <\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.17.3″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.17.3″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.2″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]<\/p>\n Sources<\/strong><\/p>\n <\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" Welcome to the final part of the blog seriesAfter 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 […]<\/p>\n","protected":false},"author":1,"featured_media":43031,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[702,579],"tags":[],"class_list":["post-43980","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-recommended-reading","category-software-development"],"yoast_head":"\n
After we covered the basics of software architecture, agile development in general, and agile architectural approaches in the previous posts<\/a><\/strong><\/span>, in the final post of the series, we will look at the requirements agile projects bring for architectures.<\/p>\n
– Security<\/span> refers to requirements for data protection, secure data transmission, access control, and the overall security of the system.
– Scalability<\/span> 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<\/span> involves requirements that define how easily the system can be maintained, updated, and extended without negatively affecting functionality.
– Extensibility<\/span> refers to how easily and seamlessly the system can be extended with new features or modules without affecting existing code.
– Interoperability<\/span> concerns the system\u2019s ability to communicate and interact seamlessly with other systems or services.
– Architectural Patterns and Styles<\/span> can be defined as requirements to ensure that the architecture follows the desired design principles.
– Technological Requirements<\/span> include specific technologies, frameworks, or platforms used in the project.
– Non-functional Requirements<\/span>: These can include non-functional requirements such as usability, accessibility, and more.<\/p>\n
– Agile Architecture Documentation<\/span>: 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<\/span>: 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<\/span>: 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<\/span>: 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<\/span>: 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<\/span>: 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.<\/p>\n
Critical Functionalities<\/span>: 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<\/span>: If the system must perform well under expected load, it is essential to make architectural decisions that optimize performance and scalability.
Integration<\/span>: If the system interacts with other external systems or services, it is urgent to carefully plan and implement the integration architecture.
Changes in Requirements<\/span>: If the requirements change, it may be necessary to quickly adapt the architecture to ensure that the system meets current needs.<\/p>\n\n