Business Analyst - How do you come up with non-functional requirement?

GeekInterview.com > Interview Questions > Management > Business Analyst

Go To First | Previous Question | Next Question

Business Analyst | Question 42 of 129

How do you come up with non-functional requirement?

Total Answers and Comments: 3

Last Update: September 03, 2007 Asked by: hasan

Sponsored Links

Best Rated Answer

—

Submitted by: sandhya001

The simple method is:

Functional Requirements are MUST TO HAVE (The system will not function without these requirements)

Non-Functional Requirements are NICE TO HAVE (The system will work however, NFR will increase the usability or performance related issues.)

Above answer was rated as good by the following members:
Israel, stallion_ts, nehasahu, rachel123, gaganrana

June 09, 2007 02:56:53

amarchis

Member Since: June 2007 Contribution: 2

RE: How do you come up with non-functional requirement...

There are a variety of methods to elicit non-functional requirements. One method that I use is to identify upfront (before the project even starts) the main categories of non-functional requirements as well as a standard set of questions to ask for each type of non-functional requirements.

Here are some key categories of non-functional requirements:
1. GUI look and feel requirements
2. Performance requirements
3. Availability requirements
4. Security requirements
5. Capacity requirements
6. Exception Handling requirements
7. Logging requirements
8. Extensibility requirements
9. Data Retention requirements
etc.

Then for each type of non-functional requirement you could develop standard questions or just as more general questions such as: "Data Retention: do you have any requirements related to how long data (or certain types of data) should be retained by the system?"

Hope this helps!
- Adrian

Is this answer useful? Yes | No

3 0

Overall Rating: +3

September 03, 2007 15:03:33

sandhya001

RE: How do you come up with non-functional requirement...

The simple method is:

Functional Requirements are MUST TO HAVE (The system will not function without these requirements)

Non-Functional Requirements are NICE TO HAVE (The system will work however NFR will increase the usability or performance related issues.)

Is this answer useful? Yes | No

1 0

Overall Rating: +1

September 03, 2007 15:33:06

sandhya001

Member Since: September 2007 Contribution: 7

RE: How do you come up with non-functional requirement...

Functional Requirements are MUST-TO-HAVE (without these requirement the system or part of the system will not function)

Non-Functional Requirement are NICE-TO-HAVE (without these requirement the system will work however it will help to enhance the usability and performance of the system. ex. when you have entering product code in cashier system you can do it by manual entering the product code by keyboard or use the scanner to read the code. the scanner is enhancing your usability of the system)

Is this answer useful? Yes | No

1 0

Overall Rating: +1

Go To Top

User Name		Remember Me?
Password

Question Bank