Requirement Engineering - Horst Rechner

Recommendations

Info

<strong>Requirement</strong>s Elicitation 2 Organise a workshop organiser brings the coffee ("feel good environment") keep the number of stakeholders limited be prepared for some level of conflicts among them too limit the number of your contacts afterwards even more
<strong>Requirement</strong>s Elicitation 3 the "deepness" (= detail level) depends on many things level of the project (prototype, demo, 24/7 application) size of the project "closeness" of the customer style of development (waterfall, V-Model, UP, XP) less agile - more complete spec needed prioritize during workshop into: MUST / MAY / OPTIONAL tell participants which documents will be the output beware of implicit requirements ("such buttons should of course have been big, round and red")
Page 1 and 2: Requirement Engineering Carsten Sch
Page 3 and 4: What is Requirement Engineering? Ca
Page 5 and 6: Why not just talk and start a cool
Page 7 and 8: Position of You in this Presentatio
Page 9 and 10: Phases
Page 11 and 12: Which documents should be created i
Page 13 and 14: Kinds of Requirements Functional de
Page 15: Requirements Elicitation 1 Make and
Page 19 and 20: Analysis Part of Workshop wrapup ba
Page 21 and 22: Documentation of Requirements Start
Page 23 and 24: Tools
Page 25 and 26: Test Director
Page 27 and 28: Test Director - Test Planning (Veri
Page 29 and 30: Test Director - Defect Management (
Page 31 and 32: Tips & Summary Document and Synchro
Page 33 and 34: Thank you for your attention!
Page 35 and 36: Abstract Requirement Engineering de
Page 37 and 38: Requirement Elicitation Exercise Tu

Requirement Engineering - Horst Rechner

Create successful ePaper yourself

Delete template?

Save as template?