Architecting Success

Model Driven Development

Marc W. George

Agenda Introduction Objectives Presentation Roadmap Presentation Review and Discussion Next Steps Resources

Introduction Consulting Object-Oriented

Information Systems Architect and Methodologist

Technical Engineer on PCI Remediation Project Responsible for help design solutions Creating the network diagrams

Deployment Topology

Technical support for the project

Objectives

Introduce and establish a Software Engineering practice based on Model Driven Development

Promote Success

Roadmap

Perspective Observation Solicitation Specification Conversation Interaction Destination

Perspective A technique of depicting volumes and spatial relationships on

a flat surface. Compare aerial perspective, linear perspective. A picture employing this technique, esp. one in which it is

prominent: an architect's perspective of a house. A visible scene, esp. one extending to a distance; vista: a

perspective on the main axis of an estate. The state of existing in space before the eye: The elevations

look all right, but the building's composition is a failure in perspective.

The state of one's ideas, the facts known to one, etc., in having a meaningful interrelationship: You have to live here a few years to see local conditions in perspective.

The faculty of seeing all the relevant data in a meaningful relationship: Your data is admirably detailed but it lacks perspective.

A mental view or prospect: the dismal perspective of terminally ill patients.

Perspectives

Perspectives

Perspectives

Perspectives

Perspectives

Observation An act or instance of noticing or perceiving. An act or instance of regarding attentively or watching. The faculty or habit of observing or noticing. An act or instance of viewing or noting a fact or occurrence for

some scientific or other special purpose: the observation of blood pressure under stress.

The information or record secured by such an act. Something that is learned in the course of observing things:

My observation is that such clouds mean a storm. A remark, comment, or statement based on what one has

noticed or observed. The condition of being observed. Navigation:

The measurement of the altitude or azimuth of a heavenly body for navigational purposes.

The information obtained by such a measurement.

Observations Requirements

Business Goal Problem Statement & Justification

Benefit Stakeholder Request

Any type of requests a stakeholder might have on the system to be developed or any type of external parameter to which the system must comply

Feature Based on the benefits listed in problem statements

Observations Business Rule

Business Constraint Supplementary Specifications

System requirements that are not readily captured in behavioral requirements artifacts such as use-case specifications

Interface Glossary Item

Provide a consistent set of definitions

Solicitation The act of soliciting. Entreaty, urging, or importunity; a petition or

request. Enticement or allurement.

Solicitations Research Interview Collaboration

Capture SME Specification

Specification The act of specifying. The state of having a specific character. Usually, specifications. a detailed description or

assessment of requirements, dimensions, materials, etc., as of a proposed building, machine, bridge, etc.

A particular item, aspect, calculation, etc., in such a description.

Something specified, as in a bill of particulars; a specified particular, item, or article.

An act of making specific.

Specifications Documents Models

Models are abstract views Modeling

Aids understanding of complex system Shows the essentials of the system from a

particular perspective and hides the non-essential details

Capture requirements precisely Communicate decisions unambiguously Explore and compare design alternatives at a low

cost Forms a foundation for implementation

Specifications The Model

Models Diagrams

Documents Specifications Plans

Miscellaneous Multimedia Files URLs

Databases Source Code

Conversation Informal interchange of thoughts, information,

etc., by spoken words; oral communication between persons; talk; colloquy.

An instance of this. Association or social intercourse; intimate

acquaintance. The ability to talk socially with others.

Conversations Language

English Dialects Interpretive

Unified Modeling Language (UML) Standard language for visualizing, specifying,

constructing, and documenting the artifacts of a software-intensive system

Bridge between business and technical resources It can be used with all processes, throughout the

development life cycle, and across different implementation technologies

Technology agnostic Standard symbols and vocabulary

Interaction Reciprocal action, effect, or influence. Physics:

The direct effect that one kind of particle has on another, in particular, in inducing the emission or absorption of one particle by another.

The mathematical expression that specifies the

nature and strength of this effect.

Interactions Business Interface

UI (User Interface) Called Operation / Procedure

API (Application Interface) File COM CORBA Web Services SOA

Destination The ultimate goal for which something is done The place to which a person or thing travels or

is sent The purpose for which something is destined Written directions for finding some location The place designated as the end

Destinations

“The Model” The Models

Provide a means of Decreasing Levels of Abstraction Organization and Navigation Solution Evolution

Destinations

Decreasing Levels of Abstraction Business Business Processes Business Process Documentation Business Process Automation Application Systems

Destinations

Organization Filing System

Folders

Navigation Hierarchy of Folders Hyperlinks

URL’s Diagrams

Destinations

Solution Evolution A process of working

out or developing A process of change in

a certain direction A process of continuous

change from a lower, simpler, or worse to a higher, more complex, or better state

Destinations Solution Evolution

Model Lineage Business Use-Case (BUCM)

Use-Case (UC) Design (DM)

Implementation (IM)

Deployment (DM) Test ™

Destinations The Models

Business Use-Case Model System Use-Case Model* Analysis Model* Design Model* Implementation Model Test Model Deployment Model Topology Model

*Requirements Model

Destinations Business Use-Case Model

Identify the tasks, activities, roles and entities that accomplish business goals

Identify Automation Points Use-Cases (Automatable/ed Business Use-Cases)

Actors (Business Workers) Entities (Business Entity)

Destinations Use-Case Model

Models User – System Interaction Clear, concise overview of the purpose and

functionality of the system All functional and non-functional requirements are

mapped to at least one use-case and visa-versa

Destinations Analysis Model

Use-Case Analysis Objects

Object Analysis Object Attributes Object Functionalities Object States Object Relationships

Destinations Design Model

Use-Case Analysis Object Analysis Design Classes

Object Evolution Identify Mechanisms and Elements

Architectural Analysis Assess Viability of Architectural Proof-of-Concepts

Destinations Implementation Model

Construct Architectural Proof of Concepts Prototype User-Interface Implement Classes

Destinations Test Model

Test Cases Test Classes Test Scripts Test Data Test Results

Destinations Deployment Model

Executables Components Sub-systems Systems Data Sets

Resources

Object Management Group (OMG) www.omg.org

IBM / Rational developerWorks www-136.ibm.com/developerworks/rational

Addison Wesley “Object Technology Series”