Personal tools
You are here: Home Knowledge Model REPOSITORY of Terms E Elicitation

Elicitation

by Pierluigi Plebani last modified Apr 25, 2012 12:16
— filed under:

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

 

 

References



 

Document Actions
  • Send this
  • Print this
  • Bookmarks

The Plone® CMS — Open Source Content Management System is © 2000-2017 by the Plone Foundation et al.