Business Analyst - What types of requirements should not be documented in use cases?

GeekInterview.com > Interview Questions > Management > Business Analyst

Go To First | Previous Question | Next Question

Business Analyst | Question 64 of 130

What types of requirements should not be documented in use cases?

Total Answers and Comments: 3

Last Update: September 30, 2008 Asked by: neetika

Sponsored Links

Best Rated Answer

—

Submitted by: chrisraeht

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.

Above answer was rated as good by the following members:
sujay_bodas

September 24, 2007 11:34:40

coolguy

Member Since: October 2005 Contribution: 3

RE: What types of requirements should not be documente...

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

Is this answer useful? Yes | No

May 19, 2008 18:19:13

chrisraeht

Member Since: May 2008 Contribution: 2

RE: What types of requirements should not be documented in use cases?

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.

Is this answer useful? Yes | No

1 0

Overall Rating: +1

September 30, 2008 14:12:23

megrath

Member Since: September 2008 Contribution: 12

RE: What types of requirements should not be documented in use cases?

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.

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank