Conference Session

Software Engineering Division Technical Session 2

Collection

2017 ASEE Annual Conference & Exposition

Authors

Venkata Rama Chaitra Thota, University of Cincinnati; Nan Niu, University of Cincinnati; Wentao Wang, University of Cincinnati; Carla C. Purdy, University of Cincinnati

Tagged Divisions

Software Engineering Division

stakeholders, evaluating thealternatives for satisfying the win conditions, managing the risks that stem from the selectedalternative(s), and obtaining the stakeholder approvals and commitments to pursuing the nextcycle are the four basic steps of the spiral model2. For example, if sensitive information is storedand accessed but the end user is not invited to participate in the trade-off analysis andprioritization of the requirements, then the software project is at risk of failing to satisfy thesecurity needs of the user.Having key stakeholders such as user and customer representatives involved is a hallmark ofagile software development3, which is considered to not only inherent the iterative andincremental natures embedded in the spiral model but

Conference Session

Software Engineering Division Technical Session 2

Collection

2017 ASEE Annual Conference & Exposition

Authors

Bruce R Maxim, University of Michigan, Dearborn; Sushil Acharya, Robert Morris University; Stein Brunvand, University of Michigan-Dearborn; Marouane Kessentini, University of Michigan-Dearborn

Tagged Topics

Diversity

Tagged Divisions

Software Engineering Division

University of Michigan-Dearborn Advancement ofTeaching and Learning Fund and the NSF Award #1245036 Collaborative Education: Building aSkilled V&VF Community. We would like to thank Ms. Raminderdeep Randhawa who workedas Research Assistant on this project and Ms. Navin Tama who worked as a Graduate StudentInstructor for the fall 2016 offering of CIS 375. They gave generously of their time and energy tothis project.Bibliography1. Branch R. (2010): Instructional Design: The ADDIE Approach, Springer, 2010.2. Ardis, M., Chenoweth, S. and Young, F. (2008): “The ‘Soft’ Topics in Software Engineering Education”, Proceedings of 38th Annual Frontiers in Education Conference (Vol. 1, Oct 2008), IEEE Press, Saratoga Springs, NY, 2008, pp. F3H1

Conference Session

Software Engineering Division Technical Session 2

Collection

2017 ASEE Annual Conference & Exposition

Authors

Walter W Schilling Jr., Milwaukee School of Engineering; Brad Dennis, Milwaukee School of Engineering

Tagged Divisions

Software Engineering Division

forth. ● Application (a): Using learned material in new and concrete situations. For example, using information, methods, concept s, and theories to solve problems requiring the skills or knowledge presented.A topic’s relevance to the core is designated in a similar manner: ● Essential (E): The topic is part of the core. ● Desirable (D): The topic is not part of the core, but it should be included in the core of a particular program if possible; otherwise, it should be considered part of elective materials. Figure 1: IEEE SE2014 Software Verification and Validation Coverage [7]One of the challenges of teaching software verification has been the lack of quality teachingmaterials at

Conference Session

Software Engineering Division Technical Session 1

Collection

2017 ASEE Annual Conference & Exposition

Authors

Zesheng Chen, Indiana University Purdue University, Fort Wayne

Tagged Divisions

Software Engineering Division

audio service by filling out an online form. Once the form issubmitted, the data are stored in the database. An administrator at ACPL can log into the systemthrough the Web interface and manage the system. The functionalities for the administratorinterface include searching, reading, creating, and updating users’ and radios’ profile, as well asassigning audio radio(s) to a user or an organization.The main challenges to implement such an architecture lie in two aspects: Figure 1. System Structure of Our Web Application (1) Ease of use. The information for both the user’s interface and the admin’s interface must be displayed in a user friendly manner. Especially, the user’s interface should be accessible to

Conference Session

Software Engineering Division Technical Session 2

Collection

2017 ASEE Annual Conference & Exposition

Authors

Sushil Acharya, Robert Morris University; Walter W Schilling Jr., Milwaukee School of Engineering

Tagged Topics

Diversity

Tagged Divisions

Software Engineering Division

Undergraduate Degree Programs in Software Engineering, [Webpage], Retrieved January 29, 2017 from URL http://sites.computer.org/ccse/SE2004Volume.pdf [5]. The Joint Task Force on Computing Curricula: IEEE-CS and ACM, (2015), Software Engineering 2014 Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering, [Webpage], Retrieved January 29, 2017 from URL https://www.acm.org/education/se2014.pdf [6]. Acharya, S., Ackerman, A. (2012), Software Engineering Education Needs more Engineering, ASEE Annual Conference & Exposition – Software Engineering Constituent Committee, June 10 – 13 – San Antonio, TX[7]. McGraw, G. Software Security - Building Security In, Addition-Wesley

Conference Session

Software Engineering Division Technical Session 1

Collection

2017 ASEE Annual Conference & Exposition

Authors

Derek David Riley, Milwaukee School of Engineering

Tagged Divisions

Software Engineering Division

. Riley, Using mobile phone programming to teach Java and advanced programming to computer scientists. Proceedings of the 43rd annual SIGCSE, 2012.[5] R. Carbon, M. Lindvall, D. Muthig, P. Costa, Integrating product line engineering and agile methods: Flexible design up front vs. incremental methods, First International Workshop on Product Line Engineering, 2006.[6] Carnegie Mellon Software Engineering Institute, URL: https://www.sei.cmu.edu/productlines/[7] M. Catala, S. Dowling, D. Hayward, Expanding the Google Transit Feed Specifications to Support Operations and Planning, No. FDOT BDK85# 977-15, 2011.[8] G. Chastek, P. Donohoe, J. McGregor, and D. Muthig, Engineering a Production Method for a Software Product Line

Conference Session

Software Engineering Division Technical Session 1

Collection

2017 ASEE Annual Conference & Exposition

Authors

Mark Hoffman, Quinnipiac University; Stefan C. Christov, Quinnipiac University

Tagged Divisions

Software Engineering Division

three, weeks 14-15, includes packaging the modified software system for the next iterationof the course, individual reflection by team members on their participation in the course project,and final presentations and demos. A weekly course assignment schedule is shown in Table 1.Students are assigned Reading Response Questions in Phase 1 (weeks 3, 4, and 5) and Phase 2(weeks 6, 8, 10, and 12). These are questions on assigned readings and need to be answered inwriting.Table 1. Course Project Phases and Weekly Assignment Schedule Phase Week(s) Assignment Purpose Program Review Install and evaluate the course project, analyze 1 Report documentation