JP6789357B2 - Item management system, item management method and item management program - Google Patents

Description

The present invention relates to an item management system, an item management method, and an item management program for managing the creation of items used in an application.

In system development consisting of tasks related to each other, it may be carried out by a project in which multiple organizations participate. A project management system that visually expresses the progress of this project is being studied (see, for example, Patent Document 1). In the project management system described in this document, a reference document referred to when the project is executed and a document management database for managing the output document to be created are used. Furthermore, when planning a project, an empty entity of the output document to be created in each process of the project is registered in the document management database. Then, the registered empty entity and the link information to the reference document are registered in association with the process, and the progress status of the project is managed. This project management system displays the process name, the title bar according to the length of the schedule of the process, and the progress bar indicating the progress of the process in correspondence with each process, and the process personnel and this personnel. Visually output the progress status in charge of.

Further, today, techniques for providing various games are being studied (see, for example, Patent Document 2). In the technique described in this document, not a completed item but a plurality of unfinished items leading up to the finished item are prepared, and the plurality of unfinished items are presented to the user to obtain the item of the user. We will improve motivation and thereby reduce the user withdrawal rate of card games.

Japanese Unexamined Patent Publication No. 2003-141320 Japanese Patent No. 5401627

As described above, many items are used in applications such as games. Furthermore, the form may change due to the evolution of items. When developing such an application, delays in the preparation of some items can affect overall development. Therefore, it is necessary to accurately manage the creation status of images and the like of each item. Further, in the item creation step, various modifications are made to the item image. It would be convenient for the user to be aware of such changes.

The present invention has been made in view of the above-mentioned problems, and an object of the present invention is an item management program, an item management method, and an item management system for efficiently and accurately managing the creation of a plurality of items used in an application. Is to provide.

The item management system that solves the above problems is a system that manages items, and is associated with an item image in which multiple users work, a creation step, and account information that identifies a user who works in the latest creation step. A storage unit to be recorded and a control unit connected to the client terminal are provided, and the control unit acquires the account information input by the user from the client terminal, and the account information that identifies the user who performs the work is obtained. From the plurality of associated item images, the number of the item images in which the account information input by the user and the account information specifying the user who performs the work match, and the contents related to the item image are acquired, and the item is obtained. The number of images and the contents related to the item image are output to the client terminal.
The item management method that solves the above problems is a method of managing items, and the item management system uses an item image of an item for which a plurality of users work, a creation step, and a user who works in the latest creation step. A storage unit in which the account information to be specified is recorded in association with the account information and a control unit connected to the client terminal are provided, and the control unit acquires the account information input by the user from the client terminal and performs work. Regarding the number of the item images and the item images in which the account information input by the user matches the account information that identifies the user who performs the work from among a plurality of item images associated with the account information that identifies the user. The contents are acquired, and the number of the item images and the contents related to the item images are output to the client terminal.
The item management program that solves the above problems is a program that manages items, and the item management system is an item image in which a plurality of users work, a creation step, and account information that identifies a working user in the latest creation step. Is provided with a storage unit associated with and recorded, and a control unit connected to the client terminal, and the control unit acquires account information input by the user from the client terminal and identifies a user who performs work. From a plurality of item images associated with the account information, the number of the item images in which the account information input by the user matches the account information that identifies the user who performs the work and the contents related to the item image are acquired. , The number of the item images and the contents related to the item images are output to the client terminal.

According to the present invention, it is possible to efficiently and accurately manage the creation of a plurality of items used in an application.

The system schematic diagram of this embodiment. Explanatory drawing of data used in this embodiment. The explanatory view of the processing procedure of this embodiment. The explanatory view of the processing procedure of this embodiment. The explanatory view of the processing procedure of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of this embodiment. The explanatory view of the processing procedure of this embodiment. Explanatory drawing of the output screen of this embodiment. Explanatory drawing of the output screen of another embodiment. Explanatory drawing of the output screen of another embodiment. Explanatory drawing of the output screen of another embodiment.

Hereinafter, one embodiment of the item management method will be described with reference to FIGS. 1 to 20.
As shown in FIG. 1, in the present embodiment, it is assumed that an item used for an application is created by using a plurality of client terminals 10 and a management server 20 connected via a network such as the Internet. Here, an item is a unit for managing deliverables, and includes, for example, a plurality of characters used in a game application. In this case, the creation of the item involves the administrator, the developer, and the creator.

The administrator belongs to the application management company, and creates the concept of the application, manages and operates the entire application, and checks the quality. The developer belongs to the application development company (developer) and works with the administrator to create the items used for the application. Then, the creator (designer) belongs to the content creation company, and together with the developer, creates an item image (asset) of the created item. When creating an item image, for example, a rough drawing, a line drawing, coloring, finishing, inspection, delivery, and other creation steps (processes) are performed. The creator creates an item image (check file) in each step and posts it to the management server 20. Then, the developer confirms the posted check file using the management server 20, and feeds back the confirmation result. In this feedback, the developer makes a "OK (approval)" or "retake (redo)" decision. The creator will modify the item if necessary, based on the developer's feedback. The roles of the administrator and the developer can be changed according to the situation. For example, when an administrator produces an application in-house, he / she has a role as a developer.

For creating an item, the administrator, the developer, and the creator use their respective client terminals 10. The client terminal 10 is a computer terminal used by each user (administrator, developer, creator) to access the management server 20. The client terminal 10 includes a communication unit, an input unit, and an output unit (touch panel display, etc.). Further, the client terminal 10 includes a control unit including a CPU, RAM, ROM, and the like. In the present embodiment, each client terminal 10 includes a browser program, and accesses the management server 20 by using the browser activated by this program.

The management server 20 is a server computer that supports application development. The present embodiment supports the creation of items for game applications. The management server 20 includes a control unit 21 including a CPU, RAM, ROM, and the like, an authority information storage unit 22, an account information storage unit 23, an item management information storage unit 24, and an image storage unit 25. By executing the management program, the control unit 21 functions as an authority management unit 211, an item management unit 212, a display control unit 213, and a history display unit 214.

The authority management unit 211 identifies an access user and executes a process of specifying the authority of this user.
The item management unit 212 executes a process of managing the process of creating an item used in the application.

The display control unit 213 executes management processing of various outputs related to the item image.
The history display unit 214 executes a process of changing and outputting the item image based on the creation history of the item image.

The authority information storage unit 22 records authority information regarding functions and privileges that can be used according to the attributes of each account. This authority information is recorded when the authority is registered. Data related to affiliation and authority are recorded in this authority information.

Information for identifying the affiliation (in this embodiment, the administrator, the developer, and the creator) is recorded in the affiliation data area.
Information about the functions and privileges that can be used for each attribute is recorded in the privilege data area. In this embodiment, the administrator has the authority to create and delete items, edit items, post comments, post reference materials, and the like. Developers have the authority to edit their own items, post comments, post reference materials, etc. The creator has the authority to edit items, post comments, post reference materials, post file checks, and deliver files.

The account information storage unit 23 records account information about a user involved in creating an item. This user information is recorded when the user is registered. In the account information, data regarding the account ID, account attributes, and contacts are recorded.

In the account ID data area, data regarding an identifier for identifying each user is recorded.
In the account attribute data area, data regarding an identifier for identifying the affiliation (management company, development company, creation company) to which this user belongs is recorded.

Data about this user's contacts is recorded in the contact data area. In this embodiment, an e-mail address is used as a contact.
Item management information for managing each item is recorded in the item management information storage unit 24. This item management information is registered when the item to be created is determined, and is updated according to the progress of item creation.

Item management information will be described with reference to FIG. In the item management information, the project information D10 is associated with the company information D01. In the company information D01, data regarding an identifier for identifying the development company that creates the application is recorded. In the project information D10, data regarding an identifier (here, a title) for identifying an application created by this development company is recorded.

A plurality of custom field information D15 is associated with the project information D10. In this custom field information D15, various items (for example, character attribute, rarity, etc.) of items used in this project can be arbitrarily set. Here, the character attribute is a parameter related to the property to which the character belongs, and sets "fire", "water", "darkness", "light", and the like. Based on this character attribute, compatibility with the opponent is determined. The rarity is a parameter representing the rank (for example, rarity value) of the item. For example, if the appearance rate of the character is low, this rarity is increased.

Category information D20 is associated with project information D10. The category information D20 is information for specifying a group for grouping items. The category information D20 includes information on the person in charge and contact information of the management company, the person in charge and contact information of the creation company, and the person in charge of the development company.

In addition, it contains information about viewing authority in the person in charge of the creator. This viewing authority is information for determining the presence / absence of an item and whether or not the item information can be viewed among other creators in charge of the category. This viewing authority includes a normal mode, a name hiding mode, and a hidden mode. In normal mode, the names and items of all creators are displayed. In name hiding mode, items from all creators are displayed, but the names of other creators are hidden. With this name concealment mode, it is possible to check images of different creators and to make the styles consistent. On the other hand, there is an advantage that personal information is not known to other creators. In hidden mode, only your own items are displayed.

Further, the category information D20 includes a notification setting for each person in charge. This notification setting is information for determining the necessity of notification when posting a comment or an image.
Group information D30 is associated with category information D20. Information about the step group used for this category is recorded in the group information D30. A step group is information for identifying a process at the time of item creation. For example, in item creation, a step group including each step of "unstarted, rough drawing, line drawing, coloring, finishing, delivery" can be specified.

Item information D40 is associated with this group information D30.
The item information D40 includes information on the item ID, number, evolution level, character name, and memo. In the present embodiment, each item (for example, a character) is identified based on an item code that combines an "item ID" and a "number". Further, in the aggregate by "item ID" and "number", the transition of the character is identified based on the "evolution level". This evolution level, such as the first level, the second level, and the third level, is originally the same character, but an identifier indicating the degree of evolution is recorded. As the evolution level rises, character growth (transition from children to adults, etc.), various parameters related to battles (attack power, defense power and weapons) are strengthened, and character images and background images are enriched (multicolor, depth and so on). Glossy color scheme) etc. are performed. When various items are set in the custom field information D15, the information corresponding to these items is recorded.

Ball information D50, comment information D60, image information D70, status information D80, and step information D90 are associated with the item information D40.
In the ball information D50, information (account ID) for identifying the current worker for this item is recorded.

The comment information D60 records information about comments posted regarding the item. The comment information D60 includes information on the posting ID, the step at the time of posting, the destination, the content of the comment, the poster, and the posting date and time (registration date and time). Further, a flag for identifying unsuccessful or read is recorded for the destination. An unread flag is recorded at the time of posting, and a read flag is recorded when the destination user views the comment.

Information about the image posted about the item is recorded in the image information D70. In this image information D70, a posting ID, a step at the time of posting, an image type, a destination, an image ID, a poster, and a posting date and time (registration date and time) are recorded. Image types include "check file", "reference image", and "delivery file". The check file is an image uploaded by the creator of the item and is an image for confirmation by the developer or the administrator. The reference image is a file other than the check file, and there is, for example, an image to be referred to when creating an item. A delivery file is an image completed for an item and delivered by the creator. The check file D71, the reference image D72, and the delivery file D73 are recorded in the image storage unit 25 described later.

Information indicating the status at each step of the item is recorded in the status information D80. In this embodiment, a flag indicating any of "working", "OK", and "retake" is recorded. "OK" and "retake" are recorded according to the confirmation result of the confirmer.

In the step information D90, information for identifying the current step is recorded in the step group set for each category. As the steps, for example, unstarted, rough drawing, line drawing, coloring, finishing, delivery and the like are recorded as described above.

Further, each step information D90 is associated with schedule information D91 and priority information D92. Information regarding the start time, deadline, and progress rate of this step is recorded in the schedule information D91. In addition, the priority information D92 records information regarding the priority for this step.
A check file D71, a reference image D72, and a delivery file D73 are recorded in the image storage unit 25 in association with the image ID of the image information D70.

(Item management process)
Next, the item management process will be described with reference to FIG. When creating an item, the administrator uses the client terminal 10 to access the management server 20.

In this case, the control unit 21 of the management server 20 executes the login process (step S100). Specifically, the authority management unit 211 of the control unit 21 acquires an account ID from the client terminal 10 and uses the account information storage unit 23 to specify the access user and the affiliation. Next, the authority management unit 211 uses the authority information storage unit 22 to specify the authority according to the affiliation of the access user. Then, the authority management unit 211 outputs a login screen to the display of the client terminal 10.

As shown in FIG. 6, the login screen 500 includes an upper area 500a and a side area 500b. The upper area 500a and the side area 500b are similarly displayed on each screen described later. The upper area 500a includes a ball number display 501 and a comment number display 502. The number of balls display 501 displays the number of items for which the user has balls. The number of comments display 502 displays the number of comments that the user is destined for and has not yet viewed. In the side area 500b, an icon 503 for designating a title set by the user as a person in charge and an icon 504 for designating each development company are displayed. Further, the login screen 500 includes a ball content display 505 and a comment content display 506. In the ball content display 505, the content related to the item for which the user's account ID is set is displayed in the ball information D50. In the comment content display 506, the summary of the comment in which the account ID of this user is the destination in the comment information D60 and the unread flag is recorded is displayed.

Next, the control unit 21 of the management server 20 executes the title creation process (step S101). Specifically, in the case of an administrator who has the authority to create an item, the authority management unit 211 allows title creation. When creating a title, the application development company is specified by using the icon 504 on the login screen 500, and the title creation is instructed. In this case, the item management unit 212 outputs the title creation screen to the display of the client terminal 10.

As shown in FIG. 7, the title creation screen 510 is provided with a title setting field 511 and a custom field setting field 512. Enter the title (project name) in the title setting field 511. Further, in the custom field setting field 512, various items (for example, character attribute, rarity, etc.) for the item belonging to the title are set. When the create button is selected on the title creation screen 510, the item management unit 212 displays the project information D10 including the title set in the title setting field 511 in the item management information storage unit 24, and the company information D01 of the development company. Record in association with. Further, the item management unit 212 records the custom field information D15 including various items set in the custom field setting field 512 in association with the project information D10.

Next, the control unit 21 of the management server 20 executes the category creation process (step S102). Specifically, the item management unit 212 outputs a category creation screen to the display of the client terminal 10.

As shown in FIG. 8, the category creation screen 520 is provided with person in charge information setting fields 521 to 523 for registering information about the administrator, the creator, and the developer. In the person in charge information setting field 521, the user identifier of the person in charge of the management company and the mail notification setting are registered. In the person in charge information setting field 522, the viewing authority of the creating company, the creating company, the user identifier of the person in charge, and the mail notification setting are registered. In the person in charge information setting field 523, the user identifier of the person in charge of the development company and the necessity of e-mail notification are registered. Further, the category creation screen 520 is provided with a step group designation field 524. When the create button is selected on the category creation screen 520, the item management unit 212 displays the category information D20 including the person in charge information set in the person in charge information setting fields 521 to 523 in the item management information storage unit 24. Record in association with project information D10. Further, the item management unit 212 records the group information D30 including the information regarding the step group designated on the category creation screen 520 in the item management information storage unit 24.

Next, the control unit 21 of the management server 20 executes the item setting process (step S103). Specifically, the item management unit 212 outputs a title screen for item registration to the display of the client terminal 10. The title screen for item registration is output when the item related to the title is not recorded in the item management information storage unit 24.

As shown in FIG. 9, the title screen 530 is provided with a search condition field 531 for searching for items included in the title. Further, the title screen 530 is provided with an individual item registration button and a plurality of item registration buttons. To register items one by one, select the individual item registration button. In this case, the item management unit 212 outputs an individual item creation screen to the display of the client terminal 10. On the other hand, when registering a plurality of items at once, select the multiple item registration button. In this case, the item management unit 212 outputs a plurality of item creation screens to the display of the client terminal 10.

As shown in FIG. 10, the developer, title, and category are displayed on the individual item creation screen 540. The individual item creation screen 540 is provided with item ID, number, evolution level, and character name setting fields 541. Further, a setting field 542 for the item specified in the custom field is provided. The individual item creation screen 540 is provided with a character attribute and rarity setting field 542 based on the custom field information D15. In the step column 543, the first step of the step group is set based on the group information D30. In the ball field 544, the user identifier of the developer is displayed based on the category information D20.

Further, as shown in FIG. 11, the developer, title, and category are displayed on the plurality of item creation screen 550. The multiple item creation screen 550 is provided with each setting field 551 of the item ID, the serial number, and the number of evolution levels. Here, the serial number setting field 551 is used to specify a number range consisting of consecutive numbers according to the number of types of items to be created.

Next, the control unit 21 of the management server 20 executes the empty item generation process (step S104). Specifically, when the create button is selected on the individual item creation screen 540 and the multiple item creation screen 550, the item management unit 212 generates item information D40 (empty item) in which no image is registered, and the item is displayed. Record in the management information storage unit 24. Here, when the individual item creation screen 540 is used, the item management unit 212 generates one item information D40. On the other hand, when the plurality of item creation screen 550 is used, the item management unit 212 generates the item information D40 which is the product of the number of serial numbers and the number of evolution levels. Then, the item management unit 212 outputs a title screen (thumbnail display mode) including an empty item.

As shown in FIG. 12, when the individual item creation screen 540 is used, the display control unit 213 of the control unit 21 outputs a title screen 560 displaying a thumbnail image of one item.

In FIG. 13, when the plurality of item creation screen 550 is used, the display control unit 213 of the control unit 21 outputs a title screen 570 displaying thumbnail images of the plurality of items. On the title screen 570, the number of items obtained by multiplying the number of serial numbers by the number of evolution levels is displayed. Here, on the title screen 570, items having the same item ID and number (item code) and different evolution levels are grouped and grouped and displayed so that they can be distinguished from other groups. This thumbnail display process will be described later with reference to FIG. At the stage where the item is registered using the individual item creation screen 540 and the multiple item creation screen 550, the image of the item is not registered, so the image is not displayed.

Next, the display of the items recorded in the item management information storage unit 24 will be described. The administrator, the developer, and the creator access the management server 20 by using the client terminal 10.

In this case, the control unit 21 of the management server 20 executes the login process in the same manner as in step S100 (step S105). In this case, on the login screen 500 shown in FIG. 6, the icon 503 of the title (project) in which the user is registered as the person in charge is displayed.

Next, the control unit 21 of the management server 20 executes the title selection process (step S106). Specifically, on the login screen 500, the icon 503 with a desired title is selected. In this case, the display control unit 213 of the control unit 21 extracts the item associated with the selected title from the item management information storage unit 24. Further, the display control unit 213 narrows down the extracted items based on the viewing authority of the access user. Specifically, in the case of administrators and developers, all extracted items are targeted. In the case of the creator, the item to be displayed is specified based on the viewing authority set in the category information D20. When the normal mode is set, all the extracted items are displayed. If the name hiding mode is set, hide the names of other creators. This name hiding mode has the advantage that images of different creators can be confirmed, the style and the like can be made consistent, and personal information is not known to other creators. In hidden mode, hide items from other creators.

Next, the control unit 21 of the management server 20 executes the thumbnail display process (step S107). In the thumbnail display process, the thumbnails of each item belonging to this title are displayed in a list. This thumbnail display process will be described later with reference to FIG.

Further, when the list display button is selected on the title screen, the control unit 21 of the management server 20 executes the list display process (step S108). In this case, the display control unit 213 of the control unit 21 outputs the title screen of the list display mode to the display of the client terminal 10.

As shown in FIG. 14, the search condition column 581 and the item list 582 are displayed on the title screen 580 of the list display mode. The search condition field 581 is used when narrowing down the items to be displayed among the items included in this title. In addition, in the item list 582, information about the item is listed by text. In this embodiment, the item code (item ID and number), step, status, character name, priority, deadline, person in charge name, and update date are displayed.

In this title screen 580, a selection box is displayed for each item.
When this selection box is selected and the batch change button is selected, the control unit 21 of the management server 20 executes the batch change support process (step S109). In this case, the item management unit 212 of the control unit 21 outputs the item edit screen to the display of the client terminal 10. On this item edit screen, a plurality of items can be edited at once. It is possible to use the batch change button displayed on the title screen. This item editing screen is provided with a setting field for editing a plurality of items at once. On this item edit screen, setting fields for editing various information related to this item, such as steps, status, balls, deadlines, priorities, rarities, character attributes, types, etc., are provided. The item management unit 212 updates the ball information D50, the status information D80, the step information D90, and the like based on the contents set on the item edit screen.

When the Gantt chart display button is selected on the title screen, the control unit 21 of the management server 20 executes the Gantt chart display process (step S110). In this case, the display control unit 213 of the control unit 21 outputs the title screen of the Gantt chart display mode to the display of the client terminal 10.

As shown in FIG. 15, the search condition column 591 and the Gantt chart 592 are displayed on the title screen 590 of the Gantt chart display mode. The Gantt chart 592 displays the progress and deadline of each step in each item. The process of creating this Gantt chart will be described later with reference to FIG.

A link to the item detail screen is set in the item code displayed on the title screen 570 in the thumbnail display mode and the title screen 580 in the list display mode.

When this link is selected, the control unit 21 of the management server 20 executes the item detail display process (step S111). Specifically, the display control unit 213 of the control unit 21 outputs the item detail screen to the display of the client terminal 10.

As shown in FIG. 16, the item detail screen 600 includes an item image display area 601, various item display areas 602, an evolution item display area 603, and a post list display area 604.
The display control unit 213 identifies the check file image having the latest posting date and time, and outputs a thumbnail image to the item image display area 601.

Information about various items about this item is displayed in the item display area 602. In this embodiment, the item code, evolution level, character name, character attribute, rarity, priority, status, step, deadline, memo, etc. are displayed. Further, in the deadline, a start date and a deadline of each step constituting the step group can be set.

In the evolution item display area 603, thumbnail images of other evolution levels of this item are displayed. Here, the display control unit 213 identifies check file images that are items with the same item code and have different evolution levels. Then, the display control unit 213 specifies a check file image having the latest posting date and time for each evolution level, and outputs a thumbnail image to the evolution item display area 603.

In the post list display area 604, the check file image and the reference image uploaded in each step included in the step group are displayed. Here, the display control unit 213 rearranges the posting date and time in the comment information D60 and the image information D70 in the order of newest and outputs them to the posting list display area 604. In this case, the comment and the image to which the same post ID is given are output in association with each other.

Further, on the item detail screen 600, a back button 605, an edit button 606, a post button 607, and a history display button 608 are displayed.
When the back button 605 is selected, the display control unit 213 returns to the link source screen.

When the edit button 606 is selected, the control unit 21 of the management server 20 executes the item editing process (step S112). Specifically, the item management unit 212 of the control unit 21 outputs the item edit screen to the display of the client terminal 10. When this item edit screen is used, the item management unit 212 acquires change information of the item displayed on the item detail screen 600 and updates each registration information.

When the post button 607 is selected, the control unit 21 of the management server 20 executes the item posting process (step S113). The item management unit 212 of the control unit 21 outputs the item posting screen to the display of the client terminal 10.

As shown in FIG. 17, the item posting screen 610 is provided with step, status, and ball setting fields 611. Further, on the item posting screen 610, an upload button 612, a destination field 613, and a comment field 614 are displayed. In the address field 613, the account ID of the other party who notifies the upload is set. In the comment field 614, enter a message for the other party.

As shown in FIG. 18, when the upload button 612 is selected, the type setting field 615 of the image to be uploaded and the path setting field 616 in which the image is stored are displayed. In the image type setting field 615, one of a check file, a reference image, and a delivery file is selected.

Then, when the post button is selected on the item posting screen 610, the item management unit 212 records the comment information D60 and the image information D70 to which the posting ID is given in association with the item information D40 in the item management information storage unit 24. To do. In this case, the logged-in contributor and the posting date and time are recorded in the comment information D60 and the image information D70. Further, the item management unit 212 records the image (check file, reference image, delivery file) specified on the item posting screen 610 in the image storage unit 25 in association with the posting ID. Further, the item management unit 212 transmits the comment input in the comment field 614 to the destination set in the destination field 613.

When the history display button 608 is selected, the control unit 21 of the management server 20 executes the image history display process (step S114). This process will be described later with reference to FIGS. 19 and 20.

(Thumbnail display processing)
Next, the thumbnail display process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes the group identification process (step S201). Specifically, the display control unit 213 of the control unit 21 identifies an item in which the item ID of the output target is set from the item management information storage unit 24. In this case, it is specified for each number and evolution level. Then, the display control unit 213 generates display columns for the number and the number of evolution levels on the title screen 530.

Next, the control unit 21 of the management server 20 executes color-coding processing for each group (step S202). Specifically, the display control unit 213 of the control unit 21 specifies the display fields to which the same item code is assigned and different evolution levels are set as the same group. Then, on the title screen 570, the display control unit 213 sets a color scheme different from the adjacent display column when it is adjacent to the display column belonging to another group, and when it is adjacent to the display column belonging to the same group. Sets the same color scheme as the adjacent display field. For example, it is assumed that the display fields of item codes "100" to "102" each including a plurality of evolution levels are sequentially adjacent to each other. In this case, each display column of the item code "100" is the first color (white), each display column of the item code "101" is the second color (blue), and each display column of the item code "100" is the first color. As in (white), blue and white are set in stripes for each display field. As a result, for example, when sorting in order of item code, items belonging to the same group are displayed adjacently in the same color, and items in different adjacent groups are displayed in different colors. Can be easily grasped. Also, when sorting by different conditions (for example, item update order), even if they belong to the same group, they are not always displayed adjacent to each other, but it is possible to grasp the groups with the same color scheme. It will be easier.

Next, the control unit 21 of the management server 20 executes the acquisition process of the latest posted image (step S203). Specifically, the display control unit 213 of the control unit 21 acquires the posted image with the latest posting date and time for each number and evolution level from the image storage unit 25. Then, the display control unit 213 generates a thumbnail of the acquired posted image.

Next, the control unit 21 of the management server 20 executes the thumbnail generation process (step S204). Specifically, the display control unit 213 of the control unit 21 outputs the generated thumbnails to each display column.
In FIG. 13, the same background color (shading) is used for items in the same group, and a background color different from that of other adjacent groups is used for display.

(Gantt chart creation process)
Next, the Gantt chart creation process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes the parent item identification process (step S301). Specifically, the display control unit 213 of the control unit 21 identifies the item information D40 associated with this project (title). Then, items having a common item ID and different numbers and evolution levels are specified as parent items.

