Enterprise Services Enterprise Services for Defense Transformation - - PowerPoint PPT Presentation

▶
enterprise services enterprise services
SMART_READER_LITE
LIVE PREVIEW

Enterprise Services Enterprise Services for Defense Transformation - - PowerPoint PPT Presentation

Nov 02, 2023 15 likes •406 views

Enterprise Services Enterprise Services for Defense Transformation for Defense Transformation Prof. Paul A. Strassmann George Mason University, February 19, 2007 1 Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION Case

slide-1
SLIDE 1

1

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Enterprise Services Enterprise Services for Defense Transformation for Defense Transformation

  • Prof. Paul A. Strassmann

George Mason University, February 19, 2007

slide-2
SLIDE 2

2

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Case Study

Hewlett-Packard Cost Reduction

slide-3
SLIDE 3

3

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Example of Application Simplification

7 7 8 6 6 3 2 2 2 2 2 2 6 6 6 6 6 6 4 3 3 2 2 2 9 9 8 5 5 5 5 5 3 3 3 3 7 7 7 7 7 7 7 4 4 4 4 1 11 11 10 10 10 10 4 3 2 2 2 2 11 9 8 8 6 6 6 5 5 5 5 5 10 10 8 8 8 7 7 7 6 6 6 6 21 21 15 14 14 13 13 4 4 4 4 4 17 17 16 16 16 16 13 13 2 2 2 2 16 16 15 13 13 12 12 12 7 7 7 4 30 30 27 27 27 27 5 5 2 2 2 2 24 24 24 24 23 22 15 13 10 10 10 10 50 100 150 200 C u r r e n t F Y 6

  • Q

2 F Y 6

  • Q

3 F Y 6

  • Q

4 F Y 7

  • Q

1 F Y 7

  • Q

2 F Y 7

  • Q

3 F Y 7

  • Q

4 F Y 8

  • Q

1 F Y 8

  • Q

2 F Y 8

  • Q

3 F Y 8

  • Q

4 Training & Cert Dashbd & Reporting Prog adm/compens Data Collection Portal Newsgram Marketing Mgt Datawarehouse C&R - deal P & S Catalog Quote/Config Mkt Dev Fund Locator Acct Mgt & P. Profiling Leads Mgt Data cleansing/Std stock protect contract A2A Integ Pricing Comm Content Publi. Fraud Mgt Rebate Comm Control - EUV C&R - promo Portal Metric Domain (All) Primary Y Region (All) Owner GCP Count of Asset Name Period Capability

slide-4
SLIDE 4

4

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Transformation Indicators - HP Case

slide-5
SLIDE 5

5

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Enterprise Data Warehouse

Legacy applications = chaos Enterprise data warehouse = order

Continuity Consolidation Control Collaboration

Single version of the truth

Data Warehouse Production Control MRP Inventory Control Parts Management Logistics Shipping Raw Goods Order Control Purchasing Marketing Finance Sales Accounting Management Reporting Engineering Actuarial Human Resources

slide-6
SLIDE 6

6

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

% Innovation vs. Sustaining % Projects On Quality Target Value-Added/IT Developer Annualized Benefit ($B) % On Time Delivery

Target Performance Metric

IT Portfolio Scorecard

$2.5B $2B $1B $3B

2004 2005 2006 2007

slide-7
SLIDE 7

7

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Opportunity to Standardize, Consolidate and Integrate

67 52 79 56 83 95

33 48 21 44 5 17

0% 20% 40% 60% 80% 100%

Low Commonality High Commonality

Marketing Ops Sales Ops Order Mgmt Supply Chain Finance HR

slide-8
SLIDE 8

8

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

A Transformation Calculator (See BASELINE January 2007)

slide-9
SLIDE 9

9

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Calculating the Transformation % - (Baseline January 2007)

slide-10
SLIDE 10

10

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Case Study

The Department of Defense

slide-11
SLIDE 11

