• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

NFR

 
Ranch Hand
Posts: 99
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi

I am in the process of collecting non functional requirements for my project.Can anyone share what are all the consideration for creating this document.
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Many of these requirements fall into "RASP":

Reliability - Unscheduled downtime
Availability - Scheduled uptime
Scalability - Users, concurrent requests, database & network load
Performance - Response times

It can be very expensive in real dollars to optimize any one of these, and fabulously expensive to optimize all of them. Prioritize, set realistic goals, consider the dollar cost of every improvement, eg 99.9% reliable to 99.999%. Users will ask for the moon until you tell them what it costs.

Also consider how you will test and prove any of these things. How do you prove "95% of screens complete within 2 seconds" or "99.999% reliable"?

Also consider "graceful degradation". What happens when one of many partner systems fails ... does your whole system fail or just report that one function is unavailable? What happens when one app server out of a cluster fails ... do users move seamlessly to the next one?

Any of that help?
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Not really a performance question - moving to our Process forum...
 
author
Posts: 608
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Keep your documentation as agile as possible. See Agile Documentation for some good strategies. The important thing is to understand the requirements, documenting them means almost nothing (not that the bureaucrats among us would agree, but then again, they don't have the skills to actually build software).

- Scott
 
Ranch Hand
Posts: 150
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by raj joe:
Hi

I am in the process of collecting non functional requirements for my project.Can anyone share what are all the consideration for creating this document.



According to RUP non-functional requirements can be classified under :
Usability - e.g. any UI issues / guidelines to adhere to
Reliability - e.g. uptime of application
Performance - e.g. response times for users
Supportability - e.g. can the system be maintained?

HTH,

Fintan
 
I've been selected to go to the moon! All thanks to this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic