specification document
Recently Published Documents


TOTAL DOCUMENTS

51
(FIVE YEARS 15)

H-INDEX

3
(FIVE YEARS 1)

Author(s):  
Henry Howland

The Common Vulnerability Scoring System is at the core of vulnerability management for systems of private corporations to highly classified government networks, allowing organizations to prioritize remediation in descending order of risk. With a lack of justification for its underlying formula, inconsistencies in its specification document, and no correlation to exploited vulnerabilities in the wild, it is unable to provide a meaningful metric for describing a vulnerability's severity, let alone risk. As it stands, this standard compromises the security of America?s most sensitive information systems.


Author(s):  
Hassan Shojaee-Mend ◽  
Haleh Ayatollahi ◽  
Azam Abdolahadi

Abstract Objective Developing an ontology can help collecting and sharing information in traditional medicine including Persian medicine in a well-defined format. The present study aimed to develop an ontology for gastric dystemperament in the Persian medicine. Methods This was a mixed-methods study conducted in 2019. The first stage was related to providing an ontology requirements specification document. In the second stage, important terms, concepts, and their relationships were identified via literature review and expert panels. Then, the results derived from the second stage were refined and validated using the Delphi method in three rounds. Finally, in the fourth stage, the ontology was evaluated in terms of consistency and coherence. Results In this study, 241 concepts related to different types of gastric dystemperament, diagnostic criteria, and treatments in the Persian medicine were identified through literature review and expert panels, and 12 new concepts were suggested during the Delphi study. In total, after performing three rounds of the Delphi study, 233 concepts were identified. Finally, an ontology was developed with 71 classes, and the results of the evaluation study revealed that the ontology was consistent and coherent. Conclusion In this study, an ontology was created for gastric dystemperament in the Persian medicine. This ontology can be used for designing future systems, such as case-based reasoning and expert systems. Moreover, the use of other evaluation methods is suggested to construct a more complete and precise ontology.


Author(s):  
Enny Dwi Oktaviyani ◽  
Licantik Licantik

Software Requirements Specification Document must be complete, unambiguous and correct because an incorrect Software Requirements Specification Document can lead to failure in software development. Software Requirements Specification document must contain non-redundant sentences. Meyer's Seven Sins describes several errors in Software Requirements Specification Document, one of which is redundancy which is a variant of noise. Redundancy is the repetition of the same information, but using different terms or phrases, thus giving the impression that new information is available. This study analyzes the performance of the framework and tools for detecting redundancy in sentence pairs in the software requirements specification document using the WordNet-based semantic similarity method. This study tries to develop the framework and tools that have been proposed in previous studies, namely by detecting redundancy in sentence pairs without fact extraction. The proposed approach and evaluation process uses Kappa values ??to determine whether the performance of the framework and assistive tools can be used to detect redundancy in sentence pairs properly. The method using literature study, data collection, problem analysis, making a framework, making auxiliary tools, and testing. The test uses the Kappa value with two scenarios, from the results of testing the framework and assistive tools can be used to detect redundancy in the Software Requirements Specification Document with a Kappa value of 0.777 with the interpretation of the kappa value is a substantial agreement at a threshold of 0.73


Author(s):  
Juneyoung Lee ◽  
Dongjoo Kim ◽  
Chung-Kil Hur ◽  
Nuno P. Lopes

AbstractSeveral automatic verification tools have been recently developed to verify subsets of LLVM’s optimizations. However, none of these tools has robust support to verify memory optimizations.In this paper, we present the first SMT encoding of LLVM’s memory model that 1) is sufficiently precise to validate all of LLVM’s intra-procedural memory optimizations, and 2) enables bounded translation validation of programs with up to hundreds of thousands of lines of code. We implemented our new encoding in Alive2, a bounded translation validation tool, and used it to uncover 21 new bugs in LLVM memory optimizations, 10 of which have been already fixed. We also found several inconsistencies in LLVM IR’s official specification document (LangRef) and fixed LLVM’s code and the document so they are in agreement.


2020 ◽  
Vol 198 (4) ◽  
pp. 906-917
Author(s):  
Anna Wojaczek ◽  
Michael Scott Brown ◽  
Tomasz Smal

Management of air transportation of strategic goods is a very complex task with many challenges. This paper describes the method used in documenting the requirements for an IT system intended to support management of air transportation of military and dual-use goods. The work was completed in conjunction with a private logistics company. The project produced a Software Requirements Specification document and a working prototype. The document and prototype are held by the Military University of Land Forces of Poland. Requirements were solicited from numerous sources. A private logistics company, numerous books and personal experience of the team members all contributed to requirements. These requirements were then analyzed and a final set of requirements was produced. Screen mock-ups and a working prototype were developed. Selected screen shots are within the paper. The working prototype was developed by constructing a database and using a code generator to produce a web application.


2020 ◽  
Vol 9 (2) ◽  
pp. 215
Author(s):  
Dwi Januarita AK

The rapid development of technology makes this technology have an impact on many fields, one of which is the business world. The number of businesses that have emerged both small and large businesses that have an impact on competition between these businesses. Today, business in the culinary field is getting tougher. The culinary business sector of restaurants is increasingly popping up in this age. We need to overcome the competition in the emerging restaurant business. By using the stages of making software requirements specifications based on ISO / IEC / IEEE 29148-2018, this restaurant business will have an international standard information system. The result of this method is a software requirements specification document (SKPL) as a reference document for all activities carried out during the development of this information system.


Software Systems are built by the Software engineers and must ensure that software requirement document (SRS) should be specific. Natural Language is the main representation of Software requirement specification document, because it is the most flexible and easiest way for clients or customers to express their software requirements [2]. However being stated in natural language, software requirement specification document may lead to ambiguities [28]. The main goal of presented work to automatically detection of the different types of ambiguities like Lexical, Syntactic, Syntax and Pragmatic. Then an algorithm is proposed to early detection the different types of ambiguities from software requirement document. Part of Speech (POS) technique and regular expression is used to detect each type of ambiguities. An algorithm presented in this paper have two main goals (1) Automatic detection of different types of ambiguities. (2) Count the total number of each types of ambiguities found and evaluate the percentage of ambiguous and non- ambiguous statements detected from software requirement document. The suggested algorithm can absolutely support the analyst in identifying different kinds of ambiguities in Software requirements specification (SRS) document.


Sign in / Sign up

Export Citation Format

Share Document