+ All Categories
Home > Documents > Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston,...

Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston,...

Date post: 14-Jan-2016
Category:
Upload: amelia-whitehead
View: 214 times
Download: 0 times
Share this document with a friend
Popular Tags:
14
Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused by Duke… …which creates an opportunity for Swigert… …which soon becomes a new problem.
Transcript
Page 1: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Problems vs. Opportunities

Duke

Haise

Lovell

Mattingly

Swigert

Liftoff of Apollo 13

“Houston, we’ve had a

problem here.”

Mattingly has a problem caused by

Duke…

…which creates an opportunity for Swigert…

…which soon becomes a

new problem.

Page 2: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Scientific Problem Solving

Scientist

Analyst

Observe a phenomenon

Recognize a variance

Formulate a Hypothesis

Conduct an experiment

Investigate Propose a solution

Page 3: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Ishikawa Chart

Root Problem

Symptom Category

Symptom Category

Symptom Category

Symptom Category

Possible Symptom Categories

4Ps: People, Place, Procedure, Policy4Ms: Manpower, Machines, Methods, Materials4Ss: Surroundings, Suppliers, Systems, Skills

Possible Symptom Categories

4Ps: People, Place, Procedure, Policy4Ms: Manpower, Machines, Methods, Materials4Ss: Surroundings, Suppliers, Systems, Skills

Observed Symptom or Variance

SecondarySymptom

Page 4: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

The Problem Space

OK SolutionsOK Solutions Good SolutionsGood Solutions Best SolutionBest Solution Great SolutionsGreat Solutions

Search SpaceSearch Space Problem SpaceProblem Space

Page 5: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Open vs. Closed Systems

Known, Defined,

Predictable

Known, Defined,

Predictable

Known, Defined,

Predictable

Known, Defined,

Predictable

Known, Defined,

PredictableSubject to Unknown,

Undefined, and UnpredictableUnknown,

Undefined, Unpredictable

Unknown, Undefined,

Unpredictable

Closed System

Open System

INPUTS PROCESSES OUTPUTS

Page 6: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Functional Decomposition

Continually redefining the system under study into subsystems until reaching a point where no further value is gained from additional subsystem identification.

Page 7: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

SDLC

PreliminaryInvestigation

PreliminaryInvestigation

AnalysisAnalysis

LogicalDesign

LogicalDesign

PhysicalDesign

PhysicalDesign

ImplementationImplementation

MaintenanceMaintenance

Page 8: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Service Agreements

29%

22%

49%

Part of Full ServiceAgreement

Linked to ApplicationDevelopment

Maintenance Only

Page 9: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Typical PIECES AnalysisSymptom P I E C E SManagement reports are often not received on time.   X        Production line throughput is below expected standards. X          Product rework is high.     X   X  Inventory control reports are inaccurate.   X        Exceptions occur frequently and must be processed by hand.

          X

Production time is higher than industry average. X          Orders are often cancelled due to excessive delivery wait time.

X          Required information to process an order not available on demand.

  X        Organizational data redundancy is high.   X        Production lines are often down for repair or maintenance. X          Line personnel are often not aware of their production quota.

  X        Data transferred from production system to sales system by hand.

        X X

Several incidents of system sabotage have been recorded.       X    

Totals 4 5 1 1 2 2

Page 10: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Preliminary Investigation

• Key Activities– Problem definition

– Estimate problem scope

– Estimate project feasibility

– Estimate resource commitment

– Go/no go decision

• Primary Deliverables– Preliminary feasibility

report

– General problem statement

Page 11: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Analysis

• Key Activities– Create logical models

of current system

– Refine problem statement via detailed symptom analysis

– Determine requirements for new system

• Primary Deliverables– DFD of current system

– ERD of current system

– Formal problem statement

– Formal requirements definition

Page 12: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Logical Design

• Key Activities– Revise current system

logical models to reflect proposed system changes

– Validate logical model of proposed system against requirements determination

• Primary Deliverables– DFD of proposed

system

– ERD of proposed system

– Final performance specifications

Page 13: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Physical Design

• Key Activities– Determine hardware

specifications– Determine software

specifications– Conduct feasibility analysis

and cost justification for new system

– Estimate implementation schedule

– Design data structures– Prepare training guidelines– Prepare preliminary testing

procedures

• Primary Deliverables– Detailed hardware

specifications

– Detailed software specifications

– Final feasibility report

– Physical data structures and data dictionary

– Implementation schedule

Page 14: Problems vs. Opportunities Duke Haise Lovell Mattingly Swigert Liftoff of Apollo 13 “Houston, we’ve had a problem here.” Mattingly has a problem caused.

Implementation

• Key Activities– Acquire hardware and

software

– Determine location requirements

– Install the new system

– Create test data and conduct initial system tests

– Train all end users

– Verify all end user and system documentation

• Primary Deliverables– Final performance test

metrics

– Fully trained end user community

– Fully installed system

– Fully converted data files


Recommended