I wanted to share an analysis of a very interesting work where they develop concepts related to software architecture solutions. We know that the architecture of a software solution is very important to the success of a development.
In my experience as a software architect in previous works dedicated to the software industry, very often expressed an effect of "do not have time to complete thearchitectural review. " What is the justification? if we can justify it. It is very expensive,time consuming, depending on the architectural documentation of the solution, a scenario that could never discuss "is a small project with a limited life cycle, with minimum documentation"
So what options do we have when the project has these characteristics, and we'resure that we execute architectural reviews?
“However, in spite of the demonstrated benefits of architecture reviews, many projects are unable or unwilling to use them. These projects tend to have the following characteristics:
- Short schedules, possibly including repeated development episodes with very short cycles, such as 3 weeks
- Tight deadlines, leaving little or no time for activities not focused on producing the product.
- Neglected documentation, especially internal documentation such as architecture documents.
- Frequently changing technological and/or user requirements
- Typically small teams” [1]
Currently, all software solution uses a design pattern. Then complete an approachwhere software solutions can be analyzed with simple features such as those developed in the paper and provided for the concept of architectural patternsbecomes a very attractive mechanism.
“We developed an architecture review method that uses the architecture patterns in a system to identify important issues in the achievement of quality attributes” [1]
This is an interesting read on the topic, I hope to enjoy.
[1] Neil B. Harrison and Paris Avgeriou, Pattern-Based Architecture Reviews. Department of Computing and Networking Sciences, Utah Valley State College,Orem, Utah, USA.
In my experience as a software architect in previous works dedicated to the software industry, very often expressed an effect of "do not have time to complete thearchitectural review. " What is the justification? if we can justify it. It is very expensive,time consuming, depending on the architectural documentation of the solution, a scenario that could never discuss "is a small project with a limited life cycle, with minimum documentation"
So what options do we have when the project has these characteristics, and we'resure that we execute architectural reviews?
“However, in spite of the demonstrated benefits of architecture reviews, many projects are unable or unwilling to use them. These projects tend to have the following characteristics:
- Short schedules, possibly including repeated development episodes with very short cycles, such as 3 weeks
- Tight deadlines, leaving little or no time for activities not focused on producing the product.
- Neglected documentation, especially internal documentation such as architecture documents.
- Frequently changing technological and/or user requirements
- Typically small teams” [1]
Currently, all software solution uses a design pattern. Then complete an approachwhere software solutions can be analyzed with simple features such as those developed in the paper and provided for the concept of architectural patternsbecomes a very attractive mechanism.
“We developed an architecture review method that uses the architecture patterns in a system to identify important issues in the achievement of quality attributes” [1]
This is an interesting read on the topic, I hope to enjoy.
[1] Neil B. Harrison and Paris Avgeriou, Pattern-Based Architecture Reviews. Department of Computing and Networking Sciences, Utah Valley State College,Orem, Utah, USA.
Comments
Post a Comment