Build & Test Prep
Table of Contents
Team Vision for Build & Test Prep Phase
Test Plan Summary
Each Engineering Requirement has been mapped to a test plan to ensure the satisfaction of the specification. The desired values for each metric have been updated and will be used to validate the test plan results. The status of each test plan is summarized with an icon and color described in the key.
Test PlansDetailed test plans have been developed around three main functions of the assignment process. Various Engineering Requirements fall into these categories and have been included on each one. Each test plan is designed to be sequential and depend on the outcome and results of the previous test plan. This iterative process will be similar to an agile method of software development.
- Testing System Functionality
- Testing Use of System
- Testing Training of System
Student Satisfaction Survey ResultsA survey was sent to students finishing MSD I and MSD II to gather data on what they thought of their assignment. A total of 51 students completed the survey.
First the students were asked how they were placed on their project teams and an equal amount were either placed on a project that they had requested as a top choice or not placed a a project that was a top choice. The remaining third of students were either on a student proposed project or didn't have a preference.
The results of this question show that there could be some improvement to the percentage of students that are placed on a project that they have selected as a top choice.
Next the students were asked how well they thought their skills and interests were matched to their assigned project. In both cases a majority of students specified that an expected amount, or over an expected amount of skills were used and their interests were congruent.
Students overall satisfaction with their assignments was also rated on a scale of 1-5 and results were positive. The negative responses for this question may be skewed due to students not satisfied with their team members rather than their team assignments.
The results of these questions show that, generally, skills and interests are satisfied by project assignments and some improvement could be made to increase the percent match even more.
Spring Assignment Results
Risk and Problem TrackingDuring this phase, a problem tracking device was created to document any problems or issues that arise during testing in MSD II. This tracker will include pertinent information on the problem and how a solution will be carried out. Any bugs in the coding aspect of the system will be documented here to ensure the team is aware of road blocks and progress.
The risk tracker has remained the same as the last review and can be found on the Planning & Execution page.
Design Review MaterialsMeeting Date: 1/24/18 1:15-1:30PM
Location: GLE 4425 Senior Design Floor
Attendees: Beth DeBartolo, Chris Fisher, John Kaemmerlen
- Test Plans
- Problem & Solution Process
- Satisfaction Survey Results
- Spring Assignment Results
- MSD I Post Mortem
- Project Plan
- Next Steps
Meeting Notes: to be recorded in the team's OneNote documents
Slide Deck: Build & Test Prep Review Presentation
Plans for next phase
- Completed Excel Macros to format student and project data
- Automated calculation of student scores
- Draft of Python code to be used for optimization
- Updated EE skills list and review of other discipline skills