564 class notes july 27, 2010
DESCRIPTION
TRANSCRIPT
Design and Analysis ProcessF
ron
t -
En
d A
na
lysi
s
Late
r =
Mor
e ex
pens
ive
Too
muc
h is
stil
l too
muc
h (M
ilita
ry)
Bew
are
Ana
lysi
s P
aral
ysis
The Gap between where they are and where they should be.
Difference is?
Pre-test (Academic)
Corporate (Tests, Interviews, Surveys, Training keeps the employee from their job. COST
Return on Investment (ROI)
Supervisor’s report usually flawed
Audience – prior knowledge, past experiences, socio-culture,
demography
Content – Knowledge, learning skill
Domain?
Task – Performance, behavior (ex. ASTD corporate training),mapping out jobs
Pragmatic – (Contract Negotiations ) Budget, Timelines, Resources – SME/Cost, Representation, Media
Kirkpatrick’s Evaluation model
• Reaction of student – what they thought and felt about the training
• Learning – the resulting increase in knowledge or capability
• Behavior – extent of behavior and capability improvement and implementation/application
• Results- the effects on the business or environment resulting from the trainee’s performance
• En.wikipedia.org/wiki/Donald_Kirkpatrick
Performance Analysis Quadrant (PAQ)
http://www.nwlink.com/~donclark/hrd/isd/analyze_system.html, downloaded July 27, 2010
Flashcard Systems Online
• Free: http://www.memorylifter.com/
• Commercial: http://www.flashmybrain.com/
• http://www.openwindow.com/
• http://www.vendant.com/FlashCardManager/program.aspx
• http://www.luminaresoft.com/
• http://ichi2.net/anki/
TED Talks
• Perceptual Blindness– Watch the white shirts pass the ball, and
completely miss the gorilla in the middle!
• Bobby McFerrin– Pentatonic skill taught by movement– Extrapolation– Reptilian directions
Agile development
• Customer satisfaction by rapid, continuous delivery of useful software • Working software is delivered frequently (weeks rather than months) • Working software is the principal measure of progress • Even late changes in requirements are welcomed • Close, daily cooperation between business people and developers • Face-to-face conversation is the best form of communication (co-location) • Projects are built around motivated individuals, who should be trusted • Continuous attention to technical excellence and good design • Simplicity • Self-organizing teams • Regular adaptation to changing circumstances
http://opencontent.org/wiki/index.php?title=564-2010-Analysis-Development
The Open Source Way, (Selections from The Cathedral and the Bazaar) • 1. Every good work of software starts by scratching a developer's personal itch. • 2. Good programmers know what to write. Great ones know what to rewrite (and reuse). • 3. "Plan to throw one away; you will, anyhow." (Fred Brooks, The Mythical Man-Month, Chapter 11)
• 4. If you have the right attitude, interesting problems will find you. • 5. When you lose interest in a program, your last duty to it is to hand it off to a competent
successor. • 6. Treating your users as co-developers is your least-hassle route to rapid code improvement
and effective debugging. (37 Signals) (Ally Carr-Chellman)• 7. Release early. Release often. And listen to your customers. • 8. Given a large enough beta-tester and co-developer base, almost every problem will be
characterized quickly and the fix obvious to someone. Or, less formally, "Given enough eyeballs, all bugs are shallow." I dub this: "Linus's Law". Must have an “enlightened despot.”
• 10. If you treat your beta-testers as if they're your most valuable resource, they will respond by becoming your most valuable resource.
• 11. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
• 12. Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.
• 13. "Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away." Antoine de Saint-Exupéry
• 14. Any tool should be useful in the expected way, but a truly great tool lends itself to uses you never expected. (Openness facilitates the unexpected.)
• 18. To solve an interesting problem, start by finding a problem that is interesting to you. • 19: Provided the development coordinator has a communications medium at least as good as
the Internet, and knows how to lead without coercion, many heads are inevitably better than one. http://opencontent.org/wiki/index.php?title=564-2010-Analysis-Development
More on Agile Development
• Ally Carr-Chellman
• 37 Signals– Wrote Ruby on Rails Programming Language
Software
ApplicationPlatform Software Licence Notes
AnkiWindowsLinux, Mac OS X, Maemo, iPhone,
Android
GPL v3 for computer
Proprietary for iPhone
Features: Server sync, multi-"sided" flashcards. Written in
Python.
Mnemosyne Any Python Platform including Windows,
Linux, Mac OS X
GPL v2 There is a plugin to review cards on Android. A Java J2ME version "will run on many mobile phones".
CramMacintosh(PowerPC & x86),
iPhone & iPod Touch (ARM)
Shareware
Keep Your WordMacintosh (PowerPC & x86) iPhone & iPod
Touch (ARM)Shareware
Super MemoWindows, Palm OS, PocketPC, Web, and
moreProprietary
http://en.wikipedia.org/wiki/List_of_flashcard_software
List of Flashcard Software from Wikipedia