Journal ArticleDOI
Requirements engineering: making the connection between the software developer and customer
Hossein Saiedian,R. Dale +1 more
TLDR
The purpose of this research and report is to investigate the key players and their roles along with the existing methods and obstacles in Requirements Elicitation and concentrate on emphasizing key activities and methods for gathering information, as well as offering new approaches and ideas for improving the transfer and record of this information.Abstract:
Requirements engineering are one of the most crucial steps in software development process. Without a well-written requirements specification, developer’s do not know what to build, user’s do not know what to expect, and there is no way to validate that the created system actually meets the original needs of the user. Much of the emphasis in the recent attention for a software engineering discipline has centered on the formalization of software specifications and their flowdown to system design and verification. Undoubtedly, the incorporation of such sound, complete, and unambiguous traceability is vital to the success of any project. However, it has been our experience through years of work (on both sides) within the government and private sector military industrial establishment that many projects fail even before they reach the formal specification stage. That is because too often the developer does not truly understand or address the real requirements of the user and his environment. The purpose of this research and report is to investigate the key players and their roles along with the existing methods and obstacles in Requirements Elicitation. The article will concentrate on emphasizing key activities and methods for gathering this information, as well as offering new approaches and ideas for improving the transfer and record of this information. Our hope is that this article will become an informal policy reminder/guideline for engineers and project managers alike. The success of our products and systems are largely determined by our attention to the human dimensions of the requirements process. We hope this article will bring attention to this oft-neglected element in software development and encourage discussion about how to effectively address the issue. q 2000 Elsevier Science B.V. All rights reserved.read more
Citations
More filters
Journal ArticleDOI
Effective Communication in Requirements Elicitation: A Comparison of Methodologies
Jane Coughlan,Robert D. Macredie +1 more
TL;DR: A four-dimensional framework is outlined and used to appraise comparatively four different methodologies seeking to promote a closer working relationship between users and designers and makes recommendations based on the four dimensions to provide fruitful considerations for system designers.
Journal ArticleDOI
Designing eHealth that Matters via a Multidisciplinary Requirements Development Approach
TL;DR: Evaluated eHealth on a feature-specific level in order to learn exactly why such a technology does or does not live up to its expectations, and enables eHealth developers to apply a systematic and multi-disciplinary approach towards the creation of requirements.
Journal ArticleDOI
User involvement in healthcare technology development and assessment: Structured literature review
TL;DR: It is shown that medical device users are not homogeneous but heterogeneous in several aspects, such as needs, skills and working environments, which is an important consideration for incorporating users' perspectives in medical device technologies.
Journal ArticleDOI
Communication issues in requirements elicitation: A content analysis of stakeholder experiences
TL;DR: This pilot study builds upon an existing theory-based categorisation of communication problems through presentation of a four-dimensional framework on communication, validated through a content analysis of interview data that can be assigned to the dimensional categories, highlighting any problematic areas.
Journal ArticleDOI
Requirements engineering for e-Government services: A citizen-centric approach and case study
TL;DR: A citizen-centric approach towards user requirements engineering for e-Government services is presented and a case study of a social support portal shows the need for repeated citizen inquiry, as the implementation of user requirements in low-fidelity prototype design is not always accepted by prospective end-users.
References
More filters
Journal ArticleDOI
Customer-developer links in software development
Mark Keil,Erran Carmel +1 more
TL;DR: Tapping into this source of information requires the establishment of one or more customer-developer links, which are defined as the techniques and/or channels that allow customers and developers to exchange information.
Journal ArticleDOI
Making customer-centered design work for teams
Karen Holtzblatt,Hugh Beyer +1 more
TL;DR: This work model develops an abstract work model that brings together data from all customers, keeping good ideas, fixing problems, and using technology to combine and remove steps to create a consolidated model.
Journal ArticleDOI
Apprenticing with the customer
Hugh Beyer,Karen Holtzblatt +1 more
TL;DR: It is the relationship between designers and customers that determines how well the design team understands the customer problem, and designers need better approaches to gathering customer requirements.
Journal ArticleDOI
Status report: requirements engineering
TL;DR: Research areas that have significant payoff potential, including improving natural-language specifications, rapid prototyping and requirements animation, requirements clustering, requirements-based testing, computer-aided requirements engineering, requirements reuse, research into methods, knowledge engineering, formal methods, and a unified framework, are outlined.