Design, Development and Delivery of Active Learning Tools in Software Verification & Validation Education

Active learning tools are critical in imparting real world experiences to the students within a classroom environment. This is important because graduates are expected to develop software that meets rigorous quality standards in functional and application domains with little to no training. However, there is a well-recognized need for the availability of effective active tools. This need has been addressed by the authors by designing, developing, and delivering, twenty delivery hours of Case Studies, sixteen delivery hours of Class Exercises, and six delivery hours of Video Case Studies for use in V&V courses. The active learning tools focus on some specific SV&V topics such as requirements engineering, software reviews, configuration management, and software testing. Four key skill areas sought after by employers, namely communication skills, applied knowledge of methods, applied knowledge of tools, and research exposure have been used to drive the development funded by a National Science Foundation grant and perfected through an industry-academia partnership. These tools have been successfully disseminated to over 25 universities with many CS, IS, SE programs incorporating the tools in their existing courses and others designing new courses based on these tools. In this paper we present data on the student feedback and pedagogical effectiveness of the strategies used to effectively incorporate and deliver the developed active learning tools by instructors at two universities. Traditional and flipped classroom delivery strategies are discussed as well as topics like pre-requisite knowledge preparation prior to class, course module presentation sequence, homework, team/individual work, collaborative discussions, and assessment tools are deliberated. The student questionnaire data from the two University Partners who used the V&V instructional activities were quite positive and showed that students were interested in the activities, saw the real-world applications, and communicated with their classmates as they solved the problems. Educational outcomes assessment demonstrated more effective learning in all key learning areas.


Introduction
Imparting real world experiences is often a challenge due to both lack of effective active learning tools and delivery strategies.This pedagogical requirement is important because graduates are expected to develop software that meets rigorous quality standards in functional and application domains with little to no training.Institutions of higher learning across the nation are responding to political, economic, social and technological pressures to be more responsive to students' needs and more concerned about how well students are prepared to assume future societal roles (Teaching Strategies, 2017).The lack of effective active learning tools has been addressed by the authors at Robert Morris University by designing, developing, delivering, and disseminating twenty delivery hours of Case Studies, sixteen delivery hours of Class Exercises, and six delivery hours of Video Case Studies for use in courses that impart knowledge on SV&V topics viz.requirements engineering, software reviews, configuration management, and software testing.Four key skill areas sought after by employers, namely communication skills, applied knowledge of methods, applied knowledge of tools, and research exposure have been used to drive the development funded by a National Science Foundation (NSF) grant and perfected through an industry-academia partnership.These tools have been successfully disseminated to over 25 universities with many CS, IS, SE programs incorporating the tools in their existing courses and others designing new courses based on these tools.
As student learning retention and eventual application of the knowledge gained depends on knowledge retention activities delivered in different settings it is important to identify and incorporate delivery strategies that meet course and/or module learning outcomes and enhances student learning.Researchers in both academia and industry have published literature on delivery strategies.Some of the more prominent strategies used in higher education are lecture, case method, discussion, active learning, cooperative learning, integrating technology and distance learning (Teaching Strategies, 2017).In this article our focus will be on both Teacher Centric and Student Centric methods with a focus on the effective and efficient delivery of the active learning tools that we have developed.The active learning tools are the results of an industry-academia partnership with an understanding that the knowledge and experience gained through these tools would be directly applicable in the workplace.Hence to effectively impart required knowledge appropriate and effective delivery strategies should be used.
In this paper we discuss strategies used to effectively incorporate and deliver the developed active learning tools by instructors at two universities.Traditional, flipped and hybrid classroom delivery strategies are discussed and topics like pre-requisite knowledge preparation prior to class and, course module presentation sequence, homework, team/individual work, collaborative discussions, and assessment tools are deliberated.In addition student feedback and assessment are also presented for each category of active learning tools and strategies that work are summarized.

Active Learning Tools
Active learning is "embodied in a learning environment where the teachers and students are actively engaged with the content through discussions, problem-solving, critical thinking, debate or a host of other activities that promote interaction among learners, instructors and the material" (Promoting Active Learning, 2017).Prince (2004) defines active learning as a classroom activity that requires students to do something other than listen and take notes.Active learning is achievable by complementing lecture materials with case studies, class exercises, and case study videos.

