The Master of Software Engineering (MSE) at Carnegie Mellon University is a master's program founded in 1989 with the intent of developing technical leaders in software engineering practice, as a joint effort between Carnegie Mellon's School of Computer Science and the Software Engineering Institute. A core component of the degree is the studio project, a capstone project that accounts for 40 percent of the course units.[1]

History

Centered around software engineering workshops conducted at the Software Engineering Institute, the degree program's original core concepts and curriculum were developed. The original faculty included many educators who remain currently active, while others have retired or died. The latter notable individuals include Norm Gibbs and Jim 'Coach' Tomayko.

A hallmark of the MSE program is that it targets software practitioners who are already working in the field.[2]

Following its inception, the program has evolved to address a demand for lighter, faster software development processes, enabled by the rapid and widening adoption of the Internet. This included extreme programming, which later became part of agile methods, all of which sought to more rapidly respond to customer requirements in contrast to more deliberative, plan-driven development.

Program directors

  • 2019–Present, Travis Breaux, Director, Masters Programs in Software Engineering
  • 2016-2019, Anthony Lattanze, Director, Masters Programs in Software Engineering
  • 2002–2016, Dr. David Garlan, Director, Masters Programs in Software Engineering
  • 1999-2001, Dr. James E. Tomayko, Director Masters Program in Software Engineering
  • 2001-2008, Mel Rosso-Llopart, Director of Software Engineering Distance Program
  • 1996-2001, Dr. James E. Tomayko, Director of Software Engineering Distance Program
  • 1992-1999, Mary Shaw, Director, Masters Program in Software Engineering
  • 1989-1991, Software Engineering Institute

Curriculum

The MSE program began as a joint effort of the School of Computer Science and the Software Engineering Institute. The degree program is an intensive 16-month curriculum designed for professional software engineers. Class sizes are generally around 20 students. Applicants to the program must have a strong background in computer science, no less than two years of relevant industry experience with an average of five years of experience.[3]

The MSE curriculum has three basic components:

  1. Core Courses develop foundational skills in the fundamentals of software engineering, with an emphasis on design, analysis, and the management of large-scale software systems.
  2. The Studio Project, a capstone project that spans the duration of the program, allows for students to plan and implement a significant software project for an external client. Inspired by the design projects in architecture programs, students work as members of a team under the guidance of faculty advisors (mentors), analyzing a problem, planning the software development effort, executing a solution, and evaluating their work.
  3. Electives allow students to develop deeper expertise in an area of speciality within the software engineering domain, or to pursue study in areas relevant to their personal and professional interests.

Core Courses

  1. Models of Software Systems - This course considers many of the standard models for representing sequential and concurrent systems, such as state machines, algebras, and traces.
  1. Methods: Deciding What to Design - This course considers the variety of ways of understanding the problem to be solved by the system one is developing and of framing an appropriate solution to that problem.
  1. Management of Software Development - This course considers how to lead a project team, understand the relationship of software development to overall product engineering, estimate time and costs, and understand the software process.
  1. Analysis of Software Artifacts - This course considers the analysis of software artifacts—primarily code, but also including analysis of designs, architectures, and test suites.
  1. Architectures for Software Systems - The course considers commonly-used software system structures, techniques for designing and implementing these structures, models and formal notations for characterizing and reasoning about architectures, tools for generating specific instances of an architecture, and case studies of actual system architectures.

Notable faculty

References

  1. ↑ Tomayko, J.E. (April 1996). "Carnegie Mellon's software development studio: A five year retrospective". Proceedings of 9th Conference on Software Engineering Education. pp. 119–129. doi:10.1109/CSEE.1996.491367. ISBN 0-8186-7249-8. S2CID 11669118.
  2. ↑ Nancy R. Mead: Software engineering education: How far we’ve come and how far we have to go
  3. ↑ Garlan, David; Gluch, P. David; Tomayko, James E.: Agents of Change: Educating Software Engineering Leaders of Tomorrow, page 59–65. IEEE Software, November 1997.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.