P18711: MSD Team Assignment Process Improvement
/public/

Problem Definition

Table of Contents

Team Vision for Problem Definition Phase

Project Summary

Twice a year for the Spring and Fall Semesters, Multidisciplinary Senior Design Projects are assigned to engineering students based on a variety of factors. The current process to create project assignments is manually completed by faculty and staff over multiple weeks. Information regarding students' disciplines, preferences, and class section is collected through a survey and results are referenced against available projects to create teams.

This process has been used for creating team assignments for multiple years. As enrollment for Senior Design has been increasing, challenges faced for creating optimal team assignments have also increased. Tracking fluctuating projects, new student additions, and class section limits in multiple locations introduces chances of error in the system.

The goal of this project is to improve the process for creating team assignments to increase efficiency and limit errors while maintaining the current level of effectiveness. To accomplish this, the current student survey will be reevaluated and streamlined for better collection of results, the logic in dividing students to projects will be captured, and project selection criteria will be prioritized.

Use Cases

The following diagram illustrates the current process that is used for Team Assignments. Problem areas are highlighted in steps completed after student surveys are completed where student enrollment and project proposals are changing.
Current State

Current State

The following two use cases identify ways that the new system should be able to create Team Assignments when student enrollment changes after the student survey is completed and the first round of Team Assignments have been made.

Use Cases: Change in Student Enrollment

Use Cases: Change in Student Enrollment

The following two use cases identify ways that the new system should be able to create Team Assignments when project proposals are added or modified and when projects need to be removed.

Use Cases: Change in Projects

Use Cases: Change in Projects

Project Goals and Key Deliverables

The end goal of this project is to build a program that will be capable of increasing levels of effectiveness in assigning MSD I & II projects to seniors. This means that this program will be capable of collecting information on student preferences, student capabilities and project needs. Ultimately, the system will streamline the assignment process and increase student satisfaction in the project they were assigned without missing any students in the process.

Deliverables:

Constraints

Project Constraints

Within this project the main constraint outside of the outlined goals is to keep all personal and private information that students and SIS potentially provide safe.

System Constraints

Customer Requirements (Needs)

Customer Requirements

Customer Requirements

House of Quality

House of Quality

House of Quality

Engineering Requirements (Metrics & Specifications)

Engineering Requirements

Engineering Requirements

Design Review Materials

Meeting Date: 9/18/17 2:30-3:00pm

Location: GLE-2255 Mobile Conference Room

Attendees: Beth DeBartolo, Chris Fisher, John Kaemmerlen

Agenda:

Meeting Notes: to be recorded in the team's OneNote documents

Slide Deck: Problem Definition Review Presentation

Plans for Next Phase


Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation