bug list. This section shall be replaced by a suitable description of the purpose. For example: The purpose of this service instance description document is to provide a documentation of the implementation and instantiation of the <XYZ> service (see [2]), realized by using the <ABC> technology as described in [3], according to the guidelines given in [1]. It describes a well-defined baseline of the service implementation by clearly identifying the service implementation version. The aim is to document the key aspects of the <XYZ> service instantiation. This includes: identification and summary of the service instance: reference to the service design description; reference to the service specification; identification of the service instance. service implementation and instantiation details: internal design decisions; configuration data; deployment information. release notes: • feature list: bug list. This service instance description template is intended to be read by software architects, designers and implementers who shall produce service implementation and instance description. This section shall describe the intended readers of the service instance description document. For example: This service instance description document is intended to be read by service providers, system engineers and developers in charge of deploying and operating an instance of the <XYZ> service SERVICE INSTANCE IDENTIFICATION Service Instance Identification Name Service instance name. ID Unique identity of service instance. Version of the XYZ service instance. Version Technology Indication of the technology used and supported by this instance (e.g. REST or SOAP). Service Specification ID Reference to the service specification. Service Specification Version Reference to the service specification.
bug list. This section shall be replaced by a suitable description of the purpose. For example: The purpose of this service instance description document is to provide a documentation of the implementation and instantiation of the <XYZ> service (see [2]), realized by using the <ABC> technology as described in [3], according to the guidelines given in [1]. It describes a well-defined baseline of the service implementation by clearly identifying the service implementation version. The aim is to document the key aspects of the <XYZ> service instantiation. This includes: identification and summary of the service instance: reference to the service design description; reference to the service specification; identification of the service instance. service implementation and instantiation details: internal design decisions; configuration data; deployment information. • release notes: feature list: bug list. This service instance description template is intended to be read by software architects, designers and implementers who shall produce service implementation and instance description. This section shall describe the intended readers of the service instance description document. For example: This service instance description document is intended to be read by service providers, system engineers and developers in charge of deploying and operating an instance of the <XYZ> service SERVICE INSTANCE IDENTIFICATION Service Instance Identification Name Service instance name. ID Unique identity of service instance. Version Version of the XYZ service instance. Technology Indication of the technology used and supported by this instance (e.g. REST or SOAP). Service Specification ID Reference to the service specification. Service Specification Version Reference to the service specification.
Service_Instance_Description_Template.docx