Service Oriented Architecture For Network Enabled Capability

1
Service Oriented Architecture For Network Enabled
Capability

• Duncan Russell Jie Xu
• School of Computing
• University of Leeds

2
SOA For NEC

• NECTISE
• NEC Architecture Requirements
• SOA Capabilities
• Key Issues for NECTISE

3
NECTISE Programme

• Network Enabled Capability Through Innovative
  Systems Engineering
• Research Involving
• 10 Universities of Bath, Cambridge, Cranfield,
  Leeds, Leicester, Loughborough, Manchester,
  Queens Belfast, Strathclyde, and York
• BAE Systems, including different business units
• UK MoD response to rapidly changing conflict
  environment
• Armed forces
• Flexible, ready, rapidly deployable
• Controlled, precise force
• BAE Systems, defence supplier
• Contribute to capability supply
• Product/Service lifecycle
• Dynamic connected network of customer-supplier

4
NECTISE Programme

• Through-Life Systems Management
• Identification of key business processes for
  exploitation of networked solutions
• Lifecycle models, including
• Architectures and cost models for evolutionary
  systems of systems
• Critical Systems Features
• Effective measurement techniques for NEC delivery
• Systems Architectures
• Architectural representations of systems of
  systems
• Evaluation of architectures
• Through-life systems evolution
• Architectural Frameworks
• Decision Support
• Decision making capability in dynamically
  reconfigurable multiple distributed organisations
• Control and Monitoring
• Toolkit for managing uncertainty
• Based on the components of
• detection (system health),
• assessment (prognostics), and
• response (reconfiguration).

5
Network Enabled Capability Requirements

• Armed Forces to be flexible, ready and rapidly
  deployable
• Application of controlled and precise force, to
  achieve realisable effects
• System integration without interdependence
• Evolvable, responding to changes in environment,
  situation, supply, information and ongoing
  development
• Dependable, managing system changes, to tolerate
  faults and through-life evolution in a secure
  manner
• Cost effective, by efficient use of assets and
  supply
• Connecting industrial and defence environments,
  and connecting pan-defence environments and
  civilian services
• Increased use of data and information, securely
  managing information and control

6
Capability Model Organisational Operational
7
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

8
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

9
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

10
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

11
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

12
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

13
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

14
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

15
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

16
NEC Architecture Requirements

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

• Flexible
• Ready
• Precise
• Integrated
• Autonomy
• Evolvable
• Dependable
• Cost Effective
• Connected
• Information Handling

17
Service Oriented Architecture

• Decentralised Middleware
• Loose Coupling
• Discovery by abstract descriptions
• Evolvable systems independent of implementation/
  platform
• Interchangeable by interface definition
• Autonomous services
• Reusable services in new contexts
• Inter-organisational
• Web Grid Services
• Open standards for inter-organisation resource
  sharing

18
SOA Capabilities

• Loose Coupling
• Define by Interface
• Late Binding
• Re-use
• Inter-organisational

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

19
SOA Capabilities

• Loose Coupling
• Define by Interface
• Late Binding
• Re-use
• Inter-organisational

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

20
SOA Capabilities

• Loose Coupling
• Define by Interface
• Late Binding
• Re-use
• Inter-organisational

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

21
SOA Capabilities

• Loose Coupling
• Define by Interface
• Late Binding
• Re-use
• Inter-organisational

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

22
SOA Capabilities

• Loose Coupling
• Define by Interface
• Late Binding
• Re-use
• Inter-organisational

• Evolvable (design/runtime)
• Availability
• Accessibility
• Autonomous
• Integrity
• Performance
• Reliable
• Regulatory
• Security
• Maintainability
• Scalability
• Resilience
• Integratability
• Upgradability
• Constructable
• Reconfigurable

23
Key Issues - SOA

• Paradigm shift for business
• Service Identification for Military platforms
• How to define the granularity of a service and
  how it relates to hardware platforms?
• Attribute Identification to define capability
• How a service is defined by its components,
  responsibilities and attributes (quality of
  service)?
• How does a service contribute to capability?
• What are the quality of service attributes
  required for NEC?

24
Key Issues - SOA

• Loose Coupling vs Tight Coupling
• If late binding is used, what parameters does a
  broker require, to select by availability,
  quality of service, security and usage policies?
• Distributed Change
• How is change managed in an uncertain NEC
  environment,
• How do you measure the correctness of SOA for
  NEC?
• What is the cost of middleware for NEC platforms?
• How do we determine the through-life cost of
  service delivery?