Technology InsertionTraining

1
Technology Insertion/Training

• CS4320
• Fall 2003

2
The Impact of Technology
What is the oldest technology that impacted the
design of the Space Shuttle?
3
Controlling Technology

• What is technology?
• Managing technology is of key importance
• Creation
• Use
• Intrinsic belief in technology since we are
  techies.
• Silver Bullet Syndrome
• Technology Impact
• Strategy for Use
• Appropriateness for Use
• Adapt or Die

4
Usual Approach

• Read article in insert your favorite magazine
  here, or get presentation from vendor.
• Buy their product.
• Give to developers.
• Simultaneously cut schedule/budget by amount of
  promised return.

5
Correct Approach

• Establish Team
• Describe end-state (where are we going? How will
  this technology be used?)
• Baseline current state (where are we now?)
• Analyze the gap.
• Prototype a solution.
• Pilot the solution.
• Roll out solution.
• Analyze lessons.

6
Analyzing Gap

• ID potential technologies and attributes
  (criteria for selection)
• Rate technology according to specific attribute
  (0-5 where 5 excellent, 0 not supported)
• Rate importance of each attribute (0-5 where 5
  must have, 0 not considered)
• Construct decision matrix

7
Decision Matrix
10
6
0
8
4
0
0
0
0
0
4
1
1
2
3
5
5
25
0
5
8
Our company needs design tool?

• What are the technologies available?
• What attributes are important to us?
• Rate them.
• Make the matrix.

9
Risks in Technology Insertion

• Learning Curve
• Cost
• Vulnerability
• Access
• Politics
• Staff Buy-In
• Blame Game

10
Remember

• Always keep in the back of your mind
• Faster is not always better.
• Cheaper is not always better.
• Automation is not always better.
• Latest versions are not always better.
• But its not always easy to fight the system.
• Having a technology plan is better than winging
  it.
• But these are short term!
• Focus on applications/requirements not specific
  technologies.

11
Training

• Education vs. Training
• Concepts vs. Skills
• Life-long learning
• On-the-job vs. Off-site
• Train the trainer
• Dont fall into the Send who we can spare trap.
• Have a plan
• What are the goals? Motivation, Retention, New
  Skills?

12
Training Plans

• Use variety of techniques
• Orient on actual environment
• Assessment and Evaluation
• End of Course evals

13
OO Design Digression

• Open Closed Principle
• Modules are open for extension, closed for
  modfication.
• Liskov Substitution Principle
• Subclasses should be substitutable for their base
  classes.
• Consider behavior, not just is a
• Square/rectangle problem
• Dependency Inversion Principle
• Depend upon abstractions, not concretions

14
More Design Digression

• Interface Segregation Principle
• Many client-specific interfaces are better that a
  single general-purpose interface
• Release-Reuse Equivalency Principle
• The granule of reuse is the granule of release.
• Common Closure Principle
• Classes that change together belong together
• Common Reuse Principle
• Classes that are not reused together do not
  belong together.

15
Still more design digression

• Acyclic Dependency Principle
• The dependencies between packages must not form
  cycles.
• Stable Dependency Principle
• Depend in the direction of stability
• Ca incoming dependencies
• Ce outgoing dependencies
• Instability Ce / (Ca Ce)

16
Yet more design digression

• Stable Abstractions Principle
• Stable packages should be abstract packages
• Nc number of classes in a package
• Na number of abstract classes in package
• Abstractness Na / Nc
• Distance A I -1