16. A system, comprising: a hardware processor configured to: define a structured set of metadata for a provider function for calculating a service order, the structured set of metadata defining one or more variants that select a fulfillment pattern, the fulfillment pattern comprising a process flow declaration that includes one or more fulfillment functions of the fulfillment pattern and sets dependencies between pairs of fulfillment functions that impose an ordered priority of execution of the one or more fulfillment functions, and including metadata retrieved from a technical catalog; define a transformation sequence, based on the metadata for the provider function, comprising customizable process logic for the provider function, wherein the customizable process logic is structured within one or more stages configured to generate the service order; dynamically generate a runtime process flow for the provider function based on the metadata and the transformation sequence, the dynamically generating including selecting at least one fulfillment pattern from the one or more fulfillment patterns based on at least one entity from one or more entities comprised in the metadata and at least one discriminator from one or more discriminators comprised in the metadata; and generate a fulfillment flow based on the at least one selected fulfillment pattern; calculate the service order with customer-facing service order line objects and referring to an entity as its subject based on the fulfillment flow, wherein the metadata comprises the entity that defines a capability that is provided, and wherein the entity comprises one or more child entities; design a configuration for the entity, wherein the configuration comprises the entity, the one or more child entities, and one or more relationships between the entity and the one or more child entities; create, for each child entity, a design context comprising a reference to both a parent entity and one or more sub-components, wherein each child entity is a subject for the design context and wherein each subject comprises either a customer order, service order or a technical order; and design, for each child entity, an instance of the child entity using a corresponding design context.
16. A system, comprising: a hardware processor configured to: define a structured set of metadata for a provider function for calculating a service order, the structured set of metadata defining one or more variants that select a fulfillment pattern, the fulfillment pattern comprising a process flow declaration that includes one or more fulfillment functions of the fulfillment pattern and sets dependencies between pairs of fulfillment functions that impose an ordered priority of execution of the one or more fulfillment functions, and including metadata retrieved from a technical catalog; define a transformation sequence, based on the metadata for the provider function, comprising customizable process logic for the provider function, wherein the customizable process logic is structured within one or more stages configured to generate the service order; dynamically generate a runtime process flow for the provider function based on the metadata and the transformation sequence, the dynamically generating including selecting at least one fulfillment pattern from the one or more fulfillment patterns based on at least one entity from one or more entities comprised in the metadata and at least one discriminator from one or more discriminators comprised in the metadata; and generate a fulfillment flow based on the at least one selected fulfillment pattern; calculate the service order with customer-facing service order line objects and referring to an entity as its subject based on the fulfillment flow, wherein the metadata comprises the entity that defines a capability that is provided, and wherein the entity comprises one or more child entities; design a configuration for the entity, wherein the configuration comprises the entity, the one or more child entities, and one or more relationships between the entity and the one or more child entities; create, for each child entity, a design context comprising a reference to both a parent entity and one or more sub-components, wherein each child entity is a subject for the design context and wherein each subject comprises either a customer order, service order or a technical order; and design, for each child entity, an instance of the child entity using a corresponding design context. 19. The system of claim 16 , wherein the designing the instance of the child entity is performed recursively for each child entity.