Utility Tree - Architecturally Significan Requirement
In the Utility Tree the use cases can be evaluated from the business relevancy versus the architectural complexity reasoning to accomplish the benefit.
Here the place to organize the use cases given its classification from the Architectural Quality Attribute Perspective.
(WIP)
Evaluation Matrix - Architectural Quality Attributes
| 1 | Alternative/Evaluation Vector | agilab.com | alchemy.com | revvity.com | |
|---|---|---|---|---|---|
| 2 | Technical Debts | Paid | |||
| Added | |||||
| 3 | Major Work Block | ||||
| 4 | Performance | ||||
| 5 | Scalability | By leveraging microservice and event-driven architecture in a cloud native platform, scalability can be achieved more effectively | |||
| 6 | Consistency | ||||
| 7 | Resource - Cost Efficiency | By leveraging SaaS components in the most of infrastructure, the Cost Efficiency can achieved more effectively - fine-tuning each application context capacity given the specific demand on it. | |||
| 8 | Deployability | ||||
| 9 | Legal/Compliance | ||||
| 10 | Interoperability | ||||
| 11 | User Experience | ||||
| 12 | Maintainability/Operability | ||||
| 13 | Auditability | ||||
High:
Medium:
Low:
References