How fast, how many users, how many transactions. Zoom, Zoom.
Software performance requirements is about setting the performance and scalability context for getting the design and development right for your web application, your web service, your messaging hub, your reporting system, your mobile device. I am creating a few checklists;
- Project risk profile: Is performance important for this project and what works against performance in the project?
- Business workflows: What is the duration of a workflow, how many types of workflow and what is the peak workflow?
- Application business volumes and growth: The application automates the workflow with transactions and how will the volumes grow?
- Non-user interaction processes (batch, messages): This is about component throughput, how many orders per second?
- Communication to down-stream SDLC processes and phases: Setting the stage for design and development.
Here is a checklist to help set the context for your team;
Project Risk profile: These are the overarching performance and capacity considerations that the entire team must be aware of. This would communicate to the team that the business just acquired 2,000 new stores and this new application must now process twice as many users and orders in the same time. Or a new government regulation will be in effect that requires every retail brokerage order to have additional review that must not slow down the order processing system.
- Performance risk: Has performance or scalability been defined as a risk? Have you asked the business this question, or the production operations team?
- Extreme response times: Are there key business transactions with extreme response time requirements? User response under one second, a component that must process 500,000 transactions per second. If you have one second to respond to a user request, you better make sure the developers know this.
- Batch windows: Is there a very strict batch processing window and is the current system neat the end of the window? Yes, there are still large batch systems, that process tremendous volumes of data, for instance Mutual fund calculations.
- Third party: Does the system depend on third party software to complete the workflow? This could be software you buy and install as part of your application, or you could be using a Web Service.
- Third party SLA: Do the third party’s provide enforceable Service Level Agreements? Are you using a SaaS vendor and do you specify the response time?
- Peak Workload: Have the key business transactions been evaluated to determine average and peak workloads? And is there process in place to review these?
- Calculation: What are the key calculations and how is their response time influenced by the type of calculation (some do more work than others). Are there key pricing calculations, or rate quoting engines, or preference calculations, inventory allocation, etc. I have seen a few pricing calculations get caught-up in the volume discount calculation, and go from 100 milliseconds to 1 second.
- System Peak: What are the attributes that drive the peak load of the application? Is it seasonal, advertising driven, back to school, weather related (insurance claims), and do you model the peak? How many developers are not aware of the peak?
- Regulatory requirements: Is there an auditing component, reporting timeline, are there large volumes of data required to capture and provide to an agency?
Your projects must have a performance risk profile defined. There may be no risk, or there may be significant risk.
The next post will be about the business workflows.