1. JVB-STC'97- 1 #*#* Successful Adoption and Use of Object Oriented Technologies STC ‘97 April 30, 1997 Jim Van Buren

2. JVB-STC'97- 2 #*#* Objective u Presentation of Model for Adoption of OT by DoD Organizations v For Non-OO capable DoD organizations v Training Issues v Development Process Issues v OO Management Issues

3. JVB-STC'97- 3 #*#* Outline u Background v Object Oriented Definitions v Technology Adoption u OO Technology Adoption v DoD Adoption Context v Training v Development Process v Management v Pushing Adoption 

4. JVB-STC'97- 4 #*#* Why OO? u Maintainability Advantages u Time to Market u Required by COTS Libraries u Reuse u... v Organizational Change v Existing System Meets Requirements v... v Resource Cost (Memory and Processing Time) Why Not OO?

5. JVB-STC'97- 5 #*#* Encapsulation Underlying Concept behind OO u An object’s interface is the only way the object can be manipulated or used u Clients know only about an object’s interface u Encapsulates Data and Methods v Allows Objects and their clients can be written in different languages v Allows Objects and their clients can run on different machines v Isolates inevitable maintenance changes v Enables Geographically Distributed Development by loosely coupled teams v Enables Evolutionary Development v Enables Reuse

6. JVB-STC'97- 6 #*#* What is OO Development? u Conceptualize and Abstract Requirements u Analysis (Develop Models) u Design (Create Architectures) u Evolve Application (Iteratively) u Identify Classes u Identify Objects u Identify Relationships u Specify Interfaces u Write Code u Fix Application (Iteratively) Macro Micro Both are Valid Views! Both are Necessary!

7. JVB-STC'97- 7 #*#* Technology Adoption u The STSC helps U.S. Air Force organizations identify, evaluate, and adopt technologies that improve software product quality, production efficiency, and predictability.” Adapted From: Fowler & Przybylinski, 1988 AdoptEvaluateIdentify Time Contact Awareness Understanding Evaluation Trial Use Commitment Adoption Institutionalization

8. JVB-STC'97- 8 #*#* Technology Adoption Based on SEI’s IDEAL Model OT is increasingly a potential solution Tailor and use “standard” STSC OT adoption plan. Pilot OT

9. JVB-STC'97- 9 #*#* Outline  u Background v Object Oriented Definitions v Technology Adoption u OO Technology Adoption v DoD Adoption Context v Training v Development Process v Management v Pushing Adoption

10. JVB-STC'97- 10 #*#* DoD Adoption Context Project Attributes u Functionality Errors not Tolerated u Schedule Predictable u Maintainable Very long software lifetime u Community expects Reviews and Documents u Move underway from Mainframe to Workstation or PC platforms

11. JVB-STC'97- 11 #*#* DoD Adoption Context (cont.) Organizational Attributes u Personnel v CiviliansVery Low Turnover v MilitaryVery High Turnover v ContractorsCritical to success u Hierarchical and Command Driven Organizations u Very Strong Mission Focus u SPI Activities underway u Training Funds controlled by Organization (not Project)

12. JVB-STC'97- 12 #*#* OT Adoption Issues General Adoption Issues u Resistance to Change u On Going Improvement Programs u Mission Requirements OO & OT Specific u Training u Development Process u Management Changes

13. JVB-STC'97- 13 #*#* Training u Focus on Paradigm Shift v Education not Training v Very Long Time Scale u Must Map to Development Process v Training not Education u Training Truisms Apply v Just in Time v Mentoring u Build Organic Training Capability v High Turnover v Long Product LifeCycle u Provide Training to Project Reviewers

14. JVB-STC'97- 14 #*#* Development Process u Incremental v Largest Process Change v A few Formal Reviews replaced by many “In Process” Reviews v Monolithic Specification (requirements or design) replaced by evolving baseline(s) u Different from the Old Process v Let the technical gurus specify it v Make sure it specifies sound software engineering processes  Formal Design and Test subprocesses  Metrics Collection  A Formal Peer Review Process  Coding Standards u Focus on the Software Architecture v Should be the first technical step

15. JVB-STC'97- 15 #*#* Management of OO Projects in the non OO organization The basics do not change... just the details.  Staffing  Get, keep, and train the right people. (Abstraction Skills)  Estimating  Different size metrics. (MOOSE, POPS, OPA)  Planning  Different milestones. (In Process Reviews)  Tracking Progress  Different measures of completeness. (Use Earned Value)  Requirements Change  RM very important due to incremental approach.  Risk  Identify and Track (Particularly New Technology Impacts)  Leadership  Different learning curves for staff.  Both new technology and new development paradigms are being introduced.  When the going gets tough the development staff will demand to use their tried and true methods.  There will be an intense desire to hack.

16. JVB-STC'97- 16 #*#* OT Adoption Issues u No Explicit Reason for OT u “Hacking” Issue v Micro OO (without Macro OO) u Estimation Techniques and Heuristics v Lack of Experience, No Industry Standards u Software Architecture v How is a Product Line Approach institutionalized? u Other Organizational Elements v i.e., CM, QA, Test have to change their processes u Expectations - OT is not a Silver Bullet.

17. JVB-STC'97- 17 #*#* Pushing OT Adoption u Specifying “... shall use OO...” does NOT work v Often get Functional Systems expressed as Objects v Developer gets “Time to Market” Savings when acquirer wanted High Maintainability u Solution Strategy v Explicitly Determine why OO  (e.g., Maintainability, Reuse, Time to Market, etc.) v This is the requirement, not “...shall use OO...” v Express the requirement in a testable way  Example: For a goal of high maintainability - Use Coupling, Cohesion, Inheritance Depth (and other) metrics to define design maintainability u Remember v OT is not a Silver Bullet.

18. JVB-STC'97- 18 #*#* Conclusions u OT Adoption needs to be planned like any other project v Good planning implies you have a process for adoption projects v The adoption process needs to be tailored for OO adoptions u DoD has a unique development culture v Most OO experience and practices relate to the commercial world u OT is not a Silver Bullet v Be explicit about your goals and OT may be the solution u Organizational Adoption of OO in a Federal Setting is not easy... but it can succeed

19. JVB-STC'97- 19 #*#* Successful Adoption and Use of Object Oriented Technologies Jim Van Buren Charles Stark Draper Laboratory Software Technology Support Center Voice:(801) 775-5555 (x3042)DSN 775-5555 (x3042) Fax:(801) 777-8069DSN 777-8069 Email:vanburej@software.hill.af.mil