KR100934879B1 - Modeling method of system program by using use case and storage media thereof - Google Patents

Abstract

The present invention relates to a method for modeling a new system program using a use case (USE CASE) consisting of a task program (TASK) program of the functional unit developed in advance, and a recording medium thereof, in particular A method of modeling a system program using a use case, comprising: mapping a plurality of tasks included in a use case to an independent task set; and a method of modeling a system program using a use case. The method includes a case in which a part of a plurality of task sets included in a case is a duplicate task set or a case in which an existing task set is used as a part of the task, and divided into services, and a method of modeling a system program using a use case. Is included in the use case If the task is a set of complex tasks, it is characterized by a configuration that includes setting up as a complex service. The system program of the selected function can be easily and quickly developed, and use cases are used by non-skilled workers to make system design and development simple and fast. It is effective.

 Use cases, tasks, system programs,

Description

MODELING METHOD OF SYSTEM PROGRAM BY USING USE CASE AND STORAGE MEDIA THEREOF

The present invention is to develop a system program for a new purpose using a task program of a functional unit developed in the existing, in particular, each task group is divided into a use case to apply to a new development program use case to reduce the development time It relates to a modeling method of a system program used and a recording medium thereof.

Humans have researched, developed, and developed many tools and devices that enable them to achieve maximum action and effectiveness with little power and effort to do all the functions of the body from the beginning.

For example, tools such as hammers and saws for hand functions, vehicle devices for bicycles, cars, airplanes and ships for foot functions, microphones and amplifiers for mouth functions, communication devices for ear functions, etc. This has been developed, and computers and the like are being developed and developed to assist the function of the head.

The computer is a hardware (HARD-WARE: H / W) consisting mainly of a mechanical device or an electronic circuit and the software that controls, monitors and operates the hardware (H / W) to be driven in a manner desired by the user. It is divided into (SOFT-WARE: S / W).

The software is also called a program, and the software language used by each worker is generally different, and it takes a lot of time and money until the development is completed. It could not be reused for programs that use the language.

For example, early programs used machine language (assembly), and the high-level languages BASIC, COBLE, FORTRAN, and C appeared to make writing programs easier and easier. Each language as described above has a different way of approaching a problem, and in particular, early languages have technical problems such as technical complexity and difficulty in developing large programs. Each programming language is called a component.

In the program, a unit having one designated function is called a task program, and one or more task programs are used to complete execution of a selected function, and the use case is a service program. This is called a system program in which one or more service programs gather to perform a large-scale selected function.

Hereinafter, a service program will be referred to as a service, a task program will be referred to as a task, a system program will be referred to as a system, and mixed for the purpose of understanding the technology.

In the prior art, in order to solve the problem that the program cannot be reused as described above, in the case of a program made of a language defined and classified as a structural language such as machine language, the control structure, code block, recursive call, and local variables are supported. Some problems were solved by using a subprogram called function.

However, since each language of the related art solves a problem by focusing on a processing method rather than data, a problem that cannot be solved in an intuitive manner still remains.

In the case of a program created in a conventional object-oriented language, an intuitive method called an object is introduced, and programming languages such as C ++, JAVA, and C # are included.

It is necessary to develop a component development method (COMPONENT BASED DEVELOPMENT: CBD) that excludes inheritance that minimizes polymorphism and wave effects of a program made by the object-oriented language and reuses it in a binary form through a clearly defined interface.

The CBD uses software to solve the creation, integration and reuse of each COMPONENT program.

As an example of such a prior art, the development stages of a structural programming object and an object oriented programming language are shown in detail in FIG.

Creating, distributing, and managing a program developed by multiple vendors in different places using a different programming language on a network is called a distributed component or a distributed program or a distributed object (hereinafter referred to as a distributed component).

The distributed components are individually and independently executed in a distributed environment where platforms, operating systems, and software are different from each other, and object-oriented languages such as CORBA, COM +, and EJB are used for development. .

An ideal distributed environment should have no restrictions on the use of distributed components by users. In this case, the distributed computer environment should be: first, providing services regardless of the programming language used for development, and secondly, are platform independent components. Third, the conditions must be easy and simple to use and maintain.

However, according to the prior art as described above, a distributed component consisting of CORBA, COM +, EJB, etc. has a problem that is not independent in its framework (FRAME WORK).

To solve the problem of such distributed components is a service-oriented architecture (SOA).

The SOA was first introduced by the GARTNER group in 1996 and is a concept that serves as a standard for EBXML and Web services. In other words, a web service is a set of interfaces using XML-based messages and a software component that realizes the concept of SOA.

Referring to FIG. 2, a background of recognizing the XML-based web service of the SOA will be described. For example, a structure and a standard for generating, distributing, and managing distributed program objects in a communication network (NETWORK) such as the Internet (INTERNET) are described. Distributed by (CORBA: COMMON OBJECT REQUEST BROKER ARCHITECTURE) and a decompression (DCOM: DISTRIBUTED COMPONENT OBJECT MODEL) of a program interface where a client program object in the network requests a service from a server program object of another computer. Many technologies based on the object concept have been developed and applied.

Distributed object technologies such as COVA, DECOM, etc. are technically immature, have no open standard, and have not been activated because there is no cooperation among VENDER.

Application of the distributed object to XML-based web services is a SOA technology, and the SOA technology defines a method for building a software infrastructure (INFRA), and by activating the web service to which the SOA is applied, Importance is being recognized. This is a service-oriented architecture or application (SOA: SERVICE ORIENTED ARCHITECTURE or APPLICATION).

However, many service methods that have been defined and proposed so far do not present specific procedures and criteria of service identification clearly, and there are many difficult problems until they are applied to actual development.

The present invention provides a method for modeling a system program using a use case that uses a use case defined as a result of program development as an element of a service-oriented means in modeling an SOA-based service, and a recording medium thereof. For that purpose.

In addition, an object of the present invention is to provide a method of modeling a system program using a use case using a use case element in service division, a service architecture template, and service derivation from a viewpoint of implementing a program system, and a recording medium thereof.

The present invention devised to achieve the above object, in the modeling method of a system program using a use case, if the plurality of tasks included in the use case is a set of independent tasks comprising a configuration comprising mapping to one service present.

Preferably, the independent tasks are not dependent on or overlap with task sets of other use cases.

In order to achieve the above object, the present invention provides a method of modeling a system program using a use case, wherein a part of a plurality of task sets included in the use case is a duplicate task set or an existing task set as a part of a task. In this paper, a configuration including dividing the case into separate services is presented.

Preferably, the duplicated task is a task set that is used in a task set of another use case while being independently operated in the use case.

In addition, the existing task is characterized in that the task set independently developed while acting independently in the use case.

The present invention devised in order to achieve the above object, in the modeling method of a system program using a use case, if the plurality of tasks included in the use case is a set of complex tasks, including a configuration comprising setting to a composite service do.

Preferably, the complex task includes at least two of a task set duplicated in a plurality of task sets included in a use case and a task set independent of an existing task set.

In order to achieve the above object, the present invention provides a process for mapping a service to a service if a plurality of tasks included in the use case are independent task sets in a recording medium recording a method of modeling a system program using a use case. A recording medium recording a method of modeling a system program using a use case including a is provided.

In order to achieve the above object, the present invention provides a recording medium recording a method of modeling a system program using a use case, wherein a part of a plurality of task sets included in the use case is a duplicate task set or an existing task set. The present invention provides a recording medium that records a method of modeling a system program using a use case including a process of dividing a case of using a as a part of a task and dividing the service into a service.

In order to achieve the above object, the present invention provides a recording medium that records a method of modeling a system program using a use case, wherein the process of setting up a complex service when a plurality of tasks included in the use case is a set of complex tasks. We present a recording medium that records the modeling method of a system program using an included use case.

