Teaching requirements engineering to undergraduate students

ABSTRACT

Requirements engineering, an integral part of the life of a software engineer, often receives little or no attention in the education of a computer science student. We report on our experiences in constructing an innovative curriculum that utilizes a three tier model of learning that provides students with hands-on experience on the various facets of requirements elicitation and management. This curriculum can be integrated into an existing course on software engineering, software requirements or the senior capstone experience. We believe our experience will be of use to other computer science and software engineering programs that are aiming at introducing requirements in the undergraduate curriculum.

References

1. Standish group chaos: A recipe for success. Standish Group International, 1999.
2. R. Bruhn and J. Camp. Capstone course creates useful business products and corporate-ready students. ACM SIGCSE Bulletin, 2004.
3. A. Cooper. The inmates are running the asylum. SAMS publishing, 2004.
4. D. Damian and D. Zowghi. Requirements Engineering challenges in multi-site software development organizations. Requirements engineering, 8(3):149--160, 2003.
5. R. Glass. Software runaways. Prentice Hall, 1998.
6. R. L. Glass. How not to prepare for a consulting assignment, and other ugly consultancy truths. Commun. ACM, 41(12):11--13, 1998.
7. R. L. Glass. Frequently forgotten fundamental facts about software engineering. IEEE Softw., 18(3):112--111, 2001.
8. H. Koppelman and B. van Dijk. Creating a realistic context for team projects in HCI. ACM SIGCSE Bulletin, 2006.
9. G. Kotonya and I. Sommerville. Requirements engineering. Wiley Chichester, 1998.
10. D. Leffingwell and D. Widrig. Managing Software Requirements: a use case approach. Pearson Education, 2003.
11. T. Lethbridge, J. Diaz-Herrera, J. Richard Jr, and J. LeBlanc. Improving software practice through education: Challenges and future trends. 2007.
12. L. Macaulay and J. Mylopoulos. Requirements Engineering: an educational dilemma. Automated Software Engineering, 2(4):343--351, 1995.
13. R. Montealegre, H. Nelson, C. Knoop, and L. Applegate. BAE automated systems (A): Denver International Airport baggage-handling system. Harvard Business School Teaching Case, page 311, 1996.
14. T. Moynihan. How experienced project managers assess risk. IEEE Softw., 14(3):35--41, 1997.
15. J. Myers Jr. Software engineering throughout a traditional computer science curriculum. In Proceedings of the fourteenth annual consortium on Small Colleges Southeastern conference, 2000.
16. E. Oz. When professional standards are lax: the CONFIRM failure and its lessons. Communications of the ACM, 37(10):29--43, 1994.
17. J. Preece, Y. Rogers, and H. Sharp. Interaction design: beyond human-computer interaction. 2006.
18. R. Pressman. Software Engineering - A Practitioners Approach. McGraww Hill, 2009.
19. K. D. Schenk, N. P. Vitalari, and K. S. Davis. Differences between novice and expert systems analysts: what do we know and what do we do? J. Manage. Inf. Syst., 15(1):9--50, 1998.
20. B. Shneiderman and C. Plaisant. Designing the user interface - Strategies for Effective Human Computer Interaction. Addison-Wesley Reading, MA, 2009.
21. I. Sommerville. Software Engineering. Addison Wesley, 2010.
22. J. Verner, K. Cox, S. Bleistein, and N. Cerpa. Requirements engineering and software project success: An industrial survey in australia and the u.s., 2004.
23. E. Walker and O. Slotterbeck. Incorporating realistic teamwork into a small college software engineering curriculum. Journal of Computing Sciences in Colleges, 2002.

Index Terms

• Social and professional topics

  • Professional topics

    • Computing education

      • Model curricula