karl reed acs/gc 30/4/2002-1 technology transfer…a national and commercial imperative chair...
TRANSCRIPT
Karl Reed ACS/GC 30/4/2002-1
Technology Transfer…A National and Commercial Imperative
Chair IEEE-Computer Society Tech. Council on Software Engineering Governor, IEEE-Computer Society(1997-1999,2000-2002),
Director, Computer Sys. & Software Engineering Board, ACS, Department of Computer Science & Computer Engineering, La Trobe
University Hon. Visiting Professor, Middlesex University
by (Visiting) Prof. Karl Reed,FACS, FIE-Aust., MSc,ARMITSchool of Information Technology, Bond Uni.
liberal use will be made of ideas from Jason Baragry, David Cleary and Jacob Cybulski
“those who fail to study history are bound to repeat it”
Karl Reed ACS/GC 30/4/2002-2
The optimists view of technology The optimists view of technology transfer..transfer..
Karl Reed ACS/GC 30/4/2002-3
BUT FIRST… FOR TT TO WORK…BUT FIRST… FOR TT TO WORK…
1. Conditions of Necessity Must Hold… The creation of an irresistible desire for or belief in the value of some technology that leads to its
adoption as a matter of urgency Demonstration that new* technology can solve some commercial problem or improve some process
2. Conditions of Sufficiency… Such a new technology must actually exist, or be capable of being created. A TT path or mechanism that is feasible must exist
/ * In this context, “new” means “..not currently exploitable by the transferee..”. The technology could be well-known
Karl Reed ACS/GC 30/4/2002-4
Our Problem…Our Problem…
Obviously we are.. We’re doing research aren’t we?
You mean it may not be? If it were believed to be true, there’d be no real TT
problem.
A. Are we making a real improvement?
B. How can we be sure this is true?
Karl Reed ACS/GC 30/4/2002-5
Some Definitions..Some Definitions.. TECHNOLOGY AWARENESS…
To be aware of some aspect of the technology not currently being used, and to understand it well enough to decide to adopt or not to adopt.
TECHNOLOGY TRANSFER… To achieve technology adoption to a level proficiency which permits use to
produce products and services on a commercial basis, or their improvement…(this is our goal, as a transferer or transferee)
TECHNOLOGY ADOPTION The process of adopting a technology which is being transferred ..(what w
e did as part of the TT process, if it worked..)
TECHNOLOGY AQUISITION The process of re-discovering or re-inventing a technology for the purpose
of having unimpeded rights to exploit it.. (We re-invent the wheel..)
Karl Reed ACS/GC 30/4/2002-6
Some Definitions..Some Definitions..(cont’d)(cont’d)
TECHNOLOGY RETENTION The maintenance of some old technology for reasons of:-
Cultural significance, at a national level (cf. Sweden, and the Japanese National Living Treasures)
legacy technology and inventories needed to support significant obsolescent products or services
Karl Reed ACS/GC 30/4/2002-7
1.1. National and Commercial Reasons for TTNational and Commercial Reasons for TT
NATIONAL… Protect living standards by seizing
a slice of a growing market, either new, established or old technology.
e.g. Korean semi-conductor, and auto, Japanese cameras, semi-conductor and auto
Ensure requisite technological diversity by preventing technological hegemony
e.g. European auto’s, ARM, telecom equipment, AIRBUS, vs dominance of Windows
COMMERCIAL.. Protect profits and market share by sei
zing slice of a new market.
Increase profits by reducing costs Create a new market Ensure product differentiation Ensure product similarity Retain key skilled employees Miss-judgment……
Karl Reed ACS/GC 30/4/2002-82. But First…Types of technology2. But First…Types of technologyWe identify seven issues…The technology :-
a. PRODUCT embodied by the complete product,Its capabilities, in function, performance etc.
b. COMPONENTS,the parts, materials, sub-systems
c. PRODUCTION used in its production,tools, design techniques
d. SKILLS the terms of human skills used in production,
e. PROCESS of productionorganisation of production, process
Karl Reed ACS/GC 30/4/2002-9
But First…Types of technologyBut First…Types of technology..(cont’d)..(cont’d)
f. ENABLING underlying technology which provides the basis for many economic areas,
Semi-conductors, metallurgy,optics, production engineering, metal-working, www….
g. MARKETING philosophy and strategies ,
h. PLANNING AND MANAGEMENT
Karl Reed ACS/GC 30/4/2002-10
AND NEXT AND NEXT Levels of technologyLevels of technology
a. BLUE-SKY ahead of state of the art and practice,Who knows if it really works, believed to be realisablee.g. Cray and the planar transistor, modern cpu design
b.STATE OF THE ART, the leading edge of the most advanced..
Only the most skilled and experienced organisations
c. STATE OF PRACTICE, BEST PRACTICE what successful organisations are doing…
d. ADVANCED future best practice,
e. ROUTINE any experienced group should be able to do this
f. BASIC any competent group should be able to do this
Karl Reed ACS/GC 30/4/2002-11
3. Barriers to TT…National Level3. Barriers to TT…National Level TRADE AND INVESTMENT POLICIES-NEGATIVE
Restrict Govt’s capacity to support local firms in technology acquisition.e.g. - US transnationals deemed Australian for grant, (export) subsidy, and Govt. purchasing
preferences - “OFFSETT” policies which force TT not legal under WTO
- Chinese Gov’t could not fund a Chinese company to develop a competitor to Windows under WTO
SECURITY AND DEFENCE AGREEMENTS US laws prevent encryption technology (and other technology) from being transferred or
developed. E.G. Japanese machine tools and submarine propellors
RESULTS… Limitation of technological diversity Difficult to “grow” an Ericsson or LG in Australia
Karl Reed ACS/GC 30/4/2002-12
3. Barriers to TT…Commercial3. Barriers to TT…Commercial ACQUISTION COST
Licensing and purchase costs may be large.
ADOPTION COSTS Training costs, Learning curve costs
LOST OPPORTUNITY COSTS.. What we would have earned if we weren’t doing this.. Resource-confiscation costs
ROI REQUIREMENT Will we ever recover our net investment over time? Can we calculate the investment up front? Ammortisation of existing investments/ inventories?
RESOURCE REQUISITIONING Impact of allocating productive resources to a new venture..
Normalised time To achieve breakevenc
Pn
Pn
7.00 1.05
3.33 1.10
2.50 1.15
2.00 1.20
1.5 1.30
1. 1.50
Karl Reed ACS/GC 30/4/2002-13
A Tech-Transfer ModelA Tech-Transfer Model
NOT THAT SIMPLE!NOT THAT SIMPLE!
Karl Reed ACS/GC 30/4/2002-14
4. Case Studies… The ANSEI Proposal4. Case Studies… The ANSEI Proposal DEVELOPED A PROPOSAL SUPPORTED BYS/W
COMPANIES-RESEACH --> INDUSTRY APPROACH TAKEN..
Show respect for companies and their achievements Show industry knowledge Formulate technico-commercial drivers, technical issues related to commercial problems Show highly leveraged returns
RESULTS… Great proposal, interdicted by the SEA initiative Enthusiasm from industry But, not from Vic government…
THE INDUSTRY WE WERE DEALING WITH…
Karl Reed ACS/GC 30/4/2002-15
Remember Our Problem…Remember Our Problem…
A. Are we making a real improvement?
B. How can we be sure this is true?
C. SE Researchers talk down to industry!
Karl Reed ACS/GC 30/4/2002-16
Our Knowledge of Industry The Australian Example..
THE SOFTWARE INDUSTRY OF THE LATE 1960'S AND EARLY 1970'S WAS…
a) PACKAGE (and hence re-use) ORIENTEDA wide range of packaged software on 16 bit and mainframes was produced. E.G. Accounting, payroll, engineering design, manufacturing, insurance, etc.
b) KNEW ABOUT PORTABILITY…Many of these were transported between different OS and machines.One suite of packages in assembler (50klocs) was "ported" to at least 6 different systems
c) RECOGNISED THE RE-USE OF SKILLS , IDEAS AND DESIGN…
The concept of "the continuity of experience" syndrome, the human "experience factory".
FORMAL PROCESS MODELS DO NOT APPEAR TO HAVE BEEN IMPORTANT
Karl Reed ACS/GC 30/4/2002-17Australia (cont’d)
THE SOFTWARE INDUSTRY BY THE MID 1980'S WAS…(cont'd)
a) A HIGH-LEVEL TOOL DEVELOPERDeveloped "4GL's" and APPLICATION GENERATORSBoth HP and DataGeneral used Australian products for their early Application GeneratorsThe product Lansa (ASPECT) is one of three Application Generators for the S/38 (now AS/400)
b) PRODUCING LARGE-SCALE MAINFRAME
PACKAGES & SYSTEMS…Major international supplier of insurance s/w,Major developer of large-scale s/w for Govt. and Industry.
c) UNDERSTOOD PROTOTYPINGCDA used SNOBOL in the mid-1970's for protoyping commercial systems.
Karl Reed ACS/GC 30/4/2002-18Australia (cont’d)
BY THE LATE 1980'S EARLY 1990'S WAS…a)PRODUCING OO LANGUAGES AND TOOLS…
The language OCHRE…
b)UNDERTAKING INDUSTRY-WIDE STUDIES…Productivity studies based on function points (Aust. Software Metrics Assoc.)SPICE (Software Quality Association/ACS)
c)DEVELOPING S/W QUALITY STDS AND CERTIFICATION… AS3563, S/W Assurance Standard being mandated by Govt.Software Quality Institute lead by Geoff Dromey at Griffith Univ.
d)OTHER THINGS… F-P estimating tools, OO based specialists consultancies…commercial use of
Formal Methods on small scale
e)TTM competency… F-P estimating tools, OO based specialists consultancies…commercial use of
Formal Methods on small scale
Karl Reed ACS/GC 30/4/2002-19
THE HISTORY…(cont'd)
THE SOFTWARE INDUSTRY'S WEAKNESSES…a)LIMITED INTERACTION WITH RESEARCH
COMMUNITY…b)JEALOUS AND SECRETIVE ABOUT
DEVELOPMENT METHODSc)ABSENCE OF TARGETED RESEARCH CENTRESd)NEEDED GREATER EMPHASIS ON WINDOWS &
MacIntosh S/W
THE SOFTWARE INDUSTRY'S ASSETS…a)Good supply of well trained graduates in CS and
EDP More than 14 000 p.a.!
(now 7 SE degrees in Australia)b)Strong managerial/ technical culture of package
and product development
Karl Reed ACS/GC 30/4/2002-20Australia (cont’d)
THE SOFTWARE INDUSTRY's PARAMETERS…
TOTAL SALES…US$1.8BS/W PRODUCT of totalDOMESTIC SHARE OF PRODUCT EXPORTS US$500M (1993 FIGURES)
by comparison, the Japanese s/w industry has less than 15% of T.O. in s/w product.
There are 40 Australian S/W companies selling product in Japan
Karl Reed ACS/GC 30/4/2002-21
Approaching Software Developers…Approaching Software Developers…
Be able to show ROI after adoption costs (equipment + training) and productivity losses due to learning curves after adoption. (improved profit)
Show resolution of competitive advantage problems (beat off competitors, maintain market share)
Show new market opportunities due to new products/services
Technico-Commercial Drivers… the linkage
Show an economic benefit
The goal is to find a high-level, one-line statement of pressing commercial issue that maps directly on to a “technology acquisition” (research) agenda (map idea to common concept base accessible to highest management)
Karl Reed ACS/GC 30/4/2002-22
Typical SE Research Agenda Australia ~ 1997
1.Re-engineering and Empirical Studies of s/w Practice,
2.Tools and Methodologies, and Design Representation,
3. Re-Use,
4. Evolving Software,
6. Object Oriented Dev.
7. Product Quality Measurement
8. Time-to-Market
9. Testing
¶ Impact of developments in run-time platforms
¶ Low-cost and evolving software
¶ User Interface Development
¶ Software Productivity
¶ Performance Predictability
¶ Software Product Quality Certification
¶ Time to Market ¶
Technico-commercial Drivers
Research-Commercial Mapping… Defining Relevance
Karl Reed ACS/GC 30/4/2002-23
The ANSEI
Technico-Comercial Driver to Research agenda
mapping
Table I - Relationship Between Technico-Commercial Issuesand Research Agendas
Technical-Commercial Issue
Proposed Research
Issue Implications Main Agenda Items Sub-Agendas OUTCOMES SupportsImpact ofdevelopments in run-timeplatforms
Addfunctionalityto legacySystems(e.g.GUI),ability tomovesoftwarebetweenplatforms,need toreducemaintance
1.Re-engineering andEmpirical Studies ofs/w Practice,
Designreasoningrecording,empericalstudies ofpractice,softwaremigration,impact onmethodologies
Tools andmethodologies, detailedknowledge ofcurrentpractice
Processimprovement,validation ofmethodologies,actual measuresof s/w quality,s/warchitecture,domainengineering,evolving s/w,nature ofsoftwareengineering
Low-costandevolvingsoftware
Modifiability,maintanance,techniquesfor designing
3. Re-Use,
4. Evolving Software,
6. Object OrientedDevelopment
8. Time-to-Market
Methodologies formodifiableand evolvingsoftware,empericalstudies ofexistingpractice
Methodologies incorp.design forevolution, s/wquality , tools
Automaticqualitymeasurement,processimprovement,nature ofsoftwareengineering
UserInterfaceDevelopment
Design forergonomics,engineeringbased onapplicationsdataprocessing
1. Re-engineering andEmpirical Studies of s/wPractice,
3. Re-Use,
5. Engineering ofUser Interfaces,
6. Object OrientedDevelopment
9. Testing
Ergonomics,characterisaton ofprocessing,methodologiesfor this
Methodologies forengineeringuserinterfaces,
Allmethodologies,ergonomics
SoftwareProductivity
Reuse,improvedmethods
1. Re-engineering andEmpirical Studies of s/wPractice,
2. Tools andMethodologies, and DesignRepresentation,
3. Re-Use,
9. Testing
Softwareresuse, andmethodologiesexplicitlyincluding this,prescriptivemethodologies, s/warchitecture,improveddesignrepresentation,projecttracking
Methodologies generatingre-usablecomponents,maximisingre-use withinsingleprojects, andmaximinsingre-use of"artifacts",includingdesign
Designrecording,nature ofsoftwareengineering,s/warchitecture,evolvingsoftware
PerformancePredicatability
Appropriatemethods forincludingconstraints indesign
1. Re-engineering andEmpirical Studies ofs/w Practice,
2.Tools andMethodologies, andDesignRepresentation,9. Testing
Performanceengineering,methodologies, operationalmathematicalmethods
Methodologies incl. newmathematicalmodels, toolssuppportingthis,diagrammingschemes
Designrecording,nature ofsoftwareengineering,s/w architecture
SoftwareProductQualityCertification
Automaticandincrementalmeasurementof product
1.Re-engineering andEmpirical Studies of s/wPractice,
2.Tools and Methodologies,and Design Representation,
3. Re-Use,
4. Evolving Software,
7. Product Q.Measurement
9. Testing
Programstructure,metrics andlanguageprocessors
Tools forautomaticmeasurement
S/Warchitecture,designrecording,nature of SE
Time toMarket
ImprovedDevelopmenttechniques,Tool support,CASE
1.Re-engineering EmpiricalStudies of s/w Practice,
2.Tools and Methodologies,and Design Representation,
3. Re-Use,
4. Evolving Software,
6. Object Oriented Dev.
7. Product QualityMeasurement8. TTM9. Testing
As forproductivity,but specialemphasis onincrementaldelivery, andqualityenhancingmethodologies
Methodologies and tools,designrecording
s/warchitecture, re-use andevolvingsoftware
Karl Reed ACS/GC 30/4/2002-24
Technology Transfer Mechanisms“Champions” in the organisations targetted.. Need to be involved by the researchers Disclosure, workshops, training, publications, technical newspapers Professional associations SIG’s and meetings Wining and dinning managers
Joint trials of technology, may need to be funded by research centre…(various models, including fully profitable contracts.. Must counter lost opportunity cost problem)“Exemplar” projects by the research centre, creating “technology pull” Incremental technologies may be easier to adopt
Karl Reed ACS/GC 30/4/2002-25Technology Transfer Mechanisms(cont’d)
NIH has cultural, economic and technical basis..
(It took ~ 5 years for Ada/Clean-room/OO to show an overall cost benefit cf Fortran at NASA/SEL)
50% productivity gain needed for break-even in one learning curve time..
Karl Reed ACS/GC 30/4/2002-26
PRESENTING A RESEARCH PROGRAMAS A TT OPPORTUNITY
§ ASSUME WE HAVE AN AGENDA IN RE-ENGINEERING.. HOW COULD WE PRESENT THIS TO A PROSPECTIVE PARTNER?
Karl Reed ACS/GC 30/4/2002-27
What if we had a large re-engineering project?
component semantics and concept extraction.. The role of re-engineering.. S/W Archaeology...
program is a model of some real world process
exactly what “concepts” are represented in terms of non-procedure replicated code fragments?
What are their semantics?
-What impact do these have on program composition?
How do these relate to different problems in the same domain? ..different problems in different domains?
How are components modified in practice and what is the outcome?
Karl Reed ACS/GC 30/4/2002-28
The role of re-engineering.. S/W Archaeology and S/W Architecture....
recovery of standard architectures
identification of s/w construction practices, e.g. shifts from one programming style to another
§ architectural styles
development of maintainability and evolvability classifications for --
development of maintainability and evolvability classifications for architectural styles
§ design methodologies
Karl Reed ACS/GC 30/4/2002-29
component semantics and concept extraction.. The role of re-engineering.. Architecture issues for the S/W Archaeologist
identification of design approaches which ensure that conceptual architectures are transferred to implementation
identification of standard mappings from conceptual to actual architectures which occur using different design approaches on different problems
Karl Reed ACS/GC 30/4/2002-30
A National Example of Tech. Acq.A National Example of Tech. Acq.Korea’s Semiconductor IndustryKorea’s Semiconductor Industry
a. ~1974, packaging chips in epoxy for US companies
b. Early 1980’s government policies to build a SC industry..
c. ~ 1986 first 256k dram
d. mid 1990’s aggressive transnationals in SC, with plants in UK etc.
e. Enabling techs.. Semiconductor physics and chemistry
Karl Reed ACS/GC 30/4/2002-31
a. Korean-Malaysian (and originally Japanese, Swedish) automobile manufacturers started with “old” technology.
b. Skill and labour-intensive industries may not need the latest plant etc.
c. Mass products for 2/3 of the world’s population must be cheap.. Where is the us$300 fully functional PC?
d. How many gates are needed in a controller for white goods? (maybe this can be achieved with a fab-plant two generations old?)
e. Environmentally sound housing may mean going back to adobe construction.
AND SO ON….
Appropriate Technologies the wave Appropriate Technologies the wave followersfollowers
Karl Reed ACS/GC 30/4/2002-32
a. TT IS NOT EASY…..
b. HOWEVER, IT IS OF NATIONAL AND COMMERCIAL IMPORTANCE.
c. TT FROM RESEARCH INSTITUTES TO INDUSTRY MUST RECOGNUSE COMMERCIAL REALITIES
d. TT DOES NOT NEED TO FOCUS ON THE BLEEDING EDGE
e. BUT, IT IS NOT EASY!
CONCLUSIONSCONCLUSIONS
Karl Reed ACS/GC 30/4/2002-33
Tak Ska du har…Tak Ska du har…
Karl Reed ACS/GC 30/4/2002-34
Stages of SE...Immature methodologies, Fortran, Cobol, Assembler-70’s,telephone systems
Systems Analysis and Design methodologies70’s-80’s
Formal Methods, info. Hiding, architecture, strong typing, CASE,RE,SCS,formalised testing, banking networks,internet,PC-OS,
OO,CMM,Process Modelling,re-use, cots,dig.flight control systems,EFTPOS
Large-scale s/w, comsumer
goods,engine management
systems, ABS
time to market, extreme
programming, web systems, free-ware,
94-00’s
Customer req dominate,ROI mandatory
Unreliable, technology history free, ROI independent-business model? s/w surprises
Cottage industry, but well intentioned
Mature?Body of Knowledge but no universal success
Cottage industry, reversion to the old-days
Determinate, quality driven, high reliability, business model oriented