What are the best ways to manage risks and assumptions when choosing quality attributes?

1 Identify and prioritize quality attributes

The first step is to identify and prioritize the quality attributes that are relevant and important for your solution. You can use various sources of information, such as business goals, user stories, scenarios, constraints, and standards, to elicit and specify the quality attributes. You can also use frameworks, such as ISO/IEC 25010, to categorize and define them. Then, you need to prioritize the quality attributes based on their impact, urgency, and feasibility. You can use techniques, such as MoSCoW analysis, Kano model, or pairwise comparison, to rank and compare the quality attributes.

2 Analyze and document trade-offs

The second step is to analyze and document the trade-offs that you need to make when choosing the quality attributes. Trade-offs are the compromises or sacrifices that you have to make when optimizing one quality attribute over another. For example, you may have to trade off performance for security, or scalability for maintainability. You need to analyze the trade-offs using criteria, such as cost, benefit, risk, and value, and document them using tools, such as utility trees, quality attribute scenarios, or design decision matrices. You also need to communicate and justify the trade-offs to the stakeholders and get their feedback and approval.

3 Assess and mitigate risks

The third step is to assess and mitigate the risks that may affect the achievement of the quality attributes. Risks are the uncertainties or threats that may cause negative consequences or deviations from the expected outcomes. For example, you may face risks such as technical complexity, integration issues, or changing requirements. You need to assess the risks using methods, such as risk identification, analysis, evaluation, and prioritization, and document them using tools, such as risk registers, risk matrices, or risk breakdown structures. You also need to mitigate the risks using strategies, such as avoidance, reduction, transfer, or acceptance, and monitor and control them throughout the solution lifecycle.

4 Validate and update assumptions

The fourth step is to validate and update the assumptions that you make when choosing the quality attributes. Assumptions are the beliefs or hypotheses that you have about the solution context, environment, or behavior. For example, you may assume that the solution will have a certain level of demand, availability, or reliability. You need to validate the assumptions using techniques, such as prototyping, testing, or experimentation, and document them using tools, such as assumption logs, assumption maps, or assumption validation matrices. You also need to update the assumptions based on the validation results, feedback, or changes, and align them with the quality attributes.

5 Review and refine quality attributes

The fifth step is to review and refine the quality attributes based on the solution evolution, feedback, and performance. You need to review the quality attributes using measures, such as metrics, indicators, or benchmarks, and evaluate them using criteria, such as satisfaction, compliance, or improvement. You also need to refine the quality attributes based on the review findings, feedback, or lessons learned, and make adjustments, enhancements, or optimizations to the solution architecture. You need to document the review and refinement process using tools, such as quality attribute reviews, quality attribute reports, or quality attribute improvement plans.

6 Learn and share best practices

The sixth and final step is to learn and share the best practices that you discover or adopt when choosing the quality attributes. You need to learn the best practices from various sources, such as industry standards, guidelines, or frameworks, or from other solution architects, experts, or communities. You also need to share the best practices with your peers, team, or organization, and contribute to the knowledge base, repository, or platform. You need to document the best practices using tools, such as best practice catalogs, best practice checklists, or best practice templates.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?