• No results found

Enterprise Services for Defense Transformation

N/A
N/A
Protected

Academic year: 2021

Share "Enterprise Services for Defense Transformation"

Copied!
39
0
0

Loading.... (view fulltext now)

Full text

(1)

Enterprise Services

Enterprise Services

for Defense Transformation

for Defense Transformation

(2)

2

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

Case Study

(3)

Example of Application Simplification

7

7

8

6

6

3

2

6

6

6

6

6

6

4

9

9

8

5

5

5

5

7

7

7

7

7

7

7

4

4

4

4

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

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.

Domain (All) Primary Y Region (All) Owner GCP

Count of Asset Name

(4)

4

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

(5)

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

Marketing

Finance

Sales

Accounting

Management

Reporting

Engineering

Actuarial

Human

(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

(7)

Opportunity to Standardize, Consolidate and Integrate

67

52

79

56

83

95

33

48

21

44

17

5

0%

20%

40%

60%

80%

100%

Low Commonality

High Commonality

(8)

8

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

(9)
(10)

10

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

Case Study

(11)

Components of Transformation in DoD

Data Strategy

Enterprise

Services

Net-Centric

Operations

Information

Assurance

(12)

12

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

Organization for Transformation in DoD

Warfighter

Mission Area

Intelligence

Mission Area

Business

(13)
(14)

14

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

(15)
(16)

16

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

(17)

Current Organization of I.T. Spending in Services

A

cq

ui

si

tio

n

-

15

Fi

na

nc

e

-

16

H

R

4

9

In

st

al

la

tio

n

-

13

Lo

gi

st

ic

s

-

15

2

Bu

dg

et

in

g

-

17

2

Infrastructure

-601 Projects

Air Force

A

cq

ui

si

tio

n

-

4

Fi

na

nc

e

-

3

H

R

4

9

In

st

al

la

tio

n

-

6

Lo

gi

st

ic

s

-

47

Bu

dg

et

in

g

-

2

Infrastructure

-181 Projects

Army

A

cq

ui

si

tio

n

-

45

Fi

na

nc

e

-

10

4

H

R

1

58

In

st

al

la

tio

n

-

21

Lo

gi

st

ic

s

-

23

2

Bu

dg

et

in

g

-

87

Infrastructure

-401 Projects

Navy

(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

A

cq

ui

si

tio

n

-

4

Fi

na

nc

e

-

3

H

R

4

9

In

st

al

la

tio

n

-

6

Lo

gi

st

ic

s

-

47

Bu

dg

et

in

g

-

2

Army

Navy

Portals

(19)
(20)

20

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

Potential Cost Reduction Through Consolidation of DoD Systems

(21)

What is Needed: A Business Transformation Engine

• Interoperability to share data;

– Reduce mediation costs

• I.T. cost reduction;

– Consolidate applications, use shared components

• Operating cost reduction;

– Automate reliability, security and information assurance

• Rapid delivery of new capabilities;

(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

(23)
(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

of “composite applications” that can utilize parts of available services.

Services Portal provides a standard interface that can be adapted to

Services Portal

(25)

Case Study

(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 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.

(27)

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;

(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);

(29)

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;

(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

(31)

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.

(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

(33)

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.

(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.

(35)
(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.

(37)
(38)

38

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

(39)

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.

References

Related documents

In this paper, we propose a novel method for tracing exactly the entire kernel path with respect to the ker- nel hyperparameter of the kLASSO regression model, even though the path

Li et al used a dual approach to stage 307 HBV patients, combining APRI or FIB-4 with LS by Fibroscan, resulting in a significant reduction in the need for liver biopsy

Some reference standards that were used in this study are representative of three main group of phenolics compound such hydroxybenzoic acids (gallic

Regarding the fact that companions without health insurance for their children were satisfied with the quality of care of the Pediatric Emergency Room, their satisfaction may

Multilevel mixed-effects linear regression models will be used to assess the impact of group (intervention vs. con- trol) on achievement scores in reading and mathematics, mean per

1) To study and improve the contribution of light-weight vehicle roof panels made of aluminum and composite materials to the vehicle chassis static and dynamic stiffness

apskaitos  dokumentacijoje  (kultūros  vertybių  dosjė). 

Real-time RT-PCR quantification of Gill-Associated virus (GAV) loads in pleopods of Penaeus monodon from the GAV load comparison replicate tanks fed A) Control diet or B)