Search

As part of being named one of ten emerging leaders in engineering education, Arizona State University (ASU) was invited to participate in the MIT-Olin Colloquium on the "Global State of the Art in Engineering Education" held in Boston in April 2019. As a group we shared innovations at our respective institutions and identified opportunities to collaborate to continue to advance the state of engineering education. In response to the guidelines for this special issue, this paper provides details on a few representative ASU achievements to date, and identifies opportunities for the continued evolution of the Fulton Schools of Engineering.

The EPICS Program was created in 1995 with the dual purposes of improving engineering education and addressing compelling needs within our communities. The model broke with many traditional academic traditions, involving students in multidisciplinary teams of students from first-year to fourth years for multiple semesters or even years on projects with local and global community partners. EPICS has been recognized as a model within engineering education and community engagement. The EPICS model has been adapted by several other institutions at the undergraduate and pre-university settings. There are currently 38 active higher education institutions with each adapting the model to their own institutional culture. This paper highlights the EPICS model and how four institutions that are recognized global leaders in engineering education have collaborated and adapted the model to their own institution's goals and culture. [ABSTRACT FROM AUTHOR]

A significant factor in the success of a software project is the management skill of the project leader. The ability to effectively plan and track a software project utilizing appropriate techniques and tools requires training, mentoring, and experience. This paper describes a collaborative effort between Arizona State University and Motorola University to develop a software project management training course. Although many such courses exist in academia and industry, this course incorporates a system dynamics simulator of the software development process. The use of this simulator to train future software project managers is analogous to the use of a flight simulator to train pilots. This paper describes the software project simulator and how it is utilized in the software project management training course. Feedback from the training course participants is also shared and discussed. Index Terms--Simulation, software project management.

Requirements volatility is a common development project risk that can have severe impacts. An empirical survey of over 300 software project managers and other software development personnel was performed to examine effects of various software development factors on requirements volatility. This paper reports the survey data results showing relationships between a number of software development process factors and requirements volatility. Key software project factors studied for their relationship with requirements volatility include process maturity level and various process techniques used for requirements engineering activities, such as requirements elicitation, prototyping, analysis and modeling, specification, and reviews. Significant correlations between the process factors and requirements volatility resulted from the analysis of some of the factors. The use of particular requirements engineering process techniques showed correlations with lower levels of requirements volatility. Other findings indicated that projects which used some types of prototypes to elicit requirements had higher levels of requirements volatility in later phases of the development cycle than lower levels, as one might expect. The presented results can be used by software development managers to proactively address and possibly mitigate the risk of requirements volatility, and to understand the potential for increased requirements volatility when certain methods are utilized. Copyright © 2010 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

Software maintenance is the dominant factor contributing to the high cost of software. In this paper, the software maintenance process and the important software quality attributes that affect the maintenance effort are discussed. One of the most important quality attributes of software maintainability is the stability of a program, which indicates the resistance to the potential ripple effect that the program would have when it is modified. Measures for estimating the stability of a program and the modules of which the program is composed are presented. and an algorithm for computing these stability measures is given. An algorithm for normalizing these measures is also given. Applications of these measures during the maintenance phase are discussed along with an example. An indirect validation of these stability measures is also given. Future research efforts involving application of these measures during the design phase, program restructuring based on those measures, and the development of an overall maintainability measure arc also discussed. [ABSTRACT FROM AUTHOR]