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. 5, Subsect. 2 Lecture: 10. Slide: 543 <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 />
[ Requirements Acquisition, Domain Requirements Acquisition ]<br />
Dines Bjorner: 8th DRAFT: October 14, 2008<br />
invisible<br />
• The domain engineer, in a sense, guides the requirement stakeholders<br />
/home/db/tseb/kap3/kap3-1<br />
⋆ through the emerging domain requirements acquisition prescription document<br />
determining what<br />
⋆ to project, instantiate, make more deterministic, extend and fit.<br />
Interface Requirements Acquisition<br />
• Interface requirements acquisition is based on the domain requirements<br />
acquisition document and on some awareness <strong>of</strong> the facilities <strong>of</strong> machine being<br />
required.<br />
• Awareness and determination <strong>of</strong> which these facilities are, or could be, evolve as<br />
a result <strong>of</strong> conducting the below steps <strong>of</strong> interface requrements.<br />
Phone: +45 4542 2141, E-mail: bjorner@gmail.com, URL: www.imm.dtu.dk/˜db
Change language