Case Studies
Case studies can serve as useful tools to teach applications of science and engineering principles.Raju and Sankar (1999) define case study education as providing students with a record of a technical and/or business issue that actually has been faced by managers, together with surrounding facts, opinions, and prejudices upon which management decisions have to depend.Using case studies as a semester-long tool to teach neuroanatomy, in which students were actively engaged in the presentation and discussion of case studies throughout the semester, resulted in more understandable and enjoyable learning experience for the students.In a study at Middlesex Community College (https://www.middlesex.mass.edu/sotl/downloads/klein.pdf), case studies were used in teaching General Biology-I where 88.2% of the students surveyed found the cases to be useful or better for learning the course content.90.9% of the students surveyed thought the cases were useful or better in making the course more interesting.Case studies were applied in six courses to help students (1) understand complex and complicated issues and describe interrelated processes; (2) discuss policy-and decision-making ideologies that either are politically or socially charged; and (3) engage in informative and focused classroom discussion.The results indicated that use of the case study method as an active learning tool provides students with a variety of important skills necessary for success both in and out of the classroom.Specifically, active learning helps students develop problem-solving, critical-reasoning, and analytical skills, all of which are valuable tools that prepare students to make better decisions and become better students and, ultimately, better employees (Kunselman & Johnson, 2004).Raju and Sankar (1999) undertook the research to develop a teaching methodology to bring real-world issues into engineering classrooms.The results of their research led to recommendations to funding agencies and educators on the need to develop interdisciplinary technical case studies so that the innovations happening in the field of engineering can be communicated to students in the classroom.The authors have disseminated twelve Case Studies.Examples of some of our Case Studies are Understanding User Requirements, A Software Test Plan, and Importance of Peer Reviews.A complete set of case studies has been published by Acharya and Manohar (2016).

Class Exercises
Class exercises provide class time to explicitly raise questions that invite student participation.When well designed for the context and presented in the right setting, class exercises raise questions for the students to exercise their thinking.Depending on the focus of the questions, the students may be more motivated to investigate the subject matter, may gain a deeper understanding of course concepts, or may improve their skills through hands-on experience using the knowledge in problem solving and design derived from the exercises.There are many ways of using class exercises in the classroom setting.For a small class size, the teacher may simply use an exercise to engage students in discussion and hands-on practice.For larger classes, the students can be assigned to small groups using the class exercise as an instrument leading to group projects.Woods and Howard (2014) effectively used class exercises for Information Technology students to study ethical issues.Day and Foley (2006) used class time exclusively for exercises, having their students prepare beforehand for class with materials provided online.Bishop and Verleger (2013) presented a comprehensive survey of the research that reviewed different ways of using class exercises in the classroom, often referred to as the "flipped classroom".Frydenberg (2013) primarily used hands-on exercises to foster student understanding in data analytics.Well designed, class exercises become very effective learning tools and can be versatile in various classroom settings.The authors have disseminated sixteen exercises (Wu, Manohar, & Acharya, 2016).Examples of some of our Class Exercises are Requirements Ambiguity, Defect Lifecycle, and IEEE Standards.

Case Study Videos
One commonly used technique to enhance the classroom learning experience is the use of video.Videos are viewed as an effective method of presenting standard material while addressing students of different learning styles.A video actively engages visual learners with its images and motions, while auditory learners can listen carefully to the narration to gain an understanding of the topic.Videos are an essential part of the flipped classroom model (discussed later), in which the preponderance of lecture material is presented before class (Bergmann & Aaron, 2012).The class time is then spent on discussion and teamwork, reinforcing the material from the previous session.However, videos can also be used in a traditional classroom, and their use can be highly effective.There is extensive experience in using audio visual materials in the classroom, ranging from the usage of filmstrips during World War II to train soldiers (Hovland, Lumsdaine, & Sheffield, 1949) to modern digital video.Watching videos can reinforce reading and lecture material, help to develop common knowledge, enhance the quality of discussion and overall student comprehension, accommodate students of different learning styles, increase student motivation, and increase teacher effectiveness (Corporation for Public Broadcasting, 2004).Videos can aid in showcasing highly complex concepts and ideas in a short period of time, provoking meaningful discussion and analysis.The video scripts were first drafted by the industry partners and subsequently confirmed by the testimonies shared in focus group discussions.The process has been described in details in a previous publication (Acharya, Manohar, & Wu, 2016).Four videos, ranging from 15 to 24 minutes, have been disseminated.Examples of some of our Video Case Study titles are Formal Inspection Scenes and Requirement Analysis Scenes.

Dissemination
Information dissemination and implementation occurred in two main forms.First, for a second consecutive year, a summer workshop on the Robert Morris Campus was held to educate university partners about the instructional materials, and the educational partners who attended completed the workshop activities as well as a brief survey about the summer workshop processes and effectiveness.Second, the Principal Investigator and two other individuals used one or more of the active learning tools including Case Modules, Class Exercises, and Video Case Studies in their courses, and student pre-post data, and/or student questionnaire data about these activities were collected.Therefore, for the current reporting year, summaries of student questionnaire data about the different instructional materials is presented from a total of three individuals, including the Principal Investigator.

Delivery Strategies
Mishra et al. (Mishra, Hacaloglu, & Mishra, 2014) report that prior knowledge about software quality concepts and good programming skills can help students to achieve success in a software verification & validation course.Furthermore they also suggest that team work can be chosen as a strategy, since it facilitates students' understanding and motivates them to study.With the active learning tools designed to impart practical knowledge into theoretical understanding, we encourage a flipped classroom model (Bonwell & Eison, 1991) in which we can maximize class time for active learning tools so as to engage the students for further digestion of the knowledge in the context of industry practices.Students are expected to be prepared outside of the classroom beforehand, with assigned textbook readings or reviewing of online materials.For effective delivery it is also recommended that students work in small teams.Overall, the flipped classroom model has proven highly effective at increasing student engagement and enhancing the preparation of students for class sessions (Day & Foley, 2006).The flipped classroom also has been shown to allow the instructor to cover more material and results in higher student performance (Mason, Shuman, & Cook, 2013).
The active learning tools engage the students in different ways to study SV&V in practice.The Case Studies are explicit in this approach: each Case Study makes the point to consider issues in realistic practices.Instructors can present the Case Study while guiding students into further study and discussion of the practical issues in SV&V.The Class Exercises are designed for interaction in the classroom during group discussions.The instructor brings the question(s) and serves as a moderator to guide the discussion session.The instructor may also use the Class Exercise to lead students into subsequent group mini projects or individual mini projects.The "Instructor Notes" component of the Class Exercise discusses these possibilities.Students are likely to find the Case Study Videos by their nature as multimedia, as highly engaging.These videos share real-life perspectives of actions and their consequences.The videos are by design in sequences of scenes.For instructional purposes, it is highly beneficial to "pause" the video at appropriate moments so as to engage the students in discussion.Suggested discussion questions accompany the videos.
The active learning tools are modularized into flexible modules of 25 delivery minutes each.Instructors may consider their various needs such as curriculum design, class time, and class size to adapt the active learning tools to the situations in their institutions.Furthermore, though we recommend it, instructors do not need to practice the flipped classroom model or may do so partially.
To summarize, the course delivery plan encourages the following:  Using the flipped classroom model (if applicable)  Have students work in small teams (2-3 students per team)  Delivering tools in one or multiple 25-minute sessions  Using pre-test and post-test instruments to tailor course delivery  Evaluating student learning of the module immediately after delivery

Active Learning Tool Assessment
The implementation partners were provided with an implementation kit that included active learning tool description, a sample syllabus, pre-tests/post-tests for active learning tool evaluation and answer key, and samples of midterm/final exams.A sample assessment instrument is shown in Figure 1.

Institutional Profiles
As this article focuses on two distinctly different institutions and their different approaches to teaching software verification and validation, it is important to understand the differences in the institutions' profiles' and activities.
This section provides background information on the two programs' profiles in this article.

a. Robert Morris University (RMU)
Robert Morris University offers an accredited Bachelors of Science degree in engineering (Software Engineering concentration), and has been accredited since 2002.The emphasis is on small class sizes (10:1 student to faculty ratio) and hands on experiences through class assignments, course projects, internships (150 hours mandatory), and an interdisciplinary capstone project (3 credits).RMU also offers B.S. in Engineering degrees in Mechanical, Industrial, and Biomedical Engineering concentrations and a B.S. in Manufacturing Engineering (the only one of its kind in Western Pennsylvania).A Software Engineering Lab is a part of the engineering departments' Learning Factory (lab space) and is used for software engineering class sizes of 8-10 students.As software engineering is offered as a concentration some of the required courses and a few of the elective courses are offered through RMU's Computer Information Systems Department (for example courses on programming languages, data structures, databases, etc.).All software engineering majors take the same set of courses to complete 117 credits out of the required 126 credits.For the remaining 9 credits which are software engineering elective courses students are free to take courses in the areas of their interests like network security, databases, etc.All software engineering courses offered by the engineering department are delivered in a 2+2 hours or 1+3 hours format for a total of 4 meeting hours per week.Even though the courses are 3 credits the extra meeting hour is used for additional hands on experiences.

b. University of Michigan-Dearborn (UMD)
The University of Michigan-Dearborn (UMD) is one of three campuses of the University of Michigan and has an enrollment of approximately 9000 students., accredited 1997).CIS also offers undergraduate degrees in Digital Forensics (DF) and in Data Science (DS).We plan to seek accreditation of these two degrees after we have our first graduates.CECS also has several masters and doctoral programs in which CIS is a participant.The primary mission of the CIS department is to provide high-quality computing education to students in the Detroit metropolitan area.Our graduates are highly sought out by potential employers and work at major companies throughout the United States.All CIS undergraduates are required to take 120 credit hours of course which includes 58 credit hours in the CIS department.Most CIS courses are offered as lecture classes with 4 contact hours each week.There are several classes which also require attendance in closed laboratory sessions.The emphasis in CECS is on small class sizes (30:1 student to faculty ratio) and offering hands on experiences through class assignments, course projects, internships, and a two semester (8 month) capstone design project course (4 credits total).The CIS capstone project experience involves students working as part of a four person team under the mentorship of a senior CIS professor to develop a software solution to a problem posed by an industrial partner.

