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

1Alternative/Evaluation Vectoragilab.comalchemy.comrevvity.com
2Technical DebtsPaid


Added


3Major Work Block



4Scalability


check mark buttoncheck mark buttoncheck mark button

By leveraging microservice and event-driven architecture in a cloud native platform, scalability can be achieved more effectively

5Resource - Cost Efficiency


check mark buttoncheck mark buttoncheck mark button

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.   

6Deployability


check mark buttoncheck mark buttoncheck mark button

By leveraging SaaS components in the most of infrastructure, the highest degree of deployability can be achieved at platform level via Infrastructure as Code (IaC), across multiple zones and in a well defined capacity.  

7Legal/Compliance


check mark buttoncheck mark button

Since the solution operates mainly in SaaS mode, some concerns from procurement and regional/legal perspectives can potentially 

8Interoperability


check mark buttoncheck mark buttoncheck mark button


9User Experience
check mark buttoncheck mark buttoncheck mark buttoncheck mark button

check mark buttoncheck mark buttoncheck mark button

UI identity is close to the status-quo solution and it has a great experience for administrative operations. Also by leveraging microservice backend architecture, a better responsiveness can be achieved. 

10Maintainability/Operability


check mark buttoncheck mark buttoncheck mark button
11Extensibility


check mark buttoncheck mark button

Although the solution is API-First oriented for transactional and batch data layers, customize or adapt existing feature demands considerable effort for change management. 

12Auditability



High:       check mark buttoncheck mark buttoncheck mark button

Medium: check mark buttoncheck mark button

Low:        check mark button 


References

LIMS