Adapting Cooperative Learning to Teach Software Architecture in Multiple-Role Teams Steve Chenoweth, Mark Ardis and Cheryl Dugas.

Slides:

Advertisements

Similar presentations

Delivery of Industrial Strength Middleware Federated Strengths Agility & Coordination Prof. Malcolm Atkinson Director 21 st January 2004.

Advertisements

IT Issues and Support Structures Simulation Education and Complex Technology Based Practice.

Unit 1, Lesson 4 Software Development Cycle AOIT Introduction to Programming Copyright © 2009–2012 National Academy Foundation. All rights reserved.

Active and Cooperative Learning in an Introductory Computer Science Course Dr. Cheryl A. Dugas.

Definitions and elements

Project Maths - Teaching and Learning Relative Frequency % Bar Chart to Relative Frequency Bar Chart What is the median height.

CEEBL Centre for Excellence in Enquiry-Based Learning Aligning collaborative learning theory with technology Adele Aubrey, Mark Jasper & Anna Verges The.

Cooperative Learning What is Coopeartive Learning ? And

 Assessment in the natural environment  Recognize and reinforce multiple modes of communication.  Train communication partners.

1 Interviewing CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 13, 2004.

1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004.

The Software Team CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute September 7, 2004 In the book – This is Ch 4.

Chapter 9 FACILITY MANAGEMENT.

Team Skill 6 - Building The Right System Part 2: Traceability, Change and Quality (Chapters of the requirements text) CSSE 371 Software Requirements.

Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.

Uml and Use Cases CS 414, Software Engineering I Mark Ardis Rose-Hulman Institute January 9, 2003.

Slide 1 Requirements Wrap-up (Chapter 31 of requirements text) and Interaction Design: Introduction (Chapters 1 of Interaction Design text) CSSE 371 Software.

1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) CSSE 371, Software Requirements and Specification Don.

1 Team Skill 3 - Defining the System (Chapters of the requirements text) CSSE 371 Software Requirements and Specification Don Bagert, Rose-Hulman.

Team Skill 6 - Building The Right System Part 1: Applying Use Cases (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.

Diversity of Interaction in a Quality Assurance Course Mark Ardis, Rose-Hulman Institute Cheryl Dugas, Indiana State University FIE 2005.

1 Quality Assurance in Construction and Maintenance (Section 13.4 of Maintenance Text; Chapter 20 of Code Complete) Steve Chenoweth CSSE 375, Rose-Hulman.

1 Team Skill 1 - Analyzing the Problem (Chapters 5-7 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman.

Multiple current exposure without mark detection Possible? Tolerance? Using only the 4 th lens: –1 st exposure: 0.1nA, 2 nd aperture (min. current) –2.

Test-First Teaching Extreme Programming Meets Instructional Design in Software Engineering Courses Mark A. Ardis Cheryl A. Dugas Rose-Hulman Institute.

1 Module 4: Empowering Marginalised Actors Purpose: Participants understand what can prevent marginalised actors from participating in the PMSD process.

Mechanical Engineering Building Blocks to Success.

Formal Cooperative Learning: Text Comprehension/Interpretation Karl A. Smith Laura Apol.

STUDY SKILLS CHAPTER 13.

T Software Development Project I Customer Info Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.

Developing a Lesson Plan Identify elements that can make up a successful lesson. Design a lesson to meet the needs of a specific group of learners. On.

Leadership training for supporting the implementation of the new KCF Training for improving governance, leaderships and school management in municipalities.

Course Introduction Software Engineering

Essential Components for Group Work  Interpersonal and Small Group Skills  Positive Interdependence  Individual Accountability  Face-To-Face Interaction.

Cooperative Learning Why, What, and How. 3 Types of Learning.

Cooperative Learning in the eMINTS Classroom May 24, 2006.

2009 Institute for Staff Development Students Today, Leaders Tomorrow 21 st Century Skills.

Yina Arenas Mona Sergi Tamal Saha.  Focus of the project  Nanosim as a case study ◦ Role playing simulation ◦ Different types of participants and services.

Cooperation in the Classroom. Learning how to work cooperatively Student Teacher Modeled Shared Guided Independence Practice Practice Coaching Coaching.

Evaluating Individual Contribution Toward Group Software Engineering Projects J. Huffman Hayes, T. Lethbridge, D. Port, USC Int’l Conf. on Software Engineering.

3D based Intelligent Interactive House Building System 1 ML WE - 01.

Cooperative Learning Professional Development Nov./Dec.

Roger Johnson & David Johnson

Structuring Cooperative Learning: Examples from Small group learning in higher education (SGLHE) Karl A. Smith University of Minnesota Cooperative.

Cooperative Learning Explain meeting clocks and have them set the appointments.

Formal Cooperative Learning: Text Comprehension/Interpretation Karl A. Smith Laura Apol.

Theories of Agile, Fails of Security Daniel Liber CyberArk.

1 Effective Interventions for Struggling Readers Comprehension: The Essence of Reading Dr. Melissa Comer Tennessee Tech University.

The iBraille Challenge Mobile App GITWL, 2015 Presented by: Cheryl Kamei-Hannan California State University, Los Angeles Ben Pomeroy Braille Institute.

U2-L10 October 10, 2008 A.Get out your newspaper article final draft. B.Answer True or False: 1.Throughout history, technology has been a major force in.

INDEPENDENT PRACTICE AND CLOSURE Lesson Planning.

Cooperative Learning Dr. Chinfen Chen. What Is Cooperative Learning? Fostering students ’ ability to work with and appreciate others. Fostering students.

Roger Johnson & David Johnson Cooperative Learning.

Managing a Classroom for Science Learning. Reading Assignment Chapter 12 in Teaching Science to Every Child: Using Culture as a Starting Point.

Systems Analyst (Module V) Ashima Wadhwa. The Systems Analyst - A Key Resource Many organizations consider information systems and computer applications.

© 2011 RIT Department of Software Engineering One large website. Complex. One small software upgrade. Easy. One 90 minute outage. Priceless? No! It was.

Guidance for Graduate Students and Early Career Faculty Karl A. Smith University of Minnesota Cooperative Jigsaw Nanyang Business School.

Cooperative Learning. Why?  Cooperative learning groups can:  Promote student learning and achievement  Increase students’ retention of knowledge 

Seating OK? Where guests properly introduced? Started on time? Materials OK (flag, etc.)? Comments Did the evaluation team appear professional? Comments.

C OOPERATIVE L EARNING M ODELS. B ASIS OF C OOPERATIVE L EARNING 1. Positive Interdependence 2. Face-to-Face Interaction 3. Individual & Group Accountability.

Presented by Sam Supervised by Prof. Michael Lyu

Operational Feasibility

Skills Practise You will undertake a 5 min (maximum) mock interview – 3 questions to answer Each person will have a role. Roles: Interviewee, Interviewer/Camera.

Kagan 101: Cooperative Learning

Paris School District Home of the Eagles

Data Structures and Database Applications ACST 3330

1st language words & bits 2nd language words & bits

Chapter 10: Human Side.

Ann D. Murray School of Family Studies and Human Services

Overview of BSSE at Rose-Hulman Institute of Technology

Presentation transcript:

Adapting Cooperative Learning to Teach Software Architecture in Multiple-Role Teams Steve Chenoweth, Mark Ardis and Cheryl Dugas

2 Outline Challenges teaching software architecture Cooperative learning Experience at Rose-Hulman and RIT

3 Architect in the Middle Maintainer Easy to Maintain User Easy to Use Developer Easy to Develop Customer Cheap to Build Architect

4 Cooperative Learning Small teams of students Positive interdependence Face-to-face interaction Individual accountability and personal responsibility Interpersonal and small-group skills Group processing

5 Course at Rose-Hulman Junior-level course in Software Architecture and Design for BSSE Students: –Invented projects –Designed architecture –Implemented skeleton of system

6 Small Teams SallySarahSamAlanAlexAliceMarkMaxMaryMaggieBenBethBertBecky

7 Projects - Teams of Teams P1: P2: P3: P4: Customer Architect Developer

8 Meetings - 1st 20 min Customer Ben Customer Beth Customer Becky Architect Mark Architect Mary Architect Max Architect Sam Architect Sally Architect Sarah Customer Alan Customer Alex Customer Alice

9 Meetings - 2nd 20 min Architect Ben Architect Beth Architect Becky Customer Mark Customer Mary Customer Max Customer Sam Customer Sally Customer Sarah Architect Alan Architect Alex Architect Alice

10 Course at RIT Senior-level course in Software Architecture for BSSE Students: –Invented projects –Designed architecture Special meeting rooms used

11 RIT Meetings - 1st 15 Minutes Room 1 Room 2 Customer Ben Customer Beth Developer Bert Developer Becky Architect Mark Architect Mary Architect Max Architect Maggie

12 RIT Meetings - 2nd 15 Minutes Room 1 Room 2 Architect Ben Architect Beth Architect Bert Architect Becky Customer Mark Customer Mary Developer Max Developer Maggie

13 RIT Meetings - 3rd 15 Minutes Room 1 Room 2 Architect Ben Architect Beth Architect Bert Architect Becky Architect Mark Architect Mary Architect Max Architect Maggie

14 Results Role playing is essential for software architecture courses Cooperative learning is effective at individual and team levels Participation on multiple projects is important

15 Slides Available