Jump to content

General Engineering Introduction/CDIO/Tasks

From Wikibooks, open books for an open world

Tasks are short statements negotiated between project managers/instructors and engineers/students that describe what is going to be done during a week. Typically the instructor types tasks into the teams page within the instructors user space. Students then repeat that task description in their weekly report pages. The same task might be worked on for four weeks. Or multiple tasks may be done in one week. The goal is to always have more tasks than time in case there are glitches, successes, materials problems, unplanned failures, etc.

Task activity is summarized in the students weekly report and detailed in a CDIO that may be shared with other team members or may be individually created/modified/reorganized.

Tasks have to be a subset of either a Conceive, Design, Implement or Operate CDIO document. Tasks thus have to come from this list:

Conceive

[edit | edit source]
  • Decisions
  • Estimation
  • Find Starting Point
  • Form/Function
  • Goals/Requirement
  • Knowledge Base
  • Needs
  • Problem Statement
  • Research
  • Risks
  • Scale
  • Scope
  • Standards
  • TradeOffs

Design

[edit | edit source]
  • Analytical Analysis
  • Brainstorm
  • Build
  • Calibration
  • Decisions
  • Drawings
  • Failure Modes
  • Material List
  • Modeling
  • Problem Statement
  • Programming
  • Reuse
  • Reverse Engineer
  • Safety
  • Simulation
  • Testing
  • Theory of Operation
  • Validation

Implement

[edit | edit source]
  • Assembly
  • Decisions
  • Integration
  • Problem Statement
  • Programming
  • Sourcing
  • Staging
  • Storage
  • Testing
  • WorkFlow

Operation

[edit | edit source]
  • Decisions
  • Disposables
  • Disposal
  • Improvement
  • LifeCycle
  • Logistics
  • Operating Instructions
  • Operation Manual
  • Problem Statement
  • Quality
  • Reporting