What Works Better? A Study of Classifying Requirements

Classifying requirements into functional requirements (FR) and non-functional ones (NFR) is an important task in requirements engineering. However, automated classification of requirements written in natural language is not straightforward, due to the variability of natural language and the absence of a controlled vocabulary. This paper investigates how automated classification of requirements into FR and NFR can be improved and how well several machine learning approaches work in this context. We contribute an approach for preprocessing requirements that standardizes and normalizes requirements before applying classification algorithms. Further, we report on how well several existing machine learning methods perform for automated classification of NFRs into sub-categories such as usability, availability, or performance. Our study is performed on 625 requirements provided by the OpenScience tera-PROMISE repository. We found that our preprocessing improved the performance of an existing classification method. We further found significant differences in the performance of approaches such as Latent Dirichlet Allocation, Biterm Topic Modeling, or Naive Bayes for the sub-classification of NFRs.Comment: 7 pages, the 25th IEEE International Conference on Requirements Engineering (RE'17

Review of a Process Prioritization in Mass Customization

Purpose – The present article aims to analyze the content of process prioritization methods and possibilities of its application in the context of Mass Customization. Design/methodology/approach – As the analysis is based on exploratory approach, qualitative methodology is the main tool used in the research. Moreover, author do not aim at providing conclusive answers to research questions; in opposition, generating relevant insights about a current situation is a goal. Findings – Results suggest that prioritization methods and principles are compatible, necessary and can be successfully applicable to Mass Customization at different process stages or even this concept types. In addition, this research reveals the need to have a combined and multidimensional prioritization at the beginning of Mass Customization processes. Research limitations/implications – Main research limitations can be divided into two parts. Firstly, when prioritization is taken into consideration, it is noticed that a limited scope of research focus on combined prioritization models as well as their effect on organizations results, especially in Public and Non-governmental sector. Secondly, in a case of concept of Mass Customization and its analysis, scientific discussions show extremum transitions to Big Data, Internet platform capabilities and overall customer flow management via modern economic theories in the last decades. Therefore, a lack of sufficient scientific attention to important parts of prioritization severely affect customer input, Design and Infrastructure of Mass Customization. In addition, both parts require not only proper understanding of the theoretical background but also following detail description of practical implication tools and guidelines as well as defining possible application effect. Since this article is based on the theoretical literature review, case studies and comparative analysis towards a practical implication are elaborated briefly. Practical implications – This research may serve as relevant insights into the context of the Mass Customization system and processes, where organizations constantly cope with prioritization by making a number of decisions on product selection, specifications, quantities, or pricing. From the perspective of process prioritization, the research serves as a concise review of main quantitative and qualitative methods, showing their demand of alignment and effect for Mass Customization. Originality/Value – The main value of the presented article can be described as a holistic theoretical focus on different types of prioritization methods and underlying points where it takes effect in Mass Customization concept. Moreover, the selected research object and findings are also valuable and applicable for organizations of different type, sector and working field

Requirements degradation for the creation of a first prototype

The requirements engineering process is typically executed, irrespective of the process model chosen, for the final commercially viable system. The system requirements generated are for a system deployed and used in its final form and function. However, the first prototype that is generated is typically representative of a minimum viable technology, and represents a degraded set of the initial system requirements specification. Typically, a first prototype is used as a technology demonstrator, and its failure or success will determine the continuation of the project, with success triggering the allocation of additional financial and personal resources. This paper explores techniques for requirements degradation that can be used to form the system requirements specification for the first prototype. A requirements Engineering methodology is proposed based upon a survey of literature. It takes into consideration the characteristics of the project, i.e. a market driven, technology implementation research project with limited budget and a flexible timeline executed in an academic environment. The techniques must take into cognizance the main risk items, and core requirements, that need to be demonstrated in the minimum viable technology to secure the future of the project. The degradation cannot undermine or jeopardize the future success of the commercially viable system in determining the subset of requirements for the minimum viable technology

Interacción de atributos al priorizar requisitos a través de objetivos

Una actividad que ejerce una fuerte influencia en la gestión de proyectos de software es establecer el orden de implementar los requisitos del software. Este ordenamiento determina la necesidad de recursos humanos y tecnológicos a lo largo del tiempo, el modo de puesta en operación parcial del software y su mantenimiento, entre otras actividades. Es uno de los motores de la evolución de los requisitos implementados y a implementar debido a realimentaciones de los usuarios al comenzar a utilizar los módulos instalados. Definir este orden es uno de los propósitos que detentan muchas técnicas de asignación de prioridades. Se ha observado que varias de estas técnicas no pueden ser aplicadas cuando se tiene un gran número de requisitos. Atendiendo a este problema, en proyectos anteriores se elaboró una propuesta para asignar prioridades utilizando los objetivos del software, de manera tal de transferir prioridades desde objetivos específicos hacia los requisitos, ya que el número de objetivos conforma un conjunto mucho menor que el de requisitos. La propuesta actual consiste en definir qué atributos deben utilizarse para establecer el orden de implementación de los requisitos.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informátic

Interacción de atributos al priorizar requisitos a través de objetivos

Una actividad que ejerce una fuerte influencia en la gestión de proyectos de software es establecer el orden de implementar los requisitos del software. Este ordenamiento determina la necesidad de recursos humanos y tecnológicos a lo largo del tiempo, el modo de puesta en operación parcial del software y su mantenimiento, entre otras actividades. Es uno de los motores de la evolución de los requisitos implementados y a implementar debido a realimentaciones de los usuarios al comenzar a utilizar los módulos instalados. Definir este orden es uno de los propósitos que detentan muchas técnicas de asignación de prioridades. Se ha observado que varias de estas técnicas no pueden ser aplicadas cuando se tiene un gran número de requisitos. Atendiendo a este problema, en proyectos anteriores se elaboró una propuesta para asignar prioridades utilizando los objetivos del software, de manera tal de transferir prioridades desde objetivos específicos hacia los requisitos, ya que el número de objetivos conforma un conjunto mucho menor que el de requisitos. La propuesta actual consiste en definir qué atributos deben utilizarse para establecer el orden de implementación de los requisitos.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informátic

Interacción de atributos al priorizar requisitos a través de objetivos

Una actividad que ejerce una fuerte influencia en la gestión de proyectos de software es establecer el orden de implementar los requisitos del software. Este ordenamiento determina la necesidad de recursos humanos y tecnológicos a lo largo del tiempo, el modo de puesta en operación parcial del software y su mantenimiento, entre otras actividades. Es uno de los motores de la evolución de los requisitos implementados y a implementar debido a realimentaciones de los usuarios al comenzar a utilizar los módulos instalados. Definir este orden es uno de los propósitos que detentan muchas técnicas de asignación de prioridades. Se ha observado que varias de estas técnicas no pueden ser aplicadas cuando se tiene un gran número de requisitos. Atendiendo a este problema, en proyectos anteriores se elaboró una propuesta para asignar prioridades utilizando los objetivos del software, de manera tal de transferir prioridades desde objetivos específicos hacia los requisitos, ya que el número de objetivos conforma un conjunto mucho menor que el de requisitos. La propuesta actual consiste en definir qué atributos deben utilizarse para establecer el orden de implementación de los requisitos.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informátic

Construcción de grafos de glosarios guiada por el estilo del discurso

La visualización de grafos es un recurso cada vez más utilizado en diferentes dominios de las ciencias de la computación. En la Ingeniería de Requisitos (IR), esta estrategia permite detectar núcleos semánticos específicos en algunos de los modelos utilizados, en forma más eficaz y eficiente que el mero estudio de los documentos. El uso concreto de grafos en glosarios del Universo del Discurso (UdeD) ha permitido detectar una influencia del estilo de la narrativa de la fuente de información, en los grafos resultantes. Aparentemente, si se ignora esa influencia, la misma se transforma en un factor perturbador que deteriora la calidad de los grafos obtenidos. En el presente proyecto se planifica aprovechar el conocimiento del estilo de la narrativa de la fuente de información, para construir grafos que permitan visualizar más eficazmente la información contenida en el glosario.Eje: Ingeniería de Software.Red de Universidades con Carreras en Informátic

Choosing a Suitable Requirement Prioritization Method: A Survey

Software requirements prioritization plays a crucial role in software development. It can be viewed as the process of ordering requirements by determining which requirements must be done first and which can be done later. Powerful requirements prioritization techniques are of paramount importance to finish the implementation on time and within budget. Many factors affect requirement prioritization such as stakeholder expectations, complexity, dependency, scalability, risk, and cost. Therefore, finding the proper order of requirements is a challenging process. Hence, different types of requirements prioritization techniques have been developed to support this task. In this survey, we propose a novel classification that can classify the prioritization techniques under two major classes: relative and exact prioritization techniques class, where each class is divided into two subclasses. We depend in our classification on the way the value of ranking is given to the requirement, either explicitly as a specific value in the case of the exact prioritization techniques class, or implicitly in the case of the Relative prioritization technique class. An overview of fifteen different requirements prioritization techniques are presented and organized according to the proposed classification criteria's. Moreover, we make a comparison between methods that are related to the same subclass to analyze their strengths and weaknesses. Based on the comparison results, the properties for each proposed subclass of techniques are identified. Depending on these properties, we present some recommendations to help project managers in the process of selecting the most suitable technique to prioritize requirements based on their project characteristics (number of requirements, time, cost, and accuracy)

Investigation of Requirements Interdependencies in Existing Techniques of Requirements Prioritization

Requirements prioritization (RP) is considered as a key role in producing a successful system by selecting the most important requirements to be released. Requirements interdependencies (RI) is one of the crucial aspects that need to be addressed in RP, since most of the requirements in reality are not independent and have dependencies between each other. Thus, ignoring RI in RP process may lead to produce inaccurate prioritization result which directly impacts the system’s success. In spite of this, little is known about the impact of RI, and obviously further research is urgently required to measure the RI in the RP techniques. Hence, this study aims to investigate and analyze the existence and the execution steps of handling RI in the existing RP techniques to improve the performance of techniques in generating accurate result and assist the researchers and practitioners to select the appropriate technique that can handle RI in prioritization process. The findings indicate that, out of 65 techniques, there are only 4 techniques that handle the RI. The result reveals that these four techniques still suffer from issues of manual process and heavily rely on the experts’ participation. Proposing a new technique is recommended to overcome the identified limitations