Click To Continue to the Next Page

Initiative Proposal

Marc W. George

Model Driven DevelopmentSoftware Development Life CycleSoftware Engineering Process

Problem Statement

The current “document centric” SDLC is inadequate to meet the needs of the business

21st Century agile IT requires: Improved Response to Business Needs Increased Productivity Increased Development Reliability Reduced Delivery Timeframes Reduced Costs

All above are required to successfully compete in today’s e-connected markets and communities as the competition focuses on these issues every day

Problem Statement Problems

Unpredictable and Unreliable Resolution of Software Requirements

Unstructured Methodology and Artifacts Project centric Formal requirements and analysis work begins too late

Labor Intensive SDLC Processes High reliance on SME’s High reliance on contractors

Non-Existent, Missing, Incomplete or Inaccurate Documentation of Existing Systems

Difficult Access to Software Requirements and Specifications Business and IT don’t form seamless and efficient

communities of practice for connecting critical software infrastructure decisions

Problem Statement Impacts

Missed Expectations Unexpected Scope Changes Rework Inability to effectively on-board resources Requirements not traceable to costs, effort, risks, or

testing Stakeholders

Business: Defines application needs IT: Delivers application solutions

Perspective Analogy

Commercial Real Estate Project – Inception Phase

Real Estate Investor / Developer I want to build a 17 story building at 1501 …

Architect It will take at least 1 year to produce the architecture and

design specifications … Staff Designer

Describe in detail what you want …. Building Inspector

See me when you have the plans … General Contractor

The labor will cost … Purchasing Agent

The materials will cost … Tenants

When we can move …

The Desired Architectural Design Specification

Perspective

Perspective The Delivered Architectural Design

Specification Location

The building will be located at 1501 S. Clinton Street in Baltimore, MD which is at the Southeast corner of the intersection of S. Clinton Street and Cardiff Avenue.

Architecture The building will a 17 story asymmetric octagonal, steel, concrete and glass structure with

a center pyramidal penthouse rooftop cascading over Cape Cod styled dormered side roofs.

Foundation The foundation will consist of both a square subterranean sub-structure and a non-uniform

asymmetric octagonal super-structure for support of the primary building structure. The cornerstone of the square subterranean sub-structure foundation will located exactly

10 feet from both S. Clinton Street and Cardiff Avenue, 125 feet below the lowest height of the existing sidewalks.

The other cornerstones of the subterranean sub-structure foundation will form a 150 feet x 150 feet square at the same depth.

The cornerstone of the octagonal super-structure foundation will located exactly 10 feet from S. Clinton Street and 25 feet from Cardiff Avenue.

The second super-structure cornerstone of the octagonal super-structure foundation will located exactly 25 feet from S. Clinton Street and 10 feet from Cardiff Avenue.

The third super-structure cornerstone of the octagonal super-structure foundation will located exactly 135 feet from S. Clinton Street and 10 feet from Cardiff Avenue.

The forth super-structure cornerstone of the octagonal super-structure foundation will located exactly 160 feet from S. Clinton Street and 25 feet from Cardiff Avenue.

…

Perspective The Desired vs. Delivered Architectural

Design Specification Should the Real Estate Investor / Developer Panic?

The Delivered Architectural Design Specification

Location The building will be located at 1501 S.

Clinton Street in Baltimore, MD which is at the Southeast corner of the intersection of S. Clinton Street and Cardiff Avenue.

Architecture The building will a 17 story asymmetric

octagonal, steel, concrete and glass structure with a center pyramidal penthouse rooftop cascading over Cape Cod styled dormered side roofs.

Foundation The foundation will consist of both a

square subterranean sub-structure and a non-uniform asymmetric octagonal super-structure for support of the primary building structure.

The cornerstone of the square subterranean sub-structure foundation will located exactly 10 feet from both S. Clinton Street and Cardiff Avenue, 125 feet below the lowest height of the existing sidewalks.

…

The Desired Architectural Design Specification

Initiative Proposal Solutions

Adopt a Model Driven Development (MDD) SDLC Establish an Enterprise Modeling Authority

Owns and Manages the Enterprise UML Model Owns, Maintains and Enforces UML Modeling Standards

