2008
DOI: 10.1007/978-3-540-89778-1_5
|View full text |Cite
|
Sign up to set email alerts
|

Advances in Requirements Engineering: Bridging the Gap between Stakeholders’ Needs and Formal Designs

Abstract: Abstract. The lions's share of the software faults can be traced to requirements and specification errors, so improvements in requirements engineering can have a large impact on the effectiveness of the overall system development process. A weak link in the chain is the transition from the vague and informal needs of system stakeholders to the formal models that support theoretical analysis and software tools. This paper explains the context for the 2007 Monterey workshop that was dedicated to this problem. It… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2008
2008
2013
2013

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(1 citation statement)
references
References 14 publications
(17 reference statements)
0
1
0
Order By: Relevance
“…The actual process of stakeholder requirements elicitation is conducted via the so-called trawling techniques collected and presented by Robertson (2000), including interviewing (Herder and Stikkelman 2004), simulation models (e.g., scenarios, prototyping) (Chung et al 1999), use-case workshops (Luqi and Kordon 2008). Several methodologies are used to identify and formalize stakeholder requirements, examples of which are Natural Language Processing (NLP), used to analyse the dialogues between stakeholders (Sawyer et al 2008;Kof 2008), the i* framework (Yu 1997;Chung et al 1999), used to reveal goals, tasks resources of and exchanges between the stakeholders (Teruel et al 2011), meta-model, used to reveal the values being exchanged and the design variables, constraints and performance indicators (Herder and Stikkelman 2004).…”
Section: The Concept Of Stakeholder Analysismentioning
confidence: 99%
“…The actual process of stakeholder requirements elicitation is conducted via the so-called trawling techniques collected and presented by Robertson (2000), including interviewing (Herder and Stikkelman 2004), simulation models (e.g., scenarios, prototyping) (Chung et al 1999), use-case workshops (Luqi and Kordon 2008). Several methodologies are used to identify and formalize stakeholder requirements, examples of which are Natural Language Processing (NLP), used to analyse the dialogues between stakeholders (Sawyer et al 2008;Kof 2008), the i* framework (Yu 1997;Chung et al 1999), used to reveal goals, tasks resources of and exchanges between the stakeholders (Teruel et al 2011), meta-model, used to reveal the values being exchanged and the design variables, constraints and performance indicators (Herder and Stikkelman 2004).…”
Section: The Concept Of Stakeholder Analysismentioning
confidence: 99%