The modeling software architecture is designed with particular functional and non-functional requirements. The organization often needs to choose model software architecture for future development from several competing organizational architectures. To achieve non-functional requirements for any modeling software architecture still remain a difficult task as many stakeholders involved in the selection process. In existing system there are three approaches, Non-Functional Requirement (NFR) approach, Quality Attribute Model approach and Intuitive Design approach. For each approach having its own bottlenecks such as decisions are not precisely determined, less modularization, no predictive model, no amenable architecture, no scale up architecture and no organizing requirements etc.,. In order to improve performance, functional behavior, security, reliability and to overcome the limitations of software architecture with quality attributes, the proposed system is to model software architecture to achieve non-functional requirements. There are several methods have been proposed to model and analyze software architecture with respect to desired quality attributes. Our proposed system is to embed three approaches such as Architecture Driven Design, Architecture Decisions and Reasoning Framework in order to implement Non-Functional Requirements. A Reasoning Framework is a mechanism for encapsulating the quality attributes knowledge and tools needed to analyze the behavior of a system with respect to some quality attributes. The reasoning framework resolves open issues of modeling to achieve non-functional requirements.
An important and well-known approach to incorporate NFR in an architecture are architectural patterns. The most well known ones are the ones from the POSA books, but there are many more out there. A good source for this is the website from the Hillside Group: www.hillside.net. Another good source are the proceedings of the PLoP conference series (like PLoP, EuroPLoP, AsianPLoP, links to these conferences are also on the Hillside website, and many proceedings are also in the ACM DL). As last I can recommend the PhD thesis from Neil Harrison: http://dissertations.ub.rug.nl/faculties/science/2011/n.b.harrison/
You should also take into account the tradeoffs between non-functional requirements in a software architecture. Some people have attempted to record these tradeoffs in catalogues that generalize their design experience by stating e.g. that improved security comes by inducing some performance cost. However, tradeoffs depend on the architecture at hand and in general the tradeoff relationships differ in each software architecture.
Some recent works that take into account such tradeoffs in reasoning for quality attributes are:
1. Mentis et al, "Quantification of interacting runtime qualities in software architectures: Insights from transaction processing in client–server architectures", 2010
2. Saadatmand et al, "Toward Model-Based Trade-off Analysis of Non-functional Requirements", 2012
- Badges
- Science topic
- Similar topics
- Design
- Architecture