Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes forum!
  • 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
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Non Functional requirements description in assumption doc

 
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have read in some posts here that folks describe in their accompanying assumption doc about how each non-functional requirement(NFR) is met in their architecture. Is it required (in the sense to make the doc complete) to detail out how each of the NFR is met or just highlight some of the common ones like scalability, performance etc?
Another thing, do we also have to propose a hardware or software load balancing solution in our architecture?

Parag
 
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Whethter or not it is _necessary_ to describe the mechanisms you've chosen to meet the NFRs I would recommend to actually do it for the following reasons:

- it doesn't hurt,
- it helps to check for completeness, and most importly
- it is a very good exercise for part iii

HTH,
Harbo
 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes and NO. You may or may not need to mention about the NFR's in the assumption doc. Whether you detail in length or just highlight it, it depends on how crucial you consider them to be in the whole architecture.
The part 3 of the exam will test some NFR knowledge so its well worth planning and documenting it within the assumption section.
load balancing holds a critical place in overall J2EE architecture design and is hence recommended as well.
 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks guy...the NFRs now have their nice little space in my document
 
Ranch Hand
Posts: 344
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It seems like it would be worth it as it helps with part III.

Ray
 
Bras cause cancer. And tiny ads:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic