 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Within systems engineering, quality attributes are realized non-functional requirements used to evaluate the performance of a system. These are sometimes named architecture characteristics, or "ilities" after the suffix many of the words share. They are usually architecturally significant requirements that require architects' attention.[1]
In software architecture, these attributed are known as "architectural characteristic" or non-functional requirements. Note that it's software architects' responsibility to match these attributes with business requirements and user requirements. Note that synchronous communication between software architectural components, entangles them and they must share the same architectural characteristics. [2]
- ^ Chen, Lianping (2013). "Characterizing Architecturally Significant Requirements" (PDF). IEEE Software. 30 (2): 38–45. doi:10.1109/MS.2012.174. hdl:10344/3061. S2CID 17399565.
- ^ Richards, Mark; Ford, Neal (2020). Fundamentals of Software Architecture: An Engineering Approach. O'Reilly Media, Incorporated. ISBN 978-1492043454.
© MMXXIII Rich X Search. We shall prevail. All rights reserved. Rich X Search