The Need to Evaluate Strategy and Tactics before the Software Development Process Begins

Samir Kherraf, Laila Cheikhi, Alain Abran, Witold Suryn, Eric Lefebvre
DOI: 10.4236/jsea.2010.37074                

Abstract

Experience has shown that poor strategy or bad tactics adopted when planning a software project influence the final quality of that product, even when the whole development process is undertaken with a quality approach. This paper addresses the quality attributes of the strategy and tactics of the software project plan that should be in place in order to deliver a good software product. It presents an initial work in which a set of required quality attributes is identified to evaluate the quality of the strategy and tactics of the software project plan, based on the Business Motivation Model (BMM) and the quality attributes available in the ISO 9126 standard on software product quality.

Keywords

Business Motivation Model, Quality of Strategy, Quality of Tactic, ISO 9126, Software Product Quality

Conflicts of Interest

The authors declare no conflicts of interest.

References

[1]	Object Management Group, “Business Motivation Model Specification,” September 2007.
[2]	ISO/IEC, “IS 9126-1, Software Engineering—Product Quality—Part 1: Quality Model,” International Organization for Standardization, Geneva, 2001.
[3]	M. de Certeau, “The Practice of Everyday Life,’’ University of California Press, 2002.
[4]	J. Hall, “Tactics, Strategies, and Quality Words,” Business Rule Journal, 2005.
[5]	ISO/IEC, “TR 9126-2, Software Engineering—Product Quality—Part 2: External Metrics,” International Organization for Standardization, Geneva, 2003.
[6]	ISO/IEC, “TR 9126-3, Software Engineering—Product Quality—Part 3: Internal Metrics,” International Organization for Standardization, Geneva, 2003.
[7]	ISO/IEC, “TR 9126-4, Software Engineering—Product Quality—Part 4: Quality in Use Metrics,” International Organization for Standardization, Geneva, 2004.
[8]	B. W. Boehm, J. R. Brown and M. Lipow, “Quantitative Evaluation of Software Quality,” Proceedings of the 2nd International Conference on Software Engineering, IEEE Computer Society, Los Alamitos (CA), 1976, pp. 592- 605.
[9]	R. G. Dromey, “Concerning the Chimera [Software Quality],” IEEE Software, Vol. 13, No. 1, 1996, pp. 33-43.
[10]	J. A. McCall, P. K. Richards and G. F. Walter, “Factors in Software Quality,” US Rome Air Development Center Reports, US Department of Commerce, Vol. 1-3, 1977.
[11]	R. Fitzpatrick, “Strategic Drivers of Software Quality: Beyond External and Internal Software Quality,” 2nd Asia-Pacific Conference on Quality Software, IEEE Computer Society, 2001.
[12]	A. Wright, “Quality’s Strategic Failure: A Review of the Key Literature,” Occasional Paper Series 2003, University of Wolverhampton, 2003.
[13]	Baldrige National Quality Program, Criteria for Performance Excellence, B.N.Q. Program, Editor, 2009-2010.
[14]	European Foundation for Quality Management, The EFQM Excellence Model 2010, EFQM, 2010.
[15]	W. Suryn, A. Abran and C. Laporte, “An Integrated Life Cycle Quality Model for General Public Market Software Products,” Software Quality Management XII Conference, British Computer Society, 2004.