week4-2 - Requirements Engineering: Requirements Gathering...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Requirements Engineering: Requirements Gathering Michael Gruninger Semantic Technologies Lab University of Toronto September 27, 2010 Gruninger (MIE350) Requirements Engineering September 27, 2010 1 / 28 Difficulties Stakeholders often dont know what they want from the computer system, and they find it difficult to articulate what they want the system to do. Stakeholders naturally express requirements in their own terms and with implicit knowledge of their own work. Different stakeholders have different requirements, which they express in different ways. Gruninger (MIE350) Requirements Engineering September 27, 2010 2 / 28 Challenge How can we identify the implicit conceptual models and goals of the users and extract a set of requirements that achieve these goals while correctly and completely capturing the user models? Gruninger (MIE350) Requirements Engineering September 27, 2010 3 / 28 Requirements Discovery In requirements discovery, we interact with stakeholders to gather information about the proposed system, and then distill the user and system requirements from this information. Techniques: questionnaires interviews scenarios viewpoints task analysis ethnography Gruninger (MIE350) Requirements Engineering September 27, 2010 4 / 28 Questionnaires A written list of questions on paper or the web Subjects usually fill it out by themselves You are not there to explain anything that is confusing! Gruninger (MIE350) Requirements Engineering September 27, 2010 5 / 28 Role of Questionnaires Quick way to gather massive amounts of data Much more data per time than interviewing everyone! Often used when system is to be used externally I You cant interview the users! Data usually easy to quantify Gruninger (MIE350) Requirements Engineering September 27, 2010 6 / 28 Questionnaire Steps Selecting participants I For a ROSI replacement, who would you survey? I Sampling Designing questionnaire I open vs. closed questions Administering questionnaire Follow-up Gruninger (MIE350) Requirements Engineering September 27, 2010 7 / 28 Open-ended Questions What does a web-user currently do to order a product? How do you make a scheduling decision?...
View Full Document

This note was uploaded on 09/20/2011 for the course MIE 350 taught by Professor M.gruninger during the Fall '10 term at University of Toronto- Toronto.

Page1 / 28

week4-2 - Requirements Engineering: Requirements Gathering...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online