11

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Components of Transformation in DoD Data Strategy Enterprise Services Net-Centric Operations Information Assurance

slide-12
SLIDE 12

12

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Organization for Transformation in DoD Warfighter Mission Area Intelligence Mission Area Business Mission Area

slide-13
SLIDE 13

13

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Distribution of DoD I.T. Spending

slide-14
SLIDE 14

14

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Most DoD I.T. Spending in Infrastructure

slide-15
SLIDE 15

15

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Scope of Business Management Systems

slide-16
SLIDE 16

16

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Business Mission in Military Services

slide-17
SLIDE 17

17

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Current Organization of I.T. Spending in Services

Acquisition - 15 Finance - 16 HR - 49 Installation - 13 Logistics - 152 Budgeting - 172 Infrastructure - 601 Projects

Air Force

Acquisition - 4 Finance - 3 HR - 49 Installation - 6 Logistics - 47 Budgeting - 2 Infrastructure - 181 Projects

Army

Acquisition - 45 Finance - 104 HR - 158 Installation - 21 Logistics - 232 Budgeting - 87 Infrastructure - 401 Projects

Navy

slide-18
SLIDE 18

18

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Proposed Ultimate Organization of I.T. Spending in Services

Shared Infrastructure - 12 Projects

Air Force

Acquisition - 4 Finance - 3 HR - 49 Installation - 6 Logistics - 47 Budgeting - 2

Army Navy

Portals

slide-19
SLIDE 19

19

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Organization for Transformation of DoD - As Defined by NII

slide-20
SLIDE 20

20

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Potential Cost Reduction Through Consolidation of DoD Systems

NOTE: Cost/Function Point = $1,200; Function Points/Application = 20,000; Function Points/Infrastructure = 200,000

slide-21
SLIDE 21

21

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

What is Needed: A Business Transformation Engine

  • Interoperability

Interoperability to share data; – Reduce mediation costs

  • I.T.

I.T. cost reduction

  • st reduction;

– Consolidate applications, use shared components

  • Operating cost reduction

Operating cost reduction; – Automate reliability, security and information assurance

  • Rapid delivery

Rapid delivery of new capabilities; – Reduce integration costs for innovation

slide-22
SLIDE 22

22

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Functions of the Business Transformation Engine Legacy Applications Transformed Applications DoD Business Process Models DoD MetaData Directory Interoperability Filter

Transformation Engine

Interoperability Controller Interoperability Rules Transformed Services Shared Services Services Directory Services Portal Client Interface

Transformation Engine

slide-23
SLIDE 23

23

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

The DoD Policy Context: Data Sharing for Net-Centric Operations

slide-24
SLIDE 24

24

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Application Transformation Functions

  • DoD Business Process Models provide the means for resolving procedural

and process issues across different Communities of Interest.

  • Shared Services include Application Development Services and Application

Component Services.

  • Transformed Services are applications that can be certified as fully compliant

with DoD policies.

  • Services Directory identifies the contents and access processes for delivery
  • f “composite applications” that can utilize parts of available services.
  • Services Portal

Services Portal provides a standard interface that can be adapted to meeting customers’ requirements.

slide-25
SLIDE 25

25

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Case Study

Managing Software

slide-26
SLIDE 26

26

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Current State of Software According to Capers Jones

  • Initial requirements are seldom more than 50% complete.
  • Finding and fi

fixing bugs is the most expensive software activity.

  • Creating documents is the second most expensive software

activity.

  • Most forms of testing touch less than 50% of the code being

tested.

  • There are more defects in test cases than in the software itself.
  • About 5% of modules in applications will contain 50% of all

defects.

  • About 7% of all defect repairs will accidentally inject new defects.
  • About 5% of software outsource contracts end up in litigation.
  • About 35% of projects > 10,000 function points will be cancelled.
  • About 50% of projects > 10,000 function points will be one year

late.

slide-27
SLIDE 27

