How natural is natural language?: how well do computer science students write use cases?

ABSTRACT

Use cases are one of the most common mechanisms for describing and analyzing software system requirements. Due to use of natural language in use case descriptions, it is often assumed that they are easy to understand for stakeholders involved in the software development process [8]. However some authors argue [17,18] that the most common pitfalls of use cases written by professionals is that the customer does not understand them. In this paper we would like to consider whether it is appropriate to take their understandability to non-technically minded stakeholders for granted.We have analyzed 88 use cases written by final-year undergraduate computer science students for an assignment at the University of Hertfordshire and point out ways in which a computing-based mindset or way of thinking infiltrates the use cases, possibly making them difficult to understand for non-technical partners and hindering or pre-empting design decisions. We suggest that the problems we observed among students indicate a need for adding a new rule and/or guideline when teaching students to write good quality use cases, which is to ensure as far as possible that their use cases are free from computing-based structures and vocabulary. We also suggest ways in which students studying technical aspects of computer science might be led into practicing the use of non-technical language.

REFERENCES

• 1: Scott W. Ambler, Lessons in Agility From Internet-Based Development, IEEE Software, v.19 n.2, p.66-73, March 2002 [doi>10.1109/52.991334]
• 2: Sarah Beecham , Tracy Hall , Carol Britton , Michaela Cottee , Austen Rainer, Using an expert panel to validate a requirements process improvement model, Journal of Systems and Software, v.76 n.3, p.251-275, June 2005 [doi>10.1016/j.jss.2004.06.004]
• 3: Camille Ben Achour , Colette Rolland , Carine Souveyet , Neil A. Maiden, Guiding Use Case Authoring: Results of an Empirical Study, Proceedings of the 4th IEEE International Symposium on Requirements Engineering, p.36-43, June 07-11, 1999
• 4: Booch, G., Jacobson, I., and Rumbaugh, J. UML Distilled, Second Edition, Addison-Wesley, 2002.
• 5: Alistair Cockburn, Writing Effective Use Cases, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 6: Mark Collins-Cope, The Requirements/Service/Interface (RSI) Approach to Use Case Analysis, Proceedings of the Technology of Object-Oriented Languages and Systems, p.172, June 07-10, 1999
• 7: Larry L. Constantine , Lucy A. D. Lockwood, Software for use: a practical guide to the models and methods of usage-centered design, ACM Press/Addison-Wesley Publishing Co., New York, NY, 1999
• 8: Cox, K., Aurum, A., and Jeffrey, R. An Experiment in Inspecting the Quality of Use Case Descriptions, Journal of Research and Practice in Information Technology, 36, 4, 2004, 211--229.
• 9: Karl Cox , Keith Phalp, Replicating the CREWS Use Case Authoring Guidelines Experiment, Empirical Software Engineering, v.5 n.3, p.245-267, November 2000 [doi>10.1023/A:1026542700033]
• 10: Cox, K., Phalp, K., and Shepperd, M. Comparing Use Case Writing Guidelines, Proc. 7th International Workshop on Requirements Engineering, (Interlaken, Switzerland, 2001). 2001, 101--112.
• 11: Alessandro Fantechi , Stefania Gnesi , G. Lami , A. Maccari, Application of Linguistic Techniques for Use Case Analysis, Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering, p.157-164, September 09-13, 2002
• 12: Holsti, O. R. Content Analysis, Addison-Wesley, 1969.
• 13: Hoh In , David Olson , Tom Rodgers, A Requirements Negotiation Model Based on Multi-Criteria Analysis, Proceedings of the 5th IEEE International Symposium on Requirements Engineering, p.312-313, August 27-31, 2001
• 14: Hooks, I. Writing Good Requirements, Proc Fourth International Symposium of the NCOSE, 1994, Vol.2, 197--203.
• 15: Natalia Juristo , Ana Maria Moreno , Marta López, How to Use Linguistic Instruments for Object-Oriented Analysis, IEEE Software, v.17 n.3, p.80-89, May 2000 [doi>10.1109/52.896254]
• 16: Krippendorf, K. Content Analysis, An Introduction to Its Methodology, SAGE Publications, Thousand Oaks, 2004.
• 17: Lilly, S., How to Avoid Use-case Pitfalls, Software development, 8, 10, January 2000, 40--44.
• 18: Susan Lilly, Use Case Pitfalls: Top 10 Problems from Real Projects Using Use Cases, Proceedings of the Technology of Object-Oriented Languages and Systems, p.174, August 01-05, 1999
• 19: Marsen, S., Biddle, R., and Noble, J. Use Case Analysis with Narrative Semiotics, Technical Report CS-TR-03-10, School of Mathematical and Computing Science, Victoria University of Wellington, 2003.
• 20: Munns, A. K., and Bjeirmi, B. F. The role of project management in achieving project success, International Journal of Project Management, 14, 2, 1996, 81--87.
• 21: Phalp, K., and Cox, K. Supporting Communicability with Use Case Guidelines An Empirical Study, Proc. EASE 2002, 6th International Conference on Empirical Assessment and Evaluation in Software Engineering, (Keele University, UK, 2002), 2002.
• 22: Pinto, J. K., and Slevin, D. P. Critical success factors across the project life cycle, Project Management Journal, 19, 3, 1988.
• 23: Pinto, J. K., Prescott, and J. E. Variations in critical success factors over the stages in the project life cycle, Journal of Management, 14, 1, 1988, 5--18.
• 24: B. Regnell , K. Kimbler , A. Wesslen, Improving the use case driven approach to requirements engineering, Proceedings of the Second IEEE International Symposium on Requirements Engineering, p.40, March 27-29, 1995
• 25: Colette Rolland , Camille Ben Achour, Guiding the construction of textual use case specifications, Data & Knowledge Engineering, v.25 n.1-2, p.125-160, March 1998 [doi>10.1016/S0169-023X(97)86223-4]
• 26: Thelin, T., Runeson, P., and Regnel, B. Usage-Based Reading - An Experiment to Guide Reviewers with Use Cases, Information and Software Technology, 43, 15, 2001, 925--938.
• 27: The Standish Group International Inc. (ed.) Chaos: Recipe for Success, http://www.standishgroup.com/sample_research/PDFpages/chaos1999.pdf, 1999, accessed 1 August 2006.
• 28: www.readysetpro.com Enterprise-Ready Software Engineering Templates, accessed 1 August 2006.
• 29: Weber, R.P. Basic Content Analysis, SAGE Publications, Newbury Park, 1990.
• 30: Karl Wiegers, Listening to the customer's voice, Software Development, v.5 n.3, p.49-55, March 1997

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Elicitation methods (e.g., rapid prototyping, interviews, JAD)

General Terms:
Design

Keywords:
education, natural language, readability, systems analysis, use case