capability maturity model for geoscience australia

9
Time R e g i s t r y W M S s e r v e r W F S s e r v e r W e b C l i e n t Implementi ng Infrastruc ture Capability Maturity Model Effort Productivity Ability to deliver new functionality using new methods Current Effort Effort of continuing software development if nothing changes Effort to build applicatio ns according to maturity

Upload: peter-scheffer

Post on 07-Aug-2015

115 views

Category:

Business


4 download

TRANSCRIPT

Page 1: Capability Maturity Model for Geoscience Australia

Time

Reg

istry

WM

S server

WF

S server

Web

Clien

t

Implementing Infrastructure

Capability Maturity ModelEffort Productivity

Ability to deliver new functionality using new methods

Current EffortEffort of continuing software development if nothing changes

Effort to build applications according to maturity

Page 2: Capability Maturity Model for Geoscience Australia

Capability Maturity Model

Time

Reg

istry

WM

S server

WF

S server

Web

Clien

t

Present Data in WFS,

WMSformat

Configuring Data

Capabilities:• Discoverability• Interoperability• Reusability

Effort ProductivityAbility to deliver new functionality using new methods

Current EffortEffort of continuing software development if nothing changes

DevelopCommunity

Schemas

Effort to build applications according to maturity

Page 3: Capability Maturity Model for Geoscience Australia

Capability Maturity Model

Time

Reg

istry

WM

S server

WF

S server

Web

Clien

t

Create & Publish

Web Services

Create Web Applications using Web Services & Registry

Reg

istry

WM

S server

WF

S server

Web

Clien

t

Capabilities:• Discoverability• Interoperability• Reusability

Capabilities:• Increased Discoverability• Broader Interoperability• Greater Reusability• Greater Data Distribution

Applying Web Services

Effort ProductivityAbility to deliver new functionality using new methods

Current EffortEffort of continuing software development if nothing changes

Present Data in WFS,

WMSformat

DevelopCommunity

Schemas

Effort to build applications according to maturity

Page 4: Capability Maturity Model for Geoscience Australia

Capability Maturity Model

Time

Reg

istry

WM

S server

WF

S server

Web

Clien

t

Create & Publish

Web Services

Create Web Applicationsusing Web Services & Registry

Business Process

Modelling

Fortress Modelling & Automation

Reg

istry

WM

S server

WF

S server

Web

Clien

t

Capabilities:• Discoverability• Interoperability• Reusability Business

Modelling

Capabilities:• Advanced Accessibility• Advanced Reusability• Advanced Applications

Effort ProductivityAbility to deliver new functionality using new methods

Current EffortEffort of continuing software development if nothing changes

Present Data in WFS,

WMSformat

DevelopCommunity

Schemas

Capabilities:• Increased Discoverability• Broader Interoperability• Greater Reusability• Greater Data Distribution

Effort to build applications according to maturity

Page 5: Capability Maturity Model for Geoscience Australia

Capability Maturity Model

Time

Reg

istry

WM

S server

WF

S server

Web

Clien

t

Create & Publish

Web Services

Create Web Applications using Web Services & Registry

Business Process

Modelling

Effort Productivity

Reg

istry

WM

S server

WF

S server

Web

Clien

t

Capabilities:• Discoverability• Interoperability• Reusability

Effort to build applications according to maturity

Ability to deliver new functionality using new methods

Capabilities:• Advanced Accessibility• Advanced Reusability• Advanced Applications

Capabilities:• Automated Software Development• High Level Productivity• Reduced need for “Straw men” – applications correct first time

Current EffortEffort of continuing software development if nothing changes

Fortress Modelling & Automation

Present Data in WFS,

WMSformat

DevelopCommunity

Schemas

Capabilities:• Increased Discoverability• Broader Interoperability• Greater Reusability• Greater Data Distribution

Page 6: Capability Maturity Model for Geoscience Australia

Satisfactory Requirements for each stage in the CMM

1. Software components installed and tested2. Sample data being served through server components3. Software configured for internal operation4. All software components interoperating with each other

Page 7: Capability Maturity Model for Geoscience Australia

Satisfactory Requirements for each stage in the CMM

1. Software components installed and tested2. Sample data being served through server components3. Software configured for internal operation4. All software components interoperating with each other

1. Selection of Community Schemas agreed and being implemented

2. Data Migration plan agreed and being implemented3. Data Distribution process adopted

Page 8: Capability Maturity Model for Geoscience Australia

Satisfactory Requirements for each stage in the CMM

1. Software components installed and tested2. Sample data being served through server components3. Software configured for internal operation4. All software components interoperating with each other

1. Selection of Community Schemas agreed and being implemented

2. Data Migration plan agreed and being implemented3. Data Distribution process adopted

1. Web Application process ratified; full build, test and deployment procedures being implemented

2. Web Services being created and reused3. Developers using Registry for publish, find, bind

Page 9: Capability Maturity Model for Geoscience Australia

Satisfactory Requirements for each stage in the CMM

1. Software components installed and tested2. Sample data being served through server components3. Software configured for internal operation4. All software components interoperating with each other

1. Selection of Community Schemas agreed and being implemented

2. Data Migration plan agreed and being implemented3. Data Distribution process adopted

1. Web Application process ratified; full build, test and deployment procedures being implemented

2. Web Services being created and reused3. Developers using Registry for publish, find, bind

1. Direct mapping of fortress modelling onto source code2. Full re-use of Web Services for building Web Applications3. BPEL and UML-to-GML tools being used (see Doug Nebert1)4. Source code being auto-generated

1. “Current standards, specifications and practices of relevance to SDI development”Doug Nebert, FGDC Secretariat. June 2005.