27

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Proliferation of Software Choices

  • More than 600 programming languages;
  • More than 40 different formal methods;
  • More than 38 different kinds of size metrics;
  • More than 26 named development methods;
  • More than 25 international standards organizations.
slide-28
SLIDE 28

28

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Proliferation of Software Development Methodologies (Partial)

  • Capability maturity model (CMM);
  • Capability maturity model integration (CMMI);
  • CASE tools;
  • CRYSTAL development approach;
  • Dynamic system development method (DSDM);
  • Extreme programming (XP);
  • ISO 9000-9004 standards;
  • Personal software process (PSP);
  • Rapid application development (RAD);
  • Structured process (TSP);
  • Unified modeling language (UML).
slide-29
SLIDE 29

29

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Proliferation of Metrics to Measure Size of Software

  • IFPUG function points;
  • Backfired function points;
  • Cosmic function points;
  • Engineering function points;
  • Feature points;
  • Mark II function points;
  • NESMA function points;
  • Object points;
  • Use-case points;
  • Web-object points;
  • Lines of code;
  • Number of source code logical statements.
slide-30
SLIDE 30

30

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Testing Requirements for a Large Systems Project

Requirements inspections Design inspections Document inspections Code inspections Test plan and test case inspection Defect repair inspection Software quality assurance reviews Unit testing Component testing New function testing Regression testing Performance testing System testing Acceptance testing

slide-31
SLIDE 31

31

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Paperwork Exceeds Programming Work

Monthly status reports to executive management; Weekly progress reports to clients; Daily communication between clients and the prime contractor; Daily communication between the prime contractor and sub contractors; Daily communication between developers and development management; Full email support among all participants; Full voice support among all participants; Video conference communication among remote locations; Automated distribution of documents and source code among developers; Automated distribution of change requests to developers; Automated distribution of defect reports to developers; Emergency or “red flag” communication for problems.

slide-32
SLIDE 32

32

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Staff Requirements for a Large Software Project (Partial List)

Configuration Control Specialists Cost Estimating Specialists Customer Liaison Specialists Data Base Administration Specialists Data quality Specialists Decision Support Specialists Domain Knowledge Specialists Human Factors Specialists Integration Specialists Maintenance specialists for post-release defect repairs Outsource/Package Evaluation Specialists Performance Specialists Project Cost Estimating Specialists Quality Assurance Specialists Technical Writing Specialists Testing Specialists

slide-33
SLIDE 33

33

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

What Happens in DoD Development Centers

  • Each unit selects a different software improvement

model.

  • The result is political battle between the units.
  • Each striving to have its choice adopted as the

standard.

slide-34
SLIDE 34

34

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Findings from Benchmark Studies

  • For several years after adoption of a new software

development approach productivity and quality levels do tend to improve.

  • When DoD is revisited years later, the new method has

been abandoned and productivity and quality results have declined back to the levels before the improvement program started.

  • New management wants to start a new software process

improvement program. Data on the earlier improvement programs has vanished.

slide-35
SLIDE 35

35

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Project Success/Failure Probabilities

slide-36
SLIDE 36

36

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

What is a Function Point?

  • A function point is a unit of measurement to express the

amount of business functionality an information system provides to a user.

  • Function points are an ISO recognized software metric to

size an information system based on the functionality that is perceived by the user of the information system.

  • The size is determined by identifying the components of the

system as seen by the end-user: the inputs, outputs, inquiries, interfaces to other systems, and logical internal files.

  • There can be 70-300 Lines of Code per Function Point.
slide-37
SLIDE 37

37

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

A Software Cost Reduction Calculator

slide-38
SLIDE 38

38

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Reduction of Software Costs through Consolidation

slide-39
SLIDE 39

39

  • Prof. Strassmann, GMU, February 2007 Lecture, REPRODUCED BY PERMISSION

Summary

  • There are thousands of ways how systems projects can fail -

there are only a few ways how they can succeed.

  • Transformation calls for consolidation of applications and data

center operations.