1 / 45

Architecting for Changes with UML

Learn how to apply object technologies, specifically UML, for system design and improve the cost-effectiveness of software development. Explore the essential versus accidental tasks in the design process and discover the benefits of domain modeling.

andynelson
Download Presentation

Architecting for Changes with UML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecting for Changes with UML Emmanuel FUCHS C2 Architect

  2. 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.

  3. 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.

  4. 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

  5. Werewolves in V cycle Documentation And mock-up Phase

  6. Werewolves in V cycle Documentation And mock-up Phase Silver Bullet werewolves

  7. 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

  8. 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.

  9. Essential And Accidental in V cycle Design Essential Accidental

  10. Essential And Accidental Gain Ratio The costs spring from the design Potential Gain 90% Essential: Design Potential Gain 10% Accidental: Development

  11. E=MC² Creation of stars and planets, Michelangelo, Sistine Chapel Simple Unifying Principles.

  12. Human Creation ? Software is a human creation No Simple Unifying Principles. Software

  13. 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.

  14. Mythical Man Month (MMM= 3M) Man t T t

  15. Mythical Man Month (MMM= 3M) Man t T Man T/3 t

  16. Mythical Man Month (MMM= 3M) The Bearing of a child takes nine months, no matter how many women are assigned. =

  17. Mythical Man Month (MMM= 3M) Man t 9 months Man = t 3 months

  18. Division Case Brass Bullet =

  19. Factory Create() =

  20. The design pattern seminal book Ralph, Erich, Richard, and John at OOPSLA 1994 The Gang of Four

  21. Great Designers: Dual Ladder Managerial Ladder Technical Ladder Senior member of the technical staff

  22. Thales People First Dual Ladder Senior member of the technical staff

  23. 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.

  24. Grady Booch: OOAD

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

  26. Barry W. Boehm spiral Pair Review

  27. Iterative and Incremental time

  28. Iterative and Incremental Iterative Incremental

  29. Iterative and Incremental Not This !

  30. Use Case Prototyping Cycle Prototyping Halfway break Start Here Review Review Refactoring

  31. Typical learning Increment Break Review Quick And Dirty Prototyping And Modelling Code and Model Refactoring Review

  32. Martin Fowler

  33. Typical Prototyping Increment Objective: Use Case Basic Functions Secondary Functions Objective: Use Case Basic Functions Secondary Functions Break Review Rapid Prototyping And Modelling Model Refactoring Review

  34. Iterative and Incremental Building Learning Modelling/Prototyping

  35. Iterative and Incremental Learning And prototyping Common V Cycle time Specifications Redaction

  36. Iterative and Incremental High Quality steady Level Pair Review CMMI

  37. 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

  38. Conclusion Thank You For Your Attention Questions are welcome Contacts : emmanuel.fuchs@thalesraytheon-fr.com

More Related