Considering the importance of architecture in software development, this article presents a proposal for managing software architecture in Scrum. The first chapter addresses the topic of locating software architecture in the Scrum. Development cycle; the second chapter describes the tasks of the software architect in Scrum. Finally, conclusions and future work are present.
Software Architecture in the Scrum Development Cycle
The fundamental idea of this proposal is to add an initial sprint call “Sprint 0” at the beginning of the development cycle. The main objective of the architect in Sprint 0 is to analyze and design the generality of the system. Which satisfies the requirements and is understandable by the team members albania phone number library from their different points of view during development. A key point is to reuse software artifacts creat from the architecture to be more agile in the development of specific products.
[3]. In Sprint 0, the architectu is built iteratively through a preliminary in the case where his target analysis of the architectural drivers (functional, quality and business requirements), and a feasibility
study of the project. It is not necessary to have all.
The requirements clear to begin the architectural design phase
To determine the architectural drivers, the highest priority business objectives, which are few in number, must be identifi. These business objectives become the quality scenarios or belize lists use cases. From this list, the ones that will have the impact on the architecture must. Architectural design can begin once the architectural drivers are defin. The requirements analysis process will then be influenc by the questions generat during architectural design.