P18711: MSD Team Assignment Process Improvement
/public/

Integrated System Build & Test

Table of Contents

Team Vision for Integrated System Build & Test Phase

The team planned to fully integrate student survey data, student SIS data, and project survey data into the Excel calculation document and the Python optimization. Doing so would involve iterative testing to ensure the format of the data would be feasible for the program. Once Spring project and student data was correctly running in the system, the fall data would be properly converted to the acceptable format for final testing.

The team was able to accomplish what we had planned during this phase. Spring assignments have been made with the Python optimization and have been compared to the actual assignments made by the MSD Office. The scores of students were compared between actual and simulated results.

The team has run the system with Fall data and the system was debugged to handle more information. The final Fall assignment results are not completely accurate to what the system is designed for as the student and project data was not collected using the same modified methodologies. The team will simulate what student and project data could have looked like and compare the assignments to the actual Fall assignments.

Test Results Summary

The original flow of data going through the MSD Office from project proposers, students, and guides was compared to the future state of team assignment data. This diagram highlights the differences that will be implemented in the upcoming Fall semester. An importance is placed on the reduction of manual data input steps for the MSD Office. This will reduce time taken to complete assignments and chance of errors made with missing data.
Test Plans

Test Plans

The following engineering requirements have been met by this phase. The lines noted as "in progress" are planned to be completed within the next two weeks before customer hand off. Completing the final test of Fall student and project data will wrap up any remaining uncertainties. The two items marked in yellow as caution are currently accounted for in the assignment process manually instead of automatically being calculated in the algorithm. In other words, the process can incorporate additional constraints, like dual degree or class section availability, by manually assigning a student to a matching project. The way that the data is collected will make it easier to address these constraints and keep them standard. The staffing scenarios in ER 13 can also be manipulated manually in the Google Sheets project list. The system is set-up to re run the optimization within minutes of inputed changes.

Test Plans

Test Plans

Risk and Problem Tracking

The updated risk matrix shows most risks dropping to a zero probability and three remaining with low probabilities. Risk 4 remains because all issues encountered by the MSD Office cannot be predicted. Risk 6 remains because the ease to modify the system as needed is not exactly predicted. Risk 10 remains because the team will not be able to predict and document any change that will be needed to made in the system in future years.

To address the possible risks, the teams contacts will be available for the MSD Office.

Risk Management

Risk Management

Functional Demo Materials

Meeting Date: 4/4/18 1:30-3:00PM

Location: GLE-4435 Design Floor Conference Room

Attendees:

Agenda:

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

Slide Deck: to be uploaded after design review meeting

Plans for next phase

The team will be handing off all documents to the MSD Office that will include:

The team will be completing the following for MSD:


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