CN110737427B

CN110737427B - Internet technology architecture, construction method and device thereof, electronic equipment and medium

Info

Publication number: CN110737427B
Application number: CN201910978421.4A
Authority: CN
Inventors: 龚光庆; 朱国平; 江涛; 镇超; 石凯; 朱嘉瑜
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2019-10-15
Filing date: 2019-10-15
Publication date: 2023-06-09
Anticipated expiration: 2039-10-15
Also published as: CN110737427A

Abstract

The present disclosure provides an internet technology architecture, and a construction method, an apparatus, an electronic device, and a medium thereof, where the internet technology architecture includes: the interaction component comprises an interface, a navigation component, an input-output component and a calling relation between the interaction component and the transaction service; transaction service, which realizes business function by calling component service and outputs the processing result of business function to interaction component, wherein one transaction service corresponds to one interaction action between one entity and service; the component service is used for assembling the object service for the transaction service to call; and an object service for encapsulating the business rules to perform read and/or write operations on data related to the entity in the data set based on the business rules.

Description

Internet technology architecture, construction method and device thereof, electronic equipment and medium

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to an internet technology architecture, and a method, an apparatus, an electronic device, and a medium for constructing the same.

Background

In order to meet the development requirements of digital banks, commercial banks need to understand industry development trends and analyze threats and opportunities existing in enterprises.

In carrying out the disclosed concept, the inventors have found that at least the following problems exist in the prior art. The business architecture relates to aspects of business bank value creation, business operation and internal management, has complex asset structure, lacks systematic analysis in the past business bank value creation process, and rarely forms systematic corresponding relation with business and Internet Technology (IT) architecture assets, which also causes that the IT architecture cannot reflect the requirements and changes of the business in time. In addition, construction and maintenance personnel are numerous, the cost is high, the iteration frequently needs specific system storage, and a corresponding relation between the business architecture asset and the IT architecture asset needs to be established.

Disclosure of Invention

In view of this, the present disclosure provides an internet technology architecture for coupling an IT architecture with a business architecture, and a construction method, apparatus, electronic device, and medium thereof.

One aspect of the present disclosure provides an internet technology architecture, comprising: interaction component, transaction service, component service, and object service. The interaction component comprises an interface, a navigation component, an input and output component and a calling relation between the interaction component and the transaction service; the transaction service realizes a business function by calling a component service and outputs a processing result of the business function to the interaction component, wherein one transaction service corresponds to one interaction action between one entity and the service; the component service is used for assembling the object service for the transaction service to call; the object service is used to encapsulate business rules to read and/or write data associated with an entity in the data set based on the business rules.

According to an embodiment of the present disclosure, a calling method between an interaction component, a transaction service, a component service, and an object service includes: transaction services can only be called by the interaction component layer application, the transaction services call component services to realize business functions, and the interaction is forbidden between the transaction services; the component services can only be called by the transaction service to the object service, the component services call the object service to form an application, and the component services are forbidden to call each other; the object services can only be called by the component services, and the data set is operated through the technical framework, so that the object services are forbidden to be called mutually; the transaction service may invoke a component service across applications, the component service prohibiting invocation of an object service across applications.

According to embodiments of the present disclosure, there is a one-to-one or one-to-many mapping relationship between interaction components and transaction services; a one-to-one or one-to-many mapping relation exists between the transaction service and the component service; there is a one-to-one or one-to-many mapping between component services and object services.

One aspect of the present disclosure provides an internet technology architecture construction method, including: the method comprises the steps that an interaction component is obtained based on an activity model of a business architecture, wherein the business architecture comprises an entity model, an activity model, a task model and a component model, the activity model, the task model and the component model provide services for entities corresponding to the entity model, a one-to-one or one-to-many first mapping relation exists between the activity model and the task model, and a one-to-one or one-to-many second mapping relation exists between the task model and the component model; acquiring transaction service based on a task model and an interaction component of a business architecture; acquiring component services based on a component model of a business architecture and transaction services; the entity model and the component service based on the business architecture acquire object services, wherein one candidate object service relates to rules and business logic of one entity; and packaging the interaction component, the transaction service, the component service and the object service based on the first mapping relation and the second mapping relation.

According to an embodiment of the present disclosure, acquiring transaction services based on a task model and interaction component of a business architecture includes: acquiring candidate transaction services based on a task model of a business architecture and an interaction component, wherein one time of human-computer interaction in the interaction component corresponds to one candidate transaction service; and processing a plurality of candidate transaction services with the same business function to obtain the transaction service, wherein a one-to-one or one-to-many mapping relationship exists between the interaction component and the transaction service.

According to an embodiment of the present disclosure, a business architecture-based component model and transaction service acquisition component service includes: acquiring candidate component services based on the component model of the business architecture and the transaction service; and merging a plurality of candidate component services with the same application function to obtain the component services, wherein the transaction service and the component services are in one-to-one or one-to-many mapping relation.

