Sharad Oberoi and Susan Finger Carnegie Mellon University Tracking Design Knowledge in Engineering Student Projects around Course Milestones.

Slides:



Advertisements
Similar presentations
CONCEPTUAL WEB-BASED FRAMEWORK IN AN INTERACTIVE VIRTUAL ENVIRONMENT FOR DISTANCE LEARNING Amal Oraifige, Graham Oakes, Anthony Felton, David Heesom, Kevin.
Advertisements

Design, prototyping and construction
Instructional Technology Enhancing Education The world we live in Internet use doubles every 100 days. Radio was in existence 38 years before 50 million.
PAYS FOR: Literacy Coach, Power Hour Aides, LTM's, Literacy Trainings, Kindergarten Teacher Training, Materials.
Register Laulima Workshop for Instructors Solutions to help you engage your students through Laulima.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
CSE 470 : Software Engineering The Software Process.
Learning and Teaching Conference 2012 Skill integration for students through in-class feedback and continuous assessment. Konstantinos Dimopoulos City.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
Team Thinking Time Variation of Design “Story Telling” in Engineering Design Teams Andy Dong Key Centre of Design Computing and Cognition University of.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
CS 501: Software Engineering
CS 501: Software Engineering
Participatory Design for Sustainable Development Matthew Kam Feb 7, 2003.
Lecture 3: Shared Workspace and Design Coordination Dr. Xiangyu WANG.
Lecture 3: Shared Workspace Awareness Dr. Xiangyu WANG 11 th August 2008.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
DesignWebs to Support Engineering Design Student Projects Sharad V. Oberoi.
Customer Focus Module Preview
Chapter 2: Business Intelligence Capabilities
2-1 Chapter 2 Information Systems for Collaboration.
S/W Project Management
© 2014 Blackboard Inc. All rights reserved.. Describe the different tools that can be used to keep students informed. Announcements Course Messages.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
CISIP Writing Framework Approaches to Teaching and Learning Science and Writing.
Project Management Development & developers
Paul Bourke DT211/3 & DT228/3 Team Project Paul Bourke Module Web Page:
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CS 3610: Software Engineering – Spring 2009 Dr. Hisham Haddad – CSIS Dept. Class Project OO Design Document Here is what you need to do for your class.
Classroom Basics for instructors
Certificate IV in Project Management Course Structure Course Number Qualification Code BSB41507.
Sharad Oberoi and Susan Finger Carnegie Mellon University DesignWebs: Towards the Creation of an Interactive Navigational Tool to assist and support Engineering.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Software Engineering Management Lecture 1 The Software Process.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Software Life Cycle Models. Waterfall Model  The Waterfall Model is the earliest method of structured system development.  The original waterfall model.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
1 Overview Comments on notebooks & mini- problem Teaching equitably Analyzing textbook lessons End-of-class check (Brief discussion) Introduction to multiplication.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Certificate IV in Project Management Certificate IV in Project Management Course Structure Course Number Qualification Code BSB41507.
Laulima Workshop for Instructors Solutions to help you engage your students through Laulima.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Sharad Oberoi Carnegie Mellon University DesignWebs: Learning in Engineering Project Teams.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Enhancing e-learning experience with online social networks Published in IET Communications J.J.P.C. Rodrigues, F.M.R. Sabino, L. Zhou Reporter: Yu Chih.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
ECE791 Senior Design Experience Project Requirements and Timeline.
Sharad Oberoi and Susan Finger Carnegie Mellon University Interactive Design Navigation Tools.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
COLLABORATIVE WEB 2.0 TOOLS IN EDUCATION USING WIKIS & BLOGS IN THE CLASSROOM.
PED 212 Entire Course PED 212 Week 1 DQ 1 Current Issues  PED 212 Week 1 DQ 1 Current Issues  PED 212 Week 1 DQ 2 Critical Thinking  PED 212 Week 2.
Designing for the Next Generation of Engineers
Software Engineering Management
Maja Holmes and Margaret Stout West Virginia University
Project life span.
Chapter 6: Database Project Management
IEEE Std 1074: Standard for Software Lifecycle
Automatic Extraction of Conceptual Maps from Design Team Documents
Design, prototyping and construction
Appendix B Agile Methodologies
Design, prototyping and construction
Presentation transcript:

Sharad Oberoi and Susan Finger Carnegie Mellon University Tracking Design Knowledge in Engineering Student Projects around Course Milestones

Collaborative learning in design Goal –Develop tools that allow instructors to monitor the progress of project-based courses and assess student interactions outside the classroom

