Skip to end of metadata
Go to start of metadata

Project Objectives and Relationship with Architecture Work

These are the project objectives, with architecture highlighted but note that it pervades many of the objectives:

  1. To support the software development process
  2. To select and support the technologies to be integrated, adapted and extended, ensuring compatibility with existing ones
  3. To develop a reference architecture for Scientific Workflow Preservation, combining existing architectures and approaches
  4. To integrate components developed in technical workpackages into the Wf4Ever codebase
  5. To explore opportunities to exploit Wf4Ever architecture and codebase in the user communities of the project, and outside the project
  6. To encapsulate process specifications and related objects as Research Objects
  7. To develop models for managing the whole lifecycle of scientific workflows and their related objects, from creation to preservation
  8. To develop personalised recommendation techniques for scientific workflows and their related objects
  9. To develop methods for computing and inspecting workflow integrity, and assessing workflow (and related Research Objects) authenticity and trustworthiness
  10. To develop ontologies for describing scientific workflows and their related objects, extending existing efforts.
  11. To evaluate Wf4Ever, by means of two use cases, which involve the preservation and reuse of scientific workflows and their related objects.
  12. To disseminate the Wf4Ever results to the Scientific Workflow, Semantic Web, Social Networks, Digital Libraries, Astronomy and Bioinformatics communities and make these results available to other EU projects
  13. To use the architecture and other project outcomes to influence relevant standardisation efforts in organisations like W3C, OAI, ISO, etc.
  14. To identify market and opportunities for Wf4Ever results

Architectural Requirements

General ideas

  • The provenance and research object components should work equally well in the wider  Web as well as within the Wf4Ever workflow preservation framework (GK)
    • These components, and their interfaces, should be as simple as possible to facilitate their exchange and/or integration with a range of Web systems as well as Wf4Ever
  • Have a simple system that addresses some common user requirements, and also provides extension points for dealing with more specialized requirements, than a single complex system that addresses all requirements (see TimBL's principles of "least power" and "independent invention" - (GK)
  • Pick on a very few key requirements, design a system to serve them, then refactor the design as new requirements are introduced (GK)
    • Do not necessarily identify *all* the user requirements, but to identify a few of the *most important* user requirements, and focus initially on those so we can deliver early gains to our users

From Workpackages

Please add architecture requirements to the page for your workpackage. In preparation for the Architecture Task Force Face to Face Meeting on 7th February, please indicate what existing components your workpackage will bring, what standards, and what are the mechanisms for integration.

WP2 Workflow Lifecycle Management UNIMAN iSOCO, UPM, PSNC, OXF

WP3 Workflow Evolution, Sharing and Collaboration UPM iSOCO, UNIMAN, PSNC, OXF

WP4 Workflow Integrity and Authenticity Maintenance iSOCO UNIMAN, UPM, OXF


WP6 Bioinformatics LUMC iSOCO, UNIMAN, PSNC, OXF

Architecture Deliverables in WP1 Software Architecture and Technology for Scientific Workflow Preservation

  • D1.3v1 Wf4Ever Architecture – Phase I (Report/Public, Month 12). Report describing the Wf4Ever architecture for the design and implementation of scientific workflow preservation systems.
  • D1.3v2 Wf4Ever Architecture – Phase II (Report/Public, Month 28). Update on D1.3v1.
  • D1.4v1 Reference Wf4Ever Implementation – Phase I (Prototype/Public, Month 20). First prototype of the reference implementation of Wf4Ever architecture.
  • D1.4v2 Reference Wf4Ever Implementation – Phase II (Prototype/Public, Month 32). Final prototype of the reference implementation of Wf4Ever architecture.
  • D1.5 Opportunities for applying Wf4Ever architecture and technologies (Report/Public, Month 36).Survey on the services and applications identified in other workflow- intensive scientific applications, which can benefit from the use of the proposed architecture and technologies. It also provides guidelines for developing applications and refactoring existing ones according to the Wf4Ever architecture.


Unable to render {children}. Page not found: Architecture Meetings.

To add a meeting, go to Architecture Task Force Meetings and click Add Page.
Remember to prefix the page title with the ISO8601-format date to help sorting and avoid confusion, for instance 2011-02-28 Architecture telcon.


To add a document, go to Architecture Documents and edit.

  • No labels