GeekInterview.com
   Home |  Tech FAQ  |   Interview Questions |  Placement Papers |  Tech Articles |  Learn |  Freelance Projects |  Online Testing |  Geeks Talk |  Job Postings |  Knowledge Base | Site Search |  Add/Ask Question

  GeekInterview.com  >  Interview Questions  >  Management  >  Business Analyst

 Print  |  
Question:  How do you come up with non-functional requirement?



June 06, 2007 02:56:53 #1
 amarchis CRM Expert  Member Since: June 2007    Total Comments: 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
     

 

Back To Question