Draft : Putting the Qualities into Architecture : Kevlin Henney, Independent Consultant
- A quality represents an aspect of value to a stakeholder of a system
- Quality includes functional and non-functional ones
- Non-functional term is a bad English use
- There is more to software system than its functional behavior and requirements
- Operational qualities
- Availability, scalability, performance, manageability, security and usability
- Qualities vary by domain
- Functional requirements are measurable, unlike “non-functional”
- Expressing and testing operational qualities require a different take on requirements
- Differ between trends versus hard limits
- Be sure that parameters are considered together and in context
- Developmental qualities
- Testability, portability, maintainability
- There is no reuse, there is use for the intent it was designed for (we cant reuse the train!)
- We should consider what matters for the system from qualities
- People are dumb enough to connect anything on internet
