Slides

264 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
264
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The proposed research programme, of nearly £7.5M over five years, has four main topics: Through Life Systems Management , which includes: identification of key business processes for exploitation of networked solutions for the NEC challenge; lifecycle models that includes architectures and cost models for evolutionary systems of systems; critical systems features and effective measurement techniques for NEC delivery. Systems Architectures , which includes: development and evaluation of a set of architectural representations of systems of systems to support NEC and through-life system evolution; specific links to the developing MoD Architectural Framework, MODAF. Decision Support, which includes development of a prototype Integrated Decision Support Environment (IDSE) to provide improved decision making capability in dynamically reconfigurable multiple distributed organisations; i.e. the supply chain structures for NEC. Control and Monitoring, which includes development of a toolkit for managing uncertainty in a NEC environment, based on the components of detection (system health), assessment (prognostics), and response (reconfiguration).
  • Initial research on Service Oriented architectures has concentrated on: Software architectures to support: IT and Business Process Management Transactions Decentralised Middleware, the communication system exists within the hosting environment of each service. Loose Coupling, which contributes: Discovery by abstract descriptions Evolvable systems independent of implementation/platform Interchangeable by interface definition Autonomous services, where each services encapsulate the business logic and reduce the inter-dependency to other services. Increased flexibility in adding, replacing and changing implementations. Reusable services in new contexts Inter-organisational SoA Patterns (IBM) There are numerous references on web services and grid services. Of particular interest to NEC, the relatively new field of grid services are aimed at resource sharing extends the web services open standards.
  • 1. supplier & customer Platforms: fres & terrier defined with use cases, prototyping. Can the platform be a service, or can fres be componentised to form service contracts and allow component replacement? What are the information services required to support IT services and platform services? Security Issues Composite applications, contractual requirements via service level agreements (how much can be automated and policed, how much is taken on trust then settled by mediation/legal resolution?
  • When can loose coupling be used in a secure environment? Does it just mean *the* supplier can alter the service implementation? I.E. Loose coupling between definition and implementation, but not interchange of services from different suppliers. If you can change services, what does this mean in long term interactions? Distributed Change, DEPENDABILITY. Reasons for change: reliable, improved performance, environment change (Platform, OS), business change (supply chain). How do we measure the effect of a possible change? For reliability, better performance, more information, more secure? SoA in embedded products? SoA increased network traffic in Military comms systems. Protected bandwidth for security: eavesdropping, revealing location, malicious damage, cost of bandwidth & power, reliance on connections. When changing business model, how is this costed and risks measured?
  • Slides

    1. 1. Service Oriented Architecture For Network Enabled Capability Duncan Russell Jie Xu School of Computing University of Leeds
    2. 2. SOA For NEC <ul><li>NECTISE </li></ul><ul><li>NEC & Architecture Requirements </li></ul><ul><li>SOA Capabilities </li></ul><ul><li>Key Issues for NECTISE </li></ul>
    3. 3. NECTISE Programme <ul><li>Network Enabled Capability Through Innovative Systems Engineering </li></ul><ul><li>Research Involving: </li></ul><ul><ul><li>10 Universities of Bath, Cambridge, Cranfield, Leeds, Leicester, Loughborough, Manchester, Queen’s Belfast, Strathclyde, and York </li></ul></ul><ul><ul><li>BAE Systems, including different business units </li></ul></ul><ul><li>UK MoD response to rapidly changing conflict environment </li></ul><ul><li>Armed forces: </li></ul><ul><ul><li>Flexible, ready, rapidly deployable </li></ul></ul><ul><ul><li>Controlled, precise force </li></ul></ul><ul><li>BAE Systems, defence supplier </li></ul><ul><ul><li>Contribute to capability supply </li></ul></ul><ul><ul><li>Product/Service lifecycle </li></ul></ul><ul><ul><li>Dynamic connected network of customer-supplier </li></ul></ul>
    4. 4. NECTISE Programme <ul><li>Through-Life Systems Management </li></ul><ul><ul><li>Identification of key business processes for exploitation of networked solutions </li></ul></ul><ul><ul><li>Lifecycle models, including: </li></ul></ul><ul><ul><ul><li>Architectures and cost models for evolutionary systems of systems </li></ul></ul></ul><ul><ul><ul><li>Critical Systems Features </li></ul></ul></ul><ul><ul><ul><li>Effective measurement techniques for NEC delivery </li></ul></ul></ul><ul><li>Systems Architectures </li></ul><ul><ul><li>Architectural representations of systems of systems </li></ul></ul><ul><ul><li>Evaluation of architectures </li></ul></ul><ul><ul><li>Through-life systems evolution </li></ul></ul><ul><ul><li>Architectural Frameworks </li></ul></ul><ul><li>Decision Support </li></ul><ul><ul><li>Decision making capability in dynamically reconfigurable multiple distributed organisations </li></ul></ul><ul><li>Control and Monitoring </li></ul><ul><ul><li>Toolkit for managing uncertainty </li></ul></ul><ul><ul><li>Based on the components of: </li></ul></ul><ul><ul><ul><li>detection (system health), </li></ul></ul></ul><ul><ul><ul><li>assessment (prognostics), and </li></ul></ul></ul><ul><ul><ul><li>response (reconfiguration). </li></ul></ul></ul>
    5. 5. Network Enabled Capability Requirements <ul><li>Armed Forces to be flexible , ready and rapidly deployable </li></ul><ul><li>Application of controlled and precise force, to achieve realisable effects </li></ul><ul><li>System integration without interdependence </li></ul><ul><li>Evolvable , responding to changes in environment, situation, supply, information and ongoing development </li></ul><ul><li>Dependable , managing system changes, to tolerate faults and through-life evolution in a secure manner </li></ul><ul><li>Cost effective , by efficient use of assets and supply </li></ul><ul><li>Connecting industrial and defence environments, and connecting pan-defence environments and civilian services </li></ul><ul><li>Increased use of data and information , securely managing information and control </li></ul>
    6. 6. Capability Model: Organisational & Operational
    7. 7. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    8. 8. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    9. 9. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    10. 10. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    11. 11. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    12. 12. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    13. 13. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    14. 14. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    15. 15. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    16. 16. NEC & Architecture Requirements <ul><li>Flexible </li></ul><ul><li>Ready </li></ul><ul><li>Precise </li></ul><ul><li>Integrated </li></ul><ul><li>Autonomy </li></ul><ul><li>Evolvable </li></ul><ul><li>Dependable </li></ul><ul><li>Cost Effective </li></ul><ul><li>Connected </li></ul><ul><li>Information Handling </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    17. 17. Service Oriented Architecture <ul><li>Decentralised Middleware </li></ul><ul><li>Loose Coupling </li></ul><ul><ul><li>Discovery by abstract descriptions </li></ul></ul><ul><ul><li>Evolvable systems independent of implementation/ platform </li></ul></ul><ul><ul><li>Interchangeable by interface definition </li></ul></ul><ul><ul><li>Autonomous services </li></ul></ul><ul><ul><li>Reusable services in new contexts </li></ul></ul><ul><ul><li>Inter-organisational </li></ul></ul><ul><li>Web & Grid Services </li></ul><ul><ul><li>Open standards for inter-organisation resource sharing </li></ul></ul>
    18. 18. SOA Capabilities <ul><li>Loose Coupling </li></ul><ul><li>Define by Interface </li></ul><ul><li>Late Binding </li></ul><ul><li>Re-use </li></ul><ul><li>Inter-organisational </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    19. 19. SOA Capabilities <ul><li>Loose Coupling </li></ul><ul><li>Define by Interface </li></ul><ul><li>Late Binding </li></ul><ul><li>Re-use </li></ul><ul><li>Inter-organisational </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    20. 20. SOA Capabilities <ul><li>Loose Coupling </li></ul><ul><li>Define by Interface </li></ul><ul><li>Late Binding </li></ul><ul><li>Re-use </li></ul><ul><li>Inter-organisational </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    21. 21. SOA Capabilities <ul><li>Loose Coupling </li></ul><ul><li>Define by Interface </li></ul><ul><li>Late Binding </li></ul><ul><li>Re-use </li></ul><ul><li>Inter-organisational </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    22. 22. SOA Capabilities <ul><li>Loose Coupling </li></ul><ul><li>Define by Interface </li></ul><ul><li>Late Binding </li></ul><ul><li>Re-use </li></ul><ul><li>Inter-organisational </li></ul><ul><li>Evolvable (design/runtime) </li></ul><ul><li>Availability </li></ul><ul><li>Accessibility </li></ul><ul><li>Autonomous </li></ul><ul><li>Integrity </li></ul><ul><li>Performance </li></ul><ul><li>Reliable </li></ul><ul><li>Regulatory </li></ul><ul><li>Security </li></ul><ul><li>Maintainability </li></ul><ul><li>Scalability </li></ul><ul><li>Resilience </li></ul><ul><li>Integratability </li></ul><ul><li>Upgradability </li></ul><ul><li>Constructable </li></ul><ul><li>Reconfigurable </li></ul>
    23. 23. Key Issues - SOA <ul><li>Paradigm shift for business </li></ul><ul><li>Service Identification for Military platforms </li></ul><ul><ul><li>How to define the granularity of a service and how it relates to hardware platforms? </li></ul></ul><ul><li>Attribute Identification to define capability </li></ul><ul><ul><li>How a service is defined by its components, responsibilities and attributes (quality of service)? </li></ul></ul><ul><ul><li>How does a service contribute to capability? </li></ul></ul><ul><ul><li>What are the quality of service attributes required for NEC? </li></ul></ul>
    24. 24. Key Issues - SOA <ul><li>Loose Coupling vs Tight Coupling </li></ul><ul><ul><li>If late binding is used, what parameters does a broker require, to select by availability, quality of service, security and usage policies? </li></ul></ul><ul><li>Distributed Change </li></ul><ul><ul><li>How is change managed in an uncertain NEC environment, </li></ul></ul><ul><ul><li>How do you measure the correctness of SOA for NEC? </li></ul></ul><ul><li>What is the cost of middleware for NEC platforms? </li></ul><ul><li>How do we determine the through-life cost of service delivery? </li></ul>

    ×