due dates

1
due dates

• Phase 2 being graded. All excellent, by the way
• Phase 3 - 4/6 - everybody OK with that?
• Phase 4 - demos - volunteers first
• If possible, read The Tao of Pooh by next week.
• lecture topics pre-project testing (today), Tao
  (4/2), legal/ethical (4/9)

2
Failures - why did these efforts fail?

• AZ, FL voting machines
• Quadraphonic sound - LPs AND CDs
• http//www.dantiques.com/quad.htm
• Movie Rental DivX
• Low-fat fast food / Non-nicotine cigarettes
• Commercials in movie theaters
• IBM PC Jr with wireless keyboard
• http//www.pcworld.com/article/id,125772-page,4/ar
  ticle.html
• http//www.digibarn.com/collections/devices/pcjr-c
  hicklet-keyboard/index.html
• 1970s-era US compact cars
• http//www.motherjones.com/news/feature/1977/09/do
  wie.html

3

• Pre-Project Testing

4
One Aspect - Market factors

• No advantage over existing brands (OS/2 Warp)
• http//www.guidebookgallery.org/ads/magazines/os2/
  os220b/pics/02
• Early adopter (Apple Newton)
• http//www.msu.edu/luckie/gallery/mp2000.htm
• Lack of interest (Tablet PC?)
• Changing standards (SONY Betamax)
• Lack of brand identity in image-driven category
  (Coleco Adam computers)
• http//www.vintage-computer.com/adam.shtml
• Ignorance of buyer behavior for product category
  (Remote Control Walkman)
• Mispositioning (Retail on the Internet, better
  than reality issue)
• Failed opportunity (Xerography)

5
Unlikely successes - passed Pre Project Testing

• Personal computers
• DVD players
• George Foreman Grill
• http//en.wikipedia.org/wiki/George_Foreman_Grill
• Cable TV
• Expensive water
• SUVs
• Brand names, prominent on clothes
• Designer house paint
• Bose Wave Radio
• http//www.epinions.com/615259_Bose_Wave_Radio?sp
  ielec
• 150 sneakers

6
Sure things

• Digital photography
• Fuel efficient cars
• White boards
• Cell phones

7
Pre-Project Testing - (5 besides marketing)

• Marketability
• Purpose
• Feasibility
• Preparation / Coverage
• Chance of Success / Effect of Failure
• Culture (development and delivery)

8
Purpose

• Is there a business or economic justification for
  the project?
• Is there a societal justification?
• Is there an academic justification?
• Is there majority or managerial support?

9
Feasibility

• Can a SW Requirements Spec be written to solve
  the problem at hand?
• Can finances support 2x the project cost?
• Can the customer support 2x the project schedule?
• Can the delivery environment support the
  solution?
• Where does the best solution fall on a technology
  scale?

10
The Technology Scale

• Animal
• Manual
• Mechanical Tension/Movement
• Hydraulic Pressure
• Pneumatic Pressure
• Mechanical Engine
• Electrical Magnetic - switch closure

• Electrical Assist - amplification
• Electrical Control - stimulus and response
• Computational Assist
• Computational Origination

11
Preparation and Coverage

• Is an adequate / optimal team available?
• Is an adequate / optimal development environment
  possible?
• Is the solution technology achievable?
• Is there adequate financial backing?
• Wheres the contingency?

12
Chance of Success /Effect of Failure

• Has the path of least resistance been chosen? -
  All factors.
• Is a dissimilar backup system required?
• Is a failed system worse than not implementing
  the system?
• Will a competitive system threaten your delivery?

13
Development Culture

• Chance of turnover, burnout limit
• Team or management resistance to optimal
  development scheme
• Management support/catalyst and help
• Team culture / parallel development
• Personalities

14
Delivery Culture

• Customer support/catalyst and help
• Education, training required of users
• Acceptance
• Satisfaction
• Gratitude

15
6 Questions often asked in Pre Project Testing

• Is it the right system?
• Will it solve the right problem?
• It is possible to overautomate - some systems
  dont justify their costs.
• People problems do not need, and will not
  respond to technological solutions.
• If it aint broke, dont go broke fixing it.

16
Question 2

• What is at risk?
• Systems for which failure disaster are a poor
  bet.
• Are partial results better than nothing?
• Is intermittent operation better than nothing?
• Is a subset of full function available upon
  failure? Is the subset better than nothing?

17
Question 3

• How big and complex will it have to be?
• Smaller, simpler software projects have distinct
  advantages over large, complex ones.

18
Question 4

• How will it fit into the existing universe?
• The nondigital portions of a system dwell in the
  real world, whose behavior is constrained by
  physical laws. Keeping much of the system
  nondigital may yield a more predictable system.

19
Question 5

• What will it require of its users?
• It is inhumane to use people as passive
  monitors, and then require them to intervene
  suddenly when things go astray. We dont improve
  the situation when we turn airline pilots or
  nuclear power plant operators into scapegoats for
  bad system design.

20
Question 6

• Will it require extensive security?
• Data wants to be free. People will find ways to
  get information.