Course Delivery
The following narrative discusses where the active learning tools are incorporated in the curriculum of the two institutions being discussed.

Delivery Strategies at RMU and UMD
In the following sections we discuss how applicable active learning tools are delivered in these institutions.

a. RMU
Blackboard Learning Management System is used at RMU as the main delivery tool for on-line programs as well as a course repository for on-ground program.Fourteen weeks of course contents for ENGR3400 are uploaded to a Blackboard shell and then shared with the class prior to the start of the semester.Figure 4 below depicts the structure of Week 7 course contents in Blackboard.
i. Homework: As the course is being delivered in a flipped classroom model, prior to coming to class students are required to read the course slides relevant for that day or week.Each course slides begins with learning outcomes and ends with possible discussion questions.Should students have any questions prior to class they are requested to email the instructor or to meet the instructor during office hours to discuss the question(s).
ii. Classwork: In class the instructor spends the initial 5-10 minutes discussing a subset of the discussion questions.Randomly selected students are asked questions and the instructor supplements the responses by providing additional thoughts.At times the instructor also carries out mini lectures (10 mins) to reinforce key concepts.At the end of an active learning tool exercise students complete a survey which takes about two minutes to complete.ii.Classwork: In class the instructor spends the initial 30 minutes introducing the day's topics and activities.Most class periods students work in small groups to complete the day's active learning tasks.
At the end of an active learning exercise students complete a survey that takes about two minutes to complete.

