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. 7, Subsect. 7 Lecture: 10. Slide: 569 <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 />
[ Business Process Reengineering, Rules and Regulations Reengineering ]<br />
Dines Bjorner: 8th DRAFT: October 14, 2008<br />
Example. 4 – Rules and Regulations Reengineering:<br />
invisible<br />
• Assume now, due to reengineered support technologies, that<br />
interlock signalling can be made magnitudes safer than before,<br />
without interlocking.<br />
• Thence it makes sense to reengineer a domain rule <strong>of</strong><br />
/home/db/tseb/kap3/kap3-1<br />
⋆ from: In any three-minute interval at most one train may<br />
either arrive to or depart from a railway station<br />
⋆ into: In any 20-second interval at most two trains may either<br />
arrive to or depart from a railway station.<br />
• This reengineered rule is subsequently made into a domain<br />
requirements, namely that the s<strong>of</strong>tware system for interlocking<br />
is bound by that rule.<br />
•<br />
Phone: +45 4542 2141, E-mail: bjorner@gmail.com, URL: www.imm.dtu.dk/˜db
Change language