Conference Session

Software Engineering Division Technical Session 1

Collection

2017 ASEE Annual Conference & Exposition

Authors

Charles Kowalec, University of Michigan; Andrew Deorio, University of Michigan

Tagged Divisions

Software Engineering Division

results examine several factors influencing the success of a partnership, including differencein cumulative grade point average (GPA), gender balance, and work habits like starting projectsearly. After controlling for GPA, we observed an association between starting projects early andincreased performance on both exams and projects. The impact was greatest among those in thelowest GPA quartile, where an early start made the difference between an average final lettergrade of C+ (lowest early-start quartile) and B- (highest early-start quartile).1 Introduction and Related WorkAn important goal of group work in education is to increase student learning of course material.In computer science courses, group work often takes the form of pair

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

principles. The results of implementing thepedagogical tools and a discussion of these results are presented in Section 6. Finally, Section 7concludes the paper and discusses future work.2. Related WorkProject-based courses in software engineering and development have been reported in theliterature. Early papers by Northrup [15] and Adams [1] describe courses where projects givestudents hands-on experience with programming in-the-large and with the software developmentlife-cycle. Both use the waterfall methodology where change to the documented configuration iscontrolled by a control board. In both papers, the course instructor serves as project manager;however, the manager reported by Adams [1] also serves on the Configuration Control Boardand the

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

incorporate SPL engineering. Wefound that our approach improved student application of reusability theory, benefitteddocumentation quality, increased student satisfaction with the course, and increased the percentageof code written reused by students from semester to semester.1. IntroductionA Software Product Line (SPL) is a set of software systems that share common assets and are easyto deploy and configure for new environments [6]. There are many approaches that can be used tocreate an SPL including model-driven development, modularization refactoring, the use of SPLdesign patterns, reuse design, and others, but few software engineering classes have time to teachor apply these concepts. Many of the strategies within SPL engineering reinforce good

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

hold a book or turnpages. Other users may be any individual who is unable to read conventional printed materialsbecause of blindness, low-vision, or a literacy issue. The project needs to provide an easy-to-access interface for users to input their data such as access to service, service type,demographics, and customer satisfaction. Moreover, the project should deliver Webfunctionalities that allow ACPL to store, retrieve, and analyze users’ data (e.g., users’ profile andother survey data) through Web browsers and mobile devices. The designed Web application isexpected to help ACPL better serve users with disabilities.The system architecture of our designed Web application is illustrated in Figure 1. A user or anorganization can apply for the

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

Validation activities, ranging from the failure of the Healthcare.gov website [1]to the problems of unintended acceleration in Toyota vehicles [2] to the Heartbleed securityvulnerability [3] to a ten-hour outage of the electronic medical records system at QueenElizabeth Hospital [4].The need for software engineers to be trained in the field of testing is well documented.Lethbridge [5] indicates that software testing and quality assurance is one of the more importanttopics for universities to include in their curriculum. However, his work also notes that this isone area in which on the job training often occurs because students are not taught adequatetesting skills. In general, there is a shortage of trained practitioners who understand

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

senior year can improve software engineering education at theundergraduate level. We believe this will also increase the pool of new professionals withpractical software engineering knowledge and skills.The materials created for these courses were developed using a variation of the ADDIE (analyze,design, development, implementation, evaluation) process model.1 When new materials werecreated the team attempted to determine the best mix of case-study review, role-play, and hands-on exercises involving work with software engineering artifacts or tools, and trigger videos tofacilitate coverage of the topics. Many of the activities implemented in these courses have beenused successfully with several groups of students. Their evolution benefited from

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

inherently collaborative. We leveraged this collaborativenature to design and execute the instructor interventions. The results comparing the top risksbetween the two semesters show the effectiveness of the instructor interventions and suggestways to further improve risk management in students’ agile software development teams.1. IntroductionIt is common for a software project to face many risks in its lifecycle, from conception andconstruction to deployment and maintenance. Risk is any potential situation or event thatnegatively affects the project’s success. While the ultimate success of software often hinges onthe fulfillment of the stakeholders’ requirements, the project failure can be multi-faceted:frequent rework, architectural mismatch

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

requirementslist has being identified. Specific exercises are being developed using an iterative developmentmethodology. Student understanding is proposed to be assessed through quizzes, exams,assignment, and a learning survey. Once developed the ALTs will be made publicly availablethrough a website. This paper discusses continuing work on the gap analysis in software securityeducation, presents proposed contents areas for ALT, shares structures of threedeveloped/proposed ALTs, presents a sample of a survey instrument, and presents a sample ALTon case study video.1. Introduction and RationaleSoftware is now ubiquitous and software security is now realized as a growing threat. Executionof insecure codes causes software security problems that lead to