The present invention having the configuration described above utilizes the use case (USE CASE) as an element of the service-oriented means, there is an industrial use effect to easily and quickly develop a system program of the selected function.

In addition, the present invention of the configuration described above uses a use case element for service division, service architecture template, service derivation, there is a convenient effect for the non-skilled person to use the system design and development simple and fast.

Hereinafter, a method of modeling a system program using a use case and a preferred embodiment of a recording medium thereof according to the present invention having the above configuration will be described in detail with reference to the accompanying drawings.

Example

3 is a logical explanatory diagram of an SOA service, according to an example of the present invention, FIG. 4 is a diagram illustrating a type of SOA service, according to an example of the present invention, and FIG. According to an example of the invention is a diagram illustrating the components of the SOA service, Figure 6 is a diagram illustrating the SOMA method of the present invention for explaining the present invention, Figure 7 is a diagram illustrating the SOA architecture of IBM for the description of the present invention 8 is an explanatory diagram of an analysis of a use case by an example of the present invention, and FIG. 9 is an explanatory diagram of a modeling method of a system program using a use case by an example of the present invention, and FIG. 10 is an example of the present invention. It is explanatory drawing of the modeling method of the system program using a use case, and FIG. 11 shows the system using a use case by an example of this invention. 12 is an explanatory diagram of a modeling method of a program, and FIG. 12 is an explanatory diagram of a system program classified into use cases according to an example of the present invention, and FIG. 13 is an illustration diagram of identifying and displaying each use case classified in FIG. 12. 14 is a flowchart illustrating a complex setting method of a use case according to an example of the present invention.

In describing an example of the present invention, drawings and descriptions of well-known technical contents that are not directly related to the present invention are omitted, and thus the present invention is clearly communicated without obscuring the gist of the present invention.

Referring to FIG. 9, a method of modeling a system program using a use case according to an example of the present invention will be described. In the method of modeling a system program using a use case, a plurality of tasks included in the use case are different from each other. If it is a set of independent tasks that do not depend or overlap with the task set of the case, it is a configuration that maps to one service.

Referring to FIG. 10, a method of modeling a system program using a use case according to an example of the present invention will be described. In the method of modeling a system program using a use case, the method is included in the use case. Some of a plurality of task sets (TASK) are duplicated task sets that are independently used in the use case of the other use cases and are duplicated in the task set of another use case, or existing tasks developed independently while acting independently in the use case It is a structure that separates the case of using a set as a task (TASK) and divides it into services.

Referring to FIG. 11, a method of modeling a system program using a use case according to an example of the present invention will be described. In the method of modeling a system program using a use case, a number of tasks included in the use case include the use case. If a plurality of task sets included in the task set is a duplicate task set, the other part is an existing task set, and the other part is a set of complex tasks that are independent task sets, the configuration is set as a composite service.

The SOA to which the present invention is applied should be able to call and use a service program required in all environments in a standardized manner, and the mechanism for invoking the service requires a platform-independent characteristic based on widely adopted standards. . The service consists of one or more tasks (TASK).

In addition, when using the called service, it is a weak coupling method that does not need to know the format structure or information of the internal data data beforehand, and stores definitions and location information of multiple called services in a single repository. Location transparency is supported by registering and invoking regardless of location through information in the repository.

Referring to FIG. 3, the SOA service is logically described. The SOA service includes a service interface (INTERFACE) and a service implementation (IMPLEMENTATION).

The SOA service is typically a business function implemented in software and exposed to the outside through a well-organized interface. The service interface is operations called by the service requester, and the service specification is all interfaces called by the service requester. That is, the SOA is an SOA that exposes a service to the outside and includes an interface of a service using an operator called by a service requester, a business function implemented by software, and an service implementation (IMPLEMENTATION) exposed to the outside as an interface. Services make it possible to interface with any program.