Collaborative learning in design Assertions –Most learning in design classes takes place in team meetings and in individual activities undertaken to help meet team goals –Prior research has shown that noun phrases can be used as surrogates for design concepts –For successful design teams, the number of distinct noun phrases expands at the initial stages of the project and contracted as the project progresses Mabogunje, A., Measuring Conceptual Design Performance in Mechanical Engineering: A Question Based Approach, Doctoral Dissertation, Stanford, CA: Stanford University, 1997.

Outline Setting –Engineering design capstone course –Ongoing project to understand collaborative learning by student design teams

Student design projects Characteristics –Students bring together knowledge from different sources: collaborate among themselves, share design knowledge negotiate with each other, faculty members and the client, in order to create engineering artifacts. –Students reuse previous knowledge and create new knowledge within the context of the problem.

Capturing in-process data For 7 years, RPCS has used the Kiva for team collaboration –Light-weight collaboration tool –Combines functions of and bboards –Widely accepted and liked by student teams; it feels likes chat and meets their needs –Each year’s Kiva has hundreds of threads and thousands of posts and files  We have 7 years of data of all the team conversations and files that would normally go through or chat

Kiva collaboration tool Takes advantage of students’ willingness to send , use IM, post on newsgroups, send text messages Allows students to cross-post and to post to teams in which they are not members Design goal: Create an interface that students perceive to be equivalent to their preferred communication modes; that is: make it feel like chat

Design education testbed RPCS: Rapid prototyping of computer systems class of Spring 2008 –Interdisciplinary, capstone design course –Class of 25 students taught by 2 instructors, 1 TA –Project on the design of a virtual coach called Guru for new power wheelchair users –The aim was to monitor wheelchair users and assist the clinician in assessing if any revisions were required in the prescriptions –Major teams in the class were: Chair, Clinician, Infrastructure and Sensors

RPCS 2008 Timeline Phase 1: Requirements exploration and definition, benchmarking, and a rough conceptual prototype Phase 2: Creation of a functional prototype that satisfies most of the feasibility constraints Phase 3: System integration and more design iterations to make final refinements

Approach Discussion posts and attachments of the class were converted to text Noun phrases were extracted using the Stanford part-of-speech tagger Number of distinct noun phrases was counted for each group

Approach Advantages of using noun phrases –Noun phrases act as an objective design document metric for predicting design process performance –The pattern of distinct noun phrases at every stage of a design artifact can reveal insights about the state of the project

Approach Three analyses were done to attribute nouns to students –First analysis: Includes only the documentation posted to the four main teams in the project –Second analysis: Includes only the documentation made by members of the teams regardless of the thread in which it was posted –Third analysis: Compares the time-based trends of noun phrases in the editing/presentation and design categories within the documentation Transformation of design concepts across phases was tracked

Results: First Analysis Extracts noun phrases only from the documentation posted to the four main teams in the project The peaks decrease with time Instructor documents included in the analysis, so design contributions made by the individual teams are not adequately reflected in their vocabulary

Results: First Analysis Aggregated noun phrase counts by week Mid-term break Phase-1 Phase-2 Phase-3

Results: First Analysis Distinct noun phrase counts by week

Results: Second Analysis The activities of the team members were tracked throughout the semester, instead of analyzing only the material posted in the teams’ threads This process attributes only the noun phrases used by members of a team to the team’s knowledge Peaks of distinct noun phrases expanded at the initial stages of the project and contracted as the project progressed

Results: Second Analysis Aggregated noun phrase counts by week

Results: Second Analysis Distinct noun phrase counts by week

Results: Third Analysis The editing/presentation and design activities were tracked separately to understand the ex­ternalization done by students around project milestones The noun phrases in the editing/presentation documents vis-à-vis the design documents and discussions were compared Student design activities were found to not necessarily follow the class deadlines, unlike those including editing of the project reports or presentations

Results: Third Analysis Noun phrase counts in design activities by week

Results: Third Analysis Noun phrase counts in editing tasks by week

Transformation of Design Concepts across Phases Some design concepts are introduced by teams in project-based courses but wane with time, i.e., they are either abandoned or transformed into a related concept in the final design Reflects how student understanding about the artifact is evolving through the project

Transformation of Design Concepts across Phases Noun phrases used by the Sensors Team to refer to the tilt of the wheelchair

Conclusions The paradigm of using noun phrases from student documentation to assess design team progress has been accepted for the past two decades. This research takes the paradigm forward and shows how noun phrases in a design project can help to measure how the class has performed from the perspective of prior research models of expan­ sion and contraction of vocabulary for successful projects. The paper also shows what activities the students are engaged in outside the instructors’ purview

Conclusions When the instructors have access to such information in real-time, they can actively monitor the progress being made by the teams They can also intervene in a timely manner in case they detect a potential teachable moment.

Questions?