Embed Size (px)
Citation preview
de la Rosa-Pohl
ECE 4336Capstone Design II
Project Design Process
University of HoustonDiana de la Rosa-Pohl
1
de la Rosa-Pohl
ADDIEDESIGN MODEL
2
de la Rosa-Pohl
ADDIE Design Model
• Analysis
• Design
• Development
• Implementation
• Evaluation
3
de la Rosa-Pohl
Some Comments
• This process is an iterative process!
• Everyone has models they use. This is just one.
4
de la Rosa-Pohl
ANALYSIS
5
de la Rosa-Pohl
ADDIE Design Model
• Analysis
• Design
• Development
• Implementation
• Evaluation
6
de la Rosa-Pohl
Analysis
• get background information
• identify problem/need (needs analysis)
• user analysis
• conduct research
• identify expected deliverables
• formulate goal
• identify desired performance outcome
sometimes calledfront-end analysis
7
de la Rosa-Pohl
Analysis
• get background information mostly given to you by client/manager
• supporting materials– product specs– design constraints
• meetings
web sites
What are other ways to get background information?
8
de la Rosa-Pohl
Analysis
• identify problem/need
problem: (What’s broken?)
need: (Why is it a problem?)
9
de la Rosa-Pohl
Analysis
• conduct research Is there even a problem that you can solve?
Is the problem worth solving?• Why? Significance• “Who Cares?” factor
Has the problem (or similar problem) been solved before?
What data/resources do you have to work with?
10
de la Rosa-Pohl
Analysis
• identify expected deliverables
What (specifically) did you deliver to your client/manager in December?
What (specifically) will you deliver to your client/manager in April?• answer this as best you can• this may change depending on your results in December
(the status of your project will be known to all in January)• you may need to renegotiate this
11
de la Rosa-Pohl
Analysis
• user analysis
WHO is going to be using your widget?• What important characteristics will impact your
design?
HOW are they going to be using this?
WHERE will your user be using this?
WHAT is the skill level of your user?
12
de la Rosa-Pohl
Analysis
• identify/formulate goal Write your overall goal statement.
• i.e., your goal for April
13
de la Rosa-Pohl
Analysis
• identify desired performance outcome Target Objective what do you want to happen?
14
de la Rosa-Pohl
DESIGN
15
de la Rosa-Pohl
ADDIE Design Model
• Analysis
• Design
• Development
• Implementation
• Evaluation
16
de la Rosa-Pohl
Design
• brainstorm alternative solutions
• decide on optimum solution within engineering constraints using engineering standards
• overview diagram
• goal/task analysis
• test plan
• schedule
• budget
17
de la Rosa-Pohl
Design
• brainstorm alternative solutions
different shapes different sizes different sensors different protocols different power supplies …you get the idea
18
de la Rosa-Pohl
Design
• decide on optimum solution
you should have done this already
19
de la Rosa-Pohl
Design
• overview diagram someone should be able to look at your
overview diagram and know what you are about to build (or have already built)
if they close their eyes, they should see it• ALL OF IT!
include what you are building and the environment that it is in (if it’s important)
it should be clear what part(s) you are building and what’s been given to you
label all important parts
20
de la Rosa-Pohl
Design
• goal analysis what should the SYSTEM be able to do?
start with the end in mind!• i.e., the target objective
work your way backwards• this should be graphical• every box is an objective
all objectives must measureable and observable!
21
de la Rosa-Pohl
Design
• task analysis what do YOU need to do to complete the
objective?• these are YOUR tasks• list as many as necessary for each box• you may also include smaller tests here• these DO NOT need to be measurable/observable
22
de la Rosa-Pohl
Design
• test plan ? ? ? ? ? ? ? ? ? ? TARGET OBJECTIVE:
Should include target dates in your test plan.
23
de la Rosa-Pohl
Design
• Project Objectives (Milestones)
Must be observable AND measureable!• Says who? Says ME! (and Gagné and Mager and others)
Robert Mager (Preparing Instructional Objectives, 1997)
• outcomes vs. process• specific vs. general• measureable vs. unmeasurable• student vs. instructor functionality of system vs. task of
engineer
24
de la Rosa-Pohl
Design• Project Objectives (Milestones)• Robert Gagné (Principles of Instructional Design, 2005)
situation• what is the stimulus?• environmental conditions?
capability verb• [discriminates, identifies, classifies, demonstrates (a rule),
generates, adopts, states (or displays), executes (a motor skill), chooses (an attitude)]
object• the “what” of the capability verb• “what” is the capability?
action verb• how the performance is to be completed
tools, constraints, or special conditions• specific equipment?• limited time, budget, error?
25
de la Rosa-Pohl
DEVELOPMENT
26
de la Rosa-Pohl
ADDIE Design Model
• Analysis
• Design
• Development
• Implementation
• Evaluation
27
de la Rosa-Pohl
Development
• build it! piece by piece
• the blood, sweat, and tears
• work through goal analysis
• work through test plan formative evaluation
28
de la Rosa-Pohl
IMPLEMENTATION
29
de la Rosa-Pohl
ADDIE Design Model
• Analysis
• Design
• Development
• Implementation
• Evaluation
30
de la Rosa-Pohl
Implementation
• doing what you said you were gonna do testing the full system
• full integration
• full-blown testing alpha testing beta testing
• record test data
31
de la Rosa-Pohl
EVALUATION
32
de la Rosa-Pohl
ADDIE Design Model
• Analysis
• Design
• Development
• Implementation
• Evaluation
33
de la Rosa-Pohl
Evaluation
• interpreting your results data “How’d we do?”
• make design decisions based on current implementation formative evaluation
• make decisions based on final implementation summative evaluation
• determine implications for future work
• suggest next steps
• documentation
• publication
34
de la Rosa-Pohl
Presentations Capstone I Report Format
Phase Task Report Section
A - Analysis background information Introduction
identify problem and need Introduction: Significance
formulate goal Introduction: Deliverables
identify expected deliverables Introduction: Deliverables
identify performance outcome Introduction: Deliverables
conduct research Background (lit review) written report only
D - Design brainstorm alternative solutions Methods (as needed)
decide on optimum solution Methods
engineering constraints Methods: Eng Constraints written report only
engineering standards Methods: Eng Standards written report only
overview diagram Methods
goal/task analysis Methods: Goal Analysis
test plan Methods: Goal Analysis
schedule Methods: Goal Analysis
budget Methods: Goal Analysis
D - Development build components and test Results
integrate components and test Results
I - Implementation full design test Results
E - Evaluation interpret results Conclusions
policy/design decisions Conclusions
implications for future work Conclusions
suggest next steps Conclusions
35
de la Rosa-Pohl
Presentations Capstone II
Report Format
*sections that would incorporate modifications of analysis; design and development must be included for individual projects if relevant.The goal is to write progress reports of your projects and use ADDIE for guidance.
Phase Task Report Section*
A - Analysis background information Introduction
identify problem and need Introduction: Significance
formulate goal Introduction: Deliverables
identify expected deliverables Introduction: Deliverables
identify performance outcome Introduction: Deliverables
conduct research Background (lit review)
D - Design brainstorm alternative solutions Methods (as needed)
decide on optimum solution Methods
engineering constraints Methods: Eng Constraints
engineering standards Methods: Eng Standards
overview diagram Methods
goal/task analysis Methods: Goal Analysis
test plan Methods: Goal Analysis
schedule Methods: Goal Analysis
budget Methods: Goal Analysis written report
D - Development build components and test Results
integrate components and test Results written report
I - Implementation full design test Results written report
E - Evaluation interpret results Conclusions
policy/design decisions Conclusions
implications for future work Conclusions
suggest next steps Conclusions written report
36
de la Rosa-Pohl
Written Report Outline*• Introduction
Significance Deliverables
• Background (properly cite sources using APA style:
https://owl.english.purdue.edu/owl/resource/560/03/ )• Methods
Engineering Constraints Engineering Standards Goal Analysis Budget
• Results• Conclusion• References
• Please note that the written reports should now represent the progress of the project. However, each report should be a complete document i.e. with all required sections written individually. Common materials/contents (data, results etc.) that belong to the team can be included. Consecutive reports should follow on the preceding individual reports (copied directly or modified according to changes made in your progressing work). So the focus is on your progress from one stage to the next in your project development.
• The main body of the reports should be ~ 8 pp long (not counting abstract, references, and supplementary materials if any)
de la Rosa-Pohl
38