According to an embodiment of the present disclosure, an object service exists a component service having a call relationship; the component services have transaction services with calling relations, and the same component service is forbidden to be called for multiple times by the same transaction service; and the transaction service corresponding to the activity model is stored in the transaction service list.

One aspect of the present disclosure provides an internet technology architecture construction apparatus, including: the system comprises an interaction component determining module, a transaction service acquiring module, a component service acquiring module, an object service acquiring module and a constructing module. The interaction component determining module is used for acquiring an interaction component based on an activity model of a business architecture, wherein the business architecture comprises an entity model, an activity model, a task model and a component model, the activity model, the task model and the component model provide services for entities corresponding to the entity model, a one-to-one or one-to-many first mapping relation exists between the activity model and the task model, and a one-to-one or one-to-many second mapping relation exists between the task model and the component model; the transaction service acquisition module is used for acquiring transaction services based on a task model and an interaction component of the business architecture; the component service acquisition module is used for acquiring component services based on a component model of the business architecture and transaction services; the object service acquisition module is used for acquiring object services based on the entity model of the business architecture and the component services, wherein one candidate object service relates to the rule and business logic of one entity; the construction module is used for packaging the interaction component, the transaction service, the component service and the object service based on the first mapping relation and the second mapping relation.

According to an embodiment of the present disclosure, a transaction service acquisition module includes: a candidate transaction service acquisition unit and a transaction service acquisition unit. The candidate transaction service acquisition unit is used for acquiring candidate transaction services based on a task model of a business architecture and the interaction assembly, wherein one time of human-computer interaction in the interaction assembly corresponds to one candidate transaction service; and the transaction service acquisition unit is used for processing a plurality of candidate transaction services with the same business function to obtain the transaction service, wherein a one-to-one or one-to-many mapping relation exists between the interaction component and the transaction service.

According to an embodiment of the present disclosure, a component service acquisition module includes: and a candidate component service acquisition unit and a component service acquisition unit. The candidate component service acquisition unit is used for acquiring candidate component services based on the component model of the business architecture and the transaction service; and the component service acquisition unit is used for merging a plurality of candidate component services with the same application function to obtain the component service, wherein the transaction service and the component service are in one-to-one or one-to-many mapping relation.

Another aspect of the present disclosure provides an electronic device comprising one or more processors and a storage device for storing executable instructions that, when executed by the processors, implement the method as described above.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, are configured to implement a method as described above.

Another aspect of the present disclosure provides a computer program comprising computer executable instructions which, when executed, are adapted to carry out the method as described above.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments thereof with reference to the accompanying drawings in which:

fig. 1 schematically illustrates an application scenario of an internet technology architecture, a method, an apparatus, an electronic device, and a medium for constructing the same according to an embodiment of the present disclosure;

FIG. 2 schematically illustrates an exemplary system architecture to which an Internet technology architecture and methods, apparatus, electronic devices, and media of construction thereof may be applied, in accordance with embodiments of the present disclosure;

FIG. 3 schematically illustrates a structural schematic of an Internet technology architecture according to an embodiment of the present disclosure;

fig. 4 schematically illustrates a structural schematic diagram of an internet technology architecture and a business architecture according to an embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow chart of an Internet technology architecture construction method according to an embodiment of the present disclosure;

FIG. 6 schematically illustrates a logic diagram of an Internet technology architecture construction method according to an embodiment of the present disclosure;

FIG. 7 schematically illustrates a logic diagram of an acquisition interaction component in accordance with an embodiment of the present disclosure;

FIG. 8 schematically illustrates a logic diagram for acquiring candidate transaction services according to an embodiment of the present disclosure;

FIG. 9 schematically illustrates a logic diagram for acquiring transaction services according to an embodiment of the present disclosure;

FIG. 10 schematically illustrates a process diagram for acquiring component services according to an embodiment of the disclosure;

FIG. 11 schematically illustrates a logic diagram of acquiring component services in accordance with an embodiment of the present disclosure;

FIG. 12 schematically illustrates a logic diagram for acquiring object services according to an embodiment of the present disclosure;

FIG. 13 schematically illustrates a block diagram of an Internet technology architecture construction apparatus according to an embodiment of the present disclosure; and

fig. 14 schematically illustrates a block diagram of an electronic device according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). The terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more features.

The embodiment of the disclosure provides an Internet technical architecture, a construction method, a construction device, electronic equipment and a medium thereof. The internet technology architecture includes interactive components, transaction services, component services, and object services. The interaction component comprises an interface, a navigation component, an input-output component and a calling relation between the interaction component and the transaction service. The transaction service realizes the business function by calling the component service and outputs the processing result of the business function to the interaction component, wherein one transaction service corresponds to one interaction action between the entity and the service. The component service is used to assemble the object service for the transaction service to call. The object service is used for encapsulating business rules to perform read operations and/or write operations on data related to the entity in the data set based on the business rules.

Fig. 1 schematically illustrates an application scenario of an internet technology architecture, a method for constructing the same, an apparatus, an electronic device, and a medium according to an embodiment of the present disclosure.

As shown in fig. 1, in the related art, there may be a difference between the service architecture and the IT architecture, for example, there is at least a partial architecture difference between the two, so that IT is inconvenient to accurately analyze service effects under the service architecture based on service data acquired by the IT architecture, and therefore, IT is necessary to construct a system for constructing a service architecture and an IT architecture that can be well coupled to an internet technology architecture.

According to the Internet technical architecture, the construction method, the device, the electronic equipment and the medium thereof, which are provided by the embodiment of the disclosure, the layout adjustment of the IT architecture is guided based on the modeling result of the business architecture, a more flexible IT service mode is provided, more accurate business influence analysis is realized, the online rhythm is developed more agilely, and the business development requirement of the future open ecology is met.

Fig. 2 schematically illustrates an exemplary system architecture to which an internet technology architecture, and methods, apparatuses, electronic devices, and media for constructing the same may be applied according to embodiments of the present disclosure. It should be noted that fig. 2 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.

As shown in fig. 2, the system architecture 200 according to this embodiment may include

terminal devices

201, 202, 203, a network 204, and a server 205. The network 204 may include a number of gateways, routers, hubs, network cables, etc. to provide a medium for communication links between the

terminal devices

201, 202, 203 and the server 205. The network 204 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can interact with other terminal devices and the server 205 through the network 204 using the

terminal devices

201, 202, 203 to receive or transmit information or the like, such as receiving a service request, transmitting a processing result, or the like. The

terminal devices

201, 202, 203 may be installed with various communication client applications, such as banking applications, government applications, monitoring applications, web browser applications, search applications, office applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

Terminal devices

201, 202, 203 include, but are not limited to, smartphones, virtual reality devices, augmented reality devices, remote cameras, tablets, laptop portable computers, and the like.

The server 205 may receive the request and process the request. For example, the server 205 may be a background management server, a server cluster, or the like. The background management server can analyze and process the received modeling request, information request, model management request and the like, and feed back processing results (such as requested information, processing results and the like) to the terminal equipment.

It should be noted that, the construction method provided by the embodiments of the present disclosure may be generally performed by the server 205 or the

terminal devices

201, 202, 203. Accordingly, the construction means provided by the embodiments of the present disclosure may be generally provided in the server 205 or the

terminal devices

201, 202, 203. The construction method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 205 and is capable of communicating with the

terminal devices

201, 202, 203 and/or the server 205.

It should be understood that the number of terminal devices, networks and servers is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Fig. 3 schematically illustrates a structural schematic diagram of an internet technology architecture according to an embodiment of the present disclosure.

The internet technology architecture may include: interactive component (UC), transaction service (ATS), component service (ACS), object service (BOS).

The interaction component comprises an interface, a navigation component, an input-output component and a calling relation between the interaction component and the transaction service. Specifically, from the task component and the use case of the service model, the interaction component describes the interaction process of completing a service function by a role and a physical application through an interface, navigation, an input and output component and a calling relationship between the interaction component and the transaction service.

The transaction service realizes business functions by calling component services and outputs processing results of the business functions to the interaction component, wherein one transaction service corresponds to one interaction action between one entity and the service. In particular, a transaction service is the ability to define the system's offerings from the user's perspective, corresponding to one role interacting with a physical application. The service function is realized through the dispatch component service, and the dispatch component service is an independent and internally consistent working unit.

The component service is used to assemble the object service for the transaction service to call. Specifically, the component service assembles object services and non-business related technical platform functions in the physical application, exposes services to the outside, and is used for transaction service call.

The object service is used to encapsulate business rules to read and/or write data associated with an entity in the data set based on the business rules. Specifically, the object service encapsulates business rules, operates business objects, decouples business logic and data access, and operates the database through the technical framework.

In one embodiment, the calling method between the interaction component, the transaction service, the component service, and the object service is as follows. Transaction services can only be called by the interaction component layer application, the transaction services call component services to realize business functions, and the interaction is forbidden between the transaction services. The component services can only be called by the transaction service to the object service, the component services call the object service to form an application, and the mutual call among the component services is forbidden. The object services can only be called by the component services, and the data set is operated through the technical framework, so that the mutual calling among the object services is forbidden. The transaction service may invoke a component service across applications, the component service prohibiting invocation of an object service across applications.

For example, to achieve service hierarchical decoupling, the service call link depth is reduced, and the call principle for each layer of service is as follows.

The transaction service (ATS) can only be invoked by the interactive component layer, which is responsible for defining the capabilities of the system to be provided externally from the user's perspective, and the scheduling component service (ACS) implements business functions.

The component service (ACS) can only be invoked by the transaction service (ATS), which is responsible for assembling the object service (BOS) within the application, forming an application providing business capabilities to other applications.

