Non Functional requirements description in assumption doc

[Parag Doshi]

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

[H. Hafer]

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

[aarti savant]

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]

Thanks guy...the NFRs now have their nice little space in my document

[Ramon Gill]

It seems like it would be worth it as it helps with part III.

Ray