A ResourceFunctionSpec specifies a function as a behavior to transform inputs of any nature into outputs of any nature independently from the way it is provided. It is typically created by a function designer who may not have specific knowledge on deployment architecture (for example using English text explanations with diagrams, like RFC standards, or preferably a machine interpretable language).<br/>The realization/deployment of a ResourceFunctionSpec may be achieved by different ways; either SoftwareSpecification, PhysicalBlackBoxSpec or SoftBlackBoxSpecification.<br/>Examples: manually or automated by software or hardware implementing algorithms etc.… without any impact on the definition of the functions itself.<br/>A SoftwareSpecification specifies properties or associated information that characterizes a software, such as:<br/>        • the release number, the status of the release, license conditions…<br/>        • hosting platform requirements such as OS, disk and memory space…<br/>        • input and output configuration and requirements<br/>and includes all files required for deployment and installation such as installation manager.<br/><br/>SoftBlackBoxSpec is a box with embedded software in it and PhysicalBlackBoxSpec is a box with any other internal mechanism realizing the function.<br/>A SoftConnectionPointSpec, resp. an ElectronicConnectionPointSpec are realization of Connection Points either as software Programming Interfaces (API) or as Electronic interface (signal processing).<br/>HostingPlatformRequirementSpec is used to represent the requirements that must be fulfilled by the platform that will run the software described in the SoftwareSpecification. These dependencies might include software libraries and packages as well as computing and network resources like CPU and memory.<br/>The derived association /SoftwareSpecificatonRequires is used to document the set of requirements of a platform which can host the concerned software.<br/>A SofwareSupportPackage represents the package acquired by a consumer from a software vendor. It can be materialized as one or several files (data) downloaded online or copied on a physical support. It contains all files required for deployment and installation such as installation manager and at minimum, one of the files constitutes the set of machine readable instructions that will be executed automatically after it is installed.<br/>An InstalledSoftware (renaming the Software concept from previous releases) consists of encoded information or computer instructions deployed on a machine such that it can be executed. An InstalledSoftware is a SoftwareSpecification deployed using the SoftwareSupportPackage and HostingPlatformRequirements.<br/>Each InstalledSoftware specifies their input and output respectively with SoftConnectionPoints.  <br/>The attributes shown for InstalledSoftware should be contained in a SoftwareSpecification entity, because their values don’t change from one instance of the same “type” of Software to another.  Also, the association to Language should be moved to a SoftwareSpecification entity.  The Language(s) supported by instances of the same “type” of Software don’t change from one instance to another.  Additionally, the 1.* association should be changed to a * since an instance of Language does not have to be associated with an instance of Software or a SoftwareSpecification.<br/><i>Note: the Software entity has been renamed InstalledSoftware in SID 17.0.</i><br/><br/>A ConfigurationFeatureSpec is a type of EntitySpecification.<br/>It is used to expose one or several ResourceFunctionSpecs to a consumer in such a way that it is easier to configure these RFSpecs from a consumer view point, at the deployment stage (intend based deployment as opposed to detailed based deployment).<br/>        • Some ConfigurationFeatureSpec may be mandatory while others can be selected or not by the consumer (for a given instantiation).<br/>        • ConfigurationFeatureSpec may have characteristics which are settable by the consumer (at instantiation time and/or during the lifetime of the ResourceFunction).<br/>The following diagram represents the main Business Entities related to ResourceFunctionSpec and their relationships:<br/>