discuss the tutorial’s key design principles and affirm their efficacy based on theobserved learning experiences. The obtained insights can inform curricular interventions that in-troduce introductory students to code quality and its disciplined improvement practices.1 IntroductionThe CS Education research literature has established the importance of teaching software qualityas part of the CS curriculum 1,2,3,4 . However, it remains subject to considerable debate whether thetopic of software quality is appropriate for introductory learners. Some computing educators arguethat promoting disciplined programming practices is incongruent with the guiding principles ofConstructivism, the educational philosophy centered around unconstrained
onlycourse-related resources in a dedicated web space, but also the use of tools such as discussingboard to communicate with the instructor and other students outside of class instruction time. Incourses where collaborative learning is essential, the communication among team members alsoplays an important role in student engagement and learning.To promote better communication in class instruction in computer science and computerengineering disciplines, three aspects are especially desirable: (1) Prompt communication. Forexample, in a class exercise, if a student comes up with a good solution for codingimplementation, it is desired that the student can share the example with the instructor and otherstudents in a simple and quick way. (2) Group
course of the semester. The code posted is analyzedfor a variety of quality markers such as variable names, commenting, syntax errors, logic errors,correctness, and handling of edge cases. The responses are analyzed for effective errorcorrections, alternative solutions provided, formatting changes recommended, etc. There is alsoan analysis of student expressions. Finally, and perhaps most interesting of all is how thesedetails change over the course of the semester. I. IntroductionImposter syndrome has long been acknowledged within the Computer Science (CS) educationalcommunity with several studies reporting over 50% of CS oriented individuals exhibitingimposter syndrome [1]. Weber State University is an open-enrollment university. Students
further improvement possibilities for the course are identified from thisstudent feedback, especially regarding the response of the more hardware oriented electricalengineering students to software engineering topics.1 IntroductionThis paper is an experience report on a senior capstone course in which basic softwareengineering principles are introduced to electrical and computer engineering students who havehad no prior exposure. Our intention is to describe a model for the incorporation of introductorysoftware engineering concepts using both classic and newer materials, with a strong emphasis onproject based application of the concepts in the senior capstone design.In this paper, we report on the evolution and evaluation of our school’s senior
others to join theirteam, and having the invitees then accept the invitation. Another project added a tabbed view forassignment creation. A third provided an anonymized view so that we can use live data in demoswithout revealing any student names. Four of these projects have led to conference papers co-authored by independent-study students [1–4] and five to workshop papers [5–9].The first masters thesis added features to support peer-reviewing student contributions to a wikitextbook [10]. This involved sequencing review of chapters so that prerequisite chapters wouldbe written and reviewed before chapters that depended on them. The first Ph.D. dissertation [11]involved the use of natural-language processing to evaluate features of reviews [12
knowledge was broughtinto and out of a hackathon and did not address the process in which students worked on projects(La Place et al., 2017).MethodsTo extend the previous knowledge transfer work and software development work, we offer thefollowing research questions: 1. What technical knowledge do students use in capstones and hackathons? 2. Where do students learn the knowledge used in capstones and hackathons? 3. How does the software development process used by students differ between capstone and hackathon projects?This is a qualitative pilot study meant to fuel future research on knowledge transfer betweenhackathons and academic experiences. The nature of hackathons often results in participantsdesigning and developing a project
, gaining significant traction in the K-12 system is standards-based grading. With standards-based grading, grading is based upon “measuring students’proficiency on well-defined course objectives.” [1] Instead of arbitrary grading scales, studentsare assessed multiple times regarding their performance on course outcomes. By doing this,there is an increase in student engagement and a more thorough comprehension of coursematerials. [2] Standards Based grading focuses on the specific, relevant skills a student shouldlearn and helps instructors to assess how well students are learning and tailor their teaching tomeet areas of concern. [3] By measuring these goals, students continue to learn. By usingrubrics to articulate these goals, students can use
the course materials. Their levelsof engagement were monitored during the semester.Course DescriptionA junior level software engineering course, CIS 375 (Software Engineering 1), offered by theComputer and Information Science (CIS) department is organized as a 14 week, four credit-hourcourse. This is a required course taken by all computing majors in the CIS department whichincludes: Computer Science (CIS), Software Engineering (SE), Data Science (DS), andCybersecurity and Information Assurance (CIA). Pre-Covid19, this course was typically offeredusing a synchronous, face-to-face format with the live lectures being recorded for streaming on-demand by students taking the same course asynchronously. The ABET student outcomes forCIS 375 appear
requirements remainedrelatively stable. We then summarize the lessons learned from these revisions and talk about howwe plan to manage changes in the future. Finally, we offer suggestions on how others might goabout industrializing their own software development projects.IntroductionIndustry and academic professionals continue to call for more collaboration in Computer Scienceand Information Technology education [1]. Project-Based Learning (PBL) [2] and ActiveLearning [3] are key instructional approaches that benefit from a strong industry connection. Inthis paper, we talk about our experience in injecting industry practice into the core of the project-based course: the project itself.One of the authors of this paper is a university professor; the
engineering through the exploration of: 1) race, gender, and identity in the engineering workplace; 2) discipline-based education research (with a focus on computer science and computer engineering courses) in order to inform pedagogical practices that garner interest and retain women and minorities in computer-related engineering fields. c American Society for Engineering Education, 2020 Experiences of Integrating Learning and Engagement Strategies (LESs) into Software Engineering CoursesAbstractThe increase in job opportunities for computing professionals in the global community has resultedin a dramatic surge in the enrollment numbers in computer science (CS) departments in