Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2015 ASEE Annual Conference & Exposition

Authors

Anna Koufakou, Florida Gulf Coast University

Tagged Divisions

Software Engineering Constituent Committee

theprevious semester). The course objectives are listed below: Learn techniques, processes, and challenges involved in requirements elicitation, analysis, validation and management; Be able to work in a group environment to perform activities and provide documentation related to all phases of software development, focusing on requirements analysis, while also carrying out design, implementation, and testing; Be able to construct UML diagrams (e.g. Sequence Diagram, State Diagram); Conduct an oral presentation and demonstration of a software project developed by a group.Table 1 shows a general outline of course topics. For example, “Writing Requirements” includesFormal/Informal/Semi-Formal techniques, SRS standards and recommended

Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2015 ASEE Annual Conference & Exposition

Authors

Barbara Victoria Bernal, Kennesaw State University, Marietta; Jeffrey Chastine, Southern Polytechnic State University

Tagged Topics

Diversity

Tagged Divisions

Software Engineering Constituent Committee

is paramount for software engineers to develop the skills and background necessaryto effectively work, communicate and innovate on an international scale. Employers’expectation for collaboration with international counterparts is an increasing computing industrystandard. The effects of the globalization have been felt in the software engineering arenathrough software engineering projects realized by diverse professionals located in differentcontinents with different industrial background, culture, time zone, and language. 1-2International student exchange programs provide educational, personal, and long-term benefits. Page 26.1387.2As a result

Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2015 ASEE Annual Conference & Exposition

Authors

Raymond Scott Pettit, Abilene Christian University; John D. Homer, Abilene Christian University ; Kayla Michelle McMurry, Abilene Christian University; Nevan Simone, Abilene Christian University; Susan A. Mengel, Texas Tech University

Tagged Divisions

Software Engineering Constituent Committee

. Page 26.230.1 c American Society for Engineering Education, 2015 Are Automated Assessment Tools Helpful in Programming Courses?AbstractAutomated assessment tools (AATs) are growing in popularity in introductory programmingcourses, but researchers may have a difficult time synthesizing valid data to draw conclusionsabout the tools’ usefulness. Our first step addressing this issue was to break down our overridingquestion—are automated assessment tools helpful in programming courses?—into four morespecific questions: (1) Have AATs proven to be helpful in improving student learning? (2) Dostudents think that AATs have improved their performance? (3) After having used the tools

Conference Session

Software Engineering Constituent Committee Technical Session 2

Collection

2015 ASEE Annual Conference & Exposition

Authors

Weifeng Xu, Gannon University; Aqeel Raza Syed, Gannon University; QING ZHENG, Gannon University

Tagged Topics

Diversity

Tagged Divisions

Software Engineering Constituent Committee

theaverage number missing and incorrect test cases drops from 16% to 5.8% when the tool is uti-lized for generating test cases.1. IntroductionSoftware engineering, as an emerging discipline, has been distinguished from computer science.There are 22 ABET [1] and 101 Department of Education's recognized institutes in U.S [2] offer-ing a bachelor degree program in software engineering. In addition to the traditional needs ofpreparing graduates to analyze, design and implement systems, both organizations indicate thatsoftware engineering curriculum must prepare graduates to validate software systems.White-box testing is a critical validation technique commonly used by software testers to exam-ine if their unit code works as expected. White-box testing

Conference Session

Software Engineering Constituent Committee Technical Session 2

Collection

2015 ASEE Annual Conference & Exposition

Authors

Heidi J. C. Ellis, Western New England University; Gregory W Hislop, Drexel University (Eng. & Eng. Tech.); Sarah Monisha Pulimood, The College of New Jersey; Becka Morgan, Western Oregon University; Ben Coleman, Moravian College

Tagged Topics

Diversity

Tagged Divisions

Software Engineering Constituent Committee

study, but provide stronger evidence thatstudent involvement in HFOSS promotes student learning in the areas of tools and techniquesand technical knowledge about the process and tools used to develop an HFOSS project.1. IntroductionSoftware engineering programs as well as most computer science programs desire to providestudents with experience working on a real-world project in order to supply students with anunderstanding of professional practice including such skills as teamwork, communication, workethic, self-confidence and more. In fact, the SE 2004 curriculum guidelines2 emphasize the needfor including professional practice in the education of software engineers. A common way toprovide this experience is through instructor and/or student

Conference Session

Software Engineering Constituent Committee Technical Session 2

Collection

2015 ASEE Annual Conference & Exposition

Authors

Temesghen Kahsai , Carnegie Mellon University; Liam O'Reilly, Swansea University; Markus Roggenbach, Swansea University

Tagged Divisions

Software Engineering Constituent Committee

six learning outcomes in more detail:1. We refrain from addressing “Describe the difference between centralized and distributed software configuration management. [Familiarity]” 4 due to the constraints posed by teaching in the first year: software configuration management is beyond the scope of programming-in-the-small.2. We achieve the same mastery level on “Demonstrate the capability to use software tools in support of the development of a software product of medium size. [Usage]” 4.3. We exceed the recommended mastery level on “Describe how available static and dynamic test tools can be integrated into the software development environment. [Familiarity]” 4 by letting students have hands-on experience with testing tools such as