business information system specification ......hershey chocolate . enterprise architecture then...

Whitemarsh Information Systems Corporation

BUSINESS INFORMATION SYSTEM SPECIFICATION DEVELOPMENT

STRATEGY FOR SUCCESS

1

2/9/2011


DATA MANAGEMENT PRACTICES

2/9/2011

2

Communities of Interest

Independent Verification &

Validation

Business Information System Specification

Data ManagementPrograms

1

2

34

5


TOPICS

1. Introduction and Rationale2. Traditional Methodology3. Methodology Problems4. Replacement Methodology5. Problem Resolutions6. Replacement Methodology Milestones7. Where Used / Past Performance8. Approach Comparison Summary9. Summary and Benefits10. Demonstration

3

2/9/2011


1.0 INTRODUCTION AND RATIONALE

Ultimate Objective Real Problems to be addressed Reasons for success and failure The Knowledge Worker Framework GAO’s Identified BIS Development Errors

2/9/2011

4


ULTIMATE OBJECTIVE

Create business information system specifications that are valid, reliable, repeatable.

Create specifications that incorporate a Version-5 prototype-proven set of “requirements.”

Build specification materials that are non-redundant, integrated, and cross-referenced within project, program, function, and enterprise.

Create implementable specifications that are predictable as to time, scope, cost, and content.

Achieve business information system success on first implementation.

2/9/2011

5


REAL PROBLEM NEEDING REAL SOLUTION

2/9/2011

6

Error Statistics Summaries from Standish Chaos Studies (1999 through 2009)

Result Classification

Percent

Utility (Gas & Electric)

365 Client/Server

2009 Chaos Report

Succeed 24 16 32

Challenged 43 53 24

Failed 33 31 44

Legend Category DescriptionSucceed On-time, within budget, features as promised

Challenged Late, greater than budgeted, less features than promised

Failed Cancelled outright


TOP REASONS FOR SUCCESS & FAILURE

Success User Involvement Executive Management Support Clear Statement of Requirements

Failure Incomplete Requirements Lack of User Involvement Lack of Resources

2/9/2011

7


A FRAMEWORK FOR THE KNOWLEDGE WORKER

2/9/2011

8


KNOWLEDGE WORKER INTERRELATIONSHIPS

2/9/2011

9


CONTINUOUS VS PROEJCT FLOW

2/9/2011

10


ENGINEERED INTO AN INTEGRATED, NON-REDUNDANT, ENTERPRISE-WIDE METADATA DATABASE OR…..?

2/9/2011

11


GAO IDENTIFIED BUSINESS INFORMATION SYSTEM DEVELOPMENT ERRORS

Deliver-ables Mission

Machine Interface “Man”

Database Object

Bus. Info Systems

Business Event

Business Function

Organ-ization

Scope 5 2 3 1 3 4

Business 5 3 2 1 6 6

System 3 2 2 1 12 8

Technology 1 0 0 0 8 6

Deployment 0 0 0 0 5 5

Operations 0 0 0 0 3 3

Pct Total 14 7 7 3 37 32

2/9/2011

12

Distribution as PCTs of about 150 IT Development errors identified by GAO across 13 multi-hundred million IT System failures


GAO ERRORS DISTRIBUTION ACROSS KNOWLEDGE WORKER FRAMEWORK

Building and Employing Enterprise Architecture Models: Scope and Business Rows, all columns. About 41% of all GAO IT errors.

Creating and Evolving Information Systems Plans: System Row, Mission through Business Event columns. About 8% of GAO IT errors.

Architecture and Engineering of Data Models: Technology Row, database object column. Less than 1% of Errors

Performing Reverse Engineering of Legacy Systems and Databases: Operations, Deployment, Technology and System Rows. Database Objects Column. Less than 2% of Errors

Forward Engineering Manufacture of New Systems and Databases:Systems, Technology Deployment and Operations Rows. Database Objects and Business Information Systems Column. About 4% of Errors

Deployment and Employment Errors:Systems through Operations Rows. Operations and Functions Columns. About 50% of Errors.

2/9/2011

13


2.0 TRADITIONAL METHODOLOGY

2/9/2011

14


3.0 METHODOLOGY PROBLEMS

Intrinsically Nothing. Operationally, everything. Long (6-9 month) cycles across interviews, document development,

software development, and functional SME demonstration & review. Significant monies spent each cycle (approx $4 million per cycle (see note)). Push-back by SMEs, et al causes:

Significant Software re-do that costs large $$$ and real delay Significant DB re-do that costs even more $$$ and even more delay

Money and time runs out well before ultimate requirements are discovered and turned into operational database and software.

All deliverables are stove-pipe documents with little to no configuration management, integration, interoperability, and traceability.

Note: Requirements & Design: 4 persons * $20K * 2 months * 6 major functions. = $960KDetailed Design, Code, Unit Test, and Demo: 6 persons * $20K * 4 months * 6 major functions = $2,880K

2/9/2011

15


TRADITIONAL DEVELOPMENT PHASES AND TIME-LINE

16

2/9/2011


4.0 REPLACEMENT METHODOLOGY

Integrate functional SMEs into small teams Iterate specification via prototypes until “uncle.” Incorporate business information system specification metadata into a

database that is: Non-redundant Integrated Interoperable Fully-traceable

Finalize business information system specification before implementation. Architecture & Design database and supporting metadata management system. Complete set of executable prototypes that demonstrate requirements. Everything in non-redundant, integrated, interoperable and traceable forms.

2/9/2011

17


5.0 SPECIFICATION PROBLEM RESOLUTIONS

2/9/2011

18

Existing Problems Resolution

Problem Solution (assumes 6 major functional areas)

Long 6-9 month cycles Days to 3-week cycles from interviews to prototype demonstrations

Very significant monies (about $4 million per cycle) before first real demonstration. $20 million for 5 cycles.

2 experts plus 2 SMEs per team ($30K per cycle) * 5 cycles & 6 functional areas = $900K for all functional areas.

User Pushback by Subject Matter Experts and Functional Users

Functional SMEs are part of teams. With 5 cycles, all requirements are teased-out through prototype generation.

Stove Pipe Architecture & Design Documents

All deliverables and prototypes are contained within a single, integrated, non-redundant and traceable specification metadata database, and supporting system.


REPLACEMENT SPECIFICATION PROCESS FLOW

2/9/2011

19


SCOPE OF METADATA DATABASE

2/9/2011

20


PROTOTYPE GENERATION

21

2/9/2011


6.0 REPLACEMENT METHODOLOGY MILESTONES

2/9/2011

22

Milestone Wk ActivitiesStart & Team Formation 2 Contract, Get team members, build schedule

Load Metabase 6 Mine Existing documents & Load Metadata Database

Cycle 1 10 Generate 1st prototype round, modify MD DB, and present to SMEs.

Cycle 2 13 Revise MD DB, generate 2nd prototype round, and present to SMEs.

Cycle 3 16 Revise MD DB, generate 3nd prototype round, and present to SMEs.

Cycle 4 19 Revise MD DB, generate 4th prototype round, and present to SMEs.

Cycle 5 22 Revise MD DB, generate 5th prototype round, and present to SMEs.

Consolidate MD DB 26 Final Revision of all Metadata to ensure highest quality

Build Final Specification 30 Produce documents from Metadata DB into Specification Documents

Support Implementation 40 Be available to provide answers and demonstrations to all vendors.


BUSINESS INFORMATION SYSTEM SPECIFICATION DEVELOPMENT

23

2/9/2011


7.0 WHERE USED / PAST PERFORMANCE

U.S. Army TACOM. From $400K to $40K per system State of California. Prototypes for Major Revision Hershey Chocolate. Enterprise Architecture then incremental

functional implementation State of Ohio. State-wide Courts System prototype then

production implementation Mars Foods. World Wide Inventory Management INCITS. $300K for a $2.4 million Membership Management

System Army CIO-G6’s AR 25-1 and DA PAM 25-1-1

2/9/2011

24


8.0 APPROACH COMPARISON SUMMARY

2/9/2011

25

Contractor awarded “whole” work at month 1. Specification mainly by contractor Heavy front end cost weighting No real specification-proven prototypes SME push-backs often too late and very costly SMEs mainly involved as reviewers

BIS Specification done “in house”. “V1” contract let only after BIS Specification

(“D’s) are proven via prototypes SME push-backs virtually eliminated Implementation Contract starts with proven

Business Information System Specification SMEs integral partners of Business Information

System Specification and QA/QC for Implementation.

Versus


9.0 SUMMARY AND BENEFITS

Strategy to create high-quality, prototype-proven business information system specification.

Quick Cycles of at most 3-weeks to arrive at design version 5 before actual implementation starts. (Changed from one 9 – 12 month cycle to five 3-week design-iteration cycles). Virtually eliminates hidden requirements.

Complete integration of all Architecture & Design documents into a metadata management database and system.

Delivery of V5 proven business information system specification to implementation contractor. Little to no room for misinterpretation. Supported by Metadata DB, copious cross-references, and prototypes.

Virtually eliminates implementation time and money on business information system specification, design, and revisions. Total focus on first-time correct implementation.

Easy to QA & QC because implementation starts with V5 of proven business information system specification.

2/9/2011

26


10.0 DEMONSTRATION Power Up Metabase System Employ Mission-Organization-Function-Position Assignment Module Employ Use Cases Module Develop and/or Revise Data Models

Employ Data Element Model Employ Specified Data Model (Concepts) Employ Implemented Data Model Employ Data Element Model (2nd time)

Employ Database Objects Module Employ Business Information Systems Module Employ Use Case Module (2nd time) Employ Operational Data Model (Physical) Employ Clarion at the Business Information System Generator

2/9/2011

27


FRAMEWORK FOR DEMONSTRATION

2/9/2011

28


IN CLOSING, THIS APPROACH… Increases Productivity. Data-driven foundation for all integrated

and non-redundant business information system specifications prior to implementation. Maximizes re-use of existing materials. 5 prototype-proof cycles.

Increases Quality. Maximizes business information system specifications accuracy across entire business domain --proven through prototypes.

Decreases Risk. Maximizes traceability, integration and non-redundancy across all business information system specifications artifacts.

Decreases Cost. Prototype-proven support: Identify once, Define/Specify once, and Implement once.

2/9/2011

29

Business Information System �Specification DevelopmentData Management PracticesTopics1.0 Introduction and RationaleUltimate objectiveReal Problem Needing Real SolutionTop Reasons for Success & FailureA Framework for the Knowledge WorkerKnowledge Worker INterrelationshipsContinuous vs Proejct FlowEngineered into an integrated, non-redundant, enterprise-wide metadata database or…..?Gao Identified Business Information System Development ErrorsGAO Errors distribution Across Knowledge Worker Framework2.0 Traditional Methodology3.0 Methodology ProblemsTraditional Development Phases and Time-line4.0 Replacement Methodology5.0 Specification Problem ResolutionsReplacement Specification Process FlowScope of metadata DatabasePrototype Generation6.0 Replacement Methodology MilestonesBusiness Information System Specification Development7.0 Where Used / Past Performance8.0 Approach Comparison Summary9.0 Summary and Benefits10.0 DemonstrationFramework for DemonstrationIn closing, This approach…