Optimization and practice of requirement analysis based on prototype portrait in software development process

Aiming at the problems of incomplete description, ambiguity and inconsistency in the traditional requirements analysis method based on prototype system in software development, this paper proposes a requirement analysis method based on prototype portrait, introduces the process of obtaining the software requirement specification and designing the software by using the prototype portrait method according to the user’s requirements, and formalizes the process of the method, and develops the software with the prototype portrait requirement document approved by the customer, so as to ensure the correctness of the designed functional requirements. The practical results show that the requirement analysis method based on prototype portrait overcomes the problems of long development cycle and high failure rate existing in the traditional requirements analysis method of prototype system, and improves the quality and cycle of software development.

A Review on Test Automation for Test Cases Generation using NLP Techniques

In the process of product development, stakeholders and top management summarize the concept and document the requirements in natural language. These ideas and descriptions documented as software requirements by the technical department. Developers develop software following this software requirement document. For testing this developed software, they derive test cases from natural language requirements and then do the testing process to find the bugs. This process involves understanding requirements and derives test cases that are used to understand by developers and testers. Due to increasing the advanced features, deriving the test cases is monotonous and takes more time. This research article shows a method to automate this process which is deriving test cases from requirements using NLP algorithms. This approach useful to reduce the time and cost of software development.

iMER-FM: Iterative Process of System Feature Model Extraction from the Requirements

Software product line engineering (SPLE) is a paradigm to promote systematic software reuse. A Feature Model (FM) is a common means to illustrate the commonality and variability of software products in a family. In most existing FM extraction approaches, keywords in the requirement document or certain types of system behavior or external events are considered features. The resulting FM is a combination of user activities and system actions (SAs), making it hard to understand. In this paper, we present an automatic approach to generate a product line FM from multiple requirement documents. We consider user activity and SAs separately in our approach and focus on the expected behaviors of the software system, together with the data being processed. The resulting FM clearly illustrates the expected functionalities of the software system and their variability in the product line. We also compared our approach with existing techniques by processing the same textual documents, and noted improvements in our results.

Usability Requirements Extraction Method from Software Document

Extracting the usability requirements are crucial during requirements review and requirements validation for different purposes. Usability requirements are hard to be determined until the real user has experienced the software. It is even more challenging when these usability requirements are documented in natural language, which has an inconsistent and unrestricted structure. Automated requirements extraction has been widely studied to facilitate the process of requirements checking. Nevertheless, the accuracy of requirements extraction method still can be improved. Thus, this paper has presented the usability keywords repository that followed the ISO 9126 and ISO 25010 usability category and has gone through the expert validation process. The usability requirement extraction method is moreover enhanced with extra procedures in conforming the usability requirement statement. First, each statement in the requirement document is checked if there is a keyword usability, whereby the keywords used must match with the usability keyword repository. In order to ensure that the selected statement is a usability requirement, the corresponding usability keyword position should be after the fixed auxiliary verbs. The performance of the improved usability requirements extraction method is then evaluated using precision, recall and accuracy.

An Automated Tool for Detection and Tutoring of Sources of Ambiguities in Requirements Documents

Software Engineering (SE) is the application of essentials to deal with the analysis, design, development, testing, deployment and management - Software Development Life Cycle (SDLC) - of software systems. Requirements Engineering (RE) is responsible for the most critical task in the SDLC; which is transforming the requirements and wishes of the software users into complete, accurate and formal specifications. One of the main responsibilities of RE is the creation of a software requirements document that exactly, reliably, and totally defines the functional and non-functional properties of the system to be developed. At some point through the RE process, the requirements are written using a Natural Language (NL). On one hand, NLs are flexible, common, and popular. On the other hand, NLs are recognized widely as inherently ambiguous. Ambiguity is noticed in a requirement document when a piece of text is interpreted in distinct ways. This may lead to erroneous software that is too expensive to correct in later phases of the SDLC. Many tools have been developed in the literature to detect ambiguities in requirements documents. Best practices for writing requirements have also been proposed to help avoid ambiguities in the first place. The goal of this paper is to combine features from both approaches by developing the Ambiguity Checker Tutor (ACTutor), which not only detects ambiguities, but also aids in tutoring requirements engineers to apply best practices while writing requirements (rather than merely listing them). The paper is mainly concerned with proving the tutoring effectiveness of ACTutor through empirical evaluation.

Algorithm for Automatic Detection of Ambiguities from Software Requirements

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.

REQUIREMENT ANALYSIS OF COMPUTER-BASED INSTRUMENTATION AND CONTROL SYSTEM FOR REAKTOR DAYA EKSPERIMENTAL

Developing and licensing of digital Instrumentation and control (I&C) system for nuclear power plant (NPP) are challenging especially for the new construction since digital technology are composite with a very high complexity of many integrated systems. National Nuclear Energy Agency of Indonesia (BATAN), who design Reaktor Daya Eksperimental (RDE), should prepare the documents to meet the licensing requirements of national regulator in this case Nuclear Energy Regulatory Agency of Indonesia (BAPETEN). BAPETEN’s chairman regulation No.6 year of 2012 is the first national requirement which state requirements related to design of computer-based system concerning on safety of power reactor that should be followed. Since BAPETEN only denotes requirements without state which code and standards to be used, therefore BATAN can add references from International Nuclear Energy Agency (IAEA) guidelines. In this paper, requirement document traceability is developed to determine which code and standards should be used to verify and validate the I&C computer-based system of RDE. The hierarchy of regulatory and utility requirements are developed to guide the design basis documentation. Developing requirements analysis of computer-based I&C system RDE are completed after determining the design requirements from the utility and regulatory requirements. This methodology will help the design engineers to follow the utility requirements by concerning to the production, and follow the regulatory requirements concerning the safety aspect.Keywords: Computer-based system, I&C System, Requirements analysis, Licensing, RDE