Detecting Vague Words & Phrases in Requirements Documents in a Multilingual Environment

2017 ◽  
Author(s):  
Breno Dantas Cruz ◽  
Bargav Jayaraman ◽  
Anurag Dwarakanath ◽  
Collin McMillan
Keyword(s):  
Requirements Documents

A Topic Modeling Approach to Study Design Requirements

2021 ◽  
Author(s):  
Cheng Chen ◽  
Jesse Mullis ◽  
Beshoy Morkos
Keyword(s):  
Domain Knowledge ◽  
Latent Dirichlet Allocation ◽  
High Volume ◽  
Management Tools ◽  
Human Errors ◽  
Domain Experts ◽  
Product Evolution ◽  
Engineering Changes ◽  
Collapsed Gibbs Sampling ◽  
Requirements Documents

Abstract Risk management is vital to a product’s lifecycle. The current practice of reducing risks relies on domain experts or management tools to identify unexpected engineering changes, where such approaches are prone to human errors and laborious operations. However, this study presents a framework to contribute to requirements management by implementing a generative probabilistic model, the supervised latent Dirichlet allocation (LDA) with collapsed Gibbs sampling (CGS), to study the topic composition within three unlabeled and unstructured industrial requirements documents. As finding the preferred number of topics remains an open-ended question, a case study estimates an appropriate number of topics to represent each requirements document based on both perplexity and coherence values. Using human evaluations and interpretable visualizations, the result demonstrates the different level of design details by varying the number of topics. Further, a relevance measurement provides the flexibility to improve the quality of topics. Designers can increase design efficiency by understanding, organizing, and analyzing high-volume requirements documents in confirmation management based on topics across different domains. With domain knowledge and purposeful interpretation of topics, designers can make informed decisions on product evolution and mitigate the risks of unexpected engineering changes.

scholarly journals IPTEKS PELAKSANAAN SEWA BARANG MILIK NEGARA PADA KANTOR PELAYANAN KEKAYAAN NEGARA DAN LELANG (KPKNL) MANADO

2018 ◽  
Vol 2 (02) ◽  
Author(s):  
Cecen A. Sadil ◽  
Dede F. Mahyudin ◽  
Wanly Harikase ◽  
Jenny Morasa
Keyword(s):  
State Revenue ◽  
Tax State ◽  
Work Units ◽  
Requirements Documents

The implementation of BMN Rental is the utilization of other parties within a certain period of time and receive cash rewards that can increase non-tax state revenue (PNBP). Based on the results of observations, it can be seen that the object of lease in the implementation of BMN leases in Manado KPKNL has covered all rental objects above, so Manado KPKNL expects reports from other work units and awareness of satker in reporting BMN after that KPKNL Manado takes investigative actions to the field , there are still many satker who complain about the high cost of rent. BMN leasing in Manado KPKNL is considered to be lacking, because there are still a lot of satker who have not fully understood the requirements for submitting the lease documents, so that when the lease application is submitted there are still many incomplete / incomplete requirements documents. Suggestions from penuis for KPKNL Manado are expected to be able to set a reasonable and affordable BMN rental price. Advice from the author is expected for each Satker to pay more attention to the requirements before applying for BMN rent.Keywords : Rental Implementation, state property (BMN).

From Textual Scenarios to Message Sequence Charts

2010 ◽  
pp. 83-105 ◽  
Author(s):  
Leonid Kof
Keyword(s):  
Natural Language ◽  
Computational Linguistics ◽  
Development Project ◽  
Message Sequence Charts ◽  
Software Development Project ◽  
Requirement Document ◽  
Requirements Documents ◽  
Message Sequence Chart

Requirements engineering, the first phase of any software development project, is the Achilles’ heel of the whole development process, as requirements documents are often inconsistent and incomplete. In industrial requirements documents natural language is the main presentation means. In such documents, the system behavior is specified in the form of use cases and their scenarios, written as a sequence of sentences in natural language. For the authors of requirements documents some facts are so obvious that they forget to mention them. This surely causes problems for the requirements analyst. By the very nature of omissions, they are difficult to detect by document reviews: Facts that are too obvious to be written down at the time of document writing, mostly remain obvious at the time of review. In such a way, omissions stay undetected. This book chapter presents an approach that analyzes textual scenarios with the means of computational linguistics, identifies where actors or whole actions are missing from the text, completes the missing information, and creates a message sequence chart (MSC) including the information missing from the textual scenario. Finally, this MSC is presented to the requirements analyst for validation. The book chapter presents also a case study where scenarios from a requirement document based on industrial specifications were translated to MSCs. The case study shows feasibility of the approach.

Sign in / Sign up

Export Citation Format

Share Document