Innovations in Natural Language Document Processing for Requirements Engineering

Bērziņš, Valdis; Martell, Craig; Luqi,; Adams, Paige

doi:10.1007/978-3-540-89778-1_11

Cited by 8 publications

(14 citation statements)

References 39 publications

(32 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This imposes extreme constraints on the accuracy of natural language processing and that we might use to derive system requirements. However, natural language processing accuracies are currently in the 90%-92% range, at best [3]. Therefore natural language processing must be augmented with other methods for removing residual errors, and accuracy must be greatly improved if it is to be seriously used for Requirements engineering.…”

Section: Synthesis Of Workhop Discussionmentioning

confidence: 99%

“…For details, see [3]. Developing tools and methods for augmenting and supporting current requirements engineering processes with tools that incorporate natural language processing appears to be a promising realistic goal, if it is coupled with integration into error checking and correction processes already used in requirements engineering.…”

Section: Synthesis Of Workhop Discussionmentioning

confidence: 99%

See 1 more Smart Citation

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

Luqi

Kordon

2008

Lecture Notes in Computer Science

View full text Add to dashboard Cite

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 provides the case study that participants were asked to use to illustrate their new methods, and summarizes the discussion and conclusions of the workshop.

show abstract

Section: Synthesis Of Workhop Discussionmentioning

confidence: 99%

Section: Synthesis Of Workhop Discussionmentioning

confidence: 99%

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

Luqi

Kordon

2008

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…We are targeting this disconnect between the specification and design. [12,13] are two software survey papers which highlight problems with requirements documents and specification. [12,13] show that designers often implement their code incorrectly.…”

Section: Specification-based Testingmentioning

confidence: 99%

“…[12,13] are two software survey papers which highlight problems with requirements documents and specification. [12,13] show that designers often implement their code incorrectly. [14] talks about the ambiguity inherent in specification and software problems associated with this.…”

Section: Specification-based Testingmentioning

confidence: 99%

Test generation for subtractive specification errors

Lee

Harris

2012

2012 IEEE 30th VLSI Test Symposium (VTS)

View full text Add to dashboard Cite

show abstract

“…Since requirements for long-lived systems are constantly changing, this gap must be bridged repeatedly, making unaided manual processes unattractive unless they can be made incremental. The main current difficulty is the error rates characteristic of current natural language capabilities, which are low enough to be useful in some contexts but not low enough to rely on without integration with other processes for detecting and removing residual errors [150]. 6) We studied ways to reduce testing effort and costs associated with technologyadvancement upgrades to systems with open architectures.…”

Section: Scientific Progress and Accomplishments During The Reportingmentioning

confidence: 99%

Documentation Driven Software Development

Luqi¹

2010

View full text Add to dashboard Cite

The public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Our objective is to develop an integrated, systematic, documentation centric approach to software development, known as Documentation Driven Software Development (DDD). The research issues for DDD are creation and application of three key documenting technologies that will drive the development process and a Document Management System (DMS) that will support them. These technologies address (1) representations for active documents; (2) representations for repositories; (3) methods for analysis, transformation, and presentation of this ABSTRACTOur objective is to develop an integrated, systematic, documentation centric approach to software development, known as Documentation Driven Software Development (DDD). The research issues for DDD are creation and application of three key documenting technologies that will drive the development process and a Document Management System (DMS) that will support them. These technologies address (1) representations for active documents; (2) representations for repositories; (3) methods for analysis, transformation, and presentation of this information.In addition, we explored new possibilities for computer-aided interfaces that help humans with routine tasks. In doing so we applied Cognitive Science and machine learning methods to design user interfaces that can learn and assist users. We also expanded our work in the area of integration of ontologies from heterogeneous sources. Specifically, we studied Knowledge System Integration Ontology (KSIO) that aligns data and information systems with current situational context for the efficient knowledge collection, integration and transfer. The role of ontology is to organize and structure knowledge (e.g. by standardized terminology) so that semantic queries and associations become more efficient. We assessed the degree to which natural language processing can be usefully applied to the analysis of requirement changes and their impact on system structure and implementation.(a) Papers published in peer-reviewed journals (N/A for none)

show abstract

Innovations in Natural Language Document Processing for Requirements Engineering

Cited by 8 publications

References 39 publications

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

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

Test generation for subtractive specification errors

Documentation Driven Software Development

Contact Info

Product

Resources

About