Requirements Engineering

Author(s):  
Fernando Flores ◽  
Manuel Mora ◽  
Francisco Alvarez ◽  
Rory O’Connor ◽  
Jorge Macias-Luevano

Requirements engineering is the process of discovering the purpose and implicit needs of a software system that will be developed and making explicit, complete, and non ambiguous their specification. Its relevance is based in that omission or mistakes generated during this phase and corrected in later phases of a system development lifecycle, will cause cost overruns and delays to the project, as well as incomplete software. This chapter, by using a conceptual research approach, reviews the literature for developing a review of types of requirements, and the processes, activities, and techniques used. Analysis and synthesis of such findings permit to posit a generic requirements engineering process. Implications, trends, and challenges are then reported. While its execution is being mandatory in most SDLCs, it is done partially. Furthermore, the emergence of advanced services-oriented technologies suggests further research for identifying what of the present knowledge is useful and what is needed. This research is an initial effort to synthesize accumulated knowledge.

Author(s):  
M. Mahmudul Hasan

Regulations and policies contain a rich source of requirements and failure to address these authoritative requirements in software system development can impose costly penalties for regulatory noncompliance. Despite the advancement of information system research, regulatory requirements compliance remains one of the primary challenges still to be efficiently dealt in system development because of the scarce information, complexity, and understanding of available approaches in requirements engineering process of a system development. This paper reports a systematic literature review of the documented approaches of regulatory requirements compliance, classifies these approaches according to different criteria and provides a qualitative analysis of their operational characteristics. The results of this analysis can serve system developers as the means of deriving appropriate methods and tools for regulatory requirements compliance in the software system development.


2020 ◽  
Vol 10 (2) ◽  
pp. 76-81
Author(s):  
Imanuel Revelino Murmanto ◽  
Dina Fitria Murad

The purpose of this study was to design an application to provide information to parents of SDK III BPK Penabur students regarding the exam schedule, and student grades via SMS. The design method used is the System Development Lifecycle method. The application design is done using the Visual Basic 6.0 programming language for designing application programs and interfaces and MySQL for designing the database. This application consists of several modules, namely the module processing data, processing values, processing SMS, and reports. The module is integrated to form a Computerized Value application and Value Access via SMS. In testing the application of Computerized Values ​​and Value Accessing Through SMS, white box testing and Black Box Testing methods are used. Tests are carried out at the module, program and system level. In addition, user testing is also done. The advantages of the application of Computerized Values ​​and Value of Access Through SMS help parents to obtain information about student learning outcomes, helping teachers to process student grades


Author(s):  
Hironori Washizaki ◽  
Tian Xia ◽  
Natsumi Kamata ◽  
Yoshiaki Fukazawa ◽  
Hideyuki Kanuka ◽  
...  

Security patterns encompass security-related issues in secure software system development and operations that often appear in certain contexts. Since the late 1990s about 500 security patterns have been proposed. Although the technical components are well investigated, the direction, overall picture, and barriers to implementation are not. Here, a systematic literature review of 240 papers is used to devise a taxonomy for security pattern research. Our taxonomy and the survey results should improve communications among practitioners and researchers, standardize the terminology, and increase the effectiveness of security patterns.


Author(s):  
Jenny Carolina Ramírez Leal ◽  
William Joseph Giraldo Orozco ◽  
Raquel Anaya Hernández

Desde el inicio de la ingeniería de Requisitos se han utilizado técnicas provenientes de diferentes contextos para obtener el conocimiento de los stakeholders y así definir los requisitos para el sistema software a construir. Este artículo presenta una propuesta metodológica para especificar de manera formalizada técnicas desde los contextos de la elicitación de conocimiento y la Comunicación, con el propósito de comprender como pueden ser aplicadas en la disciplina de ingeniería de Requisitos. Para lograrlo, se llevó a cabo cuatro etapas que permitieron definir la metodología, determinando así los niveles de granularidad de especificación de cada técnica. Con esta propuesta metodológica adaptada al marco de trabajo de Eclipse Process Framework Project (EPF) se construyó para los analistas o ingenieros de requisitos un catálogo con 24 técnicas, con el propósito de que estos usaran estas 24 técnicas en la elicitación de los requisitos de productos software y potencializar el proceso de comunicación. Encontrando que esta metodología de formalización logra ser flexible para ser incorporada en ella, cualquier otro tipo de técnica y facilitar su entendimiento.Palabras Claves: Adquisición de conocimiento, Ingeniería de requisitos, Metodología de formalización, Técnicas.Since the beginning of the Requirements engineering, techniques from different contexts have been used in order to know about this stakeholders and define the requirements for the software system to be built. This article presents a methodological proposal to specify, in a technical formalized way techniques from the contexts of the knowledge gathering (elicitation) and communication with the purpose of understanding how they can be applied in the Engineering Requirements discipline. To achieve the above, four stages that allowed defining the methodology were conducted determining in this way, the granularity levels specification of each technique. Having this methodological approach adapted to the frame of work of the Eclipse Process Framework Project (EPF) , a catalog of 24 techniques, was provided for Requirements analysts or engineers so that they will guide the implementation of these 24 techniques in the engineering discipline Requirements proving its value to potentiate the process of communication. Finding that this method of formalization happens to be flexible to be incorporated therein, any other technical and facilitate its understandingKeywords: Knowledge Acquisition, Requirements Engineering, Methodology formalization techniques.


Sign in / Sign up

Export Citation Format

Share Document