UKOLN DLF Reference Model for Discovery to Delivery Space
1. UKOLN is supported by: The ‘discovery to delivery’ DLF reference model Andy Powell, UKOLN, University of Bath [email_address] JISC-CETIS Conference, Edinburgh, November 2005 www.bath.ac.uk a centre of expertise in digital information management www.ukoln.ac.uk
2.
3.
4.
5.
6. Terminology - the DLF model Business requirement Business process Business function Abstract service Service binding Deployed service Business entity
7. Terminology - the DLF model Business requirement Business process Business function Abstract service Service binding Deployed service A business requirement is identifiable segment of an organisation’s overall mission. A business process is an identifiable portion of a business requirement. Business processes may be made up of business functions .
8. Terminology - the DLF model Business requirement Business process Business function Abstract service Service binding Deployed service A bstract services are discrete pieces of networked functionality (supporting a business process/function). A service binding is an instantiation of an abstract service – a concrete data representation, API, Web service description, etc.
9. Terminology - the DLF model Business requirement Business process Business function Abstract service Service binding Deployed service A deployed service is a service binding available at a specific location on the network. Business entity
10. Terminology - the DLF model Business requirement Business process Business function Abstract service Service binding Deployed service A business entity is something of interest – typically represented by metadata. The things that services are about. Business entity