Next, the control unit 21 of the management server 20 executes the process of specifying the child item of the parent item (step S302). Specifically, the display control unit 213 of the control unit 21 identifies the step information D90 associated with the item information D40. Then, each step (in this embodiment, rough drawing, line drawing, coloring, finishing, delivery) is specified as a child item.

Next, the control unit 21 of the management server 20 executes the acquisition process of the progress information of the child items (step S303). Specifically, the display control unit 213 of the control unit 21 acquires the schedule information D91 associated with the step information D90. Then, a bar corresponding to the progress information is displayed on the child item on the Gantt chart.

Next, the control unit 21 of the management server 20 executes the progress display process of the parent-child item (step S304). Specifically, the display control unit 213 of the control unit 21 divides the total value of the progress rate of the child items by the number of child items to calculate the progress rate of the parent item.

(Image history display processing)
Next, the image history display process will be described with reference to FIGS. 19 and 20. The image history display process is executed when the history display button 608 is selected on the item detail screen 600.

First, the control unit 21 of the management server 20 executes the item identification process (step S401). Specifically, the history display unit 214 of the control unit 21 identifies the item to be history-displayed by using the item ID and the number of the item detail screen 600.

Next, the control unit 21 of the management server 20 executes the acquisition process of all the check images (step S402). Specifically, the history display unit 214 of the control unit 21 extracts all the check files in which the item ID and the number are set from the image storage unit 25. Then, the history display unit 214 acquires the image (check image) of the called check file.

Next, the control unit 21 of the management server 20 executes the slide display process (step S403). Specifically, the history display unit 214 of the control unit 21 arranges the check images in the upload order (posting date and time order). Then, the history display unit 214 outputs the history display screen to the display of the client terminal 10.

As shown in FIG. 20, the history display screen 700 includes a page turning button 701 and an image display area 702. The history display unit 214 outputs check files to the image display area 702 in the order of the creation steps in order to the history display screen in response to the change operation by selecting the page turning button 701. Here, each check file for rough drawing (1), rough drawing (2), line drawing (1), line drawing (2), coloring, ... Finishing is recorded in the image storage unit 25 according to the registration date and time. If so, the check file images are output to the image display area 702 in the order of upload. When this page turning button 701 is selected, it is desirable to change the original image and the next image within the time when the afterimage effect is visually produced. For example, since the time resolution of the human eye is about 50 ms to 100 ms, it is easy to perceive the change by changing the time in a time shorter than this time.

According to the above embodiment, the following effects can be obtained.
(1) In the above embodiment, the control unit 21 of the management server 20 executes the title creation process (step S101). Here, the custom field information D15 is acquired. As a result, common items such as character attributes can be set in the items included in this title.

(2) In the above embodiment, the control unit 21 of the management server 20 executes the category creation process (step S102). Here, the person in charge information including the setting of the viewing authority is acquired, and the category information D20 including the person in charge information is recorded. As a result, the viewing authority can be efficiently set according to the user for each title.

Further, the group information D30 including the information about the step group is recorded. As a result, even if the title contains a plurality of items, the item creation process can be determined in common.

(3) In the above embodiment, the control unit 21 of the management server 20 executes the item setting process (step S103). Here, the individual item creation screen 540 and the plurality of item creation screen 550 are used. Then, the control unit 21 of the management server 20 executes the empty item generation process (step S104). As a result, items can be registered individually, or a plurality of items can be registered together.

(4) In the above embodiment, the control unit 21 of the management server 20 executes the title selection process (step S106). When the normal mode is set, all the extracted items are displayed. If the name hiding mode is set, hide the names of other creators. In hidden mode, hide items from other creators. This allows all information about the item to be shared in normal mode. In the name hiding mode, information of different creators such as competitors can be hidden. In this case, by looking at the items of different creators, it is possible to match the consistency (world view) of the style etc. even if the creators are different. In the hidden mode, information sharing of the item image itself can be restricted.

(5) In the above embodiment, the control unit 21 of the management server 20 executes the thumbnail display process (step S107). Here, the control unit 21 of the management server 20 executes color-coding processing for each group (step S202). As a result, it is possible to accurately grasp related images in a plurality of items. Further, the control unit 21 of the management server 20 executes the acquisition process of the most recently posted image (step S203). Here, since the items are grouped and displayed according to the evolution level, the status of the item image can be grasped in the process of creating the related item. Further, in the grouped items, the balance of the item images (richness of the character image and the background image) according to the evolution level can be grasped.

(6) In the above embodiment, the control unit 21 of the management server 20 executes the list display process (step S108). When this selection box is selected and the batch change button is selected, the control unit 21 of the management server 20 executes the batch change support process (step S109). This makes it possible to edit information about a plurality of items at once.

(7) In the above embodiment, when the Gantt chart display button is selected, the control unit 21 of the management server 20 executes the Gantt chart display process (step S110). In this case, the control unit 21 of the management server 20 executes the child item identification process (step S302) of the parent item, the child item progress information acquisition process (step S303), and the parent-child item progress display process (step S304). To do. This makes it possible to grasp not only the progress information of related items but also the status of the individual item creation process in a list.

(8) In the above embodiment, the control unit 21 of the management server 20 executes the item detail display process (step S111). The display control unit 213 identifies the check file image having the latest posting date and time, and outputs a thumbnail image to the item image display area 601. This makes it possible to grasp the creation status of the item image. Further, the display control unit 213 displays thumbnail images of other evolution levels of this item. This makes it possible to grasp the creation status of related items. Further, the display control unit 213 rearranges the posting date and time in the comment information D60 and the image information D70 in the order of newest and outputs the post list display area 604. This makes it possible to grasp the process of creating the item.

