1 / 5

Requirements Elicitation

WP1: User Requirements Collection and Analysis Dimitris Plexousakis dp@csi.forth.gr Computer Science Department, University of Crete & Institute for Computer Science - FORTH Heraklion, Crete. Requirements Elicitation. Identify relevant user communities (have we established contacts?)

willem
Télécharger la présentation

Requirements Elicitation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP1: User Requirements Collection and AnalysisDimitris Plexousakisdp@csi.forth.gr Computer Science Department, University of Crete& Institute for Computer Science - FORTHHeraklion, Crete

  2. Requirements Elicitation • Identify relevant user communities (have we established contacts?) • DELOS NoE in Digital Libraries • ERCIM • Library Representatives • German and Italian Societies of Mathematics • German Society of Physics • Greek Society of Mathematics • Hellenic Informatics Society • O.A.I user groups • Other Networks (e.g., PLANET, OntoWeb)

  3. Requirements Elicitation • specify scenarios of use • assemble and distribute customized questionnaires • questionnaires should be detailed but non-technical • assumptions about users: • familiarity with computer / web-browser use • address current practices in literature search • tools to use • distribution over WWW, e-mail • collection through WWW • avoid in-print questionnaires • web-site hosting questionnaire forms • language? (single -- English, multi?)

  4. Requirements Analysis • Many requirement analysis methodologies exist • None is obviously better than the other • Goal-based requirements analysis • questionnaire processing should lead to goal specification • goal decomposition and refinement • exception handling though scenario analysis • result in operationalizable specifications • tools to use (under investigation) • some requirements modeling tools exist • few analysis tools (e.g., GBRAT) • Must capture functional and non-functional requirements

  5. Bibliography • P. Loucopoulos, V. Karakostas “System Requirements Engineering”, McGraw-Hill, 1995 • A. Anton, “Goal-Based Requirements Analysis”, International Conference on Requirements Engineering, 1996 • C. Potts et al. “Inquiry-based Requirements Analysis”, IEEE Software 11(2), 1994 • M. Jarke (ed), “Requirements Tracing”, Communications of the ACM, 41(12), 1998 • T. Alspaugh et al. “An Integrated Scenario Management Strategy”, International Symposium on Requirements Engineering,1999 • …. Requirements Engineering Journal, ICRE conferences

More Related