a. RMU
In 2016 twelve Case Studies were successfully delivered to a class of 22 students in a room that was equipped with discussion tables and computers.
i. Homework: Some of the case study descriptions are given to the students as home reading assignments.With this approach the students come to class better prepared as they have a better understanding of the case study exercise that would be conducted that day.When time became an issue the concluding part of a case study exercise is given as home assignment.For example refining the Software Requirement Specifications (SRS) document, and developing a presentation for class.
ii. Classwork: The case study starts with students reading the case study description.The instructor also explains the case study to the class.This usually takes 5 minutes.Next the student teams are formed.
Randomness is used to form this team so that the students don't always work with the same person.This gives the students new perspectives and also forces them to leave their comfort zone.The case study results in a power point presentation or a discussion.Students are requested to use the room computers or their own should they need to research on a specific area.For example to make a list of open source configuration management tools they will search reliable websites.Student teams make the presentation with every team member participating in the presentation.Students and instructor both ask questions.For discussion question, questions are projected and responses from different teams are requested.
iii.Student Performance and Feedback: Teamwork, discussion participation, presentation, and work products were used to measure student learning.All students liked the hands-on experience, the teamwork and the team presentations.They felt they remained alert and were not distracted.Students felt they communicated well in their team settings and thought critically about content while completing the assignments.Students also felt the presentations of their work to the class gave them a sense of achievement and helped them polish their communication skills.Some student comments on the case studies were:  It gave real world examples of the legal aspects of the software which gave me a better understanding of the field. Was a good introduction for real life application.
 Very interesting an eye opening to how far people will take the legalities of their agreements.
 The activity allowed my group member and I to share thoughts.It was to the point and educational.
 The scenario was setup in a way that was easy to understand.
 Very creative and effective.It helps to learn more than the old way.

