A User Story Quality Measurement Model for Reducing Agile Software Development Risk

In Mobile communications age, the IT environment and IT technology update rapidly. The requirements change is the software project must face challenge. Able to overcome the impact of requirements change, software development risks can be effectively reduced. Agile software development uses the Iterative and Incremental Development (IID) process and focuses on the workable software and client communication. Agile software development is a very suitable development method for handling the requirements change in software development process. In agile development, user stories are the important documents for the client communication and criteria of acceptance test. However, the agile development doesn’t pay attention to the formal requirements analysis and artifacts tracability to cause the potential risks of software change management. In this paper, analyzing and collecting the critical quality factors of user stories, and proposes the User Story Quality Measurement (USQM) model. Applied USQM model, the requirements quality of agile development can be enhanced and risks of requirement changes can be reduced.

[1]  Victor R. Basili,et al.  Iterative and incremental developments. a brief history , 2003, Computer.

[2]  Ivar Jacobson,et al.  Aspect-oriented software development with use cases , 2005, Addison Wesley object technology series.

[3]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach (McGraw-Hill Series in Computer Science) , 2004 .

[4]  H. E. Dunsmore,et al.  Software engineering metrics and models , 1986 .

[5]  Anas N. Al-Rabadi,et al.  A comparison of modified reconstructability analysis and Ashenhurst‐Curtis decomposition of Boolean functions , 2004 .

[6]  Ivar Jacobson,et al.  Aspect-Oriented Software Development with Use Cases (Addison-Wesley Object Technology Series) , 2004 .

[7]  David Frankel,et al.  Model Driven Architecture: Applying MDA to Enterprise Computing , 2003 .

[8]  Mike Cohn,et al.  Introducing an Agile Process to an Organization , 2003, Computer.

[9]  Mike Cohn,et al.  User Stories Applied: For Agile Software Development , 2004 .

[10]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[11]  Daniel Galin,et al.  Software Quality Assurance: From Theory to Implementation , 2003 .

[12]  Chris Verhoef,et al.  The rise and fall of the Chaos report figures , 2010, IEEE Software.

[13]  Robert S. Arnold,et al.  Software Change Impact Analysis , 1996 .

[14]  Stephen R. Schach.  Object-Oriented Software Engineering , 2007 .

[15]  Norman E. Fenton,et al.  Software Metrics: A Rigorous Approach , 1991 .

[16]  Ralph R. Young.  Effective Requirements Practices , 2001 .

[17]  B. Boehm.  Software risk management: principles and practices , 1991, IEEE Software.

[18]  Richard E. Fairley,et al.  Risk management for software projects , 1994, IEEE Software.

[19]  Craig Larman,et al.  Agile and Iterative Development: A Manager's Guide , 2003 .

[20]  Victor Szalvay.  An Introduction to Agile Software Development By : Victor Szalvay , 2010 .

[21]  S.A. Bohner,et al.  Software change impacts-an evolving perspective , 2002, International Conference on Software Maintenance, 2002. Proceedings..