Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2014 ASEE Annual Conference & Exposition

Authors

J. Jenny Li, Kean University; Patricia Morreale, Kean University

Tagged Divisions

Software Engineering Constituent Committee

time measurements: 1) Planning time: the duration from a student receiving the problem to the time (s)he startingto write code. Because these students haven’t taken any software engineering courses, they don’thave any formal knowledge of design and specification. They rely on the reading of the projectdescription to understand the requirements of the project. So this measurement tells us how muchtime the students take to comprehend the project requirements and it is not the time for design orrequirement analysis. 2) Coding time: the duration from when the student starts to write the code to her/hisattempt to run the first usage scenario of the project. The definition of this one is critical to ouranalysis, which clearly divides up

Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2014 ASEE Annual Conference & Exposition

Authors

Vignesh Subbian, University of Cincinnati; Carla C. Purdy, University of Cincinnati

Tagged Divisions

Software Engineering Constituent Committee

) addressed in this course are: Page 24.56.21. Comprehend software development life cycle models, and project planning and organization, for both traditional and distributed projects (a, g).2. Understand how to develop specifications, design, and test code for a set of software requirements and how to measure the quality of software developed and of the development process itself (a, e).3. Use team-building skills to work with the student’s team to plan, design, implement, test, and develop a mobile application (a, c, d, e, g, k).4. Comprehend formal software engineering methods (a, e).5. Apply principles of the ACM/IEEE Software Engineering

Conference Session

Software Engineering Constituent Committee Division Technical Session 1

Collection

2014 ASEE Annual Conference & Exposition

Authors

Tanmay Bhowmik, Mississippi State University; Nan Niu, Mississippi State University; Donna Reese, Mississippi State University

Tagged Divisions

Software Engineering Constituent Committee

a plan, implement the plan, and evaluate the so-lution. We find that students show significant deficiency in the overall problem solving pro-cess, whereas many professionals follow unique and effective tracing techniques in definingthe problem, and in developing and implementing the plan. We identify the improvement ar-eas and propose a set of learning activities for Software Engineering students to enhance theirtracing skills. We implement two learning activities in a Software Engineering course andreport our experience. Our study contributes to the improvement of training students in per-forming ART and other information-intensive tasks in Software Engineering.1 IntroductionA recent study by Begel and Simon1 shows that new college

Conference Session

Software Engineering Constituent Committee Division Technical Session 2

Collection

2014 ASEE Annual Conference & Exposition

Authors

Gustavo Lopez, Universidad de Costa Rica; Alexandra Martinez, Universidad de Costa Rica

Tagged Divisions

Software Engineering Constituent Committee

Education, 2014 Use of Microsoft Testing Tools to Teach Software Testing: An Experience ReportAbstractThis paper reports our experience using Microsoft testing tools in both graduate and under-graduate Software Testing courses for four semesters. In particular, we used Microsoft Visu-al Studio Ultimate 2010 (including Microsoft Test Manager 2010) and Microsoft TeamFoundation Server 2010, which together offer an integrated and comprehensive environmentfor the application lifecycle management, including test planning, authoring, automation,execution, tracking, monitoring and managing. We assessed our experience in using thetools from the student`s and the teacher’s points of view. Based on students’ feedback

Conference Session

Software Engineering Constituent Committee Division Technical Session 3

Collection

2014 ASEE Annual Conference & Exposition

Authors

Peter J. Clarke, Florida International Univeristy; Debra Lee Davis, Florida International University; Raymond Chang Lau, Florida International University; Tariq M. King, Ultimate Software Group, Inc.

Tagged Divisions

Software Engineering Constituent Committee

StructureThe CEN4072 course topics as stated in the catalog description are: test plan creation, test case Page 24.1115.5generation, program inspections, black-box testing, white-box testing, GUI testing, and the useof testing tools. The prerequisite for CEN4072 is data structures. The students in the course areevaluated based on three exams, a team-based project, and class participation. Details on the courseproject are provided in the next subsection.The material presented to students during the course is centered around black-box and white-boxtesting techniques.3, 18 The black-box testing techniques presented include: random, equivalencepartition

Conference Session

Software Engineering Constituent Committee Division Technical Session 2

Collection

2014 ASEE Annual Conference & Exposition

Authors

Vignesh Subbian, University of Cincinnati; Carla C. Purdy, University of Cincinnati

Tagged Divisions

Software Engineering Constituent Committee

II: Code Maintenance1.5. Explain code maintenance practices of your team (give details about version control and associated tools)? How often did you update, commit and/or merge, and build?1.6. Explain the release cycle of your team. How were releases made to customers? How often did customers receive releases?1.7. When did you first learn about version control? After learning to do version control, how did it change your views on maintaining code?Examination:2.3. Share the kinds/levels of tests you wrote as a part of this course. Give specific examples, if any, of how tests found bugs in your code?2.4. What did you learn from writing test cases and test plans?2.5. What are your thoughts on code maintenance and release cycle

Conference Session

Software Engineering Constituent Committee Division Technical Session 2

Collection

2014 ASEE Annual Conference & Exposition

Authors

Janusz Zalewski, Florida Gulf Coast University; Fernando Garcia Gonzalez, Florida Gulf Coast University

Tagged Divisions

Software Engineering Constituent Committee

concept, for example, in the computer science context, it would be developing a program to run the telescope, focusing on the program development cycle, with writing (editing) the code, compiling, executing, and debugging it  experiment – this activity relies on enforcing the essential concept of scientific inquiry, which in the context of computer science would be testing the software developed for a telescope, with outlining test plans, conducting actual testing, and showing the test results  project – this activity is typical to a full-fledged engineering process, that is, developing software in four stages, with formal (a) requirements, (b) design, (c) implementation, and (d

Conference Session

Software Engineering Constituent Committee Division Technical Session 3

Collection

2014 ASEE Annual Conference & Exposition

Authors

Robert W. Hasker, Milwaukee School of Engineering; Yan Shi, University of Wisconsin - Platteville

Tagged Divisions

Software Engineering Constituent Committee

that the Intermediate Software Engineeringstudents did so poorly on the snow plow example (the example that motivated this work) suggeststhat traditional methods were not working well, at least at UW-Platteville. An obvious futurestudy would be to evaluate performance on similar problems in introductory courses which do notuse UMLGrader. It would also be useful to re-evaluate students in upper-divisional courses nowthat students are using the tool in the introductory course on a regular basis.Additional work is being done on the tool. It currently supports diagrams created in IBM RationalRose and IBM Rhapsody. Work is underway to provide support for Enterprise Architect. Inaddition, we plan to add support for comparing state diagrams and