coolguy

 Profile Answers by coolguy 

• Sep 24th, 2007

 

generally functional requirements are added in use cases...  Non-functional requirements like security, performance etc are not added in use cases.

chrisraeht

 Profile Answers by chrisraeht 

• May 19th, 2008

 

Use cases should be written from the user point of view.  How should the system function when using it.  So don't include "behind the scenes" specifics like what is stored in the data base or how the system will validate the information.  That would go in tech specs.  The people signing off on use cases are typically business users and the people using the use cases are typically software developers.

megrath

 Profile Answers by megrath 

• Sep 30th, 2008

 

Any non- functional requirements[example:usuability,design,performance..] that cannot be directly realted to the usecases should not be documented in Usecases. These non-functional requirements are documented in Supplementary Specification Document.