Differences

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

--- design:design_concept [2021.06.29 15:00]
Fil Salustri [Step 5: Refine final concept]
+++ design:design_concept [2021.11.10 11:04] (current)
Fil Salustri [Step 5: Refine final concept]
@@ Line 57: / Line 57: @@
   * Review the [[Persona]] and [[SUC]] for which they are responsible.
   * Select from the MC embodiments that are "best" for their Persona situated in the SUC.
+    * You can only pick **one** embodiment from each row of the MC.
   * Combine those embodiments into a single overall concept.
   * Document the preliminary concept and the justification for the selection of embodiments.
@@ Line 146: / Line 147: @@
     * This final concept must (a) satisfy all the requirements, and (b) satisfy the needs of all the Personas in their respective SUCs.
-**IMPORTANT NOTES**
+== Important notes ==
   * You may find you are unable to integrate the individual concepts due to some incompatibility that only became evident once individual concepts were compared.
@@ Line 155: / Line 156: @@
 ==== Step 4: Build usage scenarios of final concept ====
-:todo:
+Given a final design concept, each team will develop a single [[usage scenario]] describing the "ideal" way that a generic user ought to use the product represented in the design. See the page on [[usage scenario]]s for details.
+A reasonable metaphor for the usage scenario is that of a visual "instruction manual" for the product. The usage scenario will provide a baseline of use for subsequent analysis (see below).
 ==== Step 5: Refine final concept ====