b. UMD
In 2016 seven Case Studies were successfully delivered to a class of 36 students in a room that was equipped with discussion tables, multiple monitors, and portable white boards.Case studies were completed within the two hour class period.
i. Homework: Prior to coming to class students read the sections of the course text book (Pressman & Maxim, 2014) assigned for that day.The lecture slides and class handouts were available on UMD's Canvas course management system.
ii. Classwork: The instructor spent 30 minutes introducing the day's topics in class.Students worked in small groups to complete the day's active learning tasks.Student groups made informal presentations to summarize their group work.The instructor led the class in a debrief.
iii.Student Performance and Feedback: The student performance on the case studies was best measured in their term project work, especially the software requirements document and the test plan document.The instructor felt their work was superior to what had been observed in the past from students in this class, but no statistical tests were performed.The student comments indicated that they enjoyed the case study activities and felt that they prepared them for work required to create the term project deliverables.They also felt that sharing ideas and insights with other students during class discussions helped them learn.They enjoyed being able to apply the material covered in the textbook to solve typical work place problems.

a. RMU
In 2016 fourteen Class Exercises were successfully delivered.Though the exercises are usually 25 minutes long the delivery duration depends on the class size.For a class of 22 students 8 exercises were completed in 4 class periods and the remaining 6 exercises took the entire period, i.e., 50 mins.
i. Homework: For class exercises, there is no homework.Students are made aware that the exercises depend on the lecture materials so they are encouraged/expected to read prior to coming to class.
ii. Classwork: All class exercises are completed in class.The instructor spends the first 3-5 minutes introducing the exercise and then distributes the student handouts.Students are usually given 10-15 minutes to complete the exercise alone.However in certain exercises students are given 20-25 minutes.The questions are then discussed in class.In most of the exercises there is no teamwork involved.However in some exercise student work in teams.If the student's response is not correct they are encouraged to make corrections keeping intact their earlier response.When class finishes students are asked to submit the assignments for grading.The answer sheets are returned to the students in the next class.
iii.Student Performance and Feedback: Teamwork and discussion participation were used to measure student learning.All students liked the hands-on experience and the work carried out small teams of 2 or 3.They felt they understood what was expected and made use of lecture slides and past discussions to answer the questions.Given the opportunity to discuss their findings many felt it was good to share their thoughts and hear the thoughts of others.Most important I t was understood that answers to some questions could vary as software development problems are not like calculus problems, i.e., everyone arrives at the same answer.Some student comments on the class exercises were:  Each group presented their though on the activity.The activity also did a great job in teaching real-world situations. Interesting and provided needed perspectives.
 It made me feel like I am in the industry.Also it opens my mind to imagine my future career.
 It was a good intro into real life application.
 This activity showed how little hiccups can turn into big problems.
 This was good instruction into the relationship between developers and customers after deployment.
 Great activity that made me look at different situations from real life.
 I thought it was a good activity to get me to start thinking critically about the subject.

b. UMD
In 2016 thirteen Class Exercises were delivered.Most of the exercises were 25 minutes long so that more than one may be delivered in the same class period.Some of the exercises were designed to take 50 minutes to complete.
i. Homework: Prior to coming to class students read the sections of the course text book (Pressman & Maxim, 2015) assigned for that day.The lecture slides and class handouts were available on UMD's Canvas course management system.
ii. Classwork: The instructor spent 30 minutes introducing the day's topics in class.Handouts were distributed and students worked in small groups to complete the day's active learning tasks.Student groups made informal presentations to summarize their group work.The instructor led the class in a debrief.
iii.Student Performance and Feedback: Student performance on class exercises was assessed using two 90 minute written examinations.The class average for the first exam was 83.9% and for the second exam was 83.6%.The students liked the use of multiple diagrams to represent requirements.They also enjoyed writing meaningful questions during requirements engineering activities to help resolve the ambiguities inherent in working with customers.They felt these activities were more engaging than just listening to a lecture accompanied with slides.The students liked the redundancy that was built in the activities that often had them look at different facets of the similar problems.They felt the group work and subsequent presentation summaries help them to improve their communications skills.They enjoyed the group work and loved using the active learning classroom.They liked being able to critique testing artifacts created by others.Occasionally they would have liked more time to complete an activity.

a. RMU
In 2016 three case study videos were successfully delivered in class.
i. Homework: For Case Study Videos there is no homework.
ii. Classwork: Case Study Video assignments are worked on during class time.Each video has multiple scenes and for each scene a set of possible discussion questions are available to the instructor.For this exercise no teams are formed, students work alone but the whole class participates in the discussion.
Students are given a description document that includes a set of discussion questions for the first scene of the video being discussed.Providing the questions helps the students view the first scene with the questions in mind.For the subsequent scenes questions are shared after the scenes are viewed.After each scene the class discusses the happenings of the scene.Instructor questions are used to start the discussion.Instructor randomly selects a student and asks the question.Other students are asked to weigh in on the answer.The instructor supplements the answer with his thoughts.After the discussion concludes the next scene is played.
iii.Student Performance and Feedback: Discussions after each scene were used to measure and understand student learning and perspective.The students felt that scenes and the dramatization of the software engineering process helped them relate to industry best practices.The questions asked, the responses from their classmates, and the thoughts of the professor helped them understand why certain things would happen at work.With the understanding of the "dos" and "don'ts" as depicted in the video students felt confident on being able to execute in the real world should situation arise.Some student comments on videos shown in class were:  Insightful exercise for understanding the process.
 It did a good job at demonstrating requirement analysis while dealing with a client.
 The video was professional a real-life situation.Maybe include more group thinking.
 Gives you a good picture of the real-world.Work place is not always friendly.However you must be a professional.
 Was good to explain how V&V would be like in real world.
 Very helpful in understanding how to deal with customers.
 It was a descent representation of a how a real client interaction takes place.
 I thought it was an effective way to facilitate a discussion

b. UMD
In 2016 five case study videos were delivered in class.
i. Homework: For Case Study Videos, there is no homework.
ii. Classwork: Case Study Video assignments were worked on during class time.Each video has multiple scenes and each scene has a set of discussion questions.For this exercise, no teams were formed, students viewed the video as a class and participated in the discussion of each scene.
iii.Student Performance and Feedback: We used the video case studies as trigger films to provide a context for class discussions.The students appreciated the irony and humor presented in the videos.In many ways, the videos showed why it is important to do things right the first time and the students thought that was good.By the end of the semester, they made many comments about understanding the importance of quality as guiding principle that needs to be pervasive thought a software development organization.

Pedagogical Assessment
Results from the Summer Workshop Surveys from University Partners indicate that the educational partners liked the format and structure of the workshop, participated in the daily workshop activities, and most could see applications of the V&V instructional materials being used in their classrooms.When attendees reported that they were unlikely to use the instructional materials, they documented the link to course objectives for their upcoming schedule as the reason.Further, the University Partners reported being satisfied with aspects of the workshop such as communication, the venue, the payment system, and travel arrangements.The workshop participants were asked to evaluate all of the active learning tools in terms of the likelihood of their using these active learning tools in their teaching and the quality of the teaching tools that they experienced.The results were summarized and analyzed.Their feedback has been incorporated in the data sets for Video Case Studies are presented in Tables 1 and 2 below.Instructions provided with the materials 1 13 Depth and breadth of materials 1 4 9 The student questionnaire data from two University Partners who used the V&V instructional activities were quite positive and showed that students were interested in the activities, saw the real-world applications, and communicated with their classmates as they solved the problems.This was corroborated in the open-ended responses, and students further reported gaining new understanding of the content from the activities in their open-ended comments.Few if any negative open-ended comments were provided by students of the University Partners who utilized the V&V materials in the classes at their universities.Data from the Principal Investigator's students also supported the idea that students recognized the hands-on applied nature of the activities and learned from the activities.
Table 3 provides data from University Partner 1's classroom.As can be seen from the results, students understood the activity, used the directions, thought the assignment involved a real-world scenario, could imagine carrying out the task in their job, and thought critically during the assignment.Most students reported providing written communication and verbally sharing in either a small or large group.Some students reported that at least one member of the team was uncertain about the steps involved in the activity.Overall, these results indicate that students recognized the hands-on, applied, and collaborative nature of the real-world activity.Many students provided positive comments about the activity in terms of recognizing the importance of the content, real-world application, collaborative nature of the activity, and hands-on nature of the activity.One student indicated his or her group did not have time to compete the activity, but that was the only negative response provided by the students.
 It helped as to getting experience for asking the right questions when getting requirements.
 This shows how important clarity is in requirements.
 Enjoyed the aspect of critically thinking about user requirements.
 It was simple but logical and informative of real world use.
 Interesting interaction in some of the problems and engineer might run into when gathering requirements with customers.
 Good experience, helped us think about different real life examples of expanding on requirements.
 Good exercise especially not really understanding requirements engineering level of detail to the extent from clients.
 Good real-world problems were brought up.
 Learned from real world application.
 I thought the activity was thought out and engaging.
 Good exercise with classmates.
 Details are important!More people to find more questions! It was good exercise, nice practice.
 I think this activity makes you think about many different questions.
 I enjoyed it.We discussed a lot of gray areas that occur.
 It helped me think less vaguely about planning.
 Fun activity, wish we had more time to finish it.
 Great activity.
 Definitely the best so far.
 Seemed pretty straight forward.
