Syllabus/Schedule - Berkeley Expert Systems Technology Lab
Syllabus/Schedule - Berkeley Expert Systems Technology Lab
Syllabus/Schedule - Berkeley Expert Systems Technology Lab
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ME220<br />
Theory and Methods in Product Design<br />
Class Outline and <strong>Schedule</strong><br />
Professor Alice M. Agogino<br />
Spring 2010<br />
DAY DATE TOPIC<br />
1 M 2/15 Introduction to New Product Development (NPD)<br />
We will cover course logistics and requirements and then develop the motivation and<br />
framework for the course. Come to class prepared to discuss why new product development<br />
is important and models of the design process.<br />
Read Ch. 1: Introduction (scanned version available on bSpace as textbooks may not yet<br />
have arrived).<br />
Individual Assignment (Due before or soon after class): Complete SurveyMonkey survey. 1<br />
TBA 2<br />
Special Solidworks <strong>Lab</strong> (Catherine Newman at KAUST): <strong>Lab</strong> to make sure you have<br />
Solidworks installed.<br />
2 W 2/17 Introduction to Solid Modeling<br />
Guest Lecturer Professor Sara McMains will go over the basics of solid modeling using<br />
Solidworks.<br />
Individual Assignment Due: Solidworks installation on your own machines.<br />
TBA 3<br />
Special Solidworks <strong>Lab</strong> (Catherine Newman at KAUST): Tutorial on basic solid modeling<br />
“Lesson 1 Parts”<br />
3 M 2/22 Concept Development: Context and Planning; Tripple Bottom Line<br />
Product planning involves developing a strategy for your products in the context of your<br />
organizational goals and resources. The Tripple Bottom Line refers to considering three<br />
components to an organization’s bottom line: profit, societal benefits, and environmental<br />
impact. Be prepared to discuss the components of a Mission Statement and how it might<br />
reflect the components of a Tripple Bottom Line. Consider the thought questions at the end of<br />
Chapter 2. How is the process described in this chapter similar to/different than the process<br />
you have used in other design projects in class or work? What is the role of a design journal<br />
in the design thinking process? We also hope to introduce the Black Cloud Monitoring<br />
project in collaboration with Dar Al-Hekma, a women’s college in Jeddah, Saudi Arabia.<br />
Read Ch. 2: Development Processes and Organizations<br />
Read Ch. 3: Product Planning<br />
Scan: Google Preview of The Triple Bottom Line, Andrew Savitz and Karl Weber,<br />
http://books.google.com/books?id=pYyqRxTeMe4C&printsec=frontcover&source=gbs_navl<br />
inks_s#v=onepage&q=&f=false<br />
Individual Assignment Due: List of 20 “bugs”<br />
Individual Assignment Due: Fill out sustainability survey. See bSpace for link.<br />
Individual Assignment Due: Project proposal (first draft for feedback; see assignment on 3/3<br />
1 Except where noted, all readings and assignments are due by the start of class on the dates listed in this<br />
syllabus/schedule.<br />
2 Dates in the color orange, represent lectures or labs that involve solid modeling with Professor Sara<br />
McMains or Dennis Lieu and teaching assistant Catherine Newman.<br />
3 Dates in the color orange, represent lectures or labs that involve solid modeling with Professor Sara<br />
McMains or Dennis Lieu and teaching assistant Catherine Newman.<br />
1
to see details for format.) Feedback will be provided by instructor/TA Tuesday morning, Feb.<br />
23. The final proposal and slides will be due by 5:00 pm, Tuesday, March 2.<br />
We are all capable of identifying market needs and thus generating ideas for new products, in<br />
part by noticing the deficiencies in the products we use in everyday life. To prove to yourself<br />
that you can identify market needs, generate a list of at least 20 “bugs.” Designers at the<br />
product design firm IDEO use “bug lists” to record their observations of products and<br />
situations where products failed to meet the actual conditions of use. This list should include<br />
any observation or annoyance that comes to your mind. Note that we are looking for a list of<br />
“bugs” (e.g., my vegetable peeler hurts my hand when I peel potatoes) rather than a list of<br />
product solutions (e.g., a vegetable peeler with a soft handle). In other words, do NOT invent<br />
solutions to the problems you see – just state the problem. Upload your bug list to the course<br />
website under “assignments” and “twenty bugs”.<br />
TBA Special Solidworks <strong>Lab</strong> (Catherine Newman at KAUST): Solidworks Tutorial - “Revolves<br />
and Sweeps”<br />
4 W 2/24 Assemblies and Virtual Prototyping in Solid Modeling<br />
Guest Lecturer Sara McMains will go over will go over the basics of using assemblies for<br />
virtual prototyping in solid modeling.<br />
Individual Assignment Due: Solidworks modeling assignment specified on bSpace.<br />
TBA Special Solidworks <strong>Lab</strong> (Catherine Newman at KAUST): Solidworks Tutorial - Lesson 2<br />
“Assemblies”<br />
5 M 3/1 Equations, Degrees of Freedom and Configurations in Solid Modeling<br />
Guest Lecturer Sara McMains will go over how parametric equations and degrees of freedom<br />
can be included in solid modeling configurations.<br />
Individual Assignment Due: Assembly modeling assignment specified on bSpace.<br />
TBA Special Solidworks <strong>Lab</strong> (Catherine Newman at KAUST): Solidworks Tutorial - “Design<br />
Tables” and begin configuration assignment that is due March 8. As students will have<br />
different levels of proficiency, we are using an extended deadline to provide more time and<br />
tutoring for students as needed.<br />
6 W 3/3 Project: Proposal Presentation and Voting<br />
Students will be given an opportunity to pitch their project ideas in class. Details of the<br />
presentation below.<br />
Individual Assignment Due: Final project proposal and slides due by 5:00 pm, Tuesday,<br />
March 2 4<br />
Project Preferences Due: 5:00 pm, Thursday, March 4<br />
Your one-page proposals should include:<br />
• A brief, descriptive project title (2-4 words)<br />
• Your name, phone number, e-mail, and department affiliation<br />
• A description of the market opportunity you have identified. Your description may<br />
include any of the following: Documentation of the market opportunity, shortcomings of<br />
existing competitive products, and/or definition of the target market and its size. Please<br />
do not present product ideas at this point. Our strict focus in this phase of the course is<br />
on the market opportunity – the unfilled need or unsolved problem – and not on solution<br />
concepts.<br />
4 Unless otherwise specified, all times are KAUST times.<br />
2
These proposals will be posted to a location where all participants in the class can see them.<br />
Come to class prepared to give a VERY SHORT (i.e., 2 minute), yet convincing, presentation<br />
of your project proposal. Please prepare four slides that you can present in 30 seconds each<br />
that clearly communicate the user/market need on which you would like your classmates to<br />
work with you. We will collect all of the slides into a single presentation that we will run<br />
with PowerPoint’s timed presentation feature. Your slides should communicate the<br />
following:<br />
• The first slide MUST include your name and department affiliation.<br />
• A verbal and visual demonstration of the product opportunity you have described in your<br />
proposal.<br />
• Given that the audience will be able to read your written proposal at their leisure, you<br />
might spend your time explaining the richness of the market opportunity or<br />
demonstrating existing competitive products.<br />
• The slides are due absolutely NO LATER THAN 5 P.M. on Tuesday March 2 so that<br />
we can get the full presentation assembled for class on March 3.<br />
• By 5 p.m. on Thursday, 3/4 you must decide on your project preferences. You should<br />
vote on the FIVE projects on which you would most like to work in order of preference.<br />
Submit your preferences per the instructions on bSpace. We will process your<br />
preferences and assign teams. There is a possibility that we will ask you to vote a second<br />
time after we have eliminated some of the projects in the first round, so stay tuned.<br />
7 M 3/8 Project: Project Launch<br />
During this class session, we will talk about team dynamics and interactions as being critical<br />
to new product development success. We’ll conduct a team launch exercise in which you and<br />
your teammates debrief your MBTI profiles and the other questions on the survey. You will<br />
be given ta eam launch exercise to work on during the class. Be sure to bring your MBTI<br />
profile to class.<br />
Read Ch. 16: Managing Projects<br />
Read: “The Trouble with Teamwork” (http://www.leadertoleader.org/knowledgecenter/journal.aspx?ArticleID=80)<br />
Individual Assignment Due: Final Solidworks configuration & assembly assignment<br />
discussed on March 1.<br />
Individual Assignment Due: Complete the Jung Typology Test and the team launch survey<br />
available through the SurveyMonkey link. You will need to know your Myers Briggs profile<br />
in order to complete the survey.<br />
• The Jung Typology Test and information about it are available at<br />
www.humanmetrics.com. Read the background on the test and then take and score it.<br />
• After you have the results of your test, go to the SurveyMonkey website listed on bSpace<br />
and complete the survey there.<br />
8 W 3/10 Concept Development: Customer and User Needs Assessment<br />
In this class, we will talk about user needs understanding, and in particular the role of<br />
ethnographic research in understanding customer needs.<br />
Read Ch. 4: Identifying Customer Needs<br />
Scan: Design Research (pp. 20-80),<br />
http://www.engineeringpathway.com/ep/learning_resource/summary/?id=B8C0CE80-179F-<br />
4B6D-B097-9FFA295C448E<br />
3
Read: “Get Inside the Lives of Your Customers”<br />
Individual Assignment Due: Working with your team, find products that compete with or<br />
serve a similar purpose to the one your project team is developing. Cordinating with your<br />
team, each member should interview a potential or current user of the product about what<br />
they like and dislike about the product. This interview can be done very informally in 5-10<br />
minutes. Record what your interviewee says and interpret the data in terms of customer<br />
needs as described in Chapter 4. Pay particular attention to the guidelines provided for<br />
translating customer statements into needs statements. Prepare a one-page summary of<br />
what you have learned about the interview process. Submit both the record and interpretation<br />
of customer needs and your page of lessons learned to the assignments tab under customer<br />
interview. Also upload the interview to your project website.<br />
9 M 3/15 Concept Development: Translating the Voice of the Customer (Creating Imperatives)<br />
In this class we will move a little ahead of where your project should be to introduce you to<br />
the next step of the process – translating customer and user needs information into<br />
specifications and imperatives. We’ll introduce the basic concepts of generating<br />
specifications and imperatives, and then have you do some exercises with your project data<br />
on Wednesday to play with the concepts.<br />
Read Ch. 5: Product Specifications<br />
Read: “Turn Customer Input into Innovation”<br />
Project Deliverables Due: Mission statement, customer user needs assessment plan, project<br />
plan<br />
10 W 3/17 The Role of Industrial Design<br />
This class will look role of industrial design, user interaction and ergonomics in the design<br />
process. Bring to class (physical product or visual image) one example of what you think is a<br />
well designed product/feature and one of a badly designed product/feature.<br />
Read Ch. 10: Industrial Design<br />
Read: “Innovation as a Learning Process: Embedding Design Thinking” (on bSpace)<br />
Individual Assignment Due: Good design, bad design examples for class exercise<br />
11 M 3/22 Concept Development: Concept Generation<br />
Agogino will give lecture live at KAUST. This class session will focus on brainstorming and<br />
“ideation” techniques used by new product development teams to generate product ideas<br />
from their understanding of customer wants and needs and of the available technologies. We<br />
will use in class exercises to help you move from your individual concept ideas to team ones.<br />
Read Ch. 6: Concept Generation<br />
Read: “Creative Thinking Techniques” (http://www.virtualsalt.com/crebook2.htm)<br />
Individual Assignment Due: Each team member is to generate 20 concepts and post to your<br />
website and bring to class.<br />
Project Deliverables Due: Upload metaphors and team concepts generated during in-class<br />
studio.<br />
12 W 3/24 Peer Review on mission, user needs.<br />
Agogino will give lecture live at KAUST. The date of this peer review may change to<br />
accommodate visit schedule.<br />
Project Deliverables Due: Updated mission statement, customer/user needs analysis, and<br />
short discussion of the process you used, lessons learned, and any observations you have<br />
about your team. Prepare 10 min. team presentation for class.<br />
3/27 Spring Break<br />
3/29 Spring Break<br />
13 M 4/5 Concept Development: Considering Product Architecture<br />
4
Product architectures and product platforms can be used to reduce costs and increase<br />
personalization and variation in product lines.<br />
Read Ch. 9: Product Architecture<br />
Project Deliverables Due: Prioritized list of top 5 needs. Summarize lessons learned.<br />
In-class project exercise: Generating imperatives, design principles and specifications<br />
14 W 4/7 Concept Development: Concept Selection and Decision Making<br />
Concept screening, concept selection and other decision-analytic methods will be covered.<br />
You will perform an in-class exercise with your team, buiding on the individual assignment<br />
due today.<br />
Read Ch. 7: Concept Selection<br />
Individual Assignment: Using your team’s top 5 user needs, individually rank your concepts<br />
using concept scoring and selection. Bring to class to share with your team.<br />
15 M 4/12 Testing and Refinement: Low Fidelity Prototyping and Concept Testing Overview<br />
The class will now move to developing prototypes for communicating and testing your<br />
design concepts.<br />
Read Ch. 8: Concept Testing<br />
Project Deliverables Due: Top three concepts to use for developing early prototypes.<br />
Summarize lessons learned.<br />
16 W 4/14 Testing and Refinement: High Fidelity Prototyping<br />
High fidelity prototyping technologies include machined models of wood or soft metals, solid<br />
models, multimedia, or layered manufacturing (e.g., FDM – Fused Deposition Modeling).<br />
Examples will be shown in class.<br />
Read Ch. 12: Prototyping<br />
TBA Special Animation Evaluation <strong>Lab</strong> (Catherine Newman)<br />
Individual Assignment Due: Evaluate Solid Modeling Animations (may be done during class)<br />
17 M 4/19 Peer Review: Midterm Tradeshow on User Needs and Concept Testing<br />
Individual Assignment Due: Complete the on-line peer review and team assessment survey as<br />
per instructions on bSpace. This can be completed by 5:00 pm Tuesday, April 20.<br />
Project Deliverables Due: Updated mission statement, customer/user needs data, concepts<br />
and early prototypes. Summarize lessons learned. Be prepared to show these in a minitradeshow<br />
format. Submit the slides to your project folder no later than 5 p.m. on<br />
Sunday, April 18.<br />
Session objectives:<br />
• Update your classmates as to progress on your product development effort.<br />
• Make the first “public” presentation of your “proof-of-concept ideas”.<br />
• Gather feedback from classmates on your concept design and mockups.<br />
For this session:<br />
1. Prepare a 6-SLIDE summary of your:<br />
• Project title and team members<br />
• Mission statement<br />
5
• Target market<br />
• User research methods used<br />
• Top 5 customer needs<br />
• 2X2 using two of the top needs and placing competive products and your<br />
concepts in the right quadrant<br />
Plan to orally present this one page summary briefly at the beginning of the class in 3<br />
minutes, 30 seconds per slide. Submit the slides to your project folder no later than 5 p.m. on<br />
Sunday, April 18. This will bring the entire class up to speed on your project before they<br />
review your work and allow you to get peer feedback.<br />
2. Prepare your "proof-of-concept” sketches, product renderings and early prototypes so that<br />
everyone can understand your ideas. After the brief review at the beginning of the class, we<br />
will spend about one hour in a "tradeshow" environment during which you will wander<br />
around the classroom to look at the work. You are welcome to bring portable computers to<br />
set up your images. You should plan to handle any arrangements for using computers on your<br />
own.<br />
To support your concepts, you should have the following materials available. (Each team<br />
will likely have done different versions of these. Use what you have already developed.)<br />
• Customer/user needs hierarchy<br />
• Mapping of customer needs to specifications<br />
• Concept sketches<br />
• Product renderings or mockups (3D renderings, early physical or web mockups)<br />
• Concept screening and scoring matrices<br />
• Reason for choosing the concept(s) you have developed for today<br />
You should plan to have group members rotate responsibility for showing the concepts so<br />
that other group members can circulate. Think about the best way to efficiently and<br />
effectively collect feedback from your classmates. You may wish to have a mini-survey<br />
available for them to complete following the examples we covered in Concept Testing.<br />
Remember that each student will only have about 10 minutes to spend reviewing your work;<br />
so make your presentation as succinct as possible.<br />
From this point forward, your focus will be on developing and testing your product concept<br />
with your customer base, obtaining feedback, incorporating it into your product, and<br />
preparing intermediate and final product prototypes.<br />
18 W 4/21 Testing and Refinement: Optimal Design<br />
Summary of optimization theory and useful methods.<br />
Individual Assignment: Optimization exercise.<br />
19 M 4/26 Testing and Refinement: Robust Design<br />
We will perform an in-class Taguchi exercise in class to illustrate the theory.<br />
Read Ch. 13: Robust Design<br />
Read: “Boost your Marketing ROI with Experimental Design”,<br />
http://www.engineeringpathway.com/ep/learning_resource/summary/?id=DEB26438-7894-<br />
48C4-88B7-837BC3A9EC32<br />
6
20 W 4/28 DfX: Design for Manufacturing<br />
Design for manufacturing is one of the many “design fors” that a product development team<br />
must undertake. In this class session we’ll talk about the various “design for x” activities,<br />
including manufacturing. Consider thought questions 1 and 2 at the end of Chapter 11.<br />
We’ll disassemble and reassemble a product in class in order to evaluate its design-forassembly<br />
merits.<br />
Read Ch. 11: Design for Manufacturing<br />
21 M 5/3 DfX: Design for Environment<br />
In the first reading (Cradle to Grave), click through each of the six stages and read the first<br />
page that pops up. Following the links on each page is encouraged but entirely optional,<br />
except for the three additional links under the "emissions" page, which you should follow.<br />
What does designing products for environmental soundness entail? How might you make<br />
tradeoffs among cost, quality, features and environmental soundness when designing a<br />
product? What is sustainable design? What is the difference between the the "cradle to<br />
grave" perspective and the"cradle to cradle" alternative? How might you redesign or<br />
manufacture your product with this perspective in mind? We will also review the data<br />
collected through the Black Cloud sensor that should have been installed earlier.<br />
Read: Cradle to Grave – How Products Impact Natural <strong>Systems</strong>”<br />
Read: "The Cradle to Cradle Alternative"<br />
22 W 5/5 Life Cycle Analysis<br />
We will also hold a tutorial on using a Life Cycle Analysis software tool and have you apply<br />
it to your projects. Be sure to bring your computers to class.<br />
Read: EIO-LCA Tutorial, http://www.eiolca.net/tutorial-j/tut_1.html<br />
Read: EIO-LCA Tutorial<br />
23 M 5/10 Solid Modeling and Integration with FEM<br />
Guest lecturer Dennis Lieu will go over examples of how to integrate different forms of finite<br />
element modeling from your solid model. Bring examples from your class project to class<br />
that you would like to discuss in the lab.<br />
24 W 5/12 Solid Modeling and Optimal Design<br />
Guest lecturer Sara McMains will go over examples of how to integrate optimization with<br />
your solid model.<br />
Individual Assignment: Optimization exercise based on earlier solid modeling problem of<br />
March 1.<br />
25M 5/17 Product Development Entrepreneurship<br />
Bring in your questions about the intellectual property of your project. This would also be a<br />
good time to discuss possible funding opportunities. We may have a guest speaker from<br />
KAUST.<br />
Read Ch. 14: Patents and Intellectual Property<br />
26 W 5/19 Product Development Economics<br />
Bring in your questions about business models and financial modeling for your projtect.<br />
5/22-<br />
25<br />
Read Ch. 15: Product Development Economics<br />
Project deliverable: Draft business plan and financial model for your project.<br />
Final Exam week – Final Presentations/Tradeshow<br />
• Final Individual Deliverables: Turn in the journal you have been keeping throughout<br />
the semester. It will be returned at the beginning of the Spring semester. Complete the<br />
7
team evaluation survey.<br />
• Final Team Deliverables: Turn in your final presentation, photo of your prototype and<br />
the actual prototype, if appropriate.<br />
8