Undergraduate programs in software engineering are relatively new. The first ABET accredited programs received accreditation in 2001. There are currently 31 ABET accredited software engineering programs worldwide with additional programs being added each year. In this session, panelists will discuss their experience starting new programs, developing curriculum, and navigating accreditation issues.

Software engineering education is a technologically challenging, rapidly evolving discipline. Like all STEM educators, software engineering educators are bombarded with a constant stream of new tools and techniques (MOOCs! Active learning! Inverted classrooms!) while under national pressure to produce outstanding STEM graduates. Software engineering educators are also pressured on the discipline side; a constant evolution of technology coupled with a still emerging engineering discipline. As a handson engineering discipline, where engineers not only design but also construct the technology, guidance on the adoption of project-centric curricula is needed. This paper focuses on vertical integration of project experiences in undergraduate software engineering degree programs or course sequences. The Software Enterprise, now in its 9thyear, has grown from an upper-division course sequence to a vertical integration program feature. The Software Enterprise is presented as an implementation of a project spine curricular pattern, and a plan for maturing this model is given.

Teaching first-year students is a balance between introducing technical content and providing perspective for students to forge connections to the context of what engineers do. Making the possible impact of engineers real and visible to introductory students in an authentic manner can be challenging. This paper describes the implementation and impact for a Traffic Simulation engineering design challenge in a freshman level “Introduction to Engineering Design” course comprised of both Engineering and Computing students at Arizona State University.

The introduction of software technology in a life-dependent environment requires the development team to execute a process that ensures a high level of software reliability and correctness. Despite their popularity, agile methods are generally assumed to be inappropriate as a process family in these environments due to their lack of emphasis on documentation, traceability, and other formal techniques. Agile methods, notably Scrum, favor empirical process control, or small constant adjustments in a tight feedback loop. This paper challenges the assumption that agile methods are inappropriate for safety-critical software development. Agile methods are flexible enough to encourage the rightamount of ceremony; therefore if safety-critical systems require greater emphasis on activities like formal specification and requirements management, then an agile process will include these as necessary activities. Furthermore, agile methods focus more on continuous process management and code-level quality than classic software engineering process models. We present our experiences on the image-guided surgical toolkit (IGSTK) project as a backdrop. IGSTK is an open source software project employing agile practices since 2004. We started with the assumption that a lighter process is better, focused on evolving code, and only adding process elements as the need arose. IGSTK has been adopted by teaching hospitals and research labs, and used for clinical trials. Agile methods have matured since the academic community suggested they are not suitable for safety-critical systems almost a decade ago, we present our experiences as a case study for renewing the discussion.

Only recently has the research community started to consider how to make software process models interoperable and reusable. The task is difficult Software processes are inherently creative and dynamic difficult to define and repeat at an enactable level of detail. Additionally, interoperability and reusability have not been considered important issues. Recent interoperability and reusability solutions advocate the development of standard process model representations based on common concepts or generic schemas, which are used as a basis for translating between heterogeneous process representations. The authors propose an alternative approach through the development of process-based components. They present the Open Process Components Framework, a component based framework for software process modeling. In this approach, process models are constructed as sets of components which interact in meaningful ways. Interoperability and reuse are obtained through encapsulation of process representations, an explicit representation of process state, and an extendable set of class relationships.

Article Automated process support for organizational and personal processes Share on Authors: Kevin Gary Arizona State University, Computer Science Department, Mail Stop 5406, Tempe, AZ Arizona State University, Computer Science Department, Mail Stop 5406, Tempe, AZView Profile , Tim Lindquist Arizona State University, Computer Science Department, Mail Stop 5406, Tempe, AZ Arizona State University, Computer Science Department, Mail Stop 5406, Tempe, AZView Profile , Harry Koehnemann Arizona State University, Computer Science Department, Mail Stop 5406, Tempe, AZ Arizona State University, Computer Science Department, Mail Stop 5406, Tempe, AZView Profile , Ly Sauer Arizona State University, Computer Science Department, Mail Stop 5406, Tempe, AZ Arizona State University, Computer Science Department, Mail Stop 5406, Tempe, AZView Profile Authors Info & Claims GROUP '97: Proceedings of the international ACM SIGGROUP conference on Supporting group work: the integration challengeNovember 1997 Pages 221–230https://doi.org/10.1145/266838.266914Online:16 November 1997Publication History 3citation484DownloadsMetricsTotal Citations3Total Downloads484Last 12 Months3Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteGet Access