JP7417462B2 - Package generation device, package management system and package generation method - Google Patents

Description

The present invention relates to a software package generation device, management system, and generation method.

Patent Document 1 states, ``Determining what process to use for development work has been difficult for inexperienced managers.For this reason, organizations have been forced to define and deal with standard development processes. However, this type of development process is designed to fit all projects in an organization, and tends to become an excessive process for small projects. A risk calculation unit 11 for determining an allowable risk rate based on risk data for each activity of the development process and input data serving as risk basis, and a risk calculation unit 11 for determining an allowable risk rate for each activity forming the standard development process It is disclosed that a tailoring unit 12 is provided to determine whether or not to incorporate the project management process into the project management process (see the summary of Patent Document 1).

Patent Document 2 states, ``When installing application software on a computer, operations are performed based on arbitrarily set setup processes before and after installation of the application software, and in particular, recovery in the event of installation failure is possible. The solution was to create an installation execution definition file by specifying an installer that installs application software on a computer, and write instructions for customizing the application software installation performed by the specified installer. It is disclosed that by creating a setup instruction file, a customization process is instructed when installing application software by a specified installer (see the summary of Patent Document 2).

Patent Document 3 states that the problem is "to provide a system, method, and computer program product for representing at least one system function as a software package in a software package management system," and as a means of solving the problem, " creating at least one system functionality package representing at least one system functionality; the at least one system functionality package being installed on the information system via a software package management system; the at least one system functionality package is stored in a software package database.The system function package conforms to the software package structure, whereby the system function package is managed by a software package management system.'' (See Patent Document 3 Abstract) ).

Patent Document 4 states that the problem is to "reduce software installation time," and as a means of solving the problem, "for each of a plurality of installation candidates, the information processing device 10 saves files installed at the time of installation of the related software. Based on the above, the information processing device 10 estimates a plurality of files to be installed when installing the plurality of installation candidate software.Next, the information processing device 10 estimates the plurality of files that will be installed when the plurality of installation candidate software is installed. One or more pieces of software that result in fewer duplicate installations of the same file than when installing multiple candidate software pieces is identified.The information processing device 10 then executes the installation of the one or more pieces of software that has been identified. is disclosed (see summary of Patent Document 4).

JP2003-296528A JP2011-203917A Japanese Patent Application Publication No. 2007-128522 Japanese Patent Application Publication No. 2019-040400

Tailoring refers to rearranging a standard process or other standard process into a process that is suitable for the characteristics of a certain project. A standard process is a process defined as a standard for processes within an organization in order to maintain work efficiency and quality.

If the process changes due to tailoring, the required work environment will change, and each time the environment construction method must be redefined and the work environment for all project members must be created.

Although Patent Document 1 provides a technique for improving the quality and efficiency of process tailoring, it does not consider a method of constructing a working environment necessary for actually implementing the process.

Patent Documents 2, 3, and 4 provide techniques for improving the reliability and efficiency of environment construction, but do not consider a method for responding to situations where the necessary work environment changes.

In the above conventional technology, when tailoring is performed to rearrange a standard process into a project process suitable for the characteristics of a certain project, each member's There was a problem in that it took a huge amount of man-hours to build a working environment.

The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to shorten the time required to construct a work environment for implementing the process even when the process changes due to tailoring.

The present invention is a package generation device having a processor and a memory, and includes a process data acquisition unit that receives process data in which one or more roles are defined, and a data analysis unit that extracts environmental data for each role included in the process data. and environment construction elements corresponding to the extracted environment data for each role to generate one or more packages, generate environment construction batch information that sets the execution order of the packages, and combine the environment construction elements corresponding to the extracted environment data. and an integrated package file generation unit that generates integrated package information including the environment construction batch information.

According to the present invention, even when a process changes due to tailoring, it is possible to shorten the time required to construct a working environment when implementing the process.

Problems, configurations, and effects other than those described above will be made clear by the following description of the embodiments.

1 is a diagram showing an overview of a software package management system according to a first embodiment of the present invention; FIG. 1 is a block diagram showing an example of the configuration of a software package management system according to a first embodiment of the present invention; FIG. 1 is a diagram illustrating a first embodiment of the present invention and illustrating an example of the configuration of an integrated package file. FIG. 1 is a diagram showing an example of a tailoring operation screen of a process management system according to a first embodiment of the present invention; FIG. 1 is a diagram showing an example of a process data output operation screen of a process management system according to a first embodiment of the present invention; FIG. 1 is a diagram illustrating an example of a process overview screen and an activity details screen of a process management system according to a first embodiment of the present invention; FIG. FIG. 2 is a diagram illustrating an example of a screen output by the environment construction unit according to the first embodiment of the present invention. 1 is a flowchart illustrating a first embodiment of the present invention and illustrating an example of processing performed in a software package management system. 1 is a flowchart illustrating an example of a package generation process according to a first embodiment of the present invention. FIG. 2 is a diagram illustrating the first embodiment of the present invention and illustrating an example of the correspondence between the data structure of process data and the environment data of each role. FIG. 7 is a diagram illustrating a second embodiment of the present invention and illustrating an example of the correspondence between the data structure of process data and the environment data of each role. 12 is a flowchart illustrating a third embodiment of the present invention and illustrating an example of processing performed in a software package management system. 12 is a flowchart illustrating a fourth embodiment of the present invention and illustrating an example of processing performed in a software package management system.

Embodiments of the present invention will be described below based on the accompanying drawings.

FIG. 1 is a diagram showing an overview of a software package management system according to a first embodiment. In this embodiment, the software package management system of the present invention generates an integrated package file 113 based on the project process, and constructs the environment necessary for implementing the process on the end user terminal 115 according to the project and role. This is what makes it possible.

A software package brings together application software, data files, etc., and defines metadata that describes information about the software and data files, as well as files and installation procedures necessary for installation on a computer (end user terminal 115). This is what I did.

Hereinafter, a software package will be simply referred to as a package. The integrated package file 113 refers to a file that integrates a plurality of packages and defines necessary files and installation procedures in order to install a plurality of packages into a computer at once.

The process management system 101 in FIG. 1 is a system (or computer) that provides functions that support process management, such as project process definition, process sharing, and tailoring. The process manager 102 is a user of the process management system 101 who uses the process management system 101 to define and tailor the standard process 103.

Note that, as shown in the above-mentioned problem, tailoring in this embodiment refers to a process in which a reference process such as a standard process is rearranged into a process suitable for the characteristics of a certain project.

Tailored process data 104 is created by the process manager 102 using the process management system 101 to tailor a predefined standard process 103 in accordance with the project. Activities 105 are examples of activities included in the tailored process data 104.

Role A and role C are assigned to activity 105. Furthermore, the activity 105 is associated with environmental data 106 necessary for the role C to carry out the activity 105.

An activity refers to the work of a certain step in a process. A role represents a role assigned to a project member (end user 114). Environmental data defines information about the work environment required when a role performs an activity. Examples of information included in the environmental data include metadata such as an identification name, setting information, and the like.

The standard process 103 is also process data that includes activities and the like, similar to the tailored process data 104. As shown in tailored process data 104, the process data includes at least one or more activities. An activity is associated with at least one or more roles related to the activity and environmental data of each role. In addition to these, the process data can also include any other information regarding the process.

Tailoring involves selecting activities defined in the standard process 103, rearranging flows, and customizing environmental data linked to activities. Thereby, the tailored process data 104 becomes project-specific process data.

After performing the tailoring, the process management system 101 transmits information included in the tailored process data 104 to the package generation system 109 so that the package generation system 109 generates a package.

The package generation system 109 is a system (or computer) that generates an integrated package file 113 for constructing a working environment necessary for implementing a process based on the tailored process data 104 received from the process management system 101. .

The package generation system 109 first extracts only environmental data from the tailored process data 104, aggregates it for each role without duplication, and creates environmental data 110 for each role. The environment data 106 included in the environment data 110 for each role is extracted from the environment data included in the tailored process data 104.

Next, the package generation system 109 combines environment construction components based on the environment data 110 for each role, and generates an integrated package file 113. The environment construction component is a component of the integrated package file 113 in the form of a file or the like. The components of the integrated package file 113 will be described later using FIG. 3.

The package generation system 109 reflects the definition contents of the environment data 106 customized by tailoring in the integrated package file 113 by selecting and combining the environment construction components 112 to generate a package, as will be described later. .

The environment construction component DB (DataBase) 111 is a database system that stores the environment construction components 112.

Integrated package files 113a, 113b, and 113c are integrated package files 113 generated for role A, role B, and role C, respectively. The environment construction component 112 is an example of an environment construction component (environment construction element) 112 that constructs the environment data 106, and is incorporated into the role C integrated package file 113c.

Next, the package generation system 109 registers the generated integrated package file 113 for each role in the process management system 101. Registering the integrated package file 113 in the process management system 101 has the effect of enabling the process management system 101 to manage the work of building an environment necessary for implementing a process as an activity.

Further, this registration process enables the end user 114 of the end user terminal 115 who uses the process management system 101 to access the process management system 101 and obtain the integrated package file 113.

The registration method in this embodiment will be explained. The environment construction activity 107 is an example of an activity that constructs an environment necessary for implementing a process, and is assigned to all roles. 108a, 108b, and 108c indicate environmental data for role A, role B, and role C, respectively. Note that the environmental data 106 indicates general-purpose environmental data and is different from the environmental data 108a to 108c specialized for roles A to C.

The package generation system 109 registers the generated integrated package files 113a, 113b, and 113c for each role in the environment data 108a, 108b, and 108c, respectively. This is an example of a registration method, and other methods may be used.

The end user 114 is an example of a user of the process management system 101 who operates the end user terminal 115 to view processes and related information of the process management system 101. By accessing the process management system 101, the end users 114 can obtain information related to the processes of the projects and roles that they are responsible for.

The end user terminal 115 is an example of an information processing terminal used by the end user 114, and is a computer system on which environment construction is performed. The end user 114 views the tailored process data 104 of the process management system 101 and downloads the integrated package file 113 of the role assigned to him onto the end user terminal 115.

In FIG. 1, a case is shown in which role C is assigned to end user 114, as an example. In this case, the end user 114 of the end user terminal 115 obtains the integrated package file 113c for role C from the environment data 108c for role C, and executes environment construction for the end user terminal 115.

The end user terminal 115 reads the installation file 117 from the installation file DB 116 according to the contents of the integrated package file 113c, and constructs environment entities such as tools and templates.

The installation file DB 116 is a database system that stores the installation file 117. The installation file 117 is an example of an installation file. An installation file is an actual file that is required when constructing an environment, and specific examples include a software installer and a template file for a product created in a process. The installation file 117 stored in the installation file DB 116 is referenced by the environment construction component 112 stored in the environment construction component DB 111.

The tool environment 118 is an example of a tool usage environment built on the end user terminal 115, and represents an environment built according to the definition of the environment data 106 reflected in the integrated package file 113c.

Note that the process management system 101 may be configured as a process management device, and the package generation system 109 may be configured as a package generation device.

FIG. 2 is a functional block diagram showing an example of the configuration of a software package management system that implements this embodiment.

The software package management system of this embodiment is composed of three systems: a package generation system 109, a process management system 101, and an end user terminal 115, and three database systems: an environment construction component DB 111, a process management DB 209, and an installation file DB 116. Ru.

Each system 109, 101 and end user terminal 115 has CPUs 202a, 202b, 202c, memories 201a, 201b, 201c, and communication devices 220a, 220b, 220c, and each processing unit (described later) executes be done. Each part is connected via a bus (not shown), and each system 109, 101, end user terminal 115, and DB 116 are connected by a network 50 via communication devices 220a to 220c.

Note that the code ``202'' with no subscript is used as the code for the CPU when the individual CPU is not specified. The same applies to the symbols of other components.

Further, each system 109, 101 and end user terminal 115 has input/output devices 221a, 221b, and 221c, respectively. The input/output device 221 includes, for example, an input device such as a mouse, a keyboard, or a touch panel, and an output device such as a display. Each system 109, 101, end user terminal 115, and DB 111, 209, 116 may be constructed on different terminals, or a plurality of them may be combined and placed on the same terminal.

Descriptions of the environment construction component DB 111 and the installation file DB 116 are as described above, and will therefore be omitted here.

The process management system 101 includes a process management section 207, a data output section 208, and a process management DB 209. The process management unit 207 receives user operations, performs process definition and tailoring, and issues data output commands to the data output unit 208.

The data output unit 208 receives a data output command from the process management unit 207 and transmits the instructed data to the package generation system 109 and the end user terminal 115. The process management DB 209 is a database system that stores process data managed by the process management unit 207 and related files. Process data refers to standard process 103 and tailored process data 104.

Each functional unit of the process management unit 207 and the data output unit 208 is loaded into the memory 201b as a program.

The CPU 202b operates as a functional unit that provides predetermined functions by executing processes according to the programs of each functional unit. For example, the CPU 202b functions as the process management unit 207 by executing processing according to a process management program. The same applies to other programs. Furthermore, the CPU 202b also operates as a functional unit that provides functions for each of the plurality of processes executed by each program. A computer and a computer system are devices and systems that include these functional units.

The package generation system 109 includes a process data acquisition section 203, a data analysis section 204, an integrated package file creation section 205, a file transfer section 206, and an environment construction component DB 111.

The process data acquisition unit 203 receives the tailored process data 104 transmitted from the process management system 101 and outputs it to the data analysis unit 204. The data analysis unit 204 creates environment data 110 for each role from the tailored process data 104 input by the process data acquisition unit 203, as described later, and outputs it to the integrated package file creation unit 205.

The integrated package file creation unit 205 creates an integrated package file 113 for each role from the environment data 110 for each role input by the data analysis unit 204, as described later.

The file transfer unit 206 registers the integrated package file 113 for each role created by the integrated package file creation unit 205 in the process management system 101.

End user terminal 115 has environment construction section 210 . The environment construction unit 210 constructs the environment of the end user terminal 115. The environment construction unit 210 is implemented, for example, as application software called a package management system. A package management system is a system that manages the installation or deletion of packages, and is also called a package manager.

FIG. 3 is a diagram showing an example of the data structure of the integrated package file 113 created by the integrated package file creation unit 205.

The integrated package file 113 includes one environment construction batch file 301 and at least one package 302.

The environment construction batch file 301 is a file in which a script for controlling the entire environment construction process is written. The environment construction batch file 301 includes a pre-process 303, a package list 304, and a post-process 305.

Pre-processing 303 describes a script that performs necessary setup before implementing the environment construction process. The package list 304 describes the identification names of the packages 302 included in the integrated package file 113 as a list in the order of installation. Post-processing 305 describes a script that performs setup necessary after the environment construction process is performed.

The package 302 is defined for each implementation unit of environment construction, and is composed of one package definition file 306, one parameter list 307, at least one configuration file 308, and at least one configuration file 308. Ru.

In order to define a package that is a combination of multiple packages, it is also possible to configure the package 302 with one package definition file 306 and one or more packages 302.

The package definition file 306 describes metadata 309, an installation file list 310, installation pre-processing 311, installation processing 312, and installation post-processing 313.

The metadata 309 describes, for example, a package name, a summary description of the package, version information, and the like. The installation file list 310 describes a list of addresses of storage locations for the installation files 117 necessary for installing the package 302. As described above, the installation file 117 is stored in the installation file DB 116 and is referenced by the installation file list 310.

Installation pre-processing 311 describes a script that performs necessary setup before installation processing 312 is executed. In the installation process 312, the installation procedure for the package 302 is written as a script. The post-installation process 313 describes a script that executes the setup required after the installation process 312 is performed.

The parameter list 307 is a table that describes environment parameter names included in the environment data 110 for each role and their setting values. Parameters refer to configuration information that takes uncertain values or data until a process for a project is defined. Examples include the address of the project's data storage location and the project's identification name.

A configuration file 308 indicates a file read in each installation process 311, 312, and 313. Examples include a file that describes a script for a part of each installation process 311, 312, and 313, a file that defines execution options for a software installer, and the like.

The configuration file 308 has the role of expressing variations in the installation method of the package 302, and when a package is generated, the configuration files 308 are selected and combined according to the contents of the environment data customized by tailoring.

For example, if environment T has installation method A and installation method B, configuration files A and B are created in the package 302 of environment T, which describe the installation procedures and data for each. If installation method A is defined in the environment data related to environment T, by deleting configuration file B from the package 302 of environment T and leaving only configuration file A, the package generation system 109 can update the contents of the environment data. It is reflected in the package 302.

The environment construction batch file 301 and the package 302 are components of the integrated package file 113, and are stored as the environment construction component 112 in the environment construction component DB 111. When these environment construction components 112 are stored in the environment construction component DB 111, the package 302 includes a package definition file 306, a parameter list 307, and all setting files 308 created regarding the package 302.

A default value is described in the setting value of each parameter in the parameter list 307. When the package generation system 109 generates a package, the necessary packages 302 are copied and edited according to the contents of the environment data 110 for each role, thereby generating integrated package files 113a, 113b, and 113c for each role.

FIG. 4 is a diagram showing an example of an interface screen 410 in which the process management system 101 receives a tailoring start operation by the process manager 102. The interface screen 410 is output to the input/output device 221b of the process management system 101.

The interface screen 410 includes an area 401 showing an overview of process data to be tailored, and a tailoring button 402 that accepts a tailoring start operation from the input/output device 221b operated by the process manager 102.

FIG. 5 is a diagram illustrating an example of an interface screen 510 in which the process management system 101 receives an operation for outputting process data by the process manager 102. The interface screen 510 is output to the input/output device 221b of the process management system 101.

The interface screen 510 includes an area 501 that shows an overview of process data to be output, and a process data output button 502 that accepts a process data output operation from the input/output device 221b operated by the process manager 102.

FIG. 6 is a diagram showing an example of a process summary screen 601 in which the process management system 101 accepts an operation to output the integrated package file 113 by the end user 114. The process overview screen 601 is output to the input/output device 221c of the end user terminal 115 operated by the end user 114.

When the end user terminal 115 of the end user 114 accesses the process management system 101 and views the process corresponding to the project and role assigned to it, the process management system 101 outputs a process overview screen 601 for the process. .

In the figure, 602 is a button that accepts a transition operation to the activity details screen 603 regarding the environment construction activity 107 shown in FIG.

When the end user 114 operates the button 602 while the process overview screen 601 is displayed, the screen transitions to the activity details screen 603. The activity details screen 603 includes a download link 604 that accepts an operation to output the integrated package file 113 from the end user 114.

When the end user 114 clicks on the download link 604 via the input/output device 221c, the end user terminal 115 acquires the integrated package file 113.

FIG. 7 is a diagram showing an example of a screen 701 on which the environment construction unit 210 of the end user terminal 115 shows the progress and results of the environment construction processing to the end user 114. Screen 701 is displayed on input/output device 221c of end user terminal 115.

FIG. 8 is a flowchart illustrating an example of processing performed by the software package management system. The processes in steps S801 to S803, S807, and S808 are performed by the process management system 101. The processing in steps S804 to S806 is performed by the package generation system 109. The processes in steps S809 and S810 are performed by the environment construction unit 210 of the end user terminal 115.

The process management unit 207 of the process management system 101 receives the tailoring start operation by the process manager 102 (S801), reads the standard process 103 from the process management DB 209, performs the tailoring process (S802), and processes the tailored process data. 104 is output (S803).

The tailoring start operation is input by the process manager 102 operating the tailoring button 402 in FIG. 4, for example. The process management unit 207 stores the created tailored process data 104 in the process management DB 209.

The process management unit 207 receives a process data output command from the process manager 102 , reads the tailored process data 104 from the process management DB 209 , and outputs the tailored process data 104 to the data output unit 208 . The process data output command is input, for example, by the process manager 102 operating the process data output button 502 in FIG. 5 via the input/output device 221b.

The data output unit 208 converts the input tailored process data 104 into a specific output format and sends it to the process data acquisition unit 203 of the package generation system 109. Hereinafter, unless otherwise specified, process data 104 indicates tailored process data 104. The output format of the process data 104 may be any format as long as activity, role, and environment data are included while maintaining their relationships.

When the process data acquisition unit 203 of the package generation system 109 is implemented as a service resident in the system, when the process data acquisition unit 203 detects input of the process data 104 from the process management system 101, the process moves to step S804. .

Alternatively, it is also possible to implement a transition to step S804 by the process management unit 207 of the process management system 101 executing a script that describes processing for starting the process data acquisition unit 203 of the package generation system 109. The startup script may be executed via another system with which the process management system 101 can cooperate.

In step S804, the process data acquisition unit 203 of the package generation system 109 receives the tailored process data 104 transmitted from the data output unit 208 of the process management system 101, and sends the tailored process data 104 to the data analysis unit 204. Output.

In step S805, the data analysis unit 204 analyzes the tailored process data 104 input from the process data acquisition unit 203, creates environment data 110 for each role, and sends the environment data 110 for each role to the integrated package file creation unit 205. Data 110 is output.

The integrated package file creation unit 205 reads the environment data 110 for each role input from the data analysis unit 204, combines the environment construction components 112, and creates an integrated package file 113 for each role. The integrated package file creation unit 205 outputs the created integrated package file 113 for each role to the file transfer unit 206. Details of the process in step S805 will be described later using FIG. 9.

In step S806, the file transfer unit 206 registers the integrated package file 113 for each role input from the integrated package file creation unit 205 in the process management DB 209 of the process management system 101.

The registration in step S806 refers to the process of making the integrated package file 113 for each role available for reference from the process management system 101. The registration method described using the environment construction activity 107 in FIG. 1 is one example.

As an example of a process for realizing the registration method described using the environment construction activity 107 in FIG. Another example is storing the address data of the storage location of the integrated package file 113 for each role.

Further, as another example, the file transfer unit 206 may store the integrated package file 113 for each role in the process management DB 209. The process is not limited to these, but any process that allows the end user 114 to access the process management system 101 from the end user terminal 115 and view his/her own process information can obtain the integrated package file 113 for his or her own role. , any implementation is fine.

In addition to the integrated package file 113 for each role, the file transfer unit 206 may notify the process manager 102 of a report of the package generation processing results or may register it in the process management DB 209 of the process management system 101. The processing result report may output environmental data 110 for each role and any information obtained during the package generation process. Examples of the report include, but are not limited to, information on installed add-ons of application software, aggregation results of the number of licenses used, and the like.

Further, in step S806, instead of the file transfer unit 206 registering the integrated package file 113 in the process management DB 209 of the process management system 101, the file transfer unit 206 directly sends the integrated package file 113 to the end user terminal 115 of the end user 114. The integrated package file 113 may be distributed.

Examples of distribution methods include a method in which the file transfer unit 206 directly transmits the integrated package file 113 to the end user terminal 115, or a method in which a shared data storage area that can be accessed by the end user terminal 115 of the end user 114 is prepared separately. An example is a method in which the file transfer unit 206 stores the integrated package file 113 in its storage area, but other means may also be used.

In step S807, the process management unit 207 of the process management system 101 receives an operation to output the integrated package file 113 from the end user terminal 115 of the end user 114. The process management unit 207 reads the integrated package file 113 registered in the process being viewed by the end user 114 from the process management DB 209 and outputs it to the data output unit 208 . The output operation of the integrated package file 113 is input by the end user 114 operating the download link 604 in FIG. 6, for example. In step 808, the data output unit 208 transmits the input integrated package file 113 to the end user terminal 115.

In step S809, the end user terminal 115 receives the integrated package file 113 sent from the data output unit 208 of the process management system 101. The end user terminal 115 receives an instruction to execute the environment construction batch file 301 from the end user 114 and starts the environment construction section 210 of the end user terminal 115 . As shown in FIG. 3, the environment construction batch file 301 is included in the integrated package file 113.

In step S810, the environment construction unit 210 of the end user terminal 115 executes the preprocessing 303 of the environment construction batch file 301, and then starts environment construction according to the contents of the package list 304. As shown in FIG. 7, the environment construction unit 210 may output the progress status of the process in step S810 to the screen of the input/output device 221c of the end user terminal 115.

The environment construction unit 210 reads the packages 302 in the order described in the package list 304 of the environment construction batch file 301, acquires the necessary installation files 117 from the installation file DB 116 according to the installation file list 310, and installs each of the packages shown in FIG. Installation processes 311, 312, and 313 are executed in order. The environment construction unit 210 performs these processes on all packages 302 included in the integrated package file 113.

After the installation of all packages is completed, the environment construction unit 210 executes post-processing 305 of the environment construction batch file 301. After that, the environment construction process ends.

FIG. 9 is a flowchart showing details of the process in step S805 of FIG. 8 and an example of data input. After the software package management system performs the process in step S804 in FIG. 8, the process transitions to step S901 in FIG.

In step S901, the data analysis unit 204 of the package generation system 109 reads the tailored process data 104 input from the process data acquisition unit 203 and the data analysis script 911, and analyzes the tailored process data 104.

The data analysis script 911 is a script that describes data analysis processing of the tailored process data 104. The data analysis script 911 is created in advance by an administrator or the like according to the output format of the tailored process data 104.

The data analysis unit 204 analyzes the tailored process data 104, extracts the environmental data 106 included in the tailored process data 104 for each role, and creates environmental data 110 for each role.

If the data analysis unit 204 extracts the environmental data included in the tailored process data 104 and finds that one role contains multiple pieces of the same environmental data, the duplicate environmental data is deleted.

Thereafter, the data analysis unit 204 outputs the environment data 110 for each role to the integrated package file creation unit 205.

In step S902, the integrated package file creation unit 205 reads the environment data 110 for each role input from the data analysis unit 204 and the environment construction component list 912 acquired from the environment construction component DB 111, and creates the necessary environment construction components 913. Identify and list. The environment construction component list 912 is a table listing the correspondence between the identification names of the environment data of the process management system 101 and the environment construction components 112 stored in the environment construction component DB 111. The necessary environment construction components 913 are a group of environment construction components that the integrated package file creation unit 205 acquires from the environment construction component DB 111. Specifically, the environment construction batch file 301 and package 302 shown in FIG. 3 are included in the necessary environment construction components 913.

In step S903, the integrated package file creation unit 205 acquires a copy of the necessary environment construction component 913 identified in step S902 from the environment construction component DB 111.

In step S904, the integrated package file creation unit 205 performs processing to create an integrated package file 113 for each role included in the environment data 110 for each role.

The integrated package file creation unit 205 selects one role included in the environment data 110 for each role, and creates an empty integrated package file 113. The integrated package file creation unit 205 copies the environment construction batch file 301 included in the necessary environment construction component 913 and incorporates it into the empty integrated package file 113.

The integrated package file creation unit 205 performs package 302 creation processing for each piece of environmental data associated with the selected role. The integrated package file creation unit 205 selects one piece of environment data included in the selected role from the environment data 110 for each role, copies the package 302 corresponding to the selected environment data from the environment construction component 913, and prepares it. It is incorporated into the integrated package file 113. The integrated package file creation unit 205 reflects the parameter setting values in the parameter list 307 included in the package 302 according to the contents of the selected environment data.

Furthermore, the integrated package file creation unit 205 deletes unnecessary configuration files 308 included in the package 302 according to the contents of the selected environment data. Further, the integrated package file creation unit 205 changes the file name of the necessary configuration file 308 to a name that can be referenced from the package definition file 306 according to certain rules.

The integrated package file creation unit 205 adds the identifier of the created package 302 to the package list 304 of the environment construction batch file 301. If the metadata 309 of the package 302 includes constraints regarding the order of installation, the integrated package file creation unit 205 may change the order of the introduction order in the package list 304. The above is the package 302 creation process, which is repeated for each environmental data associated with the selected role.

When the integrated package file creating unit 205 completes creating the package 302 corresponding to all the environmental data linked to the selected role, it completes creating the integrated package file 113 for the selected role. The above is the creation process of the integrated package file 113, which is repeated for each role included in the environment data 110 for each role.

