Elicitation
by
Pierluigi Plebani
—
last modified
Apr 25, 2012 12:16
—
filed under:
KnowledgeModel
Definitions
Term: Elicitation |
Domain: Cross-cutting issues | ||||
---|---|---|---|---|---|
Engineering and Design (KM-ED) |
Adaptation and Monitoring (KM-AM) |
Quality Definition, Negotiation and
Assurance (KM-QA) |
Generic (domain independent) |
||
D o m a i n : L a y e r s |
Business Process Management (KM-BPM) |
||||
Service Composition and
Coordination (KM-SC) |
|||||
Service Infrastructure (KM-SI) |
|||||
Generic (domain independent) |
Identify sources of information about the system and
discover the requirements from these. [CD-JRA-1.1.2]
[CD-JRA-1.1.5]. In Software Engineering, elicitation is concerned with where software requirements come from and how the software engineer can collect them. It is the first stage in building an understanding of the problem the software is required to solve. It is fundamentally a human activity, and is where the stakeholders are identified and relationships established between the development team and the customer. It is variously termed "requirements capture," "requirements discovery," and "requirements acquisition." [SWEBOK] |
Competencies
-
UniDue: Requirements Engineering; http://www.sse.uni-due.de/wms/en/index.php?go=110; Klaus Pohl, Andreas Gehlert
- CITY: User-centred requirements engineering; http://hcid.soi.city.ac.uk/research/index.html; Neil Maiden, Kos Zachos, Angela Kounkou
- Tilburg: Requirements Engineering; http://www.tilburguniversity.nl/eriss/research/;
Oktay Turetken
References
- [CD-JRA-1.1.2] "Separate Design Knowledge models for software engineering and service-based computing."
- [CD-JRA-1.1.5] "Analysis on how to exploit codified HCI and codified context knowledge for SBA engineering"
- [SWEBOK] Requirements Elicitation: http://www.computer.org/portal/web/swebok/html/ch2#ch2-3