Requirements engineering: The state of the practice

Neill, Colin J.; Laplante, Phillip A.

doi:10.1109/ms.2003.1241365

Cited by 201 publications

(109 citation statements)

References 7 publications

Supporting

Mentioning

103

Contrasting

Order By: Relevance

“…The software industry commonly uses natural language (NL) notations to express software requirements [47], with NL being employed by over 60% of practitioners [32]. With the increasing adoption of agile development practices such as Scrum, the semi-structured NL notation of user stories is gaining momentum [31,38].…”

Section: Introductionmentioning

confidence: 99%

Extracting conceptual models from user stories with Visual Narrator

et al. 2017

View full text Add to dashboard Cite

Extracting conceptual models from natural language requirements can help identify dependencies, redundancies, and conflicts between requirements via a holistic and easy-to-understand view that is generated from lengthy textual specifications. Unfortunately, existing approaches never gained traction in practice, because they either require substantial human involvement or they deliver too low accuracy. In this paper, we propose an automated approach called Visual Narrator based on natural language processing that extracts conceptual models from user story requirements. We choose this notation because of its popularity among (agile) practitioners and its focus on the essential components of a requirement: Who? What? Why? Coupled with a careful selection and tuning of heuristics, we show how Visual Narrator enables generating conceptual models from user stories with high accuracy. Visual Narrator is part of the holistic Grimm method for user story collaboration that ranges from elicitation to the interactive visualization and analysis of requirements.

show abstract

Section: Introductionmentioning

confidence: 99%

Extracting conceptual models from user stories with Visual Narrator

et al. 2017

View full text Add to dashboard Cite

show abstract

“…Then, a requirements engineering process for determining the set of valid requirements for a system can be considered a humanintensive interaction process. Furthermore, while an extensive research (Beckworth & Garner, 1994;El-Eman & Madhavjin, 1995;Nikula, Fajaniemi, & Kalviainen, 2000;Juristo, Moreno, & Silva, 2002;Neil & Laplante, 2003) has been conducted on process, techniques, and their real utilization in organizations, few studies have been focused in classifying requirements and the findings show overlaps, omissions, and mixed interpretations. Then, for achieving the research purpose implicitly established in research question (a), we believe that a comprehensive and updated requirements classification is needed.…”

Section: Main Focus Of the Chaptermentioning

confidence: 99%

Handbook of Research on Modern Systems Analysis and Design Technologies and Applications

Syed¹,

Syed²

2009

View full text Add to dashboard Cite

Product or company names used in this set are for identification purposes only. Inclusion of the names of the products or companies does not indicate a claim of ownership by IGI Global of the trademark or registered trademark. Library of Congress Cataloging-in-Publication DataHandbook of research on modern systems analysis and design technologies and applications / Mahbubur Rahman Syed and Sharifun Nessa Syed. p. cm.Summary: "This book provides a compendium of terms, definitions, and explanations of concepts in various areas of systems and design, as well as a vast collection of cutting-edge research articles from the field's leading experts"--Provided by publisher.Includes bibliographical references and index. All work contributed to this book set is original material. The views expressed in this book are those of the authors, but not necessarily of the publisher.

show abstract

“…Other papers, such as [20,13,21,22,23,24] report some problems in this área but do not analyze them in depth. Some of the open issues in agüe methodologies concern elicitation of non-functional requirements and requirements documentation tasks.…”

Section: Introductionmentioning

confidence: 99%

Some Findings Concerning Requirements in Agile Methodologies

Rodríguez

Yagüe

Alarcón

et al. 2009

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. Agile methods have appeared as an attractive alternative to conventional methodologies. These methods try to reduce the time to market and, indirectly, the cost of the product through flexible development and deep customer involvement. The processes related to requirements have been extensively studied in literature, in most cases in the frame of conventional methods. However, conclusions of conventional methodologies could not be necessarily valid for Agile; in some issues, conventional and Agile processes are radically different. As recent surveys report, inadequate project requirements is one of the most conflictive issues in agile approaches and better understanding about this is needed. This paper describes some findings concerning requirements activities in a project developed under an agile methodology. The project intended to evolve an existing product and, therefore, some background information was available. The major difñculties encountered were related to non-functional needs and management of requirements dependencies.

show abstract

Requirements engineering: The state of the practice

Cited by 201 publications

References 7 publications

Extracting conceptual models from user stories with Visual Narrator

Extracting conceptual models from user stories with Visual Narrator

Handbook of Research on Modern Systems Analysis and Design Technologies and Applications

Some Findings Concerning Requirements in Agile Methodologies

Contact Info

Product

Resources

About