Semanteme identification and demand encapsulation method for software service

Abstract

The invention discloses a semanteme identification and demand encapsulation method for a software service. The method comprises the following steps of: firstly, constructing a domain model and a software service registration model, wherein the domain model comprises a domain main body model and a domain demand model; and secondly, when the software service to be registered is registered into a software service registration library, identifying the software service by using a domain main body model file and encapsulating the software service by using a domain demand model file. Thus, the technical scheme of the invention solves the problem of semanteme identification and demand encapsulation of the software service and can support semanteme-and-demand-based software service matching in a software service discovery process, realize combination of service discovery from the top to the bottom and the demand discovery from the bottom to the top and lay a foundation for subsequent software service dynamic combination.

Description

technical field [0001] The invention belongs to the technical field of information resource integration and application, and in particular relates to a method for software service semantic identification and requirement encapsulation. Background technique [0002] With the prevalence of cloud computing (Cloud Computing) today, the paradigm of software development is also undergoing tremendous changes. From the initial Web service to the current SaaS service, software forms emerge in endlessly. However, there are two main problems in the definition and use of these software services: first, they often need to search for the required services through keywords, and this kind of service matching at the grammatical level is difficult to meet the needs of users. Second, the demand positioning of software services is relatively vague. They often focus on the attributes and inherent characteristics of software services themselves, while ignoring that the purpose of software service...

AI Technical Summary

Problems solved by technology

However, there are two main problems in the definition and use of these software services: first, they often need to find the required services through keywords, and this kind of service matching at the grammatical level is difficult to meet the needs of users

2. The demand positioning of software services is relatively vague. They often focus on the attributes and inherent characteristics of software services themselves, while ignoring that the purpose of software services is to meet the needs of users

However, the current OWL-S ontology does not support the description of service roles, so that business developers cannot use the role information contained in user requirements during the service discovery process

[0007] 2. It is impossible to describe the target (ie function) corresponding to the service

Although this method can express the function of the service to a certain extent, in some cases, the function of the service cannot be accurately described by using this method, which is easy to cause confusion

Images