Referring to FIG. 4, a type of SOA service is classified into a SIMPLE service and a COMPOSITE service according to a usage method.

The complex service is a service configured to operate a specific business process by combining simple services. For example, a simple service is composed of a service 'A', or a service 'A' or a service '1', but a complex service includes a service 'A', a service 'A', and a service '1'. .

Referring to FIG. 5, a component of an SOA service is described. A service requester (CLIENT) using one or more services provided by a service provider (PROVIDER) and a value inputted by the service requester when a service requester is called, It provides the result and stores and retrieves the service provider (PROVIDER), which becomes the service user using the service provider or another service provider, and the technical information (DESCRIPTION) about the service.

A service registry (REGISTRY) is included to register a service provided by the service provider and to allow a service requester to search for and call a desired service. There is a BIND relationship between the service provider and the service requester, a FIND relationship between the service requester and the service registry, and a PUBLISH relationship between the service provider and the service registry.

In general, the concern of a company that has built a large-scale IT (INFORMATION TECHNOLOGY) system is that it is expensive, but limited people are using it for limited purposes. Except for special information for which security is requested, general information is shared by all members of the organization in terms of efficient operation of the information.

For example, in order to actively manage the performance of the members of the organization, when introducing a CIM (CORPORATE INCENTIVE MANAGEMENT) system that uses some of the identity information, pay for the introduction of the CIM system, and the linkage with the identity information system A separate connector program must be developed for this purpose. That is, it is expensive to introduce the CIM system and develop the connector program, and this process is repeated.

The SOA of the present invention simply solves at low cost in this case, and converts the employee information system into a service that can be provided externally, that is, interfaces with standard XML such as WSDL (WEB SERVICE DESCRIPTION LANGUAGE) In addition, it is only necessary to develop a signal for inputting the WSDL interface to the employee information system. This development part is easily solved by using a web application such as JSP / SERVLET or ASP.

The WSDL describes the service provided by the system in a standardized manner in detail, and thus can be easily used by understanding the standard.

The use of WEB SERVICE in the SOA is to simplify the interworking and minimize the cost. For example, when using a program such as J2EE, NET, CORBA, etc., that is, develop all interfaces as JAVA interfaces, RMI (REMOTE METHOD) INVOCATION), if you develop a new system program, you have to redevelop it for communication with JAVA.

In support of the SOA, SERVICE ORIENTED MODELING AND ARCHITECTURE (SOMA), developed by IBM, proposes three phases: IDENTIFICATION, SPECIFICATION, and REALIZATION.

Referring to FIG. 6, the IBM SOMA method is described. In the business process, a subsystem is disassembled in a top-down manner based on a business domain (BUSINESS DOMAIN) and an existing system is analyzed. A service having an acceptable function is identified by a BOTTOM-UP method, and a target service modeling is performed to find other services not identified by the top-down and bat-up method.

In this way, the BUSINESS PROCESS function is identified as a LARGE-GRAINED SERVICE, and the SMALLER-GRAINED service is identified based on the existing functions. do. That is, IDENTIFICATION is identified by domain decomposition, target service modeling, and existing system analysis.

After identification as above, component flow standardization by sub-system analysis (SUBSYSTEM ANALYSIS), information standardization by component specification (COMPONENT SPECIFICATION), service standardization (SERVICE SPECIFICATION) SPECIFICATION is specified by SERVICE FLOW SPECIFICATION and MESSAGE & EVENT SPECIFICATION.

After the standardization or specification processing as described above, the service is allocated to each component through service determination determination and the components are layered.

In other words, it determines the development of adapters and wrappers by bringing out the functions used by external business partners or users.

The wrapper (WRAPPERS) is a program that wraps the existing program for use in SOA, and the adapter (ADAPTERS) is to allow each program to send and receive data information (INFORMATION) of each other in the matching (MATCHING) state It is a program.

