Asee peer logo
Well-matched quotation marks can be used to demarcate phrases, and the + and - operators can be used to require or exclude words respectively
Displaying all 4 results
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
motivating objective was togive students on-the-job experience with SE principles where teams of 5 to 6 students developeda simulated project. Reichlmayr briefly describes the postmortem process where teams useprocess metrics to reflect on and improve process management.Two recent papers further report the use of Agile software development methodology for courseprojects [8,14]. In one paper, the authors describe an upper-level course where students use theiterative features of Agile that allow them to repeat cycles where they “see and use tools thatthey can explain and check. [8]”. The second paper describes a capstone course motivated by thedesire for students to learn transferable skills [14]. In both cases, projects last an entire semesterwhere
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
working software, each team was required to submit their ranked risk items aspart of their agile reflections at each of the 4 project milestones. The risk items were the mainsources for our data analysis and reporting.Our contributions lie in the analysis of students’ own perceptions of risks and their use of risks inmanaging the agile software development. The risks perceived by our students differed fromthose reported in prior studies9,10,11,12. Furthermore, our classification of the results of the firstoffering of the course suggested collaborative ways of identifying and mitigating the risks. Basedon the collaborative risk management, we designed several instructor interventions in our secondcourse offering and showed the effectiveness of
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
three applications. Studentresponses to the three questions were analyzed based on a four-point rubric. Responses andrubric entries are shown in Table 1. Figure 3: Sample JMeter outputVirtually all students performed acceptably on this aspect of the assignment. Few students had aperfect analysis, but most students could answer this set of simple graph interpretation questionscorrectly. This activity, however, reflects a very low-level activity on Bloom’s Taxonomy,simply applying graph interpretation skills to performance testing.Table 1: Analysis of the first three questions. - Which application is faster? - Which application delivers more throughput? - Discuss the performance differences between the three
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
, project work, and a final exam.Weekly quizzes keep students aligned with course lecture topics. The project work is assessedthrough establishment of expectations for a certain amount of effort (hours and LOC) put forthtoward the project. Students are expected to put effort toward every phase (requirements, design,implementation, testing, and maintenance), and they are required to document their effort in adigital journal. Students also are required to write a final reflection that describes theircontributions to the project and learning outcomes. The journal and reflection information isrequired to be aligned with information posted on Slack, Trello, and the code repository.4. Project DescriptionMobile applications are an excellent project