Lect.10 - Institute of Software Technology
Lect.10 - Institute of Software Technology
Lect.10 - Institute of Software Technology
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
SOFTWARE ENGINEERING: The Essentials<br />
Nov.2008 Lectures: TU Graz<br />
Chap.3, Sect. 2, Subsect. 1, Subsubsect. 2 Lecture: 10. Slide: 510 <strong>of</strong> 1352<br />
c○ Dines Bjørner, 2008<br />
Fredsvej 11<br />
DK-2840 Holte<br />
Denmark November 16, 2008, 08:48<br />
Dines Bjorner: 8th DRAFT: October 14, 2008<br />
invisible<br />
• We refer to Slide 212.<br />
/home/db/tseb/kap3/kap3-1.tex<br />
Stages <strong>of</strong> Requirements Engineering, An Overview <strong>of</strong> “What to Do ?”<br />
[2] Requirements Stakeholder Identification<br />
• The purpose <strong>of</strong> this stage <strong>of</strong> development<br />
⋆ is to identify the requirements stakeholders.<br />
⋆ They are usually a proper subset <strong>of</strong> the domain stakeholders.<br />
⋆ One does not need to interact with all domain stakeholders<br />
⋆ as that was supposedly done in the domain description development phase,<br />
⋆ and the domain description is, <strong>of</strong> course,<br />
⋄ assumed available and<br />
⋄ the basis for the requirements prescription development phase.<br />
⋆ For more specifics on this topic we refer to Slides 538–539.<br />
• For the example ‘requirements stakeholder identification’ document we refer to<br />
Appendix Slides 1144–1144.<br />
Phone: +45 4542 2141, E-mail: bjorner@gmail.com, URL: www.imm.dtu.dk/˜db
Change language