Capstone Project Wiki

User Tools

Site Tools

Trace:
project-wiki:design_reviews:opportunity_development_review

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
project-wiki:design_reviews:opportunity_development_review [2023/08/11 13:22]
dbradyr [Opportunity Development Review] 		project-wiki:design_reviews:opportunity_development_review [2023/08/19 21:11] (current)
bdj2 [Evaluation]
Line 20: Line 20:
 and any relevant technology in order to support effective and appropriate concept development. and any relevant technology in order to support effective and appropriate concept development.
  
-==== Questions ====+==== Artifact Submission for Opportunity Development ====
  
-The artifacts and the review should answer the following questions.  Satisfactory answers to these questions constitute the minimum requirements for completion of +The artifacts submitted for the Opportunity Development review should answer the questions, "What are the design objectives and the complete product requirements? What are the schedule and resources allocated to achieve these objectives?" and, "How have you validated that the product requirements and Primary Artifacts are likely to be feasible and truly represent the market's and the sponsor's desires?" To answer these questions, the team should submit a pdf file containing the following artifacts:
-Opportunity Development. +
- +
-  - What are the design objectives and the complete product requirements? What are the schedule and resources allocated to achieve these objectives? +
     - Primary Artifacts:     - Primary Artifacts:
       * **Project Background**.  A brief description of the sponsor, the design challenges, and the project that allows the reader to understand what you are tasked with doing and why it is important.       * **Project Background**.  A brief description of the sponsor, the design challenges, and the project that allows the reader to understand what you are tasked with doing and why it is important.
       * **Project Objective Statement**, as described on pages [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=62|62]] and [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=273}|264-65]] of [[https://byucapstone.byu.edu/mattson-sorensen.pdf|Product Development]].       * **Project Objective Statement**, as described on pages [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=62|62]] and [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=273}|264-65]] of [[https://byucapstone.byu.edu/mattson-sorensen.pdf|Product Development]].
       * **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=64|System Requirements Matrix]]** with sections A--D completed, organized according to the [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=239|Goal Pyramid]] on pages 230--31 of //Product Development//. You may find the template found on Box [[https://byu.app.box.com/file/676291641715|under Class Documents/Templates]] to be helpful in preparing your Requirements Matrix. \\ Be sure that your Requirements Matrix is consistent with the guidelines given on pages [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=271|262--63]], [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=283|274--75]], and [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=285|276--79]] of //Product Development//. \\ For some products, especially software-only products, it may be better to use a **[[https://en.wikipedia.org/wiki/Software_requirements_specification|Software Requirements Specification]]** instead of a Requirements Matrix.  Please consult with your coach and your pod instructor if you feel this applies to your team.       * **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=64|System Requirements Matrix]]** with sections A--D completed, organized according to the [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=239|Goal Pyramid]] on pages 230--31 of //Product Development//. You may find the template found on Box [[https://byu.app.box.com/file/676291641715|under Class Documents/Templates]] to be helpful in preparing your Requirements Matrix. \\ Be sure that your Requirements Matrix is consistent with the guidelines given on pages [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=271|262--63]], [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=283|274--75]], and [[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=285|276--79]] of //Product Development//. \\ For some products, especially software-only products, it may be better to use a **[[https://en.wikipedia.org/wiki/Software_requirements_specification|Software Requirements Specification]]** instead of a Requirements Matrix.  Please consult with your coach and your pod instructor if you feel this applies to your team.
-      * A **Project Milestones Table** that describes the stages of development to be completed, the deliverables required for each stage, the intended completion date for each stage, and the anticipated budget for each stage.  It should also list other significant milestones that will help you reach your stage review readiness. +      * A **Project Milestones Table** that describes the stages of development to be completed, the deliverables required for each stage, the intended completion date for each stage, and the anticipated budget for each stage.  It should also list other significant milestones that will help you reach your stage review readiness. This table should include significant project milestones specific to your project (i.e., not just the dates of Capstone reviews). 
 +      * **Requirement validation results** indicating the sponsor's and/or market's acceptance of the final requirements as listed in the Requirements Matrix.  Refer to other Primary Artifacts and Supporting Artifacts as necessary.
     - Supporting Artifacts should include one or more of the following, or other similar artifacts:     - Supporting Artifacts should include one or more of the following, or other similar artifacts:
       * **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=307|Market survey]]**, **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=237|focus group]]**, and/or **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=243|interview]]** procedures and results       * **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=307|Market survey]]**, **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=237|focus group]]**, and/or **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=243|interview]]** procedures and results
Line 38: Line 36:
       * **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=241|Internet]]** and/or **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=261|patent]]** research reports       * **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=241|Internet]]** and/or **[[https://byucapstone.byu.edu/mattson-sorensen.pdf#page=261|patent]]** research reports
       * White papers or other technical reports that relate to the project       * White papers or other technical reports that relate to the project
-  - How have you validated that the product requirements and Primary Artifacts are likely to be feasible and truly represent the market's and the sponsor's desires?  
-    - Primary Artifact: 
-      * Requirement validation results indicating the sponsor's and/or market's acceptance of the final requirements as listed in the Requirements Matrix.  Refer to other Primary Artifacts and Supporting Artifacts as necessary. 
-    - Supporting Artifacts should include one or more of the following: 
       * Reports on prototypes used to help the team, the market, and the sponsor better understand the challenges and goals of the project.  If no prototypes are used during Opportunity Development, it is difficult or impossible to obtain high-quality results.       * Reports on prototypes used to help the team, the market, and the sponsor better understand the challenges and goals of the project.  If no prototypes are used during Opportunity Development, it is difficult or impossible to obtain high-quality results.
       * Validation procedures used to obtain market feedback on completed requirements       * Validation procedures used to obtain market feedback on completed requirements
Line 63: Line 57:
 The rubrics used in the evaluation is shown below.  There are different rubrics for hardware or mixed projects and software projects.  Discuss with your pod instructor which rubrics you will use. The rubrics used in the evaluation is shown below.  There are different rubrics for hardware or mixed projects and software projects.  Discuss with your pod instructor which rubrics you will use.
  
-The scoresheets used by the evaluators are available on Box for [[https://byu.app.box.com/file/831600112250|hardware or mixed projects]] and for [[https://byu.app.box.com/file/1010865158823|software projects]]. +The scoresheets used by the evaluators are available on Box for [[https://byu.app.box.com/file/1271482309938|hardware or mixed projects]] and for [[https://byu.app.box.com/file/1271491926396|software projects]]. 
  
 <nodisp 16> <nodisp 16>
-NOTE TO INSTRUCTORS: This table is automatically created by [[https://byu.app.box.com/file/830893783568|ScoreSheetMaker.xlsm]].  Make the changes in ScoresheetMaker.xlsm so they will be+NOTE TO INSTRUCTORS: This table is automatically created by [[https://byu.app.box.com/file/1281677015283|ScoreSheetMaker.xlsm]].  Make the changes in ScoresheetMaker.xlsm so they will be
 consistent with the scoresheets. consistent with the scoresheets.
 </nodisp> </nodisp>
Line 85: Line 79:
  
 <nodisp 16> <nodisp 16>
-NOTE TO INSTRUCTORS: This table is automatically created by [[https://byu.app.box.com/file/830893783568|ScoreSheetMaker.xlsm]].  Make the changes in ScoresheetMaker.xlsm so they will be+NOTE TO INSTRUCTORS: This table is automatically created by [[https://byu.app.box.com/file/1281677015283|ScoreSheetMaker.xlsm]].  Make the changes in ScoresheetMaker.xlsm so they will be
 consistent with the scoresheets. consistent with the scoresheets.
 </nodisp> </nodisp>
project-wiki/design_reviews/opportunity_development_review.1691781767.txt.gz · Last modified: 2023/08/11 13:22 by dbradyr

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: Copyright Brigham Young University, all rights reserved
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki