Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to main content

Advertisement

Springer Nature Link
Log in

Testing the predictive ability of a requirements pattern language

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

    We’re sorry, something doesn't seem to be working properly.

    Please try refreshing the page. If that doesn't work, please contact support so we can address the problem.

Abstract

This paper looks at a case study in the commercial procurement of an IT system to support learners on short educational courses. It compares the use case model created before the system was built with the use case model after the system was delivered. The original use case model was created through the application of a requirements pattern language designed to be employed during the procurement phase of an IT system. The final use case model was reverse engineered from the working application. The objective was to discover how accurately the original model represented the final application to provide a measure of the potential usefulness of the pattern language during procurement.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10
Fig. 11

Similar content being viewed by others

References

  1. Fowler M, Scott K (1999) UML distilled: a brief guide to the standard object modeling language. Addison-Wesley Longman, Upper Saddle River, NJ

    Google Scholar 

  2. Jacobson I, Jonsson P, Christerson M, Overgaard G (1992) Object-oriented software engineering: a use case driven approach. Addison-Wesley Longman, Upper Saddle River, NJ

  3. Kulak D, Guiney E (2000) Use cases: requirements in context. Addison-Wesley Longman, Upper Saddle River, NJ

    Google Scholar 

  4. Fantechi A, Gnesi S, Lami G, Maccari A (2003) Applications of linguistic techniques for use case analysis. Requirements Eng 8(3):161–170

    Article  Google Scholar 

  5. Pooley R, Stevens P (1999) Using UML: software engineering with objects and components. In: Booch GJ, Rumbaugh J (eds) Object technology series. Addison-Wesley Longman, Harlow

  6. Cockburn A (2001) Writing effective use cases. Addison-Wesley Longman, Upper Saddle River, NJ

  7. Fenton N, Pfleeger SL (1996) Software metrics: a rigorous & practical approach. Thomson Computer Press, London

    Google Scholar 

  8. Zave P (1997) Classification of research efforts in requirements engineering. ACM Comput Surv 29(4):315–321

    Article  Google Scholar 

  9. Spivey JM (1989) The Z notation: a reference manual. Prentice-Hall, Upper Saddle River, NJ

    Google Scholar 

  10. Dardenne A, van Lamsweerde A, Fickas S (1993) Goal-directed requirements acquisition. Sci Comput Programming 20(1–2):3–50

    Google Scholar 

  11. Khazaei B, Roast C (2003) The influence of formal representation on solution specification. Requirements Eng 8(1):69–77

    Article  Google Scholar 

  12. van Lamsweerde A (2000) Formal specification: a roadmap. In: Finkelstein A (ed) The future of software engineering, ACM Press, New York

  13. Regnell B, Andersson M, Bergstrand J (1996) A hierarchical use case model with graphical representation. In: Proceedings of the IEEE international symposium and workshop on engineering of computer-based systems. IEEE Computer Society, Friedrichshafen, Germany

  14. Various (2003) OMG unified modeling language specification, vol 1.5. Object Management Group

  15. Alexander I, Farncombe A, Mohammed S (2002) Towards better railway system specifications through scenarios. In: The railway technology conference (RailTex), Birmingham. http://easyweb.easynet.co.uk/ iany/consultancy/railway_scenarios/railway_scenarios.htm

  16. Adolph S, Bramble P, Cockburn A, Pols A (2002) Patterns for effective use cases. In: Agile software development. Addison-Wesley Longman, Upper Saddle River, NJ

  17. Biddle R, Noble J, Tempero E (2001) Patterns for essential use cases. In: KoalaPLoP, Melbourne

  18. Biddle R, Noble J, Tempero E (2002) Essential use cases and responsibility in object-oriented development. In: Proceedings of the Twenty-fifth Australasian Computer Science Conference (ACSC2002). Australian Computer Society Inc., Monash University, Melbourne. http://crpit.com/Vol4.html

  19. Mylopoulos J, Chung L, Nixon B (1992) Representing and using nonfunctional requirements: a process-oriented approach. IEEE Trans Software Eng 18(6):483–497

    Article  Google Scholar 

  20. Beck K, Cunningham W (1987) Using pattern languages for object-oriented programs. In: Proceedings of the Object-oriented Programming, Systems, Languages, and Applications Conference (OOPSLA87). ACM Press, Orlando, FL

  21. Gamma E, Helm R, Johnson R, Vlissides J (1995) Design patterns: elements of reusable object-oriented software. Addison-Wesley Longman, Upper Saddle River, NJ

    Google Scholar 

  22. Gzara L, Rieu D, Tollenaere M (2000) Patterns approach to product information systems engineering. Requirements Eng 5:157–179

    Google Scholar 

  23. de Farias G, Ferreira C, van Sinderen P (2000) A component-based groupware development methodology. In: Proceedings of the 4th International Enterprise Distributed Object Computing Conference, Makuhari. http://citeseer.nj.nec.com/302797.html

  24. Merrick P, Barrow P (2003) Towards a requirements formalism in procurement. In: Proceedings ot the 8th annual Conference of the United Kingdom Academy of Information Systems, Warwick, England, June 2003

  25. Abbott RJ (1983) Program design by informal English descriptions. Commun ACM 26:882–894

    Article  Google Scholar 

  26. Connolly T, Strachan A, Begg C (1995) Database systems: a practical approach to design, implementation and management. Addison-Wesley Longman, Harlow

    Google Scholar 

  27. Staff writers (2002) Value for money evaluation in complex procurements. Office of government commerce (OGC), Norwich, UK

  28. Staff_writers (2003) The green book: appraisal and evaluation in central government. HM Treasury, London, The Stationary Office. http://www.ogc.gov.uk/sdtoolkit/reference/ogc_library/related/Green_Book_03. pdf

  29. Kruchten P (2000) The rational unified process: an introduction. Addison-Wesley Longman, Upper Saddle River, NJ

    Google Scholar 

  30. Taylor A (2001) IT projects sink or swim. Comput Bull 42(1):24–26

    Google Scholar 

  31. Anda B, D. H, S. D, J. M (2001) Estimating software development effort based on use cases: experiences from industry. In: 4th international conference on the unified modeling language. Springer, Toronto. http://www.idi.ntnu.no/emner/sif8080/docs/faglig/uml2001-anda.pdf

  32. Anda B, Angelvik E, Ribu K (2002) Improving estimation practices by applying use case models. In: Proceedings of the 4th International Conference on Product Focused Software Process Improvement, Rovaniemi, December 2002, LNCS, vol 2559, Springer, Berlin Heidelberg, New York http://www.simula.no/publication_one.php?publication_id=500

  33. Anda B (2003) Empirical studies of construction and application of use case models. University of Oslo, Norway

  34. Ribu K (2001) Estimating object-oriented software projects with use cases. Master’s thesis, University of Oslo. http://www.stud.ifi.uio.no/ kribu/oppgave.pdf

  35. Boehm B, Horowitz E (2000) Software cost estimation with COCOMO II. Pearson Education

  36. Albrecht AJ (1979) Measuring application development productivity. In: IBM applications development symposium, Monterey, CA

  37. Kitchenham B (1991) Estimation. In: Fenton N (ed) Software metrics: rigourous and practical approach. Chapman and Hall, London, p 132

  38. Berry DM (1998) Software and house requriements engineering: lessons learned in combating requirements creep. Requirements Eng 3:242–244

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

  1. School of Computer Science, Universtiy of East Anglia, NR4 7TJ, Norwich, UK

    Peter Merrick & Patrick Barrow

Authors
  1. Peter Merrick
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Patrick Barrow
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Peter Merrick.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Merrick, P., Barrow, P. Testing the predictive ability of a requirements pattern language. Requirements Eng 10, 85–94 (2005). https://doi.org/10.1007/s00766-004-0193-5

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-004-0193-5

Keywords

Search

Navigation