Inicio Nosotros Búsquedas
Buscar en nuestra Base de Datos:     
Palabras claves o descriptores: EMPIRICAL STUDIES (Comienzo)
2 registros cumplieron la condición especificada en la base de información BIBCYT. ()
Registro 1 de 2, Base de información BIBCYT
Publicación seriada
Referencias AnalíticasReferencias Analíticas
Autor: Conradi, Reidar ; Fuggetta, Alfonso
Título: Improving Software Process Improvement
Páginas/Colación: pp. 92-99
Url: Ir a http://doi.ieeecomputersociety.org/10.1109/MS.2002.1020295http://doi.ieeecomputersociety.org/10.1109/MS.2002.1020295
IEEE Software Vol. 19, no. 4 Jul./Aug. 2002
Información de existenciaInformación de existencia

Palabras Claves: Palabras: EMPIRICAL STUDIES EMPIRICAL STUDIES, Palabras: ORGANIZATIONAL BEHAVIOR ORGANIZATIONAL BEHAVIOR, Palabras: PROCESS IMPROVEMENT PROCESS IMPROVEMENT, Palabras: SOFTWARE PROCESS SOFTWARE PROCESS, Palabras: STANDARDS STANDARDS

Resumen
RESUMEN

RESUMEN

 

Several issues and problems exist for software process improvement application. According to the authors' experiences, two dichotomies characterize software process improvement efforts and approaches: disciplined vs. creative work and procurer risks vs. user satisfaction. Based on these perspectives, the authors introduce six theses to illuminate the problems of pursuing software process improvement and discuss possible remedies. Approaches to software process improvement must be substantially extended to take into account organizational, economic, and strategic issues. Researchers must also perform systematic empirical studies around such technologies, by combining methods from software engineering and social sciences, for example.

 

Registro 2 de 2, Base de información BIBCYT
Publicación seriada
Referencias AnalíticasReferencias Analíticas
Autor: Runeson, Per per.runeson@telecom.lth.se
Oprima aquí para enviar un correo electrónico a esta dirección ; Andersson, Carina carina.andersson@telecom.lth.se
Oprima aquí para enviar un correo electrónico a esta dirección; Thelin, Thomas thomas.thelin@telecom.lth.se
Oprima aquí para enviar un correo electrónico a esta dirección; Andrews, Anneliese andrews@cs.du.edu
Oprima aquí para enviar un correo electrónico a esta dirección; Berling, Tomas tomas.berling@ericsson.com
Oprima aquí para enviar un correo electrónico a esta dirección
Título: What Do We Know about Defect Detection Methods?
Páginas/Colación: pp. 82-89
Url: Ir a http://doi.ieeecomputersociety.org/10.1109/MS.2006.89http://doi.ieeecomputersociety.org/10.1109/MS.2006.89
IEEE Software Vol. 23, no. 3 May/June 2006
Información de existenciaInformación de existencia

Palabras Claves: Palabras: DEFECT DETECTION DEFECT DETECTION, Palabras: EMPIRICAL STUDIES EMPIRICAL STUDIES, Palabras: EVIDENCE-BASED SOFTWARE ENGINEERING EVIDENCE-BASED SOFTWARE ENGINEERING, Palabras: INSPECTION INSPECTION, Palabras: TESTING TESTING

Resumen
RESUMEN

RESUMEN

 

Serious efforts are spent on defect detection during software development. So, it's important to use the most efficient and effective defect detection methods. This guide can help practitioners choose efficient and effective defect detection methods using the evidence-based software engineering (EBSE) approach. Using 12 empirical studies, including 10 experiments and two case studies, the authors compare inspection and testing techniques and then derive practical implications. While research results are often inconclusive, the authors recommend that practitioners generally use inspections for requirements and design, and testing for code. Also, because different defect detection methods find different types of defects, the methods might be complementary. Finally, they list factors that help frame the question and guide practitioners in further steps to integrate and evaluate the detection methods in their environments.

 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

UCLA - Biblioteca de Ciencias y Tecnologia Felix Morales Bueno

Generados por el servidor 'bibcyt.ucla.edu.ve' (3.144.199.59)
Adaptive Server Anywhere (07.00.0000)
ODBC
Sesión="" Sesión anterior=""
ejecutando Back-end Alejandría BE 7.0.7b0 ** * *
3.144.199.59 (NTM) bajo el ambiente Apache/2.2.4 (Win32) PHP/5.2.2.
usando una conexión ODBC (RowCount) al manejador de bases de datos..
Versión de la base de información BIBCYT: 7.0.0 (con listas invertidas [2.0])

Cliente: 3.144.199.59
Salida con Javascript


** Back-end Alejandría BE 7.0.7b0 *