The object service (BOS) can only be invoked by the component service (ACS), which is responsible for providing specific processing power for business objects, encapsulating business rules, decoupling business logic and data access, and operating on databases through a technical framework.

The transaction service (ATS), the component service (ACS), and the object service (BOS) do not allow the same layer to call each other, the transaction service (ATS) may call the component service (ACS) across applications, and the component service (ACS) does not allow the object service (BOS) to be called across applications.

Fig. 4 schematically shows a structural schematic diagram of an internet technology architecture and a business architecture according to an embodiment of the present disclosure.

As shown in fig. 4, there is a one-to-one or one-to-many mapping relationship between the interaction component and the transaction service. There is a one-to-one or one-to-many mapping between transaction services and component services. There is a one-to-one or one-to-many mapping between component services and object services.

In order to facilitate understanding of the technical scheme of the present disclosure, a service architecture is briefly described.

The business architecture is constructed based on value streams and mainly comprises a business model, a entity model and a service model. The business model is specific to multiple dimensions, and may include an activity value chain (also called an activity model, as shown by the activity of the flow model in fig. 4), a task flow (also called a task model, as shown by the task group of the flow model in fig. 4), and an operation component (also called a component model, as shown by the task component of the flow model in fig. 4). N in fig. 4 is a positive integer greater than 0, where the values of n in fig. 4 may be the same or different and are used only to indicate a one-to-one or one-to-many relationship. For example, the value of n in the business case may be the same as or different from the value of n in the flow model.

The construction process of the service architecture is described below.

Firstly, dividing the service field according to a plurality of dimensions based on the value stream to respectively obtain a plurality of value chains aiming at the plurality of dimensions. The business mode of the commercial bank is analyzed, and the business fields are divided according to different value flows, so that the components of the business fields in various dimensions are conveniently obtained. For example, the division may be stepwise according to the dimensions of the activities, tasks, steps.

Specifically, the plurality of value chains for the plurality of dimensions includes: an active value chain (corresponding to an active model), a task flow (corresponding to a task model), and an operational component (corresponding to a component model), the active value chain comprising at least one task flow, the task flow comprising at least one operational component. Wherein the active value chain includes an active start point and an active end point, the active value chain being associated with a plurality of entities. The task flow corresponds to a business flow, the business flow corresponds to at least one product, and serves an entity. The operating component corresponds to an entity and a product.

In one embodiment, for business domains, corresponding business and business classifications may be categorized into management domains and product domains (made up of enterprise-level value chains) according to whether or not the customer is oriented. For value flows, a higher order value chain under each business domain. For the activity dimension, the method is based on event driving, results are numerous and have unique identification, a plurality of entities are involved to complete in cooperation, complete value delivery is achieved in the activity dimension, and clear starting points and end points exist. For the task dimension, which is performed by one entity, there is a role of responsibility division. For the step dimension, it is the implementation step that one entity performs a specific task.

The entities and the products required by the entities associated with each value chain are then obtained. The entity can be represented by the entity model, the data of the entity model can be stored in a database, and in actual use, the entity model can be thinned and dataized to obtain a C 'model, and the C' model can be operated by an object service.

In particular, entities and products required by the entities, such as financial-type products, associated with each value chain may be determined and obtained based on the business architecture.

Then, a business model, an entity model and a product model aiming at a plurality of dimensions are respectively constructed aiming at the value chain, the entity and the product of the plurality of dimensions, wherein a one-to-one or one-to-many mapping relationship exists between the entity and the entity model in the business field, and a one-to-one or one-to-many mapping relationship exists between the service and the service model in the business field. Each model can correspond to a file, so that a user can conveniently call, operate, update and the like from a server. Thus, the whole business architecture can utilize a plurality of models stored in a server to perform business operation and Internet technology architecture construction.

The business architecture construction method can lead the asset classification of the business architecture (such as business banking architecture) to be detailed and the information to be closely linked, and can clearly provide the view of the business architecture. The business architecture asset is linked with the IT architecture asset, the business architecture asset can correspond to the condition that the IT architecture asset falls to the ground, and the business architecture and the IT architecture are integrated.

The business architecture provided by the embodiment of the disclosure achieves obvious effects in the aspects of creating an intelligent system, creating important product services, simplifying business process services, subdividing customer services, intelligent accurate marketing, data information management, supporting operation analysis, optimizing performance assessment, perfecting system specifications and the like through engineering means such as top-level design of the business architecture, model construction, information system landing and the like, and provides strong support for improving benefit contribution, market competitiveness and customer satisfaction. In addition, the enterprise-level business architecture model is convenient to construct continuously, and an asset foundation for deep fusion of business and IT technology is built. The business architecture modeling work in the business field is convenient for the fields to make business top layer planning, business architecture asset construction and IT accepting planning under the strong support of business departments, and based on business architecture modeling achievements, the information system is guided to apply layout adjustment, a more flexible IT service mode is provided, more accurate business influence analysis and more agile research and development online rhythm are realized, and the business development requirement of future open ecology is met.

