Rate Quality Attributes

1
Rate Attributes
2
Get Recommendations
3
Generate Diagram

Rate each quality attribute on a scale of 1-5 based on its importance to your project.
(1 = Not important, 5 = Extremely important)

Important Note

Ratings equal to 1 will not be counted when determining architecture recommendations. To ensure an architecture style is recommended, rate all its favored quality attributes greater than 1.

You must rate at least 3 quality attributes with importance > 1 to proceed to the next step.

Required attributes are the minimum set that must be rated > 1 to meet at least one architecture style.

Project Information

Please provide some information about your team before rating quality attributes.

The size of your development team affects architectural complexity and coordination needs.
Team experience level influences architectural complexity and implementation approach.
The number of concurrent users affects scalability, performance, availability, and reliability requirements.
Tech Stack
Select your preferred technologies and versions. This information will be used when generating diagrams.
Advanced Options
Exclude Architecture Styles

Select architecture styles you want to exclude from recommendations:

Importance Weights

Optionally adjust the importance weight for each quality attribute category:

Quality Attributes

Rate each quality attribute on a scale of 1-5 based on its importance to your project.

Rate this attribute > 1 to include these architecture styles in recommendations.

🏗️ Operational Qualities
Attribute Description Rating
Accessibility

The degree to which a system is available to as many people as possible, including those with disabilities.
Your rating:
Availability Favored Required
Favored by:
Microservices (as Availability) Serverless (as Availability)

The degree to which a system or component is operational and accessible when required for use.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Configurability Favored
Favored by:
Layered (as Configurability) Layered Architecture (Generic) (as Configurability) AI Agent Architecture (as Configurability)

The ability to easily configure and reconfigure a system to adapt to different user requirements or environments.
Your rating:
Cost Efficiency Favored
Favored by:
Serverless (as Cost Efficiency)

The ability of a system to provide required functionality at an acceptable cost.
Your rating:
Deployability Favored
Favored by:
Microservices (as Deployability) Monolithic (as Deployability)

The ease with which a system can be deployed to a production environment.
Your rating:
Extensibility Favored
Favored by:
Layered Architecture (Generic) (as Extensibility) AI Agent Architecture (as Extensibility)

The ability to extend a system with new functionality with minimal impact on existing code.
Your rating:
Fault Tolerance Favored Required
Favored by:
Microservices (as Fault Tolerance) Event-Driven (as Fault Tolerance) Serverless (as Fault Tolerance) AI Agent Architecture (as Fault Tolerance)

The ability of a system to continue operating properly in the event of the failure of some of its components.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Flexibility Favored Required
Favored by:
Service-Oriented (as Flexibility) AI Agent Architecture (as Flexibility)

The ease with which a system or component can be modified for use in applications or environments other than those for which it was specifically designed.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Interoperability Favored Required
Favored by:
Service-Oriented (as Interoperability) AI Agent Architecture (as Interoperability)

The ability of a system to work with other systems without special effort on the part of the user.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Maintainability Favored Required
Favored by:
Layered (as Maintainability) Monolithic (as Maintainability) Service-Oriented (as Maintainability) Layered Architecture (Generic) (as Maintainability)

The ease with which a system or component can be modified to correct faults, improve performance, or adapt to a changed environment.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Modifiability Favored Required
Favored by:
Layered (as Modifiability) Microservices (as Modifiability) Event-Driven (as Modifiability) Service-Oriented (as Modifiability) Layered Architecture (Generic) (as Modifiability) AI Agent Architecture (as Modifiability)

The ease with which a system can be changed to add new features or modify existing ones.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Observability Favored Required
Favored by:
Microservices (as Observability) Event-Driven (as Observability) Serverless (as Observability) AI Agent Architecture (as Observability)

The ability to measure the internal states of a system by examining its outputs.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Performance Favored Required
Favored by:
Microservices (as Performance) Event-Driven (as Performance) Monolithic (as Performance) Serverless (as Performance) AI Agent Architecture (as Performance)

The degree to which a system or component accomplishes its designated functions within given constraints, such as speed, accuracy, or memory usage.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Reliability

The ability of a system to perform its required functions under stated conditions for a specified period of time.
Your rating:
Resilience Favored
Favored by:
Microservices (as Resilience) Event-Driven (as Resilience) Serverless (as Resilience) AI Agent Architecture (as Resilience)

The ability of a system to recover from failures and continue to function.
Your rating:
Scalability Favored Required
Favored by:
Microservices (as Scalability) Event-Driven (as Scalability) Service-Oriented (as Scalability) Serverless (as Scalability) AI Agent Architecture (as Scalability)

The capability of a system to handle a growing amount of work, or its potential to be enlarged to accommodate that growth.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Security Favored Required
Favored by:
Layered (as Security) Microservices (as Security) Service-Oriented (as Security) Layered Architecture (Generic) (as Security)

The protection of system items from accidental or malicious access, use, modification, destruction, or disclosure.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Testability Favored Required
Favored by:
Layered (as Testability) Monolithic (as Testability) Layered Architecture (Generic) (as Testability)

The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

Required: Rate this attribute > 1 to meet at least one architecture style.
Your rating:
Throughput Favored
Favored by:
Event-Driven (as Throughput)

The amount of work that a system can process in a given amount of time.
Your rating:
Usability Favored
Favored by:
Layered (as Usability) Monolithic (as Usability) Layered Architecture (Generic) (as Usability)

The ease with which a user can learn to operate, prepare inputs for, and interpret outputs of a system.
Your rating: