Requirements Elicitation and Validation with Real World Scenes Peter Haumer, Klaus Pohl and Klaus Weidenhaupt Rens van Erk
Overview (1/2) Authors: Peter Haumer, Klaus Pohl and Klaus Weidenhaupt University of Aachen, Germany CREWS Project Topic: Requirements Elicitation and Validation with Real World Scenes Published in: Institute of Electrical and Electronics Engineers (IEEE) Transactions on Software Engineering (1998) Origins: Requirement engineering Rich media
Overview (2/2) Purpose: Making the abstraction process which leads to the definition of the conceptual models more transparent. Focus: “On the one hand, new concepts are elicited from the RWEs. On the other hand, the current-state models can be validated against the RWEs.” – Haumer et al. (1998). Main phases: Record observations Comparing requirement and model Creating requirement Relating requirement to model
Related literature Software requirement engineering: “occurs at the start of software development and involves the analysis and negotiation of what capabilities and features a proposed system needs to possess“ – Sommerville & Kotonya (1998) Main method: Software Requirement Engineering Methodology Philosophy of Haumer et al. (1998) adopted in other papers: Van Lamsweerde (2001) Lamsweerde & Willemet (1998) Liu & Yu (2004) Zowghi & Coulin (2005)
Process- Deliverable Diagram (1/2)
Process- Deliverable Diagram (2/2)
Example (1/2) SAFA Software ERP Product Mainly Dutch customers Development of a new product Based on the functionalities of the existing system
Example (2/2)
Questions? Thank you for your attention! Rens van Erk