and Guidelines Provides UML Modeling Training and Mentoring Critiques and Reviews All UML Modeling Reverse Engineers Existing Systems

Fully Deploy UML Modeling Tools and Supporting Infrastructure

CareFirst already owns sufficient licenses to start

Initiative Proposal Goals

Simplify and Solidify the Current SDLC Processes

Use a “model centric” SDLC Specify and Use a Common Business Process Modeling,

Requirements Specification, Analysis and Design Language

Unified Modeling Language (UML) Define Common Development Models

Enterprise UML Model (EUM) Produce Common Development Artifacts

Transforms (Artifact Automation)

MDD SDLC Modeling

Aids understanding of complex systems Shows the essentials of the systems from a particular

perspective Can hide non-essential details

Captures requirements precisely Communicates decisions unambiguously Evolves business requirements into solutions Is traceable Is provable Forms a foundation for implementation Creates reusable assets Allows exploring and comparing design

alternatives at a low cost

Common Language 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

Can be used with all processes, throughout the development life cycle, and across different implementation technologies

Technology agnostic Standard symbols and vocabulary

Common Language Why UML?

Globally accepted by software vendors Supported and integrated by a number of key

technologies owned by CareFirst Pega Proforma SystemArchitect WebSphere RAD Rational Solution Architect / Modeler

Purchased and Used by HSC Architect: 5 Floating Licenses / 5 Node Locked Licenses Modeler: 20 Floating Licenses / 20 Node Locked Licenses

Understood by consulting firms Supports the full lifecycle from inception to

code generation

Current CareFirst Specifications

Common Language

Common Language

Desired Evolution of CareFirst Specifications

Common Language

Desired CareFirst Specifications Goal

Common Models & Artifacts

Common Artifacts The Model

Models Model Elements

Use-Cases Databases Classes

Diagrams Source Code

Documents Specifications Plans Miscellaneous

Multimedia Files URLs

Common Artifacts

Enterprise Systems Organization and Classification

Common Artifacts

Release and Retirement Organization

Common Artifacts

Single Point of Access Documentation

What’s missing? Formal SDLC Methodology

Formal Definitions Scope vs. Goals vs. Objectives vs. Functional vs. Non-

functional Requirements Conceptual vs. Logical vs. Physical Requirements vs. Specifications vs. SOP’s Business Process Modeling vs. System Modeling Solution Design vs. System Design

Use Maturity Currently using Use-Cases for limited

requirements and analysis and not leveraging them universally

Not using other UML tools/models Training

Very Limited

Next Steps Inception Phase

Form a team to fully understand approach taken by HSC and evaluate it for CareFirst

Current CareFirst practices, i.e. CMMI Target IT state

Define going-forward rollout plan Elaboration Phase

Maintain and evolve current investment HSC Projects still have modeling to do

Facets Upgrade EBPP Workflow

Initiative Proposal Risks

Resistance to Process Change Knowledge Protectionism Domain Protectionism Bureaucracy Latency Exuberant Expectation

Collaboration Latency Insufficient Management Support & Funding Insufficient Resources

Model Management Training & Mentoring Critiquing and Reviewing

Objective To strengthen CareFirst’s position as the

leading Mid-Atlantic health benefits supplier by making IT agile and more:

Responsive to business needs. Reliable in delivering solutions. Efficient in producing solutions. Effective in resolving IT problems and issues.

Reaction

Possible Deliverable

Desired Deliverable

Reaction References

Model Driven DevelopmentSoftware Development Life CycleSoftware Engineering Process Initiative Proposal

Alternative: S:\Corporate Shared\Corporate Initiatives\2006 Initiatives\HSC\Technical Design Competency Center\MDD SDLC SEP Initiative Proposal\MDD SDLC SEP Initiative Proposal.doc

Projected Operational Savings with a MDD SDLC

Alternative: S:\Corporate Shared\Corporate Initiatives\2006 Initiatives\HSC\Technical Design Competency Center\MDD SDLC SEP Initiative Proposal\POS with MDD SDLC.xls

CareFirst Enterprise UML Model T:\Operations\IT\IT Shared\HSC Publishing Point\Current

Edition\Enterprise\index.html