Requirement Engineering - Horst Rechner

Recommendations

Info

Requirement A requirement is " a singular documented need of what a particular product or service should be or do. It is most commonly used in a formal sense in systems engineering or software engineering. It is a statement that identifies a necessary attribute, capability, characteristic, or quality of a system in order for it to have value and utility to a user." -- [Wikipedia] Sets of requirements are used as inputs into the design, implementation and test stages of product development.
What is Requirement Engineering? Can be seen as transformation of the requirements of the client for his product (e.g. software) to requirements for the system development. see [Man04] p.54 Requirements engineering includes the analysis and management of the requirements using engineering techniques.
Page 1: Requirement Engineering Carsten Sch
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 and 16: Requirements Elicitation 1 Make and
Page 17 and 18: Requirements Elicitation 3 the "dee
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?