DEFINE THE PROBLEM

1
The Design Process

• DEFINE THE PROBLEM
• FORMULATE SOLUTIONS
• Trade-offs between design parameters
• Research and data gathering
• Subsystem concepts, System diagrams, and state
  diagrams
• DESIGN AND DEVELOP
• Design Sketches, CAD, circuit diagrams, state
  diagrams
• Feasibility testing - Soft models, breadboards,
  code testing
• Build component fabrication, parts assembly,
  circuit fabrication, code
• Subsystem Testing
• Integration and Testing
• Optimization
• DOCUMENT AND PRESENT
• Design Records
• Design Review Presentations

2
Brainstorming

• Guidelines from Tools and Tactics of Design,
  P.G. Dominick et al., (John Wiley, 2001)
• Criticism is Ruled Out
• Creative and Imaginative Thinking is Encouraged
• Quantity is the Metric
• Combining and Extending is Good

• Eliminate Biases/ Overcome Assumptions
• Try to avoid preconceived biases
• It needs a plug because how else would it charge
  the battery?
• All robots use optical sensors!
• That will never work!
• Robots never use those!
• Avoid forcing elements into a design because
• Ive got one of those in my garage
• Theyre cheap
• I understand how they work
• The rhumba has one

3
Formulating Solutions

• Research and Data Gathering
• What is the state of the art?
• What works and what doesnt? Why?
• What sensors are use in autonomous robots?
• What types of electrical imterconnects are used?
• Has anyone ever built something like this
  before?
• Are there typical control algorithms for robots?
• How much do things cost? Weigh?
• How much power do they require?

4
Formulating Solutions

• DOs
• Include ideas that simplify fabrication
• Design to use commercially available parts
• Design for ease of assembly and maintenance
• Design mechanisms with dual (multiple) functions
• Design to minimize moving parts
• Design to minimize number of electronic
  components, controllers, etc.
• Design to minimize electrical interconnects and
  wiring
• Design for low energy consumption (lightweight,
  low friction, low current)
• .

5
Team Building

• Discuss and define project expectations
• Come to agreement on the project expectations
• Beat the other team?
• Build the fastest one?
• Get an A? Get a C?
• Learn about each others prior experience,
  weaknesses and strengths
• All team members should be expected to
• Work hard and to work together productively
• Participate in the design process
• Do quality work (e.g, be thorough, write well,
  make accurate technical presentations)
• Meet deadlines
• Apply whatever technical/engineering skills they
  possess
• Learn some new things about the technical
  aspects of your design topic

6
Team Building

• Establish and adhere to a working agreement
• Establish structure for your meetings
• All team members take responsibly for adhering
  to the agreement
• Periodically review teams performance relative
  to the working agreement
• Build you own skills Identify skill areas where
  you want to improve

7
Team Building
STAGES OF TEAM DEVELOPMENT

• 1 The Forming Stage
• Attempting to define tasks
• Determining acceptable behavior
• Floundering about where to begin
• Over depending on a single individual
• Tending to dive into solutions
• Being too polite not wanting to make waves

• 2 The Challenging Stage (Storming)
• Arguing among team members
• Showing defensiveness
• Establishing unrealistic goals
• Questioning the credibility of others
• Choosing sides
• Being rude

• 3 The Accepting Stage (Norming)
• Attempting to achieve harmony
• Expressing opinions more openly
• Sharing information
• Showing less resistance to team tasks
• Learning the best ways to do things

• 4 The Collaborating Stage (Performing)
• Balancing contributions
• Focusing on goals and results
• Solving problems collectively
• Being able to reach a consensus and closure
• Encouraging criticism and constructive conflict
• Sharing accountability
• Following through on commitments
• Pushing for higher standards

8
Team Building

• Surviving The Forming Stage
• Use active listening
• Make a point of soliciting input from all
  members
• Avoid rushing to conclusions
• Acknowledge other contributions, let people know
  their input is valued
• Spend time establishing clear structure and a
  sense of direction
• See Table 3.4 Team Norms
• See Table 3.5 General guides for Effective
  Listening

9
Project Planning

• Problem Statement
• A clear written statement that defines the
  problem to be solved
• Solution ? Defined functionality
• Written statement
• System overview
• Concept diagrams for different subsystems
• Plan and Schedule
• Major milestones to be accomplished (with target
  dates)
• Work breakdown tasks
• Timeline schedule (for example, Gantt Chart)
• Personnel assignments
• Assignments for engineering tasks
• Assignments for management tasks
• Regular meeting schedule
• Costs

10
Project Planning

• Work Breakdown Structure
• Identify all tasks and subtasks needed to
  complete the project
• Estimate the time required to complete each task.
  If the task is so undefined (e.g. build vehicle)
  that a required time cannot be determined, break
  it down into subtasks. Smallest unit is defined
  by units on Gantt chart (2 days? ½ week? 1 week?)
• Determine the sequence in which the tasks must be
  scheduled
• Identify deadlines (Status reports,
  presentations, demonstrations)
• Identify Major/Minor Milestones (measurable)
• Sensor communicates to microcontroller
• Lift mechanism assembled and tested to lift 10
  lb
• Vehicle driven forward using microprocessor

11
Project Planning
Gantt Chart