skip to main content
US FlagAn official website of the United States government
dot gov icon
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
https lock icon
Secure .gov websites use HTTPS
A lock ( lock ) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

Explore Research Products in the PAR
It may take a few hours for recently added research products to appear in PAR search results.


Title: Management of Implicit Requirements Data in Large SRS Documents: Taxonomy and Techniques
Implicit Requirements (IMR) identification is part of the Requirements Engineering (RE) phase in Software Engineering during which data is gathered to create SRS (Software Requirements Specifications) documents. As opposed to explicit requirements clearly stated, IMRs constitute subtle data and need to be inferred. Research has shown that IMRs are crucial to the success of software development. Many software systems can encounter failures due to lack of IMR data management. SRS documents are large, often hundreds of pages, due to which manually identifying IMRs by human software engineers is not feasible. Moreover, such data is evergrowing due to the expansion of software systems. It is thus important to address the crucial issue of IMR data management. This article presents a survey on IMRs in SRS documents with the definition and overview of IMR data, detailed taxonomy of IMRs with explanation and examples, practices in managing IMR data, and tools for IMR identification. In addition to reviewing classical and state-of-the-art approaches, we highlight trends and challenges and point out open issues for future research. This survey article is interesting based on data quality, hidden information retrieval, veracity and salience, and knowledge discovery from large textual documents with complex heterogeneous data.  more » « less
Award ID(s):
2018575
PAR ID:
10385907
Author(s) / Creator(s):
; ; ;
Date Published:
Journal Name:
ACM SIGMOD Record
Volume:
51
Issue:
2
ISSN:
0163-5808
Page Range / eLocation ID:
18 to 29
Format(s):
Medium: X
Sponsoring Org:
National Science Foundation
More Like this
  1. ; (, Journal of optical communications and networking)
    Abstract—Optical system management software has been migrating toward software-defined networking (SDN) methods and interfaces. The increased programmability of SDN promises greater flexibility, dynamic operation, and multivendor compatibility for optical systems. However, physical layer control systems are complicated by transmission engineering requirements, including quality of transmission, optical power stability, and multidomain service guarantees. These challenges and recent commercial and research efforts to address them are examined. 
    more » « less
  2. ; (, Requirements Engineering)
    Software systems and product lines often use configurable features to specify a portfolio of product variants from a common core. Typically, their requirements also include constraints on which combinations of features are valid. Especially for larger systems and systems where the specifications are scattered among documents, the analysis of a new product’s variability-related requirements is challenging. To address this, we introduce a scalable, tool-supported framework that uses a variability model to automate checks for missing and inconsistent fea- tures and constraints. Our approach also extends and scales traditional variability requirements engineering by incorporating combinatorial interaction testing tech- niques to build valid product variants covering all configurations in the variability model and to automatically discover faulty feature settings in failed builds. Results from evaluation on two configurable systems show that our framework is effective both at early detection of missing, incorrect, and inconsistent variability requirements and at later finding faulty feature configurations. 
    more » « less
  3. ; ; (, International journal of engineering education)
    Engineering student writers must document their reference sources in their theses, papers, proposals, reports, and related documents that they prepare. This is generally done in Microsoft Word or in a LaTeX software package and typically done in the IEEE citation style which is widely used in engineering and technology. In this work, we identify 25 primary reference types and 21 secondary reference types that are used in present-day engineering writing. Because all 46 of these engineering reference types are typically not available in commercial reference management software, we have generated customization files for the widely used EndNote reference management software package that enable referencing to be done using either Cite-While-You-Write (CWYW) for Word users or using BibTeX for LaTeX users. These customization files and instructions on how to install and use them, herein called the Georgia Tech Engineering Reference Management System (GTERMS), are made available on an open-access free-to-use basis. 
    more » « less
  4. ; (, Proceedings of the 54th Hawaii International Conference on System Sciences)
    null (Ed.)
    Our systematic literature review aims to survey research on regulatory and security standard requirements as addressed throughout the Software Development Lifecycle. Also, to characterize current research concerns and identify specific remaining challenges to address regulatory and security standard requirements throughout the SDLC. To this end, we conducted a systematic literature review (SLR) of conference proceedings and academic journals motivated by five areas of concern: 1. SDLC & Regulatory Requirement 2. Risk Assessment and Compliance requirements 3. Technical Debt 4. Decision Making Process throughout the SDLC 5. Metric and Measurements of found Software Vulnerability. The initial search produced 100 papers, and our review process narrowed this total to 20 articles to address our three research questions. Our findings suggest that academic software engineering research directly connecting regulatory and security standard requirements to later stages of the SDLC is rare despite the importance of compliance for ensuring societally acceptable engineering. 
    more » « less
  5. ; (, Proceedings of the 54th Hawaii International Conference on System Sciences)
    null (Ed.)
    Our systematic literature review aims to survey research on regulatory and security standard requirements as addressed throughout the Software Development Lifecycle. Also, to characterize current research concerns and identify specific remaining challenges to address regulatory and security standard requirements throughout the SDLC. To this end, we conducted a systematic literature review (SLR) of conference proceedings and academic journals motivated by five areas of concern: 1. SDLC & Regulatory Requirement 2. Risk Assessment and Compliance requirements 3. Technical Debt 4. Decision Making Process throughout the SDLC 5. Metric and Measurements of found Software Vulnerability. The initial search produced 100 papers, and our review process narrowed this total to 20 articles to address our three research questions. Our findings suggest that academic software engineering research directly connecting regulatory and security standard requirements to later stages of the SDLC is rare despite the importance of compliance for ensuring societally acceptable engineering. 
    more » « less
  • Citation Formats
  • MLA
  • APA
  • Chicago
  • BibTeX
  • Save / Share this Record
  • Send to Email