The IT architecture provided by the embodiment of the disclosure inherits an IT service model of a business architecture model and a design method thereof. Under the guidance of enterprise-level business architecture, IT service is designed through a systematic method, and a corresponding service calling principle is matched, so that an IT service model of an inherited business architecture model is formed, service design standardization is effectively improved, service layering decoupling is realized, and service calling link depth is reduced. Under the guidance of an enterprise-level business architecture, an enterprise-level business model is designed through a systematic method, the design of all-line reusable components is guided, the reusable components are identified, and the level of all-line componentization is improved.

Another aspect of the present disclosure provides an internet technology architecture construction method. Fig. 5 schematically shows a flowchart of an internet technology architecture construction method according to an embodiment of the present disclosure.

As shown in fig. 5, the internet technology architecture construction method may include operations S501 to S509.

In operation S501, an interaction component (UC) is obtained based on an activity model of a business architecture, where the business architecture may include an entity model, an activity model, a task model, and a component model, where the activity model, the task model, and the component model provide services for entities corresponding to the entity model, a first mapping relationship between the activity model and the task model exists, and a second mapping relationship between the task model and the component model exists. Reference may be made to the above for service architecture, and no further description is given here.

Fig. 6 schematically illustrates a logic diagram of an internet technology architecture construction method according to an embodiment of the present disclosure.

As shown in fig. 6, the inputs to the build method include business use cases (for the active models in the business architecture), process models (for the task models and component models in the business architecture), and entity models. After the candidate service identification and service inventory validation process, the service components may be determined. The IT architecture can then be built up step by step using the way the service components are assembled.

Fig. 7 schematically illustrates a logic diagram of a get interaction component according to an embodiment of the disclosure.

As shown in fig. 7, specifically, two phases may be included: a validation input stage and an identification UC stage.

In the stage of identifying UC, the service requirement is provided in the form of task component and service use case, and the identification of UC is inherited from the description and definition of user interface and interaction component in the service use case. The UC design is used to describe the interaction processes supported by the application. The UC should generally include all information about related application functions, and the UC design content is future incorporated into a management and control system for unified management, and the principle shown below is followed.

a. The UC number should be unique within the system. And identifying all interfaces and navigation relations of the UC from the service use cases, and naming each interface according to the interface naming standards of the enterprise.

b. And displaying the interface navigation relationship in a graphical mode. The direction of the jump of the interface is indicated by a directional arrow. The arrow position is at the function button that is triggered.

c. The interface field (interface input/output information definition) should follow the information standard.

d. The input information is business original information as much as possible, for example, the information provided by the user is only name and certificate number, and the interface should not require inputting the customer number.

e. For those that do not involve a user interface, timing/conditional triggers, it is temporarily deemed unnecessary to write the UC design section.

f. UCs are typically used to describe a set of interface interactions for a channel, and if the interfaces and interface interactions for multiple channels are the same (e.g., some same function in multiple mobile applications (apps)), then they may be incorporated into a UC.

g. A UC belongs exclusively to an external interactive logical application and exclusively to a physical application.

In operation S503, the business architecture-based task model and interaction component acquire a transaction service.

In operation S505, a component service is acquired based on the component model of the business architecture and the transaction service.

In operation S507, object services are acquired based on the business architecture' S entity model and component services, wherein one candidate object service relates to a rule and business logic of one entity.

In operation S509, the interactive component, the transaction service, the component service, and the object service are packaged based on the first mapping relationship and the second mapping relationship.

In one embodiment, the business architecture based task model and interaction component acquisition transaction services may include the following operations.

Firstly, a task model and an interaction component based on a business architecture acquire candidate transaction services, wherein one human-computer interaction in the interaction component corresponds to one candidate transaction service.

Then, a plurality of candidate transaction services with the same business function are processed to obtain transaction services, wherein a one-to-one or one-to-many mapping relationship exists between the interaction component and the transaction services.

As shown in FIG. 7, an optimized business case description may be determined based on the activity model and channel defined cases, and then user interactions (i.e., interaction components) are determined based on the optimized business case.

Fig. 8 schematically illustrates a logic diagram for acquiring a candidate transaction service according to an embodiment of the present disclosure.

As shown in fig. 8, in combination with the division and the functional description of the task group (task model of the business architecture) in the flow model, each man-machine interaction process in UC is identified as a candidate transaction service (man-machine interaction refers to interaction between an interface and a background, and may not include operations on the interface), and the task group implemented by non-manual operation is defined as a transaction service.

Fig. 9 schematically illustrates a logic diagram for acquiring transaction services according to an embodiment of the present disclosure.

As shown in fig. 9, when the transaction service is extracted based on all transaction services identified by the business use case and the task group, firstly, the transaction service list of the existing IT architecture is queried, and whether the existing transaction service with the same or similar function exists or not is identified through names, function descriptions, ranges and the like, if the existing transaction service is similar, the existing transaction service implementation is suggested to be changed. CPCP in fig. 9 represents a client-product-channel-platform model.

Transaction services are the ability to define the system's offerings from the user's perspective, corresponding to one character interacting with the system. The service function is realized through the dispatch component service, and the dispatch component service is an independent and internally consistent working unit.

The transaction service may include the following: summary, english name, chinese name, definition, scope, corresponding task(s), implementation notes, transaction mapping (corresponding to existing IT architecture), service input output, error code, business rules (describing call and processing logic for component service ACS).

Wherein, for the input and output information of transaction service, if the information is identified from UC, the requirement of interface input and output information in UC should be satisfied. If the trigger is the access trigger of the partner, the UC is required to be identified and defined for the scene with a designated interface (such as the interface of the enterprise), otherwise, only the ATS is required to be identified and defined. The business rules of the transaction service mainly describe the scheduling of the component service, and the transaction service realizes the business delivery by calling and combining the component service. The name and value fields of the input/output field, such as corresponding to the C' entity attribute, should be consistent with the entity attribute.

In another embodiment, the business architecture-based component model and transaction service acquisition component service may include the following operations.

First, a candidate component service is obtained based on a component model of a business architecture and a transaction service.

Then, combining a plurality of candidate component services with the same application function to obtain a component service, wherein the transaction service and the component service are in one-to-one or one-to-many mapping relation.

Fig. 10 schematically illustrates a process diagram of acquiring component services according to an embodiment of the present disclosure.

As shown in fig. 10, a process of confirming data of a service operation, a process of confirming a physical application of the data, and a process of identifying a component service may be included. Wherein the inputs of the process of validating data of a service operation include use case rules, a transaction service list and a task component list, and the outputs include standardized processing rules. The input of the process of confirming the physical application of the data is the output of the process of confirming the data of the service operation, and the output thereof is the correspondence relationship between the processing rule and the physical application. The input to the process of identifying component services includes standardized processing rules that are output as a component service manifest.

Fig. 11 schematically illustrates a logic diagram of acquiring component services according to an embodiment of the present disclosure.

As shown in fig. 11, the process of acquiring the transaction service may include an enumerating transaction service process and a merging transaction service process. In the process of listing transaction services, task components in the flow model are analyzed, and candidate component services are identified by combining the splitting of the business components to the physical applications, business objects operated by the task components and business processing of the ATS. And determining ACS service attribution application through the primary responsibility business object and the secondary responsibility business object marked in the flow model, wherein the service corresponding to one task component can be attributed to a plurality of applications. It is not suggested to split component services of similar functionality by different channels, partners.

The enumerating transaction service process may have the principles shown below. The primary responsibility business object and the secondary responsibility business object operating according to one task component may correspond to physical applications, such as deposit applications and media applications, to which different business components correspond. But the same component service may not provide services across business components. The component service can operate all object services in the application, the object service component service which can not call other applications can not reversely call a transaction service, one component service must belong to a physical platform, and the services belonging to different physical applications are identified as different component services.

In the merging transaction service stage, for all the identified candidate component services, all the candidate component services which are processed by the business logic are merged into one component service, and the component service needs to follow the component service calling principle with definite application architecture.

The method comprises the steps of assembling object services and non-business related technical platform functions in an internal logic application, completing processing logic crossing different object services, exposing services to the outside, and calling transaction services, wherein component services can comprise the following contents: summary, english name, chinese name, definition, scope, corresponding task component(s), implementation notes, service input and output, error code, business rules (describing calls to BOS and own processing logic).

Fig. 12 schematically illustrates a logic diagram of acquiring an object service according to an embodiment of the present disclosure. As shown in fig. 12, regarding the determination of the object service, two processes may be included: the process of collecting steps and the process of identifying business object services.

For rules and business logic which only relate to processing of one business object, the rules and the business logic can be identified as a candidate object service, the object service can not provide services for external exposure and can only be called by component services, and the identification principle can be as follows.

a. Only use case rules that operate business entities are enumerated.

b. The same operations for the same business object are refined in each business rule.

c. The object service implements a minimum unit of business logic.

d. All object services identified must support all state transitions and queries of the business object.

e. The object service can only operate business entities within the present business object.

f. The object service cannot invoke any other service.

Among other things, the object service may include the following: object service overview, module chinese name, module english name, definition, scope, input/output, error code, business rule.

In one embodiment, the object service has a component service with a calling relationship. The component services have transaction services with calling relations, and the same component service is forbidden to be called by the same transaction service for a plurality of times. Transaction services corresponding to the activity model are stored in a transaction service list. TTD in fig. 12 is an abbreviation of task component, and corresponds to a task model in a business architecture.

In particular, all object services must have component service calls. All component services must have transaction service calls and the same component service should not be called multiple times by the same transaction service. The transaction services required for all use cases must be present in the transaction service list. Transaction services corresponding to tasks that are purely system-implemented (functions that do not require manual implementation) must exist in the transaction service inventory.

