Thursday, June 11, 2009

SOA Principles

Design Fundamentals
- Design Characteristic (Te-Zhen)
- Design Principle (Yuan-Zhe)
- Design Paradigm (Si-Lu)
- Design Pattern (Mo-Shi)
- Design Pattern Language (Mo-Shi-Yu-Yan)
- Design Standard (Bia0-Zhun)
- Best Practice (Jin-Yan-Zhong-Jie)

Fundamental Design Framework
Design Principles Centered


Design Patterns Centered

Service-Oriented Computing
- Service-Oriented Architecture
- Service-Oriented Design Paradigm
- Service-Oriented Solution Logic
- Service Compositions
- Services
- Service Inventory

Web Service Architecture
- Service Contract
- Core Service Logic (Business Logic)
- Message Processing Logic


Service -Oriented as a Design Paradigm
- Standardized Service Contract
- Service Loose Coupling
- Service Abstraction
- Service Reusability
- Service Autonomy
- Service Statelessness
- Service Discoverability
- Service Composability

Design Principles




Principles and Design Granularity
- Service Granularity
- Capability Granularity
- Data Granularity
- Constraint Granularity

Impacts of Standardized Service Contract
- Service Loose Cupling (affects the quality of attainable)
- Service Abstractio (affects the extent of attainable)
- Service Reusability (establishes conventions that affect the potential of attainable)
- Service Discoverability (Introduces contract design conventions that can enhance or constrain)
- Service Composability (may introduce contract content requirements that support)

Service Contract Coupling Types
- Logic-to-Contract Coupling (contract drives logic)
- Contract-to-Logic Coupling (logic drives contract)
- Contract-to-Technology Coupling underlying technology)
- Contract-to-Implementation Coupling (implementation environment)
- Contract-to-Functional Coupling (external logic)

Service Consumer Coupling Types
- Consumer-to-Implementation Coupling
- Consumer-to-Contract Coupling

Coupling and Service Models
- Entity Services
- Utility Services
- Task Services
- Orchestrated Task Services

Impacts of Service Loose Coupling
- Standardized Service Contract (can influence the design standards for)
- Service Abstraction (emphasizes some forms of)
- Service Reusability (establishes a complementary form of centralization that maximizes opportunities for)
- Service Autonomy (Increases levels of attainable)
- Service Discoverability (regulates published meta information used for)
- Service Composability (helps prevent dependencies that inhibit)

Type of Meta Abstraction
- Technology Information Abstraction
- Functional Abstraction
- Programmatic Logic Abstraction
- Quality of Service Abstraction

Contract Content Abstraction Levels
- Detailed Contract
- Concise Contract
- Optimized Contract
- Mixed Detailed Contract

Access Control Levels
- Open Access
- Controlled Access
- No Access

Impacts of Service Abstraction
- Standardized Servie Contract (can influence the design standards used for)
- Service Reusability (regulates the quantity and nature of meta information published in support of)
- Service Composability (regulates the quantity and nature of meta information published in support of)
- Service Discoverability (regulates the quantity and nature of meta information published in support of)
- Service Lossse Coupling (can influence the extent of attainable)

Measures of Planned Reuse
- Tactical Reusability
- Targeted Reusability
- Complete Reusaqbility

Impacts of Service Reusability
- Standardized Service Contract (encourages the design of highly generic)
- Service Abstraction (challenges)
- Service Loose Coupling (emphasizes)
- Service Discoverability (emphasizes)
- Service Autonomy (emphasizes)
- Service Statelessness (emphasizes)
- Service Composability (forms the basis of)

Risk Associated with Service Reusability and Commercial Design
- Cultural Concerns
- Governance Concerns
-Reliability Concerns
- Security Concerns
- Commercial Design Requirement Concerns
- Agile Delivery Concerns

Type of Service Autonomy
- Runtime Autonomy (execution)
- Design-Time Autonomy (governance)

Measuring Service Autonomy
- Service Contract Autonomy
- Shared Autonomy
- Service Lgic Autonomy
- Pure Autonomy

Impacts of Service Autonomy
- Standardized Service Contract (encourages the normalization of)
- Service Loose Coupling (directly supports)
- Service Abstraction (can influence the level of)
- Service Reusability (increases the potential of)
- Service Statelessness (increases the potential of)
- Service Composability (increases the potential of)

Types of State
- Active and Passive
- Stateless and Stateful
- Session and Context Data

Measuring service Statelessness
- Non-Deferred State Management (low-to-no istatelessness)
- Partially Deferred Memory (reduced statefulness)
- Partial Architectural State Management Deferral (moderate statelessness)
- Full Architectural State Management Deferral (high statelessness)
- Internally Deferred State Management (high statelessness)

Impacts of Service Statelessness
- Service Reusability (increases service scalability and availability in support of)
- Service Autonomy (can establish design characteristics that can both support and hinder)

Type of Discovery
- Design-Time Discovery
- Runtime Discovery

Discoverability Meta Information
- Functional Meta Data
- Quality of Service Meta Data

Impacts of Service Discoverability
- Standardized Service Contract (influences the content and design standards for)
- Service Abstraction (needs to be balanced against)
- Service Reusability (supports enterprise-wide)
- Service Composability (supports the creation and evolution of)

Impacts of Service Composability
- Standardized ServiceContract (supports)
- Service Loose Coupling (supports)
- Service Abstraction (supports)
-Service Reusability (supports)
-Service Autonomy (supports)
-Service Statelessness (supports)
-Service Discoverability (supports)

Evolutionary Cycle States of a Composition
- Composition Design Assessment
- Composition Runtime Assessment
- Composition Governance Assessment

Impacts of Service Composability
- Standardized Service Contract (Influences design standards for)
- Service Abstraction (introduces the "hidden composition members" consideration which requres careful positioning of)
- Service Loose Couping (emphasizes decreased)
- Service Reusability (introduces special considerations because it is a sophisticated form of)
- Service Autonomy (amplifies the need for high levels of)
- Service Statelessness (requires highly standardized)
- Service Discoverability (encourages composition-centric meta data in support of)

No comments:

Post a Comment