Design For Changes

50 %
50 %
Information about Design For Changes

Published on December 30, 2007

Author: elfuchs

Source: slideshare.net

Architecting for Changes with UML Emmanuel FUCHS C2 Architect

 

What, Why, How Facts: There Is N o 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: T he 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.

Facts:

There Is N o 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:

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

B usiness/ D omain 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 Op e rations training and simulation.

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 Op e rations training and simulation.

 

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

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

Werewolves in V cycle Documentation And mock-up Phase

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

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

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

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.

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.

Essential And Accidental in V cycle Essential Accidental Design

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

 

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

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

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.

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.

 

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

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

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

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

Division Case = Brass Bullet Division (A/B) Division (B = 0) Division (B <> 0)

Brass Bullet

Factory Create() = Division (A/B) Division (B = 0) Division (B <> 0) Factory

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

 

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

Thales People F irst Dual Ladder Senior member of the technical staff

 

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 .

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 .

Grady Booch: OOAD

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

 

Barry W. Boehm spiral Pair Review

Iterative and Incremental time

Iterative and Incremental Incremental Iterative

Iterative and Incremental Not This !

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

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

Martin Fowler

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

Iterative and Incremental Learning Modelling/Prototyping Building

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

Iterative and Incremental CMMI Pair Review High Quality steady Level

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

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

Conclusion Thank You For Your Attention Questions are welcome Contacts : [email_address]

Thank You For Your Attention

Questions are welcome

Contacts :

[email_address]

Add a comment

Related presentations

Related pages

Design for Change ::

WHY IS DESIGN FOR CHANGE NEEDED . To make Everyone believe That Children Are not helpless, change is possible and they can drive it. Read More
Read more

Design for Change | Germany

Aktuelle Dokumentation über ein Design for Change Projekt in Deutschland. Ziel! … ist es, Kinder und Jugendliche über die Methode von Design Thinking ...
Read more

Design for Change USA

Who we are. DESIGN FOR CHANGE is a curriculum and technology platform that builds character, capacity and confidence by engaging young people in social ...
Read more

Design for Change

Welcome to Design for Change - a community of people passionate about applying creative and technical skills to solve problems, address challenges and ...
Read more

Design for Change - YouTube

DESIGN for CHANGE is the largest global movement driven by children who believe that 'every child can' Design for Change reaches 35 countries, over 300,000 ...
Read more

Designs for Change

Designs for Change (DFC) is a 24-year-old, multi-racial, educational research and reform organization. Our basic mission is to serve as a ...
Read more

Design for Change

english. design. for. change
Read more

Design for Change

Design for Change. places citizens at the heart. of the city as contributors. to urban development. Every year, the Design for Change competition brings ...
Read more

Design for Change

Design for Change is an interior design firm that specializes in collaborating with individuals to create homes that both nurture and inspire. Based in ...
Read more