Architecture applicative

1. What is your current application development style?
2. What types of languages does your organization use?

1. How common is re-use in your organization?
2. What types of re-use do you engage in and how is re-usability measured?

1. How are your organization’s applications/systems integrated?
2. What types of integration technologies has your organization employed?
3. How widely is XML used in your organization? How sophisticated is its use?
4. Are SOA-enabling technologies, such as ESB, shared data environment, or registry, being used?

1. How is business logic represented within your organization’s applications?
2. How reliable are your organization’s business-critical applications?

Silo
(Level 1)

Modules

Application architectures and topologies are monolithic and lack integration between other systems across the enterprise.

The use of web services or other SOA constructs are not present.

Integrated
(Level 2)

Objects

Application architectures and topologies are monolithic with minimal separation of concerns between architectural layers or application tiers.

Applications use minimal integration between other systems. Integration is usually implemented using point-to-point techniques.

Componentized
(Level 3)

Components

SOA development practices are applied inconsistently across the organization.

Most application architecture topologies have a separation of concerns both physically and logically in presentation, business logic, and data tiers.

The use of SOA-enabling technologies – such as an ESB – is inconsistent across the enterprise.

Services
(Level 4)

Services

Service components of application architectures employ SOA patterns such as separation of concerns between logical and physical layers of the presentation and business logic.

Service integration is achieved using an ESB in some but not all business units.

Composite Services
(Level 5)

Applications Composed of Composite Services

Application architectures are designed with a separation of concerns at the logical and physical layers.

ESB integration patterns are used to support application and process integration to achieve sharing of services.

Virtualized Services
(Level 6)

Virtualized Services

Application architecture is decoupled from infrastructure components.

Extensive use of ESB architecture patterns to support Business Process Management (BPM).

Dynamically Re-Configurable Services
(Level 7)

Dynamic Application Assembly, Context-aware Invocation

Application architecture supports dynamically reconfigurable business and infrastructure services and SOA solution for internal or external partner consumption.