Overall, the data from University Partner 1 indicate the students enjoyed and recognized the application involved in the Case Module: Understanding User Requirements.
The same active learning tools were delivered at implementation University Partner 2 (UMD) and the student survey data for the same set of questions shown in Table 3 showed that across the activities, students understood the activity, used the directions, communicated about the content in a small group, provided written communication, and thought critically during the assignment.Most students viewed the activity as a real world application and could imagine carrying out the activities as part of their jobs.A small number of students were uncertain how to carry out the activity.It also appears that instructor did not utilize large group or formal presentations of these activities.Overall, as with the results from University Partner 1, these results from University Partner 2's classroom indicate that students recognized the hands-on, applied, and collaborative nature of the real-world activity.
Almost all of the comments from the students related to the Exercise: SRS Review were positive:  It was awesome.It was helpful too.
 Very informative and a good process to go through.I believe it will be a positive application to a real work scenario.
 It was a neat experience finding defects for this SRS.I enjoyed it.
 The activity went well but I seem to miss some of the defects in the SRS.The yield of my individual defect identified was small.The major defects I found were overlooked by most of the team.
 Useful to practice what we learned in a real life scenario.
 I learned a lot from this activity.As I was preparing the defect log, I found several errors in the SRS document but I felt that I was being too critical and that the errors I was pointing out were unimportant.But after completing this activity, I now know to be critical and have more errors than too few.
 This was helpful in that in provided real hands-on experience doing software requirements' inspection.This was my very first time performing this activity and it was immensely helpful.
 I believe activity is extremely applicable to real world inspections and would help me in the future as an SQA inspector.
 Being familiar with the inspection meeting.Did preparation of the inspection.
 I prefer hands-on activities that mimic scenarios that will occur in my professional career.
 The activity is a good activity; we practice what we have studied in class.
 I think it was a useful activity and I learned more about the other students' perspectives.
 It is interesting and it showed how easy it is to have big issues appear in an SRS document.
 This activity cleared up a lot of things about the inspection process.
 This activity provided valuable experience in SRS review similar to what I have experienced in an internship in previous summers.
 Cool.Helps us understand of inspection procedure.
 Good hands on activity.
 I thought this was extremely beneficial and taught great real world application.
 This activity is practical and interesting.I did a lot of research on SRS inspection online.Also read a few papers of different types of SRS defects, really learned from it.Enjoyed teamwork with classmates, made friends, we actually met once before real inspection and helped each other.
 Small time constraint, couldn't see all major defects.
Table 4 captures student feedback at RMU after a successful delivery of a case study module titled "Understanding User Requirements".The class size was 29 however some students did not turn in the assessment and few students were absent on the day this exercise was delivered.40% of the students were also international with English not being their first language.They had some issues understanding the survey questions.The assessment results show that most of the students who were in the class when this case study exercise was conducted understood the exercise and were able to complete it.
Table 4. Student feedback at RMU for a case study module

Question Yes No
My team and I understood the purpose of the activity.23 My team and I could complete the activity with the directions that were provided.

1
At least one member of my team was uncertain of how to carry out the steps of the activity.

19
The activity used a real-world application.

