Checklist

The checklist for the capture of requirements is as follows:

  • Are scalability targets identified and approved by key stakeholders?
  • Are the targets for throughput and response time identified?
  • Do the objectives differentiate between actual scalability and observed scalability?
  • Are the scalability targets assessed for rationality?
  • Are the expectations of the stakeholders established for what is feasible in the architecture?
  • Are all scalability targets defined within the context of the organizational workload?
  • Is a framework established to identify the expected scalability and how they combine to produce overall scalability dashboards?
  • Is a solution to collect management and instrumentation information devised on actual scalability and compared to organizations scalability requirements?
  • Is the data collated adequate to identify potential root causes for scalability bottlenecks?

The checklist for architecture definition is:

  • Has enough testing and analysis been completed to understand the likely scalability capabilities of the application?
  • Is the major potential scalability problem in your architecture established?
  • What workload can your application handle? Are the different classes of workload prioritized?
  • How far can the proposed architecture be scaled without major architecture updates?
  • Are the scalability-related assumptions identified?
  • Has the architecture been reviewed for common scalability bottlenecks?

Scalability KPIs/KRAs

  • Ability to scale to support up to X, for example, 50,000,000 unique browsers in any given calendar month by 2020
  • Ability to scale up to X, for example, 2 million active registrations
  • Ability to support a frequency of up to X, for example, 20 sessions for each unique browser in any given calendar month
  • Support up to X, for example, 50 page impressions served per browser session
  • Support up to X, for example, 250 million page impressions in any given calendar month
  • Support up to X, for example, 5,000 concurrent users at peak periods
  • Support an average of X , for example, 20 minutes per user session
  • Support up to X, for example, 250,000 bulk add file uploads per calendar month
  • Support up to X, for example, 50 concurrent bulk add and image file uploads in peak periods
  • Support an average of X, for example, 20 images per upload
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset