1. Delivering peace of mind Architecting for Changes with UML Emmanuel FUCHS C2 Architect

2. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006

3. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 What, Why, How Facts: There Is No Way to Make a Simplified Software System Specification. Design Is Complex Because of Human to Human Communication. What: Apply Object Technologies for System Design : UML Object Domain Model. Why: The Costs Spring From the Design Not From the Construction How: Dual Ladder Of Advancement for Experts Recognizing. Dual Process Management and Technical Process. Spiral Use Case Driven Prototyping and Refactoring Process.

4. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Business/Domain modeling 1986: Ada OOD Grady Booch. 1990: OSI level 7 Application Service Element (ASE). 1992: NAOS: DCE IDL, Boehm Spiral. 1994: CORBA IDL. 1996: European Commission, Eurocontrol, ATC domain model. 1997: OMG transportation domain task force. 2001: OMG Radar Interface Standard definition. 2003: OMG Architecture Driven Modernization (ADM). 2004: Air Operations training and simulation.

5. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006

6. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Fred Brooks IBM OS/360 project manager: 1965 The Mythical Man-Month : 1975. No Silver Bullet: Essence and Accidental in Software Engineering: 1986. MMM Second Edition: 1995. No Silver Bullet Refired

7. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Werewolves in V cycle Documentation And mock-up Phase

8. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Werewolves in V cycle Documentation And mock-up Phase werewolves Silver Bullet

9. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Well Known Silver Bullets Ada OSI telecom CORBA Relation Data Base …. They all failed because of the lack of domain model (essence). No Silver Bullet Refired : OOD Brass Bullet

10. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Essential VS Accidental Real gains are in the design not in the construction: Essential Task: The fashioning of complex conceptual structures that compose the abstract software entity. Accidental Task: The representation of the abstract software entities in programming language. The costs spring from the design (The Essential) Essential = Design. Accidental = Development.

11. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Essential And Accidental in V cycle Essential Accidental Design

12. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Essential And Accidental Gain Ratio The costs spring from the design Potential Gain 90% Potential Gain 10% Essential: Design Accidental: Development

13. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006

14. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 E=MC² Creation of stars and planets, Michelangelo, Sistine Chapel Simple Unifying Principles.

15. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Human Creation ? No Simple Unifying Principles. Software is a human creation Software

16. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Brook Suggestions and remarks Buy Versus Build: COTS, Open Source. Components Based Development. Requirement refinement and rapid Prototyping: Use Case driven. Early Operational Handbook. Based on COTS. Refactoring. Incremental development-grow no build: Spiral iterative and incremental development. Functional Value Analysis Great Designers: Dual Ladder of advancement Architects of the future.

17. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006

18. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Mythical Man Month (MMM= 3M) t t Man T

19. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Mythical Man Month (MMM= 3M) t t Man T T/3

20. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Mythical Man Month (MMM= 3M) The Bearing of a child takes nine months, no matter how many women are assigned. =

21. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Mythical Man Month (MMM= 3M) t t Man 9 months 3 months =

22. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Division Case Division (A/B) Division (B = 0) Division (B <> 0) = Brass Bullet

23. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Factory Division (A/B) Division (B = 0) Division (B <> 0) Create() Factory =

24. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 The design pattern seminal book Ralph, Erich, Richard, and John at OOPSLA 1994 The Gang of Four

25. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006

26. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Great Designers: Dual Ladder Managerial Ladder Technical Ladder Senior member of the technical staff

27. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Thales People First Dual Ladder Senior member of the technical staff

28. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006

29. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Modeling method Grady Booch: Object Oriented Analysis and design with application. “A modeling method is a disciplined process for generating a set of models that describe various aspects of a software system under development using some well-defined notation.” UML is “only” the notation. We need a process: a modeling process.

30. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Grady Booch: OOAD

31. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Management Process Technical Process Dual Track Process CMMI DOD498 For example :RUP (Rational Unified Process) SSS ICD SSDD IRS SRS Business/Domain Model (UML) Sys-EM

32. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006

33. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Barry W. Boehm spiral Pair Review

34. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Iterative and Incremental time

35. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Iterative and Incremental Incremental Iterative

36. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Iterative and Incremental Not This !

37. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Use Case Prototyping Cycle Prototyping Refactoring Review Start Here Halfway break

38. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Typical learning Increment Quick And Dirty Prototyping And Modelling Code and Model Refactoring Review Break

39. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Martin Fowler

40. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Typical Prototyping Increment Rapid Prototyping And Modelling Model Refactoring Objective: Use Case Basic Functions Secondary Functions Review Objective: Use Case Basic Functions Secondary Functions Break

41. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Iterative and Incremental Learning Modelling/Prototyping Building

42. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Iterative and Incremental time Specifications Redaction Common V Cycle Learning And prototyping

43. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Iterative and Incremental CMMI Pair Review High Quality steady Level

44. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Conclusion Domain modeling Discover domain essential objects. Dual management ladder for expert recognizing Dual process management and technical process Spiral global process Domain process modeling SOA: Require Business/Domain model. Web Service. Work Flow, orchestration. WEB 2.0 Browser DOM example: IDL

45. THALESRAYTHEONSYSTEMS PROPRIETARY May 23 2006 Conclusion Thank You For Your Attention Questions are welcome Contacts : emmanuel.fuchs@thalesraytheon-fr.com