According to the IT architecture construction method provided by the embodiment of the disclosure, under the guidance of the enterprise-level business architecture, the IT service is designed through the systematic method, and the IT service model inheriting the business architecture model is formed by matching with the corresponding service calling principle, so that the standardization of service design is effectively improved, service layered decoupling (decoupling of a database and a service and decoupling of a component service and a transaction service) is realized, and the service calling link depth is reduced (the aim of prohibiting multiple calls of the same service and prohibiting the same-level internal calling can be realized).

An aspect of the present disclosure provides an internet technology architecture construction apparatus, and fig. 13 schematically shows a block diagram of the internet technology architecture construction apparatus according to an embodiment of the present disclosure.

As shown in fig. 13, the illustrated internet technology architecture construction apparatus 1300 may include: an interaction component determination module 1310, a transaction service acquisition module 1320, a component service acquisition module 1330, an object service acquisition module 1340, and a build module 1350.

The interaction component determining module 1310 is configured to obtain an interaction component based on an activity model of a business architecture, where the business architecture includes an entity model, an activity model, a task model and a component model, the activity model, the task model and the component model provide services for entities corresponding to the entity model, a one-to-one or one-to-many first mapping relationship exists between the activity model and the task model, and a one-to-one or one-to-many second mapping relationship exists between the task model and the component model.

The transaction service acquisition module 1320 is configured to acquire transaction services based on the task model and the interaction component of the business architecture.

The component service acquisition module 1330 is configured to acquire component services based on the component model of the business architecture and the transaction service.

The object service acquisition module 1340 is configured to acquire object services based on entity models and component services of business architecture, where one candidate object service relates to rules and business logic of one entity.

The building module 1350 is configured to encapsulate the interaction component, the transaction service, the component service, and the object service based on the first mapping relationship and the second mapping relationship.

Optionally, the transaction service acquisition module 1320 may include: a candidate transaction service acquisition unit and a transaction service acquisition unit.

The candidate transaction service acquisition unit is used for acquiring candidate transaction services based on a task model of a business architecture and an interaction component, wherein one man-machine interaction in the interaction component corresponds to one candidate transaction service.

The transaction service acquisition unit is used for processing a plurality of candidate transaction services with the same business function to obtain transaction services, wherein a one-to-one or one-to-many mapping relation exists between the interaction component and the transaction services.

Further, the component service acquisition module 1330 may include a candidate component service acquisition unit and a component service acquisition unit.

The candidate component service acquisition unit is used for acquiring candidate component services based on the component model of the business architecture and the transaction service.

The component service obtaining unit is used for merging a plurality of candidate component services with the same application function to obtain the component service, wherein the transaction service and the component service are in one-to-one or one-to-many mapping relation.

It should be noted that, the implementation manner, the solved technical problems, the realized functions and the obtained technical effects of each module/unit and the like in the apparatus portion embodiment are the same as or similar to the implementation manner, the solved technical problems, the realized functions and the obtained technical effects of each corresponding step in the method portion embodiment, and are not described in detail herein.

Any number of the modules, units, or at least some of the functionality of any number of the modules, units, or units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or in hardware or firmware in any other reasonable manner of integrating or packaging the circuits, or in any one of or in any suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, units according to embodiments of the disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.

For example, any of the interaction component determination module 1310, the transaction service acquisition module 1320, the component service acquisition module 1330, the object service acquisition module 1340, and the build module 1350 may be combined into one module to be implemented, or any of the modules may be split into multiple modules. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the present disclosure, at least one of the interactive component determination module 1310, the transaction service acquisition module 1320, the component service acquisition module 1330, the object service acquisition module 1340, and the build module 1350 may be implemented, at least in part, as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or as hardware or firmware in any other reasonable manner of integrating or packaging the circuitry, or as any one of or a suitable combination of any of the three. Alternatively, at least one of the interaction component determination module 1310, the transaction service acquisition module 1320, the component service acquisition module 1330, the object service acquisition module 1340, and the build module 1350 may be at least partially implemented as computer program modules that, when executed, perform the corresponding functions.

Fig. 14 schematically illustrates a block diagram of an electronic device according to an embodiment of the disclosure. The electronic device shown in fig. 14 is merely an example, and should not impose any limitations on the functionality and scope of use of embodiments of the present disclosure.

As shown in fig. 14, an electronic device 1400 according to an embodiment of the present disclosure includes a processor 1401 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1402 or a program loaded from a storage section 1408 into a Random Access Memory (RAM) 1403. The processor 1401 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 1401 may also include on-board memory for caching purposes. The processor 1401 may include a single processing unit or a plurality of processing units for performing different actions of the method flows according to embodiments of the present disclosure.

In the RAM 1403, various programs and data necessary for the operation of the electronic device 1400 are stored. The processor 1401, ROM 1402, and RAM 1403 are communicatively connected to each other through a bus 1404. The processor 1401 performs various operations of the method flow according to the embodiment of the present disclosure by executing programs in the ROM 1402 and/or the RAM 1403. Note that the program may be stored in one or more memories other than the ROM 1402 and the RAM 1403. The processor 1401 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in one or more memories.

According to an embodiment of the disclosure, the electronic device 1400 may also include an input/output (I/O) interface 1405, the input/output (I/O) interface 1405 also being connected to the bus 1404. Electronic device 1400 may also include one or more of the following components connected to I/O interface 1405: an input section 1406 including a keyboard, a mouse, and the like; an output portion 1407 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 1408 including a hard disk or the like; and a communication section 1409 including a network interface card such as a LAN card, a modem, and the like. The communication section 1409 performs communication processing via a network such as the internet. The drive 1410 is also connected to the I/O interface 1405 as needed. Removable media 1411, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memory, and the like, is installed as needed on drive 1410 so that a computer program read therefrom is installed as needed into storage portion 1408.

According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from the network through the communication portion 1409, and/or be mounted from removable media 1411. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1401. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 1402 and/or RAM1403 described above and/or one or more memories other than ROM 1402 and RAM 1403.

Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. These examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

1. An internet technology architecture construction method, comprising:

an interaction component is obtained based on an activity model of a business architecture, wherein the business architecture comprises an entity model, an activity model, a task model and a component model, the activity model, the task model and the component model provide services for an entity corresponding to the entity model, a first mapping relation of one-to-one or one-to-many exists between the activity model and the task model, and a second mapping relation of one-to-one or one-to-many exists between the task model and the component model;

Acquiring transaction service based on the task model of the business architecture and the interaction component;

acquiring component services based on the component model of the business architecture and the transaction service;

acquiring object services based on the entity model of the business architecture and the component services, wherein one candidate object service relates to rules and business logic of one entity; and

and packaging the interaction component, the transaction service, the component service and the object service based on the first mapping relation and the second mapping relation.

2. The internet technology architecture construction method of claim 1, wherein the business architecture-based task model and the interaction component acquiring transaction services comprises:

acquiring candidate transaction services based on a task model of a business architecture and the interaction component, wherein one time of human-computer interaction in the interaction component corresponds to one candidate transaction service; and

and processing a plurality of candidate transaction services with the same business function to obtain transaction services, wherein a one-to-one or one-to-many mapping relation exists between the interaction component and the transaction services.

3. The internet technology architecture construction method of claim 1, wherein the business architecture-based component model and the transaction service acquisition component service comprise:

Acquiring candidate component services based on the component model of the business architecture and the transaction service; and

and merging a plurality of candidate component services with the same application function to obtain a component service, wherein the transaction service and the component service are in one-to-one or one-to-many mapping relation.

4. The internet technology architecture construction method according to claim 1, wherein:

the object service has a component service with a calling relationship;

the component services have transaction services with calling relations, and the same component service is forbidden to be called for multiple times by the same transaction service; and

and the transaction service corresponding to the activity model is stored in a transaction service list.

5. An internet technology architecture construction apparatus, comprising:

the interaction component determining module is used for acquiring an interaction component based on an activity model of a business architecture, wherein the business architecture comprises an entity model, an activity model, a task model and a component model, the activity model, the task model and the component model provide services for an entity corresponding to the entity model, a first mapping relation of one-to-one or one-to-many exists between the activity model and the task model, and a second mapping relation of one-to-one or one-to-many exists between the task model and the component model;

The transaction service acquisition module is used for acquiring transaction service based on the task model of the business architecture and the interaction component;

the component service acquisition module is used for acquiring component services based on the component model of the business architecture and the transaction service;

the object service acquisition module is used for acquiring object services based on the entity model of the business architecture and the component services, wherein one candidate object service relates to rules and business logic of one entity; and

and the construction module is used for packaging the interaction component, the transaction service, the component service and the object service based on the first mapping relation and the second mapping relation.

6. The internet technology architecture construction device of claim 5, wherein the transaction service acquisition module comprises:

the candidate transaction service acquisition unit is used for acquiring candidate transaction services based on a task model of a business architecture and the interaction component, wherein one time of human-computer interaction in the interaction component corresponds to one candidate transaction service; and

and the transaction service acquisition unit is used for processing a plurality of candidate transaction services with the same business function to obtain transaction services, wherein a one-to-one or one-to-many mapping relation exists between the interaction component and the transaction services.

7. The internet technology architecture construction device of claim 5, wherein the component service acquisition module comprises:

a candidate component service acquisition unit for acquiring a candidate component service based on the component model of the business architecture and the transaction service; and

and the component service acquisition unit is used for merging a plurality of candidate component services with the same application function to obtain the component service, wherein the transaction service and the component service are in one-to-one or one-to-many mapping relation.

8. An electronic device, comprising:

one or more processors;

storage means for storing executable instructions which when executed by the processor implement the method according to any one of claims 1 to 4.

9. A computer readable storage medium having stored thereon executable instructions which when executed by a processor implement the method according to any of claims 1 to 4.