skip to main content
10.1145/3183377.3183393acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
short-paper
Public Access

10+ years of teaching software engineering with itrust: the good, the bad, and the ugly

Published:27 May 2018Publication History

ABSTRACT

This paper presents an experience report with a junior-level software engineering course at North Carolina State University. We provide an overview of the course structure and the course project, iTrust, that has been developed by students over 25 semesters. We summarize reflections from faculty, teaching assistants, and students (through course evaluations). From our lessons learned, we present our course improvements as we prepare for the next ten years of software engineering courses. Our main lessons learned are 1) course technologies have a lifespan and require periodic updating to balance student learning and working with a legacy system; 2) teaching assistant longevity and support is critical to course success; and 3) the value of working with a large, legacy system in a semester long course is supported by faculty, teaching assistants, and eventually students.

References

  1. Jürgen Börstler and Thomas B. Hilburn. 2016. Team Projects in Computing Education. Trans. Comput. Educ. 16, 2, Article 4 (March 2016), 4 pages. Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. Heidi JC Ellis. 2008. Software Engineering: Effective Teaching and Learning Approaches and Practices: Effective Teaching and Learning Approaches and Practices. IGI Global. Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. Howard Hills. 2001. Team-based learning. Gower Publishing, Ltd.Google ScholarGoogle Scholar
  4. J. Lave and E. Wenger. 1991. Situated Learning: Legitimate Peripheral Participation. Cambridge University Press.Google ScholarGoogle ScholarCross RefCross Ref
  5. Mary Shaw. 2000. Software Engineering Education: A Roadmap. In Proceedings of the Conference on The Future of Software Engineering (ICSE '00). ACM, New York, NY, USA, 371--380. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. 10+ years of teaching software engineering with itrust: the good, the bad, and the ugly

    Recommendations

    Comments

    Login options

    Check if you have access through your login credentials or your institution to get full access on this article.

    Sign in
    • Published in

      cover image ACM Conferences
      ICSE-SEET '18: Proceedings of the 40th International Conference on Software Engineering: Software Engineering Education and Training
      May 2018
      187 pages
      ISBN:9781450356602
      DOI:10.1145/3183377

      Copyright © 2018 ACM

      Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

      Publisher

      Association for Computing Machinery

      New York, NY, United States

      Publication History

      • Published: 27 May 2018

      Permissions

      Request permissions about this article.

      Request Permissions

      Check for updates

      Qualifiers

      • short-paper

      Upcoming Conference

      ICSE 2025

    PDF Format

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader