Non Functional Requirements – Performance

-
Requirements, especially non-functional ones, need to be SMART:
  • Specific
  • Measurable
  • Attainable (Achievable, Actionable, Appropriate)
  • Realisable (Realistic)
  • Time-bound (Timely, Traceable)
For performance requirements (should these be more correctly called performance goals?), the following aspects are most relevant:
  1. Response time – how fast the system responses to requests
  2. Throughput handling – how many requests the system can handle
  3. Concurrency – how many threads/ users can operate simultaneously
To specify performance requirements, consider the following:
  1. Expected daily load: number of invocations/ day. E.g. System is expected to receive (on average) 500 requests everyday
  2. Expected peak load: max invocations / day. E.g. System is expected to hit a peak load of 1000 requests on certain days
  3. (Maximum) Response Time: invocations need to respond within certain timeframe. E.g. System needs to respond to requests within 5 seconds
The last point (response time) deserves further explanation. As response time is highly dependent on the environment and tends to fluctuate, it makes more sense to specify this requirements in terms of average and/ or percentile (see this page)

One may specify the Response Time this way:
Average Response Time3 seconds or less
95th percentile5 seconds or less

Comments

Rachel Leong said…
Traditionally, it has always been Performance Requirements and it forms a section in the Requirements Document.
24/07/2011, 01:27
Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

How to depict (Professional-Looking) Logical Network Diagrams in Astah

-
Image
I have always had to create (professional-looking) UML diagrams using Visio-like icons. You’ve got to admit that showing a bunch of boring UML boxes hardly interests anyone less technical (like anyone whose designation has the words “manager” or “director”). This is actually possible in Astah! I’ve created a template for future projects that allows me to produce logical network diagrams that look like the following: To create this diagram, you need to do the following: Assign various icons to stereotypes. I created the following for my use: Create a new UML Deployment Diagram Every element in the diagram is created as a Node The nodes are subsequently assigned the appropriate <<stereotype>>. E.g. Internet is <<internet>>, WebZone FW is <<firewall>>, Web LB is <<loadBalancer>> Ensure the “Icon Notation” is set to “Customized Icon” for each node Instead of the boring boxes, the corresponding icons automatically gets displayed!
Read more