1 / 13

Delivering User Needs: A middleware perspective

Delivering User Needs: A middleware perspective. Steven Newhouse Director. OMII-UK. A partnership between projects: my Grid at Manchester (Carole Goble - Chair) OGSA-DAI at Edinburgh (Malcolm Atkinson) OMII at Southampton (Dave De Roure) Started January 2006

elvina
Download Presentation

Delivering User Needs: A middleware perspective

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Delivering User Needs:A middleware perspective Steven Newhouse Director

  2. OMII-UK • A partnership between projects: • myGrid at Manchester (Carole Goble - Chair) • OGSA-DAI at Edinburgh (Malcolm Atkinson) • OMII at Southampton (Dave De Roure) • Started January 2006 • Manchester – Expanded Engineering activity • Southampton – Expanded Community activity • Edinburgh – Continuation of OGSA-DAI team All funded for 3 years ©

  3. Objectives of OMII-UK • To distribute a sustained, well-engineered, interoperable, documented and supported set of easily-used integrated middleware services, components and tools • To engage proactively with user communities in defining and developing this distribution • To maintain a leading international role in advanced e-Infrastructure middleware provision ©

  4. OMII-UK Activities • User engagement • Forming partnerships with targeted user communities • Sourcing • Working with UK and international service developers and middleware providers • Software Engineering • Quality-assured software engineering, coordinated across OMII-UK partners and the managed programme • Grid engagement • Tracking and engagement with the standards processes • Sustainable business • Attracting partnerships and new investors ©

  5. Gathering Requirements Townhall & SIG meetings Users Forum & Users’ Groups Embedded Staff & Scenarios Review ‘Rejected’ Requirements USER COMMUNITY Life-scientists Engineers Social Scientists Application Developers System Administrators Grid Deployers Service Providers Engagement Requirements Capture Prioritisation (Operations) Assessment Technical Refinement Review & Comment Technical Assessment Prioritisation (Management) Software Engineering Responsive Mode (Unsolicited) Open/Directed Calls Explicit Contract Integration into roadmap Integration Delayed RELEASE Integration (Operations) Technical Planning Commissioning ©

  6. Capturing & Delivering Needs • Defining the problem… • What are you going to solve? • How will you measuring success/failure? • Mapping to an architecture • Leveraging infrastructure, e.g. security, management • Layered middleware, e.g. upperware, underware • Reusing components, e.g. standard implementations • Granularity • Generic reusable vs. domain specific interfaces ©

  7. Upperware Underware OMII-UK & NGSLife Sciences Gateway Bioinformatics & Life Science Users Middleware Taverna SOAPLab Services GRIMOIRES OMII: e-Infrastructure Services Core NGS Middleware OGSA-DAI GridSAM Hardware Resources ©

  8. Managing Service Complexity Tools • User Perspective: • One service invocation does all • Customised to their problem • Generic Middleware Provider: • Re-factor to exploit: • Lower-level services • Generic operations on the services • Need to work with deployed infrastructure • Build on standards • Promote reusability • In meeting requirements • A healthy tension, e.g. a registry • User Capability  Software Engineering Username & password Middleware Upperware Underware X.509 Infrastructure ©

  9. Delivering The Software • Commissioning the required software • (Re-) packaging into a distribution • Verifying portability through deployment • NMI Build and Test Framework • ETICS - e-Infrastructure for Testing, Integration and Configuration of Software • OMII-Europe • Repeatable testing • Measure robustness – bugs discovered per cycle ©

  10. Standards • Upperware Specifications • Community/Domain Driven: IVOA, Bioinformatics • Middleware Specifications • JSDL, BES, WS-DAI, • Underware Specifications • WS-Eventing, WS-Notification, WS-RM, WS-R, UDDI • Infrastructure • TCP, HTTP, … Build on standards so that you get your core infrastructure for free! ©

  11. Architecture Clients Management Portlets Account Authorisation … Domain Specific Portlets Workflow Jobs … Upper/Middle/Lower ware Services Infrastructure Services JSR-168 Portlet Environment WS-Security Static Webpages AXIS TOMCAT ©

  12. OMII-UK Activities • User engagement • Forming partnerships with targeted user communities • Sourcing • Working with UK and international service developers and middleware providers • Software Engineering • Quality-assured software engineering, coordinated across OMII-UK partners and the managed programme • Grid engagement • Tracking and engagement with the standards processes • Sustainable business • Attracting partnerships and new investors ©

  13. Summary • Don’t try and own the whole problem • You don’t want to go there! • Interested in partnerships to drive development • Build on the emerging e-Infrastructure • Need to develop a shared understanding • You should not need to learn software engineering • ‘We’ should not need to learn about astronomy • Contact • Mail: s.newhouse@omii.ac.uk • http: www.omii.ac.uk ©

More Related