23
I could imagine carrying out this activity as part of my job.I thought critically about content while completing this assignment.23 Provided your overall thoughts about this activity: -This activity showed us how there is a lot of short cuts we take when speaking.We need to be able to clearly describe what we want and need.
-Group discussions are helpful only if you are in the right group.
-After this exercise, I have a good idea of writing a requirement.
-This activity allowed me and my teammate to share thoughts.
Table 5 captures student feedback at UMD after a successful delivery of an exercise module titled "Test Cases for a Given Requirement".The class size was 35 however only 23 returned the surveys.A few students were also absent.The assessment results show that most of the students who were in class when this exercise was conducted understood the exercise and were able to complete it.They also had to work in smaller groups and then participate in the class discussion.Students who provided their thoughts were supportive of the exercise.
Table 5. Student feedback at UMD for an exercise module

Question Yes No
My team and I understood the purpose of the activity.21 My team and I could complete the activity with the directions that were provided.21 At least one member of my team was uncertain of how to carry out the steps of the activity.

19
The activity used a real-world application.20 1

Conclusion and Recommendations
As student learning retention depends on knowledge retention activities delivered in different settings it is important to identify and incorporate delivery strategies that meet course and/or module learning outcomes.The paper discussed the design, development and delivery of several active learning tools for improved pedagogy of software V&V education.The flipped classroom strategy was also used to effectively incorporate and deliver the active learning tools developed at RMU and customized to suit their needs at UMD. Teamwork, discussion participation, presentation, and work products were used to measure student learning.Student work was found to be better to what had been observed in the past from students in their classes.Students surveyed liked the hands-on experience, the teamwork, and the team presentations.They felt they remained alert and were not distracted.Students also felt they communicated well in their team settings and thought critically about content while completing the assignments.Student comments indicated that they enjoyed the activities and felt that these activities would help them for future work in these areas.

Figure 2 .
Figure 2. Active learning tools in project website

Figure 4 .
Figure 4. Course contents in Blackboard

22 1 I
communicated verbally in a small group while completing this activity.22 1 I communicated verbally in a large group while completing this activity.3 20 I/we provided written communication as part of this activity.22 1 I/we made a formal presentation as part of this activity.1 22 This has helped students to prepare and be punctual in class.Student performance in this course is measured in terms of ABET outcomes.A class assessment performed in Spring 2013 when case studies were not available showed a weakness in learning outcome "e" (an ability to identify, formulate, and solve engineering problems) where less than 60% of the students scored better than 80% in the assessment tasks.When the case studies were delivered in the Spring 2015 term the student performance in outcome "e" was excellent range (>=90%).This presents clear evidence that the case study based teaching method is more effective in delivering an ability to identify, formulate, and solve engineering problems to the students.The developed tools have been taught in spring 2014, spring 2015, and spring 2016 semesters.Experience from previous delivery is used in course planning for the succeeding delivery.Likewise findings from the assessments are used to revise the developed active learning tools.CIS 375: Software Engineering 1 is the first software engineering course taken by all SE, CIS, and DF majors.This course was created in 1997 as a general software engineering lecture course and is currently offered as 4 credit hour class.The topics covered include software process models, requirements engineering, requirements modeling, project management, configuration management, software quality, software architecture and design, user experience design, design patterns, and testing.Students complete a team software development project and write several milestone documents as part of the project deliverables.During 2016 active learning tools, developed at RMU, were examined, and adapted for use in CIS 375.Several additional activities were developed at UMD to cover topics outside the scope of ENGR 3400 as taught at RMU.In the Fall 2016 semester CIS 375 was taught using a flipped classroom model with majority of the 4 contact hours being used for engaged/experiential learning.5% of the total student grade is allocated to class participation and 75% was allocated to term project deliverables.The remaining 20% of the student grade came from the two in class examinations.Experience from this delivery is being used to revising the next offerings of this course and the active learning materials.
configuration management, and software testing to provide student's knowledge relevant to the software development industry.To ensure adequate contact hours to cover the contents contact hours for this 3 credit course was increased to 4 hours.After the active learning tools were developed in 2014 the course is being taught using the recommended flipped classroom model with majority of the 4 contact hours being used for engaged/experiential learning.40% of the total student grade is allocated to class assignments.

Table 1 .
Strategic partner summary of similarity and likely use of Video Case Studies

Table 2 .
Strategic partner summary of quality of Video Case Studies

Table 3 .
Student evaluations of individual instructional activities from University Partner 1 for case module: understanding user requirements could imagine carrying out this activity as part of my job.
-Good idea for those who have less experience -Good exercise -It was good -Helped clear up the test case issue