Evaluation and Documentation of Software Architectures in Software Companies: An Exploratory Study
software architecture, evaluation of software architectures, quality attributes
Often the software architect responsible for the definition and evaluation architectural can not establish that non-functional requirements must be identified as a priority in the development of their systems and ultimately not determine them at the time of definition of the architecture, which may allow that unforeseen failures can occur during system implementation and that may require more time and resources to be corrected than was previously treated. In many cases, either by lack of professionals or the need for rapid deployment of a system, the non-functional requirements are not even considered for the definition of software architecture as it is not carried out due architecture documentation, making it difficult access and understanding of architecture by other team members and hindering the maintenance of components / architecture modules and their relationships. This work together to seek up to software companies which are the main strategies used for the architecture definition of activities and architectural documentation are performed.