Since the definition or identification of the service depends on the service architecture representing the logical configuration of the service set, the establishment of the service architecture is an important element for service identification, and the architecture provided by IBM is PSVAUI (PROVIDES A SERVICE-ORIENTED VIEW ON). APPLICATIONS & THE UNDERLYING INFRASTRUCTURE). The architecture is divided into nine types of services, from infrastructure services to business innovation (BUSINESS INNOVATION) and optimization services (OPTIMIZATION SERVICE). Each service communicates through an ESPR (ENTERPRISE SERVICE BUS). Likewise, IBM's SOA architecture (ARCHITECTURE) is shown.

The above service architecture or service modeling method is not specific, and it is difficult to find the service commonality and role commonality of each layer due to the fact that it is closely related to each vendor's solution. Product development needs to be considered.

In order to model the service, it is necessary to define and distinguish a service architecture representing a logical configuration of a service set. In the present invention, the service architecture and the component architecture are limited to the application architecture. The service architecture consists of a business service layer that combines component services or composition services according to the business process logic, a component service layer that provides component services, which is the core concept of SOA, and an infrastructure service layer that provides infrastructure to each layer. .

The above services are considered by dividing the layers of the architecture, and the services targeted for identification and development among the three layers of the architecture are services placed in the business service layer and the component service layer. It is divided into (COMPOSITION SERVICE) and component service (COMPONENT SERVICE).

In other words, it is a service placed in the business service layer. It defines a composition service as a service that integrates the functions of many component services according to business process logic and corresponds to the business functions or activities that can be recognized in the component service layer. It is called a component service, which is a unit service.It is a service that is newly created according to an implementation form, a service that uses a web service existing inside or outside, and an adapter technology that does not provide a web service interface. It is divided into three types of wrapped services.

According to the present invention, a method of modeling a service as a result of being applied to a plurality of system programs is described. A plurality of use cases defined as UML (UNIFIED MODELING LANGUAGE) is used to control the interaction between the user and the system. It utilizes the features and characteristics that need to interact between the user and the system. In other words, the use case is a goal of a system that must be implemented, and it is easy to identify a service using this.

Referring to FIG. 8, the analysis of the use case is described. When there is a request or request for development of a system program, the use case required for system configuration is modeled, the use case is specified, and the use case is used. ANALYSIS the case to develop a system program.

At this time, the analysis of the use case proceeds a plurality of use case analysis at the same time.

The use case analysis includes a 1: 1 mapping method, a partitioning method, and a compounding method.

Referring to FIG. 9, an example of a 1: 1 mapping method according to an exemplary embodiment of the present invention is a method of developing one service in one use case.

In the 1: 1 mapping method, when a plurality of tasks 110 constituting a set constitutes one use case 100 and is independent of each other without dependency or overlap, the service is divided into one service. That is, a method of mapping one use case 100 to one service program 120 is performed.

According to another example of the present invention with reference to FIG. 10, a division method will be described. One use case 100 is composed of a plurality of sets of tasks 110, and sets of tasks 110 are independently of each other. If some of the functions are duplicated or the task 110 is a set of previously used functions, the respective task 110 sets are separated into one or more service programs 120.

The state shown in the upper part of FIG. 10 is configured as a separate service program if the set of some tasks 110 among the plurality of tasks 100 constituting the use case 100 is a set of tasks 110 used in the past. In addition, the set of remaining tasks 110 is configured as a separate service program 120. That is, one use case 100 is divided into small service programs 120.

Referring to FIG. 11, according to another example of the present invention, a complex method will be described. A plurality of tasks 110 included in one use case 100 may be overlapped, an existing task 110 may be a set, or an independent task set. In this case, each of the service programs 120 is configured, and each service program 120 is configured in one composite service program 130.

Referring to FIG. 12, a diagram in which a system program is classified as a use case according to an example of the present invention will be described. Thesis verification, article performance search, patent verification, performance search by task, task search, article performance search, and patent performance search , Use cases such as patent performance inquiry and manpower information inquiry.

FIG. 13 is a table identifying each use case classified in FIG. 12 and identified nine.

Referring to FIG. 13 in detail, the paper verification use case is mapped 1: 1 to the paper verification service program, the patent verification use case is mapped 1: 1 to the patent verification service, and the performance inquiry use case for each task is the paper performance inquiry service. And patent performance inquiry service.

In addition, assignment search use cases are mapped 1: 1 to assignment search service, thesis performance search use cases are mapped 1: 1 to thesis performance search service, and thesis achievement inquiry use cases are mapped 1: 1 to thesis performance inquiry service. Is shown.

In addition, the patent performance search use case is mapped to the patent performance search service, the patent performance inquiry use case to the patent performance inquiry service, and the manpower information inquiry use case to the human resource inquiry service.

A process of setting the performance inquiry use case for each task as a thesis performance inquiry service and a patent performance inquiry service will be described with reference to FIG. 14.

Referring to FIG. 14, the composite case setting method of the use case will be described according to an example of the present invention. A performance inquiry use case for each task is selected (S100), and information on the selected performance inquiry use case for each task is displayed (S110). . The information displayed is task information.

Check whether the information of the displayed use case is the article information (S120), if the article information is indicated by the article information or thesis performance inquiry service (S130), and if the article information is not the patent information (S140), If the patent information, it is displayed as a patent information or patent performance lookup service (S150).

The present invention having the above-described configuration has advantages such as reducing the time required for the development of a program and completing the development quickly, by classifying and reusing a previously developed program as a use case in developing a system program.

Although the present invention has been described as an example, it is not necessarily limited to such an example, and various modifications can be made without departing from the technical spirit of the present invention. Therefore, the examples disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited thereto. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

1 is a detailed diagram of the development stage of a structured programming language and an object-oriented programming language according to the prior art;

2 is a background explanatory diagram recognizing as XML-based web service of general SOA,

3 is a logical explanatory diagram of an SOA service according to an example of the present invention;

4 is an explanatory diagram of types of SOA services according to an example of the present invention;

5 is an explanatory diagram of components of an SOA service according to an example of the present invention;

6 is a diagram illustrating an SOMA method of IBM for the purpose of illustrating the present invention;

7 is a diagram illustrating an SOA architecture of IBM for the purpose of illustrating the present invention;

8 is an explanatory diagram of an analysis of a use case by one example of the present invention;

9 is an explanatory diagram of a modeling method of a system program using a use case according to an example of the present invention;

10 is a diagram illustrating a modeling method of a system program using a use case according to an example of the present invention;

11 is an explanatory diagram of a modeling method of a system program using a use case according to an example of the present invention;

12 is a diagram illustrating diagrams in which system programs are classified into use cases according to an example of the present invention;

FIG. 13 is a diagram illustrating identifying and displaying each use case classified in FIG. 12.

14 is a flowchart illustrating a complex setting method of a use case according to an example of the present invention.

          ** Explanation of symbols on the main parts of the drawing **

100: use case 110: task

120: service program 130: complex service program

Claims (10)

In the modeling method of a system program using a use case, If a plurality of tasks included in the use case is an independent task set that is not dependent or overlaps with a task set of another use case, it maps to one independent service, Some of the tasks included in the use case are task sets that are independently used in the use case and are duplicated in task sets of other use cases, or some of the task sets developed independently while acting independently in the use case. It separates the cases used as tasks of each and maps them to the split service. If the plurality of tasks included in the use case is a set of complex tasks including at least two of a task set duplicated in the plurality of task sets included in the use case and a task set independent of the existing task set, the task maps to the composite service. A modeling method of a system program using a use case including the above. delete delete delete delete delete delete A computer-readable recording medium recording a process relating to a modeling method of a system program using the use case of claim 1. delete delete

Images