After completing the creation of the integrated package files 113 for all roles, the integrated package file creation unit 205 outputs the created integrated package files 113 for each role to the file transfer unit 206, and transitions to S806 in FIG. 8.

According to this embodiment, the software package management system of the present invention generates the integrated package file 113 based on the project process, and constructs the environment necessary for implementing the process on the end user terminal 115 according to the project and role. becomes possible.

In this way, the software package management system of this embodiment can shorten the time required to construct a working environment when implementing a process even when the process changes due to tailoring.

Further, in the above embodiment, the process management system 101 and the package generation system 109 are executed on different computers, but they may be executed on the same computer.

Further, in the above embodiment, the end user terminal 115 is operated by the end user 114, but it may be a computer that builds software. In this case, the integrated package file 113 creates an environment for the build computer. Further, instead of the end user terminal 115, a terminal for specific work may be used.

Example 2 will be described using FIGS. 10A and 10B. In the second embodiment, a case will be described in which the data structure of process data managed by the process management system 101 is different from that in the first embodiment. The other configurations and processes are the same as those in the first embodiment, so their explanations will be omitted.

This embodiment expands the range of process data data structures that can be handled by the software package management system of the present invention, thereby allowing users of the software package management system of the present invention to create formats that better suit the needs of their organizations. This makes it possible to configure the environment of the end user terminal 115 according to the process while managing process data.

FIG. 10A is a diagram showing the correspondence between the data structure of the tailored process data 104 and the environment data 110 for each role in the first embodiment shown in FIG.

The process data 104 in the first embodiment includes at least one activity 105. The activity 105 is associated with at least one or more roles related to the activity 105 and environmental data of each role.

FIG. 10B is a diagram showing the correspondence between the data structure of the tailored process data 104 and the environment data for each role in the second embodiment. The data structure of Example 2 is shown as process data 1001.

Process data 1001 in Example 2 includes at least one activity. Activity 1002 is an example of an activity included in process data 1001. Role A and role B are assigned to activity 1002. Furthermore, only one piece of environmental data 1003 (T3) is associated with the activity 1002.

In the case of FIG. 10B, the environment data 1003 is regarded as environment data that defines a necessary environment for all roles assigned to the activity 1002, for example.

In this case, when the data analysis unit 204 of the package generation system 109 analyzes the process data 1001, the administrator or the like can link the environment data 1003 to all the roles assigned to the activity 1002, as shown in FIG. A data analysis script 911 is created.

The data analysis unit 204 of the package generation system 109 uses the data analysis script 911 to extract environmental data for each role, and the result is the environment data 1004 for each role.

Although the second embodiment has described an example of a variation of the process data structure, it is also possible to employ other process data structures.

This embodiment expands the range of process data data structures that can be handled by the software package management system of the present invention, and allows users of the software package management system of the present invention to format process data in a format that better suits the needs of their organization. It becomes possible to construct the environment of the end user terminal 115 according to the process while managing the process.

Example 3 will be explained using FIG. 11. FIG. 11 is a flowchart illustrating an example of processing performed by the software package management system. In the first embodiment, in step S803 in FIG. 8, the data output unit 208 of the process management system 101 transmits the tailored process data 104 to the package generation system 109. In the third embodiment, a process in which the process data acquisition unit 203 of the package generation system 109 requests the process management unit 207 of the process management system 101 to output the tailored process data 104 will be described. The other configurations and processes are the same as those in the first embodiment, so their explanations will be omitted.

In this embodiment, when the process data acquisition unit 203 of the package generation system 109 fails to receive the tailored process data 104 from the process management system 101, it is possible to reacquire the tailored process data 104. It is.

Step S801 and step S802 in FIG. 11 represent the same processing as step S801 and step S802 in FIG. 8 described in the first embodiment, so the explanation will be omitted. After the tailoring process ends in step S802, the package generation system 109 starts package generation process in step S1101.

In step S1101, the process data acquisition unit 203 of the package generation system 109 is activated by the operation of the input/output device 221b by the process manager 102 or by the process management unit 207 of the process management system 101.

In step S1102, the process data acquisition unit 203 of the package generation system 109 receives the input of the data acquisition command, and transmits a request to output the tailored process data 104 to the process management unit 207 of the process management system 101.

The data acquisition command is issued, for example, by operating the input/output device 221b of the process manager 102 or by the process management unit 207 of the process management system 101. The data acquisition command includes information that can identify the tailored process data 104 to be output (hereinafter referred to as output data identification information). The output request includes output data identification information included in the data acquisition command.

In step S1103, the process management unit 207 of the process management system 101 receives a request from the package generation system 109 to output the tailored process data 104, and outputs the tailored process data 104 to the data output unit 208.

The data output unit 208 converts the input tailored process data 104 into a specific output format and sends it to the process data acquisition unit 203 of the package generation system 109. The output format of the process data 104 may be any format as long as activity, role, and environment data are included while maintaining their relationships. Thereafter, the process moves to S804 in FIG.

In step S1104, the process data acquisition unit 203 of the package generation system 109 receives the tailored process data 104 transmitted from the data output unit 208 of the process management system 101, and sends the tailored process data 104 to the data analysis unit 204. Output.

The process data acquisition unit 203 determines whether or not the reception was successful (S1105). If the reception was unsuccessful, the process moves to step S1102 and transmits a request to output the tailored process data 104 again. If the process data acquisition unit 203 has successfully received the tailored process data 104, the process data acquisition unit 203 ends the reception of the tailored process data 104.

After the process data acquisition unit 203 finishes receiving the tailored process data 104 through the process in step S1104, the process transitions to S902 in FIG.

According to this embodiment, even if the process data acquisition unit 203 of the package generation system 109 fails to receive the tailored process data 104 from the process management system 101, it is possible to reacquire the tailored process data 104.

Example 4 will be explained using FIG. 12. FIG. 12 is a flowchart illustrating an example of processing performed by the software package management system.

In the first embodiment, the data output unit 208 of the process management system 101 transmits the integrated package file 113 to the end user terminal 115 in step S808 in FIG. In the fourth embodiment, a process in which the environment construction unit 210 of the end user terminal 115 requests the process management unit 207 of the process management system 101 to output the integrated package file 113 will be described. The other configurations and processes are the same as those in the first embodiment, so redundant explanations will be omitted.

This embodiment expands the range of methods for the end user terminal 115 to acquire the integrated package file 113 from the process management system 101, and allows the end user 114 to simply start up the environment construction unit 210 of the end user terminal 115. This makes it possible to configure the environment for the terminal 115.

Step S810 in FIG. 12 represents the same process as S810 in FIG. 8 described in the first embodiment, and therefore a description thereof will be omitted.

In step S1201, the end user terminal 115 receives an operation for starting the environment construction unit by the end user 114, and starts the environment construction unit 210.

In step S1202, the environment construction unit 210 of the end user terminal 115 receives input of integrated package file designation information by the end user 114 operating the input/output device 221c.

The integrated package file specification information includes information that can identify the tailored process data 104 to be output, and the identification name of the role of the end user 114, as information necessary to identify the integrated package file 113 to be acquired. included.

The environment construction unit 210 of the end user terminal 115 transmits a request to output the integrated package file 113 to the process management unit 207 of the process management system 101. The output request includes integrated package file specification information.

In step S1203, the process management unit 207 of the process management system 101 receives an output request for the integrated package file 113 from the environment construction unit 210 of the end user terminal 115, and outputs the integrated package file specified in the output request from the process management DB 209. 113 and outputs it to the data output unit 208. The data output unit 208 transmits the input integrated package file 113 to the environment construction unit 210 of the end user terminal 115.

In step S1204, the environment construction unit 210 of the end user terminal 115 receives the integrated package file 113 sent from the process management unit 207 of the process management system 101.

The environment construction unit 210 of the end user terminal 115 reads the integrated package file 113 and executes the environment construction batch file 301 included in the integrated package file 113. Thereafter, the process moves to S810 in FIG.

This embodiment expands the range of methods for the end user terminal 115 to acquire the integrated package file 113 from the process management system 101, and allows the end user 114 to simply start up the environment construction unit 210 of the end user terminal 115. It becomes possible to construct an environment for the terminal 115.

<Conclusion>

As described above, the package generation system 109 of the above embodiment can have the following configuration.

(1) A package generation device (package generation system 109) having a processor (CPU 202a) and a memory (201a), comprising a process data acquisition unit (203) that receives process data (104) in which one or more roles are defined; , a data analysis unit (204) that extracts environment data (106) for each role included in the process data (104), and an environment construction element (environment construction component 112) corresponding to the extracted environment data (106). ) for each role to generate one or more packages (302), generate an environment construction batch file (301) in which the execution order of the packages (302) is set, and combine the packages (302) and the environment construction. A package generation device comprising: an integrated package file generation unit (205) that generates an integrated package file (113) including a batch file (301).

With the above configuration, the package generation system 109 can generate the integrated package file 113 based on the project process, and can construct the environment necessary for implementing the process on the end user terminal 115 according to the project and role. Become.

(2) In the package generation device according to (1) above, the process data acquisition unit (203) receives the tailored process data (104), and the data analysis unit (204) A package generation device characterized by executing a preset analysis process (data analysis script 911) corresponding to the tailored process data (104).

With the above configuration, the package generation system 109 can shorten the time required to construct a working environment when implementing the process even when the process changes due to tailoring.

(3) In the package generation device according to (1) above, the data analysis unit (204) analyzes the role defined for each of one or more activities (105) included in the process data (104). The integrated package file generation unit (205) acquires the environment construction element (112) corresponding to the environment data (106) from a preset environment construction element list (environment construction parts list 912). Features of the package generation device.

With the above configuration, the package generation system 109 can extract environment data for each role from process data to which activities are connected, and generate environment data 110 for each role.

(4) In the package generation device according to (3) above, the integrated package file generation unit (205) is configured to create an environment on a computer (end user terminal 115) that executes the activity (105). A package generation device characterized in that an installation file (installation file list 310) specifying necessary installation files is added to the integrated package file (113).

With the above configuration, the end user terminal 115 that executes activities according to the role can build a work environment by executing the software listed in the installation file list 310 of the integrated package file 113.

(5) A process management device (process management system 101) that has a processor (202b) and a memory (201b) and outputs process data, and an integrated package file (113) that has a processor (202a) and a memory (201a) and outputs process data. ); and a terminal (end user terminal 115) having a processor (202c) and a memory (201c) and executing an integrated package file (113). The system includes a process data acquisition unit (203) that receives the process data (104) in which one or more roles are defined from the process management device (101), and a process data acquisition unit (203) that receives the process data (104) in which one or more roles are defined; A data analysis unit (204) that extracts environment data (110) for each role included in (104), and an environment construction element (environment construction component 112) corresponding to the extracted environment data (110) for the role One or more packages (302) are generated by combining each package (302), an environment construction batch file (301) is created in which the execution order of the packages (302) is set, and the package (302) and the environment construction batch file (301) are combined. ), the process management device (101) has an integrated package file generation unit (205) that generates an integrated package file (113) containing ) for each role, and the terminal (end user terminal 115) acquires the integrated package file (113) according to the role and executes the environment construction batch file (301). ) A package management system comprising an environment construction unit (210) that executes processing according to the following.

With the above configuration, the package generation system 109 can generate the integrated package file 113 based on the project process, and can construct the environment necessary for implementing the process on the end user terminal 115 according to the project and role. Become. As a result, even if the process changes due to tailoring, it is possible to shorten the time required to build a working environment when implementing the process on the end user terminal 115.

(6) In the package management system according to (5) above, the process data (104) acquisition unit receives the tailored process data (104), and the data analysis unit (204) A package management system characterized by executing a preset analysis process (911) corresponding to the tailored process data (104).

With the above configuration, the package generation system 109 can shorten the time required to construct a working environment when implementing the process even when the process changes due to tailoring.

(7) In the package management system according to (6) above, the process data acquisition unit (203) requests the process management unit (207) to transmit the tailored process data (104). A package management system that is characterized by:

With the above configuration, the package generation system 109 can acquire the tailored process data 104 from the process management system 101 in response to a request from the process data acquisition unit 203.

(8) The package management system according to (5) above, characterized in that the environment construction unit (210) requests the process management unit (207) to transmit the integrated package file (113). A package management system.

With the above configuration, the environment construction unit 210 of the end user terminal 115 can acquire the integrated package file 113 according to the role.

Note that the present invention is not limited to the embodiments described above, and includes various modifications. For example, the embodiments described above are described in detail to explain the present invention in an easy-to-understand manner, and the present invention is not necessarily limited to having all the configurations described. Furthermore, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Further, addition, deletion, or replacement of other components to a part of the configuration of each embodiment can be applied singly or in combination.

Further, each of the above-mentioned configurations, functions, processing units, processing means, etc. may be partially or entirely realized in hardware by designing, for example, an integrated circuit. Moreover, each of the above-mentioned configurations, functions, etc. may be realized by software by a processor interpreting and executing a program that realizes each function. Information such as programs, tables, files, etc. that implement each function can be stored in a memory, a recording device such as a hard disk, an SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

Further, the control lines and information lines are shown to be necessary for explanation purposes, and not all control lines and information lines are necessarily shown in the product. In reality, almost all components may be considered to be interconnected.

101 Process management system 103 Standard process 104 Tailored process data 105 Activity 106 Environment data 107 Environment construction activities 108a to 108c Environment data 109 Package generation system 110 Environment data for each role 111 Environment construction parts DB
112 Environment construction components 113 Integrated package file 115 End user terminal 116 Installation file DB
117 Installation file 118 Tool environment 201a to 201c Memory 202a to 202c CPU
203 Process data acquisition unit 204 Data analysis unit 205 Integrated package file creation unit 206 File transfer unit 207 Process management unit 208 Data output unit 209 Process management DB
210 Environment Construction Department

Claims (10)

A package generation device having a processor and a memory,
a process data acquisition unit that receives process data in which one or more roles are defined;
a data analysis unit that extracts environmental data for each role included in the process data;
Generate one or more packages by combining environment construction elements corresponding to the extracted environment data for each role, generate an environment construction batch file in which the execution order of the packages is set, and combine the packages and the environment construction. an integrated package file generation unit that generates an integrated package file including a batch file;
A package generation device comprising: The package generation device according to claim 1,
The process data acquisition unit includes:
Accepting the tailored process data,
The data analysis section includes:
A package generation device that executes a preset analysis process corresponding to the tailored process data. The package generation device according to claim 1,
The data analysis section includes:
Extracting the role defined for each of one or more activities included in the process data,
The integrated package file generation unit includes:
A package generation device characterized in that an environment construction element corresponding to the environment data is acquired from a preset environment construction element list. The package generation device according to claim 3,
The integrated package file generation unit includes:
A package generation device characterized in that an installation file list specifying installation files necessary for constructing an environment on a computer that executes the activity is added to the integrated package file. a process management device that has a processor and a memory and outputs process data;
a package generation device having a processor and memory and generating an integrated package file;
A package management system comprising: a terminal having a processor and a memory and executing the integrated package file;
The package generation device includes:
a process data acquisition unit that receives the process data in which one or more roles are defined from the process management device;
a data analysis unit that extracts environmental data for each role included in the process data;
Generate one or more packages by combining environment construction elements corresponding to the extracted environment data for each role, generate an environment construction batch file in which the execution order of the packages is set, and combine the packages and the environment construction. an integrated package file generation unit that generates the integrated package file including a batch file;
has
The process management device includes:
a process management unit that manages the integrated package file generated by the package generation device for each role;
The terminal is
A package management system comprising: an environment construction unit that acquires the integrated package file according to the role and executes processing according to the environment construction batch file. The package management system according to claim 5,
The process data acquisition unit includes:
Accepting the tailored process data,
The data analysis section includes:
A package management system characterized by executing a preset analysis process corresponding to the tailored process data. 7. The package management system according to claim 6,
The process data acquisition unit includes:
A package management system that requests the process management unit to transmit the tailored process data. The package management system according to claim 5,
The environment construction department is
A package management system that requests the process management unit to transmit the integrated package file. A package generation method for generating a package on a computer having a processor and memory, the method comprising:
a process data acquisition step in which the computer receives process data in which one or more roles are defined;
a data analysis step in which the computer extracts environmental data for each role included in the process data;
The computer combines environment construction elements corresponding to the extracted environment data for each role to generate one or more packages, generates an environment construction batch file in which the execution order of the packages is set, and executes the package. and an integrated package file generation step of generating an integrated package file including the environment construction batch file;
A package generation method characterized by including. The package generation method according to claim 9,
The process data acquisition step includes:
Accepting the tailored process data,
The data analysis step includes:
A package generation method characterized by executing a preset analysis process corresponding to the tailored process data.

Images