Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Design Principles by Mind Map: Design Principles
3.7 stars - 3 reviews range from 0 to 5

Design Principles

Standardized Service Contract

Goals

Natural operability

Less data transformation

Capabilities are better understood

Design Characteristics

Service contract provided

Standardized through design standards

Implementation requirements

Design standards and conventions

Formal processes for service modeling

Contract first approach

Service Loose Coupling

Goals

An environment where Services and Consumers can evolve with minimal impact

Coupling Types

Logic-to-Contract, "Contract First"

Contract-to-Logic

Contract-to-Technology

Contract-to-Implementation

Contract-to-Functional, Parent Process Coupling, Service-to-Consumer Coupling, Functional Coupling and Task Services

Consumer-to-Implementation

Consumer-to-Contract, Coupling Levels, Non-Centralized, Centralized

Service Abstraction

Goals

Keep the contract detail concise and balanced

Types

Technology

Functional Capabilities

Programmatic Logic, Internal details, Design, Source code

Quality of Service, SLA, Concurrent threshold, Availability limitations, Business Rules

Measuring

Contract Content Abstraction Levels, Detailed, Concise, Optimized

Access Control Levels, Open Access, Controlled Access, No Access

Service Reusability

Goals

High ROI

Increase business agility

Enable agnostic service models

Service Autonomy

Goals

Increase runtime reliability, performance, predictability

Increase control

Types

Runtime Autonomy, Execution performance, Reliability, Predictability, Security control

Design-Time Autonomy, Scalability, Enhance hosting environment, Change technology

Levels

Service Contract Autonomy

Shared Autonomy

Service Logic Autonomy

Pure Autonomy

Service Statelessness

Goals

Increase scalability

Improve service reuse

Types

Active, Stateless, Stateful, Session data, Context data, Business data

Passive

Levels

Non-deferred State Management (low-to-no statelessness)

Partially Deferred Memory (reduced statefulness)

Partial Architectural State Management Deferral (moderate statelessness)

Full Architectural State Management Deferral (high statelessness)

Service Discoverability

Goals

Highly discoverable services

Purpose and capabilities clearly expressed

Types

Design-Time discovery

Runtime discovery, UDDI

Discoverability Meta Information, Functional, Quality of Service

Service Composability

Goals

Goals of Service Reusability. Composition is a form of service reuse.

Terms

Composition (Instance)

Composition Member, Composition Member Capability

Composition Controller, Sub-Controllers, Composition Controller Capability, Designated Controllers