Requirements Elicitation: A Survey of Techniques, Approaches, and Tools

Zowghi, Didar; Coulin, Chad

doi:10.1007/3-540-28244-0_2

Cited by 340 publications

(358 citation statements)

References 42 publications

Supporting

Mentioning

304

Contrasting

Unclassified

Order By: Relevance

“…The sources of information for developing the use-case are through domain knowledge analysis [50,61], related literatures [62,63] on the subject and refinement through regression testing of the framework. The use-case portrays how the actor, a structural engineer in this case, interacts with the proposed system to produce appraisal results of alternative design solutions.…”

Section: Prototype Implementationmentioning

confidence: 99%

Structural sustainability appraisal in BIM

Oti

Tizani

Abanda

et al. 2016

Automation in Construction

View full text Add to dashboard Cite

The provision of Application Programming Interface (API) in BIM-enable tools can contribute to facilitating BIM-related research. APIs are useful links for running plug-ins and external programmes but they are yet to be fully exploited in expanding the BIM scope. The modelling of n-Dimensional (nD) building performance measures can potentially benefit from BIM extension through API implementations. Sustainability is one such measure associated with buildings. For the structural engineer, recent design criteria have put great emphasis on the sustainability credentials as part of the traditional criteria of structural integrity, constructability and cost. This paper examines the utilization of API in BIM extension and presents a demonstration of an API application to embed sustainability issues into the appraisal process of structural conceptual design options in BIM. It concludes that API implementations are useful in expanding the BIM scope. Also, the approach including process modelling, algorithms and object-based instantiations demonstrated in the API implementation can be applicable to other nD building performance measures as may be relevant to the various professional platforms in the construction domain.

show abstract

Section: Prototype Implementationmentioning

confidence: 99%

Structural sustainability appraisal in BIM

Oti

Tizani

Abanda

et al. 2016

Automation in Construction

View full text Add to dashboard Cite

show abstract

“…Therefore, in simple terms, the research defined creative requirements work as the production of requirements that are both useful and new to project stakeholders. There is no shortage of techniques to elicit and acquire existing, and hence not new requirements and requirements-related knowledge from stakeholders, as the classifications reported in [10], [11] that encourage creative thinking about the requirements of a future system -both scenarios [12], [13] and prototypes [14], [15] direct stakeholders to explore and discover future system behaviours and qualities, some of which might be novel and hence creative -while brainstorming seeks to exploit group dynamics to generate more requirements, some of which might be novel and hence creative. However, the discovery of requirements that are novel is not the primary intended functions of these techniques.…”

Section: Related Workmentioning

confidence: 99%

Stimulating Stakeholders' Imagination: New Creativity Triggers for Eliciting Novel Requirements

Burnay

Horkoff

Maiden

2016

2016 IEEE 24th International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

Abstract-Requirements engineering is a creative process in which stakeholders and engineers work together to create ideas for new products, services and systems. Several techniques have proved to be effective for eliciting creative requirements. Yet, most of these techniques are heavy to implement and require long periods of time to be applied correctly. Few lightweight creativity techniques have been developed for use in requirements engineering. One such lightweight technique is the creativity trigger, which provides simple guidance to stakeholders and engineers to help produce creative requirements. While easy to apply, creativity triggers were derived informally from experience of practitioners and have not been validated in a systematic way. This paper reports design and preliminary validation research, that sought to provide empirical foundations for a more complete set of lightweight creativity triggers, to be used by stakeholders and engineers to quickly and simply generate new and useful requirements on products, services and systems.

show abstract

“…the Sales feature in Figure 1 refers to six such requirements. To enable acceptable implementation of the feature, the feature's requirements are elicited [25] and refined until they comply with the solution's environment and design [26].…”

Section: Feature Trees For Release Planningmentioning

confidence: 99%

Release Planning with Feature Trees: Industrial Case

Fricker

Schumacher

2012

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Abstract. [Context and motivation] Requirements catalogues for software release planning are often not complete and homogeneous. Current release planning approaches, however, assume such commitment to detail -at least implicitly. [Question/problem] We evaluate how to relax these expectations, while at the same time reducing release planning effort and increasing decisionmaking flexibility. [Principal ideas/results] Feature trees capture AND, OR, and REQUIRES relationships between requirements. Such requirements structuring can be used to hide incompleteness and to support abstraction. [Contribution] The paper describes how to utilize feature trees for planning the releases of an evolving software solution and evaluates the effects of the approach on effort, decision-making, and trust with an industrial case.Keywords: features, abstraction, release planning, roadmapping, case study. IntroductionSoftware releases are planned by allocating requirements to development projects [1]. A strategic release plan aligns the development of an evolving software solution with market and stakeholder needs, company objectives, and constraints such as time and resources. Release planning is a central concern in iterative development, where multiple iterations, rather than a single project, are defined [2]. Release planning involves the following steps [3]. Requirements are elicited and specified. Criteria [4] are defined to evaluate and prioritize requirements [5]. Releases are then scoped by allocating the prioritized requirements to development projects. The resulting release plans are implemented, delivered, and analyzed with post-release reflections [6].Requirements that enter release planning are often of low quality [7]. Their homogeneity [8], completeness, and understanding [9] are hard to ensure due to the limited effort invested before a development project is funded. This situation contradicts with the assumptions of release planning approaches that scope projects simply by prioritizing and allocating available requirements. Consequently, the results are not trusted and not used for guiding ensuing development steps [10].Release Planning with Feature Trees: Industrial Case 289 This paper describes in detail how to hide the requirements-related problems by structuring the release planning inputs. The approach, whose initial ideas were introduced in an earlier position paper [11], is based on variability modeling [12] that allows abstracting from requirements with AND, OR, and REQUIRES relationships [13]. Variability is here used to structure decision options [14] for product evolution. This paper then introduces an industrial case [15] to understand how to use variability modeling in a real-world context of continuous agile product management [16]. Evaluated were feasibility of the approach and its effects on effort, decision-making, and trust were evaluated.The paper is structured as follows. Section 2 describes background and motivation. Section 3 introduces variability-based release planning. Section 4 describe...

show abstract

Requirements Elicitation: A Survey of Techniques, Approaches, and Tools

Cited by 340 publications

References 42 publications

Structural sustainability appraisal in BIM

Structural sustainability appraisal in BIM

Stimulating Stakeholders' Imagination: New Creativity Triggers for Eliciting Novel Requirements

Release Planning with Feature Trees: Industrial Case

Contact Info

Product

Resources

About