Build-Test Review (B/TR)
In this phase, the system design is translated into a physical and/or software solution. This will involve developing software, building hardware components, integrating off-the-shelf products, or a combination of these approaches (depending on the project). At the completion of this stage, the primary development work will be complete. Teams should have a functioning, though not yet optimized, prototype or demo that will be refined and fully tested for performance during the final weeks of the semester.
** TWO PAGE LIMIT for Executive Summary. Final Design Package Outline is a separate document and does not count in the two page limit.
Executive Summary
Project Title: [Your Project Title]
Team Name: [Your Team Name]
Date: [Submission Date]
Overall professionalism (10 points)
1. Project Overview (10 points)
- Overview of project. Include Key Success Measures and current value proposition.
2. Project Completion Status (30 points)
Depending on your project and its current status, consider including the following discussion points:
- Have you made significant changes to your design since the last design review? If so, what prompted the changes? How have you documented those changes? Have the changes introduced additional risk?
- What is the true status of your project at this point? Does your solution work? Are there things that are not working? Explain transparently.
- Have you made all updates and additions to your documentation so that it is current with your project progress?
3. Project Testing (30 points)
Testing is a critical step in system design and ensures that your product meets the requirements of your sponsor.
- Explain what testing has been done. Is that testing adequate to fully verify functionality?
- Summarize your test results. Reference test artifacts.
- Does your project meet your requirements? If not, what is your plan to optimize your product so that it does?
- Do preliminary test results indicate that the project outcome will be successful?
- Have you done a preliminary validation with your sponsor to ensure the final product will meet their needs?
4. Schedule and Work Plan (10 points)
- Summarize key points of your detailed work plan, including specifics for each team member from now until the end of the project. (A screenshot of your project management tool should be included as an artifact with a reference to it in this section). A recovery plan should be evident if you are behind schedule for your project.
5. Outline for Final Design Package (10 points) (THIS SHOULD BE A SEPARATE DOCUMENT AND DOES NOT COUNT AS PART OF THE TWO PAGES FOR THE EXECUTIVE SUMMARY)
- This should include a thorough outline of all the documentation that will be included in your final design package and will form the basis of the Final Design Package. This should be a SPECIFIC LIST of each individual document in the order they will be included in the Final Design Package.
- What documentation still needs to be completed to provide your sponsor with a complete design package? DENOTE which items in your outline are complete and which still need to be completed.
Possible Documentation
At this point, the team should be working toward a Final Design Package. The Final Design package should include everything needed for complete transfer to the sponsor FOR YOUR PROJECT. Final versions of each document are not expected at this time, as some results will likely be forthcoming and final refinements will still need to be made.
Put yourself in the place of your sponsor. If you were an engineer seeing this project for the first time and were tasked with continuing or implementing the project, would you have everything you need to do that?
Presentation
- BRING SOME FORM OF A DEMO OF YOUR PROJECT TO THE PRESENTATION. This could be a physical prototype, a short video of your working prototype/software, or whatever demo makes sense for your project.
- Updated project overview
- Updated requirements with sponsor approval
- Status of design and prototyping
- Roadblocks
- Testing results so far
- List of design documentation that will be delivered to sponsor as Final Design Package
Grading Criteria
Executive Summary
100 points
1. (10 points) Overall professionalism, grammatically correct, make sense overall
2. (10 points) Overview
- Has the team succinctly and intelligibly summarized the concept architecture?
- Has the team thoughtfully considered the value proposition and how their work impacts that?
3. (30 points) Project Completion Status
- Are changes since the DDR clearly addressed?
- Is the status of the project obvious and clearly explained?
- Is it clear what updates and additions still need to be made to your documentation?
- Does the team understand what still needs to be done/can be done?
4. (30 points) Project Testing
- Has adequate testing been done to verify results so far? If not, does the team demonstrate a clear understanding of what additional testing must be done?
- Are test results clear, and have they been well documented?
- Has the team clearly shown whether or not the project meets the requirements?
5. (10 points) Schedule and Work Plan
- Does the team have a detailed plan for the final stretch, including specific timelines and team member assignments?
- Has the team thoughtfully considered the documentation?
6. (10 points) Final Design Package outline
- Based on the outline, does it look like someone could take the Final Design Package and continue development or implement the project with ease?
- Does the outline list every document, repository, etc that the sponsor will need?
- Is it evident which documents, repositories, etc are complete and what still needs to be worked on?
Presentation
(100 points total)
1. (10 points) Overall professionalism, everyone on time, slides are clean and clear
2. (10 points) Updated Project Overview (1 slide)
- Has the team succinctly and intelligibly summarized the project and its impact to the sponsor?
3. (10 points) Updated Requirements (1-2 slides)
- Are changes to the original plan addressed?
- Are changes documented?
- Does the team have sponsor approval for changes?
4. (30 points) Status of Design and Prototyping (slides/demo)
- Did the team provide a demo of a working system?
- Have the KSMs been met? If not, is there a clear plan in place for how the team will meet them?
- Is the current status of the project obvious?
- Does the team demonstrate a clear understanding of what else needs to be done?
5. (10 points) Roadblocks (1 slide)
- Has the team acknowledged and addressed roadblocks?
- Is the team’s plan for overcoming roadblocks reasonable?
6. (20 points) Test Results (1-3 slides)
- Has adequate testing been performed to ensure the project will meet the requirements?
- Do you have confidence future test plans are adequate to fully validate the results?
- Has the team clearly shown whether or not the project meets the requirements?
- Does the team have a clear understanding of what is needed to completely validate the product?
7. (10 points) List of System Design Package documents
- Did the team provide a thorough list of documentation to be provided to sponsor as the System Design Package?
- Do these documents, when combined, ensure a transferable design?