In the business context section, the solution architect needs to provide a high-level overview of business capabilities and requirements that the solution is going to address. This section only contains an abstract view of requirements. Detailed requirements need to be a part of a separate requirements document. However, the external link of the requirements document can be provided here. You should include the following primary subsections:

• Business capabilities: Provide a brief description of business capabilities for which the solution is being designed. Make sure to include the benefits of capabilities and how they will address customer needs.
• Key business requirements: List all key business concerns that the solution is going to address. Provide a high-level view of key requirements and add a reference to the detailed requirements document.
• Key business processes: Solution architects should show key processes with a business process document. The following diagram illustrates a simplified view of an e-commerce application business process model:

• Business stakeholders: List stakeholders who are directly or indirectly impacted by the project. This includes sponsors, developers, end users, vendors, partners, and so on.
• NFRs: Solution architects need to focus more on NFRs as these often get missed by the business user and development team. At a high level, an NFR should include:
  • Scalability: How can the application scale as workload fluctuates? (For example, scale from 1,000 transactions per second to 10,000 transactions per second in a given day or month.)
  • Availability and reliability: What is acceptable downtime for system availability? (For example, 99.99% availability or 45 minutes' downtime per month.)
  • Performance: What is the performance requirement? Where can the system handle the load increase without impacting the end-user experience? (For example, the catalog page needs to load within 3 seconds.)
  • Portability: Can the application run on multiple platforms without any additional work? (For example, the mobile app needs to run in the iOS and Android operating systems.)
  • Capacity: What is the maximum workload that the application can handle? (For example, the maximum number of users, the number of requests, expected response time and expected application load, and so on.)

The conceptual view of architecture is a sweet spot that provides a good system overview for both business and technical stakeholders. Let's learn more about the conceptual view in more detail.