Meta data model for managing work products and deliverables

A computer program product, comprising a computer readable storage medium having a computer readable program code stored therein, said computer readable program code containing instructions executable by a processor of a computer system to implement a method of tracing a business requirement to an implemented service in a systems development lifecycle by processing data conforming to a data model, said data model comprising:

• a first asset type (functional requirement type) that represents a functional requirement;
• a second asset type (process element type) that represents a process element;
• a third asset type (business service type) that represents a business service;
• a fourth asset type (standard type) that represents a standard;
• a fifth asset type (service design type) that represents an information technology (IT) service design;
• a sixth asset type (service component type) that represents a service component of said business service;
• a first relationship between said functional requirement type and said process element type, wherein said first relationship specifies that said functional requirement is represented as said process element;
• a second relationship between said process element type and said business service type, wherein said second relationship specifies that said process element identifies said business service;
• a third relationship between said business service type and said standard type, wherein said third relationship specifies that said business service conforms to said standard;
• a fourth relationship between said business service type and said service design type, wherein said fourth relationship specifies that said business service is designed as said IT service design;
• a fifth relationship between said standard type and said service design type, wherein said fifth relationship specifies that said standard is a design template for said IT service design;
• and
• a sixth relationship between said service design type and said service component type, wherein said sixth relationship specifies that said service design provides design guidelines for said service component,
• wherein said service component realizes a service interface represented by a service interface type, wherein said service interface specifies said implemented service represented by a service implementation type,
• wherein said functional requirement type, said process element type, said business service type, said service design type, said service component type, said first relationship, said second relationship, said fourth relationship, and said sixth relationship provides a tracing between said functional requirement and said implemented service, and
• wherein said first asset type, said second asset type, said third asset type, said fourth asset type, said fifth asset type, and said sixth asset type are heterogeneous asset types.