Upload
hidayaterwin
View
221
Download
0
Embed Size (px)
Citation preview
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 1/16
Faculty of Information and Communication Technology | UTeM
A Case Study Of
Requirement Elicitation:A TALE OF THREE STUDENTS
Erwin Hidayat M031010018
Fajrian Nur A. M031010021
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 2/16
IntroductionIntroduction
Faculty of Information and Communication Technology | UTeM
� 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
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 3/16
ProblemsProblems
Faculty of Information and Communication Technology | UTeM
Once upon a time there were three students of computer science: Pat, Terry,
and Chris. With new computer science degrees in hand, they are beginning
their first jobs.
�� PatPat has gone to work for Consolidated Flange and Widget :
Develop an automated system that will allow us to process orders at least
24 hours sooner, on the average, and will allow us to ship our products to
customers at least three days sooner than currently.
�� TerryTerry has taken a job with Zooming Airplane Company :
Develop the software that will allow the Z-676 to land itself, without pilot intervention, at major airports.
�� ChrisChris has gone to work for Megabuck Codemeisters:
Develop a new product that will sell at least one million copies at a retail
price of at least $200.
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 4/16
Case 1: PatCase 1: Pat in Consolidated Flange and Widget
Requirements:
Develop an automated system that will allow:
1.P
rocess orders at least 24 hours sooner, on average2. Ship products to customers at least three days sooner than currently.
User:
Sales Representatives, Order Processing Personnel, Shipping Department
Personnel, and Accounting Personnel
Stakeholders:
Customer,
Developer,
Department managers and company executives
.
Faculty of Information and Communication Technology | UTeM
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 5/16
Case 2: TerryCase 2: Terry in Zooming Airplane Company
Requirements:
Develop the software that will allow the Z-676 to land itself, without pilot
intervention, at major airports.
User:
Engineers
Stakeholders:
Government (Aviation Administration Department)Pilot,
Zooming Airplane Company
Faculty of Information and Communication Technology | UTeM
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 6/16
Case 3: ChrisCase 3: Chris in Megabuck Codemeisters
Requirements:
Develop a new product that will sell:
1. at least one million copies2. at a retail price of at least $200
User:
Buyer
Stakeholders:Government,
Competitor,
Retailer
Faculty of Information and Communication Technology | UTeM
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 7/16
Generic Categories of Requirements Elicitation Techniques
1. Asking
Identify the appropriate person, and ask what the requirements are.
2. Observing and inferring
Observe the behavior of users of an existing system, and then infer their
needs from that behavior.
3. Discussing and formulatingDiscuss with users their needs and jointly formulate a common
understanding of the requirements.
4. Negotiating with respect to a standard set.
Faculty of Information and Communication Technology | UTeM
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 8/16
5. Studying and identifying problems
Perform investigations of problems to identify requirements for improving asystem.
6. Discovering through creative processes.
For very complex problems with no obvious solutions, employ creative
processes involving developers and users.
7. Postulating.
To identify features or capabilities that the user might want.
Faculty of Information and Communication Technology | UTeM
Generic Categories of Requirements Elicitation Techniques [ctd]
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 9/16
High-Level Techniques of Requirements Elicitation
1. Joint Application Design (JAD)
�
A technique for promoting cooperation, understanding, and teamworkamong buyers, users, and developers.
� Provides 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.
Faculty of Information and Communication Technology | UTeM
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 10/16
2. Prototyping
�
To create a system that illustrates the relevant features, when there is nosimilar existing system
3. Brainstorming
� A simple group technique for generating ideas
�
Allows people to suggest and explore ideas in an atmosphere free of criticism or judgment
Faculty of Information and Communication Technology | UTeM
High-Level Techniques of Requirements Elicitation [ctd]
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 11/16
4. Interviewing
� 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
5. Market Analysis
� A common activity performed by almost all companies who makeproducts 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
Faculty of Information and Communication Technology | UTeM
High-Level Techniques of Requirements Elicitation [ctd]
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 12/16
Requirements Elicitation Techniques forCase 1: PatCase 1: Pat
1. Discussing and formulating requirements with the users
a. Joint Application Designb. Brainstorming
2. Postulating requirements
Faculty of Information and Communication Technology | UTeM
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 13/16
1. Discuss and Formulate requirements with the hardware
engineers
� Hardware engineers are those who understand the flight
characteristics and controls of the aircraft
2. Observing pilots landing
Faculty of Information and Communication Technology | UTeM
Requirements Elicitation Techniques forCase 2: TerryCase 2: Terry
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 14/16
1. Market Analysis, identify very general requirement
2. Prototyping, find out the detailed requirements
3. Postulating the requirements
4. Study the existing systems to identify their weaknesses
5. Asking and discussing with users
� Q uestionnaire
� Brainstorming
Faculty of Information and Communication Technology | UTeM
Requirements Elicitation Techniques forCase 3: ChrisCase 3: Chris
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 15/16
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 successfulrequirements elicitation effort.
Faculty of Information and Communication Technology | UTeM
Conclusion
8/7/2019 Tale of Three Students
http://slidepdf.com/reader/full/tale-of-three-students 16/16
Faculty of Information and Communication Technology | UTeM
� Thank You