1. 1 Interviewing CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 13, 2004

2. 2 Outline Needs vs. Features vs. Requirements Interview preparation Phases of an interview

3. 3 Needs vs. Features Customers may jump from needs to features Capture those features Look for needs that suggest features

4. 4 Where Should You Hold an Interview? Non-threatening environment  Customer's turf  Room large enough for group Free from distractions

5. 5 Interview Preparation Do some research Prepare questions Prepare agenda Select roles:  Leader  Note taker  Questioners

6. 6 Interview Phases 1. Establish user profile 2. Assess the problem 3. Understand the environment 4. Recap for understanding 5. Analyst's inputs 6. Assess solution 7. Assess opportunity 8. Assess reliability, performance 9. Other requirements 10. Wrap-up

7. 7 1. Establish User Profile Do some research first Determine background of interviewee Find out what will constitute success or failure

8. 8 2. Assess the Problem Find out what the problems are How are problems addressed now?

9. 9 3. Understand the Environment Find out about the users Find out about the computing environment How much help will users need?

10. 10 4. Recap for Understanding Paraphrase what you have heard so far Is anything missing?

11. 11 5. Analyst's Inputs Ask about problems that you would expect to be present Rank these problems relative to others

12. 12 6. Assess Solution What if... How important would it be?

13. 13 7. Assess Opportunity Determine the market for the solution Determine the value of the solution

14. 14 8. Assess Reliability and Performance Determine nonfunctional needs:  reliability  performance  support

15. 15 9. Other Requirements Any external requirements? Any other requirements not already mentioned?

16. 16 10. Wrap-up What should we have asked? How can we follow up?