(9) In the above embodiment, the control unit 21 of the management server 20 executes the image history display process (step S114). Here, the control unit 21 of the management server 20 executes the acquisition process of all the check images (step S402). The slide display process is executed (step S403). This makes it possible to grasp changes in the item image during the creation process. In particular, since the posted check image is output to a specific image display area, the change can be easily grasped by the image change operation.

The above embodiment may be changed as follows.
-In the above embodiment, the control unit 21 of the management server 20 executes a thumbnail display process (step S107), a list display process (step S108), and a Gantt chart display process (step S110). Here, the progress status of the related item may be output as an image. In this case, the display control unit 213 of the control unit 21 acquires the item code to be displayed from the client terminal 10. Then, the display control unit 213 acquires the image with the latest posting date and time in each step for all the items related to this item. Then, the display control unit 213 outputs the history display screen to the display of the client terminal 10.

As shown in FIG. 21, the history display screen 710 arranges related items on the first axis (for example, the horizontal axis) and arranges each step on the second axis (vertical axis). Then, the latest check image is output in the matrix of the first axis and the second axis. As a result, the images of related items can be compared in the first axis direction, and the progress status can be grasped in the second axis direction.

-In the above embodiment, the control unit 21 of the management server 20 executes the thumbnail display process (step S107). Here, the step and status of this image may be output in association with the thumbnail image. In this case, the display control unit 213 of the control unit 21 outputs the latest step or status recorded in the image information D70 to the title screen of the thumbnail display mode.
As shown in FIG. 22, the title screen 720 in the thumbnail display mode includes the step display 711 and the status display 712.

-In the above embodiment, the control unit 21 of the management server 20 executes the Gantt chart display process (step S110). In this Gantt chart, thumbnail images of each item may be output.

-In the above embodiment, the control unit 21 of the management server 20 executes the image history display process (step S114). In this case, the page turning button 701 is output to the display of the client terminal 10 on the history display screen 700 including the image display area 702. Here, the status may be output.

As shown in FIG. 23, on the history display screen 700, the status display 704 of the image displayed in the image display area 702 is output. As a result, not only the change of the image but also the confirmation result of this image can be grasped.

When the page turning button 701 is selected, the original image and the next image are displayed repeatedly at a predetermined time interval (for example, 1 second) a predetermined number of times (for example, 5 times), and then the next image is displayed. You may try to. The repeated display makes it easier to grasp the changed part.

-In the above embodiment, in the image history display process, the control unit 21 of the management server 20 executes all check image acquisition processes (step S402) and slide display process (step S403). Here, the developer may be able to write a correction instruction (in red) on the image of the check file in the feedback. In this case, the control unit 21 of the management server 20 assigns a posting ID to this feedback and records it in the item management information storage unit 24. Further, the control unit 21 of the management server 20 records the image information D70 in which the image ID is given to the image in which the correction instruction is written in the check file. In this case, the image in which the correction instruction is written is recorded in the image storage unit 25 as a check file (with correction instruction). Then, in the image history display process, the page is turned in the order of the check file image and the check file (with correction instruction) image. As a result, the correction instruction given in the feedback can be grasped in the image history display process.

-In the above embodiment, in the thumbnail display process, the control unit 21 of the management server 20 executes a color-coded process for each group (step S202). Here, if it is adjacent to a display field belonging to another group, set a different color scheme from the adjacent display field, and if it is adjacent to a display field belonging to the same group, use the same color scheme as the adjacent display field. Set. As a result, the background colors are displayed in a striped pattern of two colors in which the background colors are alternately different for each adjacent group. Here, the items forming the group may be set to different colors. For example, the control unit 21 of the management server 20 sets the display fields to the first color (white) and the second color (blue) in order when items belonging to different groups are individually adjacent to each other. Further, when the items belonging to the same group are adjacent to each other, the control unit 21 of the management server 20 sets the display fields of both to the third color (yellow). This makes it easy to recognize items belonging to the same group even if the background color is different each time depending on the sorting order at the time of sorting.

Next, the technical idea that can be grasped from the above embodiment and another example will be added below.
[1]
A system that manages items
According to the item creation step, the item image of the item associated with the search key, the creation step, the storage unit that records the information for determining whether or not to browse, and the storage unit.
Equipped with a control unit connected to the client terminal
The control unit
Identify the viewing authority based on the user information acquired from the client terminal,
Obtain the search key from the client terminal and
All the item images associated with the search key are acquired from the storage unit, and a display screen for displaying a list of item images that can be viewed with the viewing authority is generated.
An item management system characterized by outputting the display screen to the client terminal.
[2]
The item management system according to claim 1, wherein the creator information is displayed according to the viewing authority in the list display of the display screen.
[3]
When the viewing authority of the client terminal is the first authority, a display screen displaying the creator is generated together with the acquired item image, and when the viewing authority of the client terminal is the second authority, the creator. The item management system according to claim 2, wherein a display screen for displaying the acquired item image is generated without displaying.
[4]
The item image is associated with an item creation step for each project for creating a plurality of items, and step information indicating the degree of progress of the creation step is recorded in the storage unit.
The control unit
Obtain information about the project from the client terminal
Identify the item image belonging to the project as the parent item and
Identify the child item associated with the parent item creation step and
The item according to any one of claims 1 to 3, wherein a screen showing the degree of progress of the parent item, which integrates the progress of the child item and the progress of the child item, is generated based on the step information. The item management system described.
[5]
The item management system according to any one of claims 1 to 4, wherein an evolutionary form is specified for each item, and items having different evolutionary forms are associated with each other.
[6]
A way to manage items
The item management system has a storage unit that records the item image of the item associated with the search key, the creation step, and information for determining whether or not the item can be viewed according to the item creation step.
Equipped with a control unit connected to the client terminal
The control unit
Identify the viewing authority based on the user information acquired from the client terminal,
Obtain the search key from the client terminal and
All the item images associated with the search key are acquired from the storage unit, and a display screen for displaying a list of item images that can be viewed with the viewing authority is generated.
An item management method characterized by outputting the display screen to the client terminal.
[7]
A program that manages items
The item management system has a storage unit that records the item image of the item associated with the search key, the creation step, and information for determining whether or not the item can be viewed according to the item creation step.
Equipped with a control unit connected to the client terminal
In the control unit
Identify the viewing authority based on the user information acquired from the client terminal,
Obtain the search key from the client terminal and
All the item images associated with the search key are acquired from the storage unit, and a display screen for displaying a list of item images that can be viewed with the viewing authority is generated.
An item management program characterized by outputting the display screen to the client terminal.

10 ... Client terminal, 20 ... Management server, 21 ... Control unit, 211 ... Authority management unit, 212 ... Item management unit, 213 ... Display control unit, 214 ... History display unit, 22 ... Authority information storage unit, 23 ... User information Storage unit, 24 ... Item management information storage unit, 25 ... Image storage unit, 700 ... History display screen.

Claims (10)

A system that manages items
An item image that multiple users work on, a creation step, and a storage unit that records account information that identifies the user who works in the latest creation step in association with each other.
Equipped with a control unit connected to the client terminal
The control unit
Obtain the account information entered by the user from the client terminal,
Among a plurality of item images associated with account information that identifies a user who performs work, the number of item images in which the account information input by the user matches the account information that identifies the user who performs work and the above. Get the content about the item image and
An item management system that outputs the number of item images and the contents related to the item images to the client terminal. The item image for each creation step is stored in the storage unit.
The control unit
The identification information of the item image is acquired from the client terminal,
The item images of all the creation steps associated with the acquired identification information are acquired from the storage unit.
The item management system according to claim 1, wherein the acquired item image is output to the client terminal in the order of the creation steps. In the storage unit, the item image for each level that transitions as the application in which the item image is used progresses is stored.
The control unit
The identification information of the item image is acquired from the client terminal,
All the item images of the above level associated with the acquired identification information are acquired from the storage unit.
The item management system according to claim 1, wherein the acquired item image is output to the client terminal. In the storage unit, the item image for each evolution level that transitions as the game application in which the item image is used progresses is stored.
The item according to claim 3, wherein the control unit acquires all the item images of the evolution level associated with the acquired identification information from the storage unit, and outputs the acquired item images to the client terminal. Management system. The item image is stored in the storage unit in association with an item code indicating an aggregate and information about the project.
The control unit
Obtain information about the project from the client terminal and
The item image associated with the information about the project is acquired from the storage unit.
In any one of claims 1 to 4, when item images belonging to the different aggregates are adjacent to each other on the display screen displayed on the client terminal, the display for identifying the different aggregates is set. The item management system described. The item image is stored in the storage unit in association with information about the project and a search key.
The control unit
Obtain information about the project and a search key from the client terminal,
The item management system according to any one of claims 1 to 5, which acquires information about the project and the item image associated with the search key from the storage unit and outputs the information to the client terminal. The control unit
When it is determined whether or not the viewing authority of the user associated with the account information is the authority to display the creator information of the item image, and the viewing authority is the authority to display the creator information. The item image and the creator information are output to the client terminal, and when the viewing authority is the authority that cannot display the creator information, the item image is output to the client terminal and the creator information is output. The item management system according to any one of claims 1 to 6, wherein the item is not output to the client terminal. The item image is associated with an item creation step for each project for creating a plurality of items, and step information indicating the degree of progress of the creation step is recorded in the storage unit.
The control unit
Obtain information about the project from the client terminal
Identify the item image belonging to the project as the parent item and
Identify the child item associated with the parent item creation step and
The item management system according to any one of claims 1 to 7, which generates a screen showing the degree of progress of the parent item by integrating the progress of the child item and the progress of the child item based on the step information. .. A way to manage items
The item management system has a storage unit in which an item image in which multiple users work, a creation step, and account information that identifies a user who works in the latest creation step are recorded in association with each other.
Equipped with a control unit connected to the client terminal
The control unit
Obtain the account information entered by the user from the client terminal,
From a plurality of item images associated with account information that identifies a user who performs work, the number of item images in which the account information input by the user matches the account information that identifies the user who performs work and the above. Get the content about the item image and
An item management method for outputting the number of item images and the contents related to the item images to the client terminal. A program that manages items
The item management system has a storage unit in which an item image in which multiple users work, a creation step, and account information that identifies a user who works in the latest creation step are recorded in association with each other.
Equipped with a control unit connected to the client terminal
In the control unit
Obtain the account information entered by the user from the client terminal,
Among a plurality of item images associated with account information that identifies a user who performs work, the number of item images in which the account information input by the user matches the account information that identifies the user who performs work and the above. Get the content about the item image and
An item management program that outputs the number of item images and the contents related to the item images to the client terminal.