m


  



 


 

A Case Study Of
Requirement Elicitation:
͞A TALE OF THREE STUDENTS͟

Erwin Hidayat M031010018

Fajrian Nur A. M031010021
 m

  



 


 

Êntroduction
¦ Requirements Elicitation is the process of discovering the
requirements for a system by communication with customers,
system users and others who have a stake in the system
development. (Sommerville et. al., 1997)

¦ Requirements are the most common source of errors in a project

 m

  



 


 

£roblems
Once upon a time there were three students of computer science: £at, Terry,
and Chris. With new computer science degrees in hand, they are beginning
their first jobs.
¦ £at has gone to work for Consolidated Flange and Widget :
!
   
         
   
      
  
       
 
      
      
¦ Terry has taken a job with Zooming Airplane Company :
!
          
    
 
   .
¦ Chris has gone to work for Megabuck Codemeisters:
!
    
                
     
 m

  



 


 

Case 1: £at in Consolidated Flange and Widget

` 

Develop an automated system that will allow:
1. £rocess orders at least 24 hours sooner, on average
2. Ship products to customers at least three days sooner than currently.

Sales Representatives, Order £rocessing £ersonnel, Shipping Department
£ersonnel, and Accounting £ersonnel
 
Customer,
Developer,
Department managers and company executives

.
 m

  



 


 

Case 2: Terry in Zooming Airplane Company

` 

Develop the software that will allow the Z-676 to land itself, without pilot
intervention, at major airports.

Engineers
 
Government (Aviation Administration Department)
£ilot,
Zooming Airplane Company
 m

  



 


 

Case 3: Chris in Megabuck Codemeisters

` 

Develop a new product that will sell:
1. at least one million copies
2. at a retail price of at least $200

Buyer
 
Government,
Competitor,
Retailer
 m

  



 


 

Generic Categories of
Requirements Elicitation Techniques
r


Êdentify the appropriate person, and ask what the requirements are.

 




Observe the behavior of users of an existing system, and then infer their
needs from that behavior.

  


  

Discuss with users their needs and jointly formulate a common
understanding of the requirements.

  
 with respect to a standard set.
 m

  



 


 

Generic Categories of
Requirements Elicitation Techniques [͙ctd]
[ 

 
 
 
£erform investigations of problems to identify requirements for improving a
system.

!  

 
   

For very complex problems with no obvious solutions, employ creative
processes involving developers and users.

  

To identify features or capabilities that the user might want.
 m

  



 


 

High-Level Techniques of
Requirements Elicitation
r 


 
 
"

¦ A technique for promoting cooperation, understanding, and teamwork
among buyers, users, and developers.
¦ £rovides a process that facilitates creating a shared vision of what the
system should be.
¦ Developers may help the users formulate problems and explore
solutions, and the users gain a feeling of involvement, ownership, and
commitment to the success of the system.
 m

  



 


 

High-Level Techniques of
Requirements Elicitation [͙ctd]
 

¦ To create a system that illustrates the relevant features, when there is no
similar existing system





¦ A simple group technique for generating ideas
¦ Allows people to suggest and explore ideas in an atmosphere free of
criticism or judgment
 m

  



 


 

High-Level Techniques of
Requirements Elicitation [͙ctd]

 #

¦ An important technique for eliciting detailed information from an
individual.
¦ More structured technique that can be learned
¦ Software engineers can gain proficiency with training and practice

[  

 
¦ A common activity performed by almost all companies who make
products for sale.
¦ Often used for software requirements elicitation when the product is a
personal productivity software package for small computers, or a
business support product that will be marketed to many companies
 m

  



 


 

Requirements Elicitation Techniques for

Case 1: £at
r  


  
  
 #   
a. Joint Application Design
b. Brainstorming

  
  

 m

  



 


 

Requirements Elicitation Techniques for

Case 2: Terry
r  

m  
#  # 



¦ Hardware engineers are those who understand the flight
characteristics and controls of the aircraft

 
  


 m

  



 


 

Requirements Elicitation Techniques for

Case 3: Chris
r  

 $ identify very general requirement

 
$ find out the detailed requirements

  
   


   % 
   
    # 


[


  

 #  
¦ åuestionnaire
¦ Brainstorming
 m

  



 


 

Conclusion
1. Assortment of requirement elicitation techniques that best fit
the kind of system being built are needed in tailoring realistic
project.

2. Need to study the case before determining the techniques to

be used because not all cases can be resolved with the same
techniques.

3. There are always many participants in a successful

requirements elicitation effort.
m

  



 


 

¦ Thank You