Software Requirements Quality: Using Analytics to Challenge Assumptions at Intel

IEEE Software ◽  
2020 ◽  
pp. 0-0
Author(s):  
Anastasia Griva ◽  
Stephen Byrne ◽  
Denis Dennehy ◽  
Kieran Conboy
Keyword(s):  
Software Requirements ◽  
Requirements Quality

scholarly journals Challenges of Software Requirements Quality Assurance and Validation: A Systematic Literature Review

IEEE Access ◽  
2021 ◽  
Vol 9 ◽  
pp. 137613-137634
Author(s):  
Issa Atoum ◽  
Mahmoud Khalid Baklizi ◽  
Izzat Alsmadi ◽  
Ahmed Ali Otoom ◽  
Taha Alhersh ◽  
...  
Keyword(s):  
Quality Assurance ◽  
Literature Review ◽  
Systematic Literature Review ◽  
Software Requirements ◽  
Requirements Quality

scholarly journals Quality Assurance Techniques in SRS Documents

2019 ◽  
Vol 9 (2S) ◽  
pp. 14-18
Keyword(s):  
Quality Assurance ◽  
Natural Language ◽  
Software Requirements ◽  
Test Case ◽  
Software Development Process ◽  
Language Analysis ◽  
Requirements Quality ◽  
Requirements Documents ◽  
Experimental Stage ◽  
Foundation Stone

For development of software, the most important aspects are the software requirements. They are the foundation stone for initiating any software development process. Software requirements documents contain the needs of the customers in natural language. By using various methods like reviews, inspections, walkthroughs, the content of the software requirement can be checked manually to reduce ambiguity. In recent years there is an attempt to automate these activities as a result of advancement in automation of natural language analysis. Automation of text mining techniques and text analysis is leading to feasibility of automation of requirements documents processing. The process can be completed in minutes now which were taking weeks earlier. Automation of analysis of text has triggered numerous possibilities for quality assurance of requirements. The possibilities of automation are model checking automation, automated rule checking, automated test case execution and measurement automation. In future more tools will enter the scene for automation of requirements quality assurance. At present most of them are in experimental stage. There is a definite need for more research in this field.

Completeness Concerns in Requirements Engineering

2011 ◽  
pp. 619-624 ◽  
Author(s):  
Jorge H. Doorn ◽  
Marcela Ridao
Keyword(s):  
Requirements Engineering ◽  
Software Requirements ◽  
Modeling And Analysis ◽  
Domain Experts ◽  
Requirements Definition ◽  
Elicitation Process ◽  
Software Artifact ◽  
Requirements Quality ◽  
Closed Populations ◽  
Future Work

The difficulties that software developers must face to understand and elicit clients’ and users’ necessities are widely known. The more complex the context of the problem, the more difficult the elicitation of software requirements becomes. Many times, requirements engineers must become themselves problem-domain experts during the acquisition of knowledge about the context of the application. The requirements engineering (RE) objective is to systematize the process of requirements definition (Maculay, 1993; Maté & Silva, 2005; Reubenstein & Waters, 1991) along with creating a compromise among clients and users with developers since they must both participate and collaborate together. The requirements engineering process consists of three main activities: elicitation, modeling, and analysis of the application domain (Kotonya & Sommerville, 1998; Sommerville & Sawyer, 1997). Later, requirements management deals with the changes in the requirements and the irruption of new ones. RE provides methods, techniques, and tools to help requirements engineers elicit and specify requirements, ensuring their highest quality and completeness. However, the problem of completeness is a certain menace to requirements quality and casts a serious doubt on the whole RE process. Completeness is an unreachable goal, and to estimate the degree of completeness obtained at a certain step in the project is even more difficult. The requirements engineer faces a universe of discourse (UofD) that he or she will hardly ever fully know. This situation is not unique during the whole software development process since something similar happens while testing. The use of statistical models to predict the number of defects in a software artifact was successfully introduced some time ago (Petersson, Thelin, Runeson, & Wohlin, 2003). In this article, the use of capture and recapture information is applied in the RE field in order to make an estimation of the number of undiscovered requirements after a requirements elicitation process. The following section analyses the validation problem in RE. Then, a section describing the use of LEL (languageextended lexicon) and scenarios in requirements engineering is included. After that, the problem of estimating closed populations is studied. Later, the use of capture and recapture in the RE domain is introduced, and finally, some future work and conclusions are presented.

Gestión de riesgos empresariales: los necesarios cambios

Oikos ◽  
2016 ◽  
Vol 19 (39) ◽  
pp. 93 ◽  
Author(s):  
Ricardo Vega Bois
Keyword(s):  
Risk Management ◽  
Quality Management ◽  
Management System ◽  
Quality Management System ◽  
Iso 9000 ◽  
Management Control ◽  
System Requirements ◽  
Requirements Quality ◽  
Management Recommendations ◽  
Environmental Audits

RESUMENLa normas de la serie ISO 9000 – 2000, Sistema de Gestión de Calidad, Requisitos de un Sistema de Gestión de Calidad, Recomendaciones para la mejora de desempeño en base a un Sistema de Gestión de calidad y Directrices para la realización de auditorías medioambientales y de calidad, han sido base para la evaluación, implementación, aplicación y seguimiento de sistemas de Control de Gestión Empresarial, estando en la actualidad (2015) en un procesos de revisión y propuesta, lo que implicará algunos cambios de forma y otros de fondo interesantes de considerar.Palabras clave: gestión, riesgos, control de gestión, calidad, normas internacionales.Enterprise risk management: the necessary changesABSTRACTThe standards ISO 9000 - 2000 Quality Management System, System Requirements Quality Management Recommendations for improving performance based on a Quality Management System and Guidelines for conducting environmental audits and quality have been the basis for evaluation, implementation, enforcement and monitoring systems Control Management, being at present (2015) in a review and proposal processes, which involve some changes in form and other interesting background consider.Keywords: management, risk, management control, quality international standards.Gestão de riscos empresariais: as mudanças necessárias RESUMO As normas da série ISO 9000-2000, Sistema de Gestão da Qualidade, Requisitos de um Sistema de Gestão de Qualidade, Recomendações para a melhora do desempenho com base a um Sistema de Gestão da Qualidade e Diretrizes para a realização de auditorias meio ambientais e de qualidade, têm sido a base para a avaliação, implementação, aplicação e fiscalização de Sistemas de Controle de Gestão Empresarial, sendo na atualidade (2015) num processo de revisão e proposta, que implicará algumas mudanças na forma e outros de fundo interessante de considerar.Palavras-chave: gestão, risco, controle de gestão, qualidade, normas internacionais.

Sign in / Sign up

Export Citation Format

Share Document