Consequences and Characteristics of a Quality Software Development Process and Aspects that Influence It: An Expert Assessment

• Jeann M. Andrade UFRJ
• Adriano B. Albuquerque UFRJ
• Fábio B. Campos UFRJ
• Ana Regina C. Rocha UFRJ

DOI: https://doi.org/10.5753/sbqs.2004.16183

Abstract

The systematization of software development through the use of software engineering processes has the power to bring many benefits to software development organizations, however, characterizing objectively, what is an effective and efficient process is not a simple task. This characterization is important in many times: in the definition of an adequate process to the organization and its projects; in the deployment of this process; in the monitoring of its results and in its improvement. To initiate this characterization, a survey was conducted, presenting three distinct groups of questions related to software processes, that aimed to answer the following questions: What benefits the use of a software engineering process can bring? Which are the main characteristics that an effective process must have?, and, finally, Which organizational, human and technician aspects can influence the effectiveness of the processes. The consolidated results of the research are presented, allowing a preliminary analysis of which aspects would be more relevant to be considered in the definition, utilization and improvement of processes.

Keywords: Software Process, Process Improvement, Decision making, Software Quality

References

REED, K., 2000, Software engineering – a new millenium?, IEEE Software, July-August.

MCT/SEPIN – Secretaria de Política de Informática e Automação / Ministério da Ciência e Tecnologia, 2002, Qualidade e Produtividade no Setor de Software Brasileiro – 2001 / n.4., Brasília.

PAULK, M. C., CURTISS, B., CHRISSIS, M. B., WEBER, C. V., 1993, Capability Maturity Model for Software, Version 1.1, Pittsburgh, Software Engineering Institute.

ZAHRAN, S., 1997, Software Process Improvement – Practical Guidelines for Business Success; Addison-Wesley.

ISO/IEC 12207, 1995, ISO/IEC 12207. Information technology – software life cycle, International Standard Organization.

ISO 9000, 2000, Quality Management Systems – Fundamental and Vocabulary.

FARIAS, L. L., 2002, Planejamento de Riscos em Ambientes de Desenvolvimento de Software Orientados à Organização, Tese de M.SC., COPPE/UFRJ, Rio de Janeiro, Brasil.

NOGUEIRA, M. O., ROCHA, A. R., 2003, Práticas Relevantes em Engenharia de Software: uma avaliação de especialistas, II Simpósio Brasileiro de Qualidade de Software, Fortaleza, CE, Brasil.

FLORAC, W., CARLETON, A. E., 2000, Measuring the Software Process: Statistical Process Control for Software Process Improvement, Addison-Wesley.

PFLEEGER, S. L., 2000, Improving Predictions, Products, Processes and Resources, In: Software Engineering, cap.13, pp. 563-592.

GRUHN, V., 2000, Software Process Landscaping, Software Process: Improvement an Practice, 5:111-120.

EMAM, K. E., 2001, Software Engineering Process, in IEEE - Trial Version.

OLIVEIRA, K. M., 1999, Modelo para Construção de Ambientes de Desenvolvimento de Software Orientados a Domínio, Tese de D.SC., COPPE/UFRJ, Rio de Janeiro, RJ, Brasil.

LEUNG, H. K. N., YUEN, T. C. F., 2001, A Process Framework for Small Projects, Software Process: Improvement an Practice, 6:67-83.

HEFNER, R., TAUSER, J., 2001, Things They Never Taught You in CMM School, 26th Annual NASA Goddard Software Engineering Workshop, November, pp. 27-29.

MESSNARZ, R., 1999, Road map for Readers and How to Use the Book, In: Richard Messnarz and Colin Tully (eds.), Better Software Practice for Business Benefit: Principles and Experience, IEEE Computer Society, cap1, pp.1-13.

KALTIO, T., KINNULA, A., 2000, Deployng the Defined SW Process, Software Process: Improvement and Practice, 5:65-83.

CATTANEO, F., FUGGETA, A., SCIUTO, D., 2001, Pursuing Coherence in Software Process Assessment and Improvement, Software Process: Improvement and Practice, 6:3-22.