Evaluating the Applicability of a Use Case Precedence Diagram Based Approach in Software Development Projects through a Controlled Experiment

  • José Antonio Pow-Sang
  • Arturo Nakasone
  • Ana María Moreno
  • Ricardo Imbert
Part of the Communications in Computer and Information Science book series (CCIS, volume 29)


Use Cases are the most utilized technique to specify software requirements. Currently, there are several proposals based on this technique to address the problem of determining the scope and construction sequence of a software, but most of them lack ease of use from the developer’s perspective. In this paper, we present an approach to determine software construction sequences which emphasizes easiness from the developers’ point of view and a controlled experiment based on this approach with professionals who have had at least two years of experience in software projects. The results obtained from this experiment show that our approach enables developers to define construction sequences more precisely than with other ad-hoc techniques.


use case requirements precedence software engineering experimentation 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Basili, V.R., Caldiera, G., Rombach, H.D.: Goal Question Metric Paradigm. In: Marciniak, J.J. (ed.) Encyclopedia of Software Engineering. Wiley, Chichester (1994)Google Scholar
  2. 2.
    Carver, J., Jaccheri, L., Morasca, S.: Issues in Using Students in Empirical Studies in Software Engineering Education. In: METRICS 2003, p. 239. IEEE Computer Society, Los Alamitos (2003)Google Scholar
  3. 3.
    Denne, M., Cleland-Huang, J.: The Incremental Funding Method: Data-Driven Software Development. IEEE Software 21(1) (2004)Google Scholar
  4. 4.
    Du, G., McElroy, J., Ruhe, G.: Ad Hoc Versus Systematic Planning of Software Releases - A Three-Staged Experiment. In: Münch, J., Vierimaa, M. (eds.) PROFES 2006. LNCS, vol. 4034, pp. 435–440. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  5. 5.
    Du, G., McElroy, J., Ruhe, G.: A family of empirical studies to compare informal and optimization-based planning of software releases. In: ISESE 2006, pp. 212–221. IEEE Computer Society, Los Alamitos (2006)CrossRefGoogle Scholar
  6. 6.
    Firesmith, D.: Prioritizing Requirements. Journal of Object Technology 3(8) (2004),
  7. 7.
    Jacobson, I.: Object-Oriented Software Engineering. In: A Use Case Driven Approach. Addison-Wesley, Reading (1992)Google Scholar
  8. 8.
    Juristo, N., Moreno, A.M.: Basics of Software Engineering Experimentation. Kluwer Academic Publishers, Boston (2001)zbMATHGoogle Scholar
  9. 9.
    Kundu, D., Samanta, D.: A Novel Approach of Prioritizing Use Case Scenarios. In: APSEC 2007, pp. 542–549. IEEE Computer Society, Los Alamitos (2007)Google Scholar
  10. 10.
    Moisiadis, F.: Prioritizing Scenario Evolution. In: ICRE 2000, pp. 85–94. IEEE Computer Society, Los Alamitos (2000)Google Scholar
  11. 11.
    Moisiadis, F.: Prioritising Use Cases and Scenarios. In: TOOLS’37-2000, pp. 108–119. IEEE Computer Society, Los Alamitos (2000)Google Scholar
  12. 12.
    Ngo-The, A., Ruhe, G.: A systematic approach for solving the wicked problem of software release planning. In: Soft Computing, vol. 12, pp. 95–108. Springer, Heidelberg (2008)Google Scholar
  13. 13.
    Object Management Group, OMG Unified Modeling Language USA (2008),
  14. 14.
    Pow-Sang, J.A., Jolay-Vasquez, E.: An Approach of a Technique for Effort Estimation of Iterations in Software Projects. In: APSEC 2006, pp. 367–376. IEEE Computer Society, Los Alamitos (2006)Google Scholar
  15. 15.
    Rational Software, Rational Unified Process version 2001A.04.00.13, USA (2001)Google Scholar
  16. 16.
    Rosenberg, D., Scott, K.: Use Case Driven Object Modeling with UML. Addison-Wesley, Massachusets (1999)Google Scholar
  17. 17.
    Ruhe, G., Omolade, M.: The Art and Science of Software Release Planning. IEEE Software 22(1), 47–53 (2005)CrossRefGoogle Scholar
  18. 18.
    Ryser, J., Glinz, M.: Using Dependency Charts to Improve Scenario-Based Testing. In: 17th International Conference on Testing Computer Software TCS 2000, Washington D.C., USA (2000)Google Scholar
  19. 19.
    Software Engineering Institute (SEI), Capability Maturity Model® Integration,
  20. 20.
    Some, S.: Specifying Use Case Sequencing Constraints using Description Elements. In: Sixth International Workshop on Scenarios and State Machines (SCESM 2007), vol. 4. IEEE Computer Society, Los Alamitos (2007)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • José Antonio Pow-Sang
    • 1
    • 3
  • Arturo Nakasone
    • 2
  • Ana María Moreno
    • 3
  • Ricardo Imbert
    • 3
  1. 1.Departamento de IngenieríaPontificia Universidad Católica del PerúLima 32Peru
  2. 2.National Institute of InformaticsTokyoJapan
  3. 3.Facultad de InformáticaUniversidad Politécnica de Madrid(Madrid)Spain

Personalised recommendations