-This step is similar to [[#Step 2: Refine preliminary concepts|Step 2]], except that now you all work collaboratively to refine the final concept.
+This step is similar to [[#Step 2: Refine preliminary concepts|Step 2]], except that now you all work collaboratively in your teams to refine the final concept.
 Specifically:
-  - Working together, look for several [[interaction error]]s in your final concept by analyzing the [[usage scenario]]s.
+  - Working together, look for several [[interaction error]]s in your final concept by analyzing the [[usage scenario]] from the point of view of each [[Persona]].
   - Working together, look for ways to address the interaction errors of the final concept to improve the concept.
 Remember to document the interaction errors you identify in this step just as you did in Step 2.
-==== OLD STUFF BELOW TO BE HIDDEN ====
+/* OLD STUFF BELOW TO BE HIDDEN
-:here:
 In this step of our [[design process]], we want to identify at least some of the most likely suitable concepts that are implied by the morphological chart.  (Or, conversely, we want to eliminate the least likely concepts, some of which have already been identified when we searched for [[inconsistent embodiment]]s.)
@@ Line 262: / Line 262: @@
 A complete tutorial on the tool is available at {{mec325_rdcg_tutorial.pdf}}.
-The Google Sheet itself is available [[https://docs.google.com/spreadsheets/d/1E-Tv8Np-WBVvroCn2J3fYxeubdytru9GtH4ug6_GzAI/edit?usp=sharing|here]]((Original slightly buggy version is [[https://docs.google.com/spreadsheets/d/1NpgdqLJgxxrqxZrtQ2HDeA8cbqOrIMULuOEAr0pRR4M/edit?usp=sharing|here]])). **You must make a copy of this Sheet before trying to use it.** If you "break" the spreadsheet, just download a fresh copy.
+The Google Sheet itself is available [[https://docs.google.com/spreadsheets/d/1B-m-glsSjGbmY54oAglT6oTEPlHfQ1-lSTjw_dOjHTg/edit?usp=sharing|here]]. **You must make a copy of this Sheet before trying to use it.** If you "break" the spreadsheet, just download a fresh copy.
 **SPECIAL NOTE 1:** When you load the spreadsheet for use, look for the ''MEC325'' menu in the menu-bar. If you do not see it, try reloading the spreadsheet.
 **SPECIAL NOTE 2:** The "brute force" method will not run if there are more than 200 concepts total - this is just to keep the sheet from taking up too many resources in your browser.
+END OF OLD, HIDDEN STUFF */
 ===== Deliverables =====
+The deliverables for this stage include the following.
+  - All of the preliminary concepts developed in [[#Step 1: Select preliminary concepts|Step 1]].
+    * Each concept will fit on one page: half a page for a sketch of the concept, followed by no more than half a page description of its key features. Include in the description only features that are not already evident in the sketch.
+  - Descriptions of all the IEs that were addressed during refinement of the preliminary concepts, per [[#Step 2: Refine preliminary concepts|Step 2]].
+  - All the refined preliminary concepts, per [[#Step 2: Refine preliminary concepts|Step 2]].
+    * Each concept will fit on one page: half a page for a sketch of the concept, followed by no more than half a page description of its key features. Include in the description key changes that were made during refinement.
+  - Three pages summarizing the final concept, per [[#Step 3: Integrate preliminary concepts|Step 3]]. (One page sketch plus up to two pages of description of how the preliminary concepts were combined.)
+  - All the usage scenarios developed, per [[#Step 4: Build usage scenarios of final concept|Step 4]].
+    * Each US must make clear what Persona and SUC were involved.
+  - Descriptions of all the IEs that were addressed during refinement of the final concept, per [[#Step 5: Refine final concept|Step 5]].
+  - The refined final concept, including a 1 page sketch of the concept and up to two pages of explanation of the refinements.
-The deliverables from this part of the process are as follows.
-  - A brief statement of whether you used the brute force or the hill-climbing search, and why.
-  - Regardless of whether you used brute force or hill-climbing, include the documentation described in the pertinent section above.
-  - Whether you used brute force or hill-climbing, a list of the final 5-15 concepts left at the end. Each concept should be represented by a sketch of the concept roughly showing all the embodiments, and a brief verbal description (100-200 words) of the concept.
 ===== However =====
+:todo:
+/* OLD STUFF (NOW IRRELEVANT) BELOW.
 It is vitally important to be able to justify every decision you make in this stage of the process.
@@ Line 282: / Line 295: @@
 This step of the process is best done in one, long sitting.  It may be difficult to organize the time, but you will likely work faster and better if you can do the entire exercise in one (preferably) or two sessions.  Do not work on this in short bursts punctuated by distractions or other tasks - it is likely to lead to terrible results.
-===== Examples =====
-Consider the example discussed in the [[ideation]] page and reproduced below.  We will consider the brute force search in this case.  This is not a full example, but it is intended to show some aspects of the method.
-<WRAP box>
-//**Example problem**//
-Design problem: You have to design a joint for a detachable robotic arm. It's basic systems are:
-  - Structural system (to resist physical forces during operation)
-  - Connection system (to attach and disconnect automatically)
-  - Power system (to transmit power)
-  - Data system (to transmit data)
-Here are some ways to embody these systems.  (This can be thought of as a textual version of a [[morphological chart]]. However, do not think that //you// can just list embodiments this way. //You// have to create a proper morphological chart.)
-A. Structural system
-  - Bolt and lug
-  - Concentric rods/shafts
-  - Cup and socket (like, say, your shoulder joint)
-  - Meshed teeth in compression (as in the Canadarm; see image.)
-  - Motorized hooks
-  - Magnetics
-B. Connection/disconnection system
-  - Mechanical gearing
-  - Solenoid/electrical actuators
-  - Hydraulics
-C. Power system
-  - Space-rated electrical wire with mechanical connector
-  - Space-rated electrical wire with magnetic connector
-  - Induction transmission
-D. Data system
-  - Space-rated electrical wire
-  - RF transmission (as in radio)
-  - IR transmission (as is a TV remote)
-  - Microwave transmission
-  - Laser (optical fibre) transmission
-</WRAP>
-This set of embodiments represents 270 total concepts.  So we could use the Brute Force method in this case.
-We start by taking the first 10 concepts that do not have inconsistent embodiments.  Normally, this would include concepts A1-B1-C1-D1 through A1-B1-C2-D5.
-However, say we have decided that C2-D2 would be an inconsistent embodiment because of the RF noise between the magnetic connector in the power system and the RF receiver in the data system.  So we remove concept A1-B1-C2-D2 and replace it with the next concept, A1-B1-C3-D1.
-Now we consider the next concept, A1-B1-C3-D2, but we have C3-D2 also listed as an inconsistent embodiment, so we discard it and go on to A1-B1-C3-D3.
-We then compare A1-B1-C3-D3 to each of the 10 concepts currently in our list and look for a concept that we believe will be less suitable than it, with respect to the requirements.
-Since all the concepts so far have A1 and B1 in common, we can start by focusing on C3 and D3.  While induction transmission of power and IR data communications both have disadvantages in space application((Induction transmission has significant losses compared to direct connections, and IR transmission in space can be affected by the severe temperature differences between sunlit and shaded regions.)), they pose a distinct advantage together.  In conjunction, they remove all need for direct, fixed connections between the robot elements.  This will significantly reduce the physical complexity of the connector that we are designing because with C3-D3.  Reduced complexity (i.e., increased simplicity) will generally reduce cost and increase reliability.  So concept A1-B1-C3-D3 has certain merits.
-In this example, we cannot really judge which concept in our list is the worst compared to A1-B1-C3-D3 because we do not have a precise set of requirements.  (This underscores how important it is to have a crisp and complete set of requirements during this stage of the design process.)  Still, we may argue that concept A1-B1-C1-D1 is significantly worse than A1-B1-C3-D3 because the former will require higher precision connection (especially during the connection and disconnection operations) than the latter.
-So we (a) discard A1-B1-C1-D1 for A1-B1-C3-D3, and (b) note why the latter is preferred to the former.
-**NOTE TO STUDENTS.** You //will// have a usable set of requirements, so you //will// be expected to judge much more precisely why a given concept is better or worse than some other concept.
+*/
-We continue in this fashion until we have checked every possible concept.
 /*

DesignWIKI

User Tools

Site Tools

Differences

Page Tools