JP6646708B2 - 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 creation of items used in an application.

  In a system development or the like including tasks related to each other, a project in which a plurality of organizations participate may be performed. A project management system that visually represents the progress of the project has been studied (for example, see Patent Document 1). The project management system described in this document uses a reference document that is referred to when a project is performed and a document management database that manages an output document created. Furthermore, at the time of project planning, an empty entity of an output document to be created in each step 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 of the project is managed. This project management system displays, for each process, a process name, a title bar corresponding to the length of the schedule of the process, and a progress bar indicating the progress of the process in association with each other. Visually output the progress status of which is in charge.

  In addition, technologies for providing various games are being studied today (for example, see Patent Document 2). According to the technology described in this document, not a completed item, but a plurality of unfinished items up to a completed item are prepared, and the plurality of unfinished items are presented to the user, so that the user can obtain the item. The motivation is improved, and thereby the rate of leaving the user of the card game is reduced.

JP 2003-141320 A Japanese Patent No. 5401627

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

  The present invention has been made in view of the above-described problems, and has as its object to provide 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 for an application. Is to provide.

  (1) An item management system that solves the above-mentioned problem is a system that manages items, and stores an item ID in which an item ID, an evolution level, and a step are associated with each other, and step information on a progress rate of the step. And a control unit connected to a client terminal, wherein the control unit specifies items having the same item ID and different evolution levels as parent items, and each of the items having the same item ID and the same evolution level. The step is specified as a child item, the progress rate of the specified child item is obtained from the storage unit, and the progress of the parent item is specified and displayed based on the progress rate of the child item.

  (2) In the item management system, the control unit divides a value obtained by summing a progress rate of the child item having the same item ID and the evolution level of the parent item, the item ID, and the evolution level by the number of the child items. The progress rate of the parent item is calculated, a bar corresponding to the progress information of the child item is displayed on the Gantt chart, and the parent item of the child item is displayed on the Gantt chart over the progress rate of the child item. Is preferably displayed.

  (3) In the item management system, it is preferable that the control unit outputs a thumbnail image of the child item in the Gantt chart.

  According to the present invention, the creation of a plurality of items used for an application can be managed efficiently and accurately.

FIG. 1 is a system schematic diagram of the embodiment. FIG. 4 is an explanatory diagram of data used in the embodiment. FIG. 4 is an explanatory diagram of a processing procedure according to the embodiment. FIG. 4 is an explanatory diagram of a processing procedure according to the embodiment. FIG. 4 is an explanatory diagram of a processing procedure according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 4 is an explanatory diagram of a processing procedure according to the embodiment. FIG. 4 is an explanatory diagram of an output screen according to the embodiment. FIG. 11 is an explanatory diagram of an output screen according to another embodiment. FIG. 11 is an explanatory diagram of an output screen according to another embodiment. FIG. 11 is an explanatory diagram of an output screen according to another embodiment.

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

  The administrator belongs to an application management company, and creates an application concept, and manages, operates, and checks the quality of the entire application. The developer belongs to the application development company (developer), and creates items to be used for the application together with the administrator. The creator (designer) belongs to a content creation company, and creates an item image (asset) of the created item together with the developer. When an item image is created, for example, a creation step (process) such as rough drawing, line drawing, coloring, finishing, inspection, and delivery is performed. The creator creates an item image (check file) in each step and posts it to the management server 20. Then, the developer uses the management server 20 to check the posted check file, and feeds back the check result. With this feedback, the developer makes a determination of “OK (approval)” and “retake (redo)”. The creator modifies the item as necessary based on the developer's feedback. Note that 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, the administrator has a role as a developer.

  For creating an item, an administrator, a developer, and a creator use the 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 (such as a touch panel display). Further, the client terminal 10 includes a control unit including a CPU, a RAM, a ROM, and the like. In the present embodiment, each client terminal 10 includes a browser program, and accesses the management server 20 using the browser started by the program.

  The management server 20 is a server computer that supports application development. In the present embodiment, creation of items for the game application is supported. The management server 20 includes a control unit 21 including a CPU, a RAM and a ROM, 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. 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 by executing the management program.

The authority management unit 211 identifies the access user and executes a process of identifying the authority of this user.
The item management unit 212 executes a process of managing a creation process of an item used for an application.

The display control unit 213 performs 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.

  In the authority information storage unit 22, authority information on usable functions and authority is recorded according to the attribute of each account. This authority information is recorded when the authority is registered. In this authority information, data on affiliation and authority are recorded.

In the affiliation data area, information for identifying the affiliation (in this embodiment, an administrator, a developer, or a creator) is recorded.
In the authority data area, information on functions and authority that can be used in each attribute is recorded. In the present 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, and submit reference materials. The creator has the authority to edit the company's items, post comments, post reference materials, post file checks, and deliver files.

  The account information storage unit 23 records account information relating to a user involved in the creation of an item. This user information is recorded when the user is registered. In the account information, data relating to an account ID, account attributes, and contact information are recorded.

In the account ID data area, data on an identifier for identifying each user is recorded.
In the account attribute data area, data relating to an identifier for specifying the affiliation (management company, development company, creation company) to which this user belongs is recorded.
In the contact data area, data on the contact information of this user is recorded. In this embodiment, a mail address is used as a contact.

  The item management information storage unit 24 records item management information for managing each item. The item management information is registered when an item to be created is determined, and is updated according to the progress of the item creation.

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

  A plurality of custom field information D15 is associated with this project information D10. In the custom field information D15, it is possible to arbitrarily set various items (for example, character attributes, rarity, etc.) of the items used in this project. Here, the character attribute is a parameter relating to the property to which the character belongs, and sets “fire”, “water”, “darkness”, “light”, and the like. Compatibility with the opponent is determined based on the character attribute. The rarity is a parameter indicating the rank (for example, rare value) of the item. For example, when the appearance rate of the character is low, the rarity is increased.

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

  Further, it includes information on the viewing authority of the person in charge of the creating company. The browsing authority is information for judging the presence / absence of an item and the availability of browsing of item information between other creators in charge of a category. The browsing authority includes a normal mode, a name hiding mode, and a non-display mode. In the normal mode, the names and items of all creators are displayed. In the name hiding mode, items of all creators are displayed, but the names of other creators are hidden. In the name concealment mode, images of different creators can be confirmed, and consistency in style and the like can be achieved. On the other hand, there is an advantage that personal information is not known to other creators. In the non-display mode, only items of the company are displayed.

Further, the category information D20 includes a notification setting for each person in charge. This notification setting is information for determining whether or not notification is necessary when posting a comment or an image.
The group information D30 is associated with the category information D20. In the group information D30, information on the step group used for this category is recorded. The step group is information for specifying a process at the time of item creation. For example, in the item creation, a step group including each step of “not yet started, rough drawing, line drawing, coloring, finishing, delivery” can be designated.

This group information D30 is associated with item information D40.
The item information D40 includes information on an item ID, a number, an evolution level, a character name, and a memo. In the present embodiment, each item (for example, a character) is identified based on an item code obtained by combining an “item ID” and a “number”. Further, a transition of the character is identified based on the “evolution level” in the aggregate of “item ID” and “number”. The evolution level is the same as the original character, such as the first level, the second level, and the third level, but an identifier indicating the degree of the evolution is recorded. As the evolution level rises, character growth (transition from children to adults, etc.), reinforcement of various parameters (attack, defense, weapons, etc.) related to battles, and enrichment of character images and background images (multicolor, depth, (A glossy color scheme) and the like. When various items are set in the custom field information D15, information corresponding to these items is recorded.

The item information D40 is associated with ball information D50, comment information D60, image information D70, status information D80, and step information D90.
In the ball information D50, information (account ID) for specifying a current worker in charge of this item is recorded.

  In the comment information D60, information on a comment posted on the item is recorded. The comment information D60 includes information on the post ID, the step at the time of posting, the destination, the content of the comment, the poster, and the posting date (registration date). Further, a flag is recorded for the destination to identify whether it is unconnected or read. An unread flag is recorded at the time of posting, and a read flag is recorded when the destination user views the comment.

  In the image information D70, information on an image posted on the item is recorded. In the image information D70, a post ID, a post step, an image type, a destination, an image ID, a contributor, and a post date / time (registration date / time) are recorded. The image type includes “check file”, “reference image”, and “delivery file”. The check file is an image uploaded by the creator of the item and is an image to be confirmed by the developer or the administrator. The reference image is a file other than the check file, and includes, for example, an image used as a reference when creating an item. The delivery file is an image completed for the 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 25 described later.

  In the status information D80, information indicating the status of each step of the item is recorded. In the present 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 specifying a current step in a step group set in categories is recorded. As the steps, for example, unstarted, rough drawing, line drawing, coloring, finishing, delivery, and the like are recorded as described above.

  Further, schedule information D91 and priority information D92 are associated with each step information D90. The schedule information D91 records information on the start time, deadline, and progress rate of this step. In the priority information D92, information on the priority for this step is recorded.

  The check file D71, the reference image D72, and the delivery file D73 are recorded in the image storage unit 25 in association with the image ID of the image information D70.

(Item management processing)
Next, the item management processing will be described with reference to FIG. When creating an item, the administrator accesses the management server 20 using the client terminal 10.
In this case, the control unit 21 of the management server 20 executes a login process (Step S100). Specifically, the authority management unit 211 of the control unit 21 acquires the account ID from the client terminal 10 and specifies the access user and the affiliation using the account information storage unit 23. Next, the authority management unit 211 uses the authority information storage unit 22 to specify the authority according to the access user's affiliation. Then, the authority management unit 211 outputs a login screen on 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 that the user has a ball. The comment number display 502 displays the number of comments that have been addressed to this user and have 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. The login screen 500 includes a ball content display 505 and a comment content display 506. The ball content display 505 displays, in the ball information D50, the content of the item for which the user's account ID is set. The comment content display 506 displays an outline of a comment in which the account ID of this user is the destination and the unread flag is recorded in the comment information D60.

  Next, the control unit 21 of the management server 20 executes a title creation process (Step S101). Specifically, in the case of an administrator who has the authority to create items, the authority management unit 211 allows title creation. When creating a title, the application development company is specified using the icon 504 on the login screen 500, and the creation of the title is instructed. In this case, the item management unit 212 outputs a 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 column 511 and a custom field setting column 512. In the title setting field 511, a title (project name) is input. Further, in the custom field setting column 512, various items (for example, character attributes, rarity, etc.) of items belonging to the title are set. When the create button is selected on the title creation screen 510, the item management unit 212 stores the project information D10 including the title set in the title setting column 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 custom field information D15 including various items set in the custom field setting column 512 in association with the project information D10.

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

  As shown in FIG. 8, the category creation screen 520 is provided with staff information setting fields 521 to 523 for registering information on administrators, creators, and developers. In the clerk information setting column 521, a user identifier and a mail notification setting of a clerk of the management company are registered. In the person in charge information setting column 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. The user ID of the person in charge of the development company and the necessity of mail notification are registered in the person in charge information setting column 523. Further, a step group designation field 524 is provided on the category creation screen 520. When the create button is selected on the category creation screen 520, the item management unit 212 stores the category information D20 including the clerk information set in the clerk information setting fields 521 to 523 in the item management information storage unit 24. The information is recorded in association with the project information D10. Further, the item management unit 212 records, in the item management information storage unit 24, group information D30 including information on the step group specified on the category creation screen 520.

  Next, the control unit 21 of the management server 20 executes an item setting process (Step S103). Specifically, the item management unit 212 outputs a title screen for item registration on the display of the client terminal 10. The title screen for item registration is output when an 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 column 531 for searching for an item included in the title. Further, the title screen 530 is provided with an individual item registration button and a multiple item registration button. To register items individually one by one, select the individual item registration button. In this case, the item management unit 212 outputs an individual item creation screen on the display of the client terminal 10. On the other hand, when registering a plurality of items collectively, a plurality of items registration button is selected. In this case, the item management unit 212 outputs a multiple item creation screen to the display of the client terminal 10.

  As shown in FIG. 10, the individual item creation screen 540 displays a developer, a title, and a category. The individual item creation screen 540 is provided with setting fields 541 for item ID, number, evolution level, and character name. Further, a setting field 542 for an item designated as a custom field is provided. The individual item creation screen 540 is provided with character attribute and rarity setting columns 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. The ball column 544 displays a developer user identifier based on the category information D20.

  In addition, as shown in FIG. 11, on the multiple item creation screen 550, a developer, a title, and a category are displayed. The multiple item creation screen 550 is provided with setting columns 551 for an item ID, a serial number, and the number of evolution levels. Here, using the serial number setting column 551, a number range consisting of consecutive numbers is designated according to the number of types of items to be created.

  Next, the control unit 21 of the management server 20 executes an empty item generation process (Step S104). Specifically, when a 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 information is recorded 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 multiple item creation screen 550 is used, the item management unit 212 generates item information D40 in a number obtained by multiplying the number of serial numbers by the number of evolution levels. Then, the item management unit 212 outputs a title screen (thumbnail display mode) including empty items.

  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 multiple 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 a plurality of items. The title screen 570 displays the number of items obtained by multiplying the serial number and the evolution level. 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 as to be distinguished from other groups. This thumbnail display processing will be described later with reference to FIG. When an item is registered using the individual item creation screen 540 and the multiple item creation screen 550, no image of the item is registered and no image is displayed.

  Next, the display of 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 using the client terminal 10.

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

  Next, the control unit 21 of the management server 20 executes a title selection process (Step S106). Specifically, on the login screen 500, an icon 503 of 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 an administrator or a developer, all extracted items are targeted. In the case of the creator, the item to be displayed is specified based on the browsing authority set in the category information D20. When the normal mode is set, all extracted items are to be displayed. If the name hiding mode is set, the names of other creators are hidden. This name concealment mode has the advantage that it is possible to confirm images and the like of different creators, to ensure consistency in style and the like, and that other creators do not know personal information. In the non-display mode, items of other creators are hidden.

  Next, the control unit 21 of the management server 20 executes a thumbnail display process (Step S107). In the thumbnail display processing, a list of thumbnails of each item belonging to this title is displayed. This thumbnail display processing 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 a list display process (step S108). In this case, the display control unit 213 of the control unit 21 outputs the title screen in the list display mode to the display of the client terminal 10.

  As shown in FIG. 14, a search condition column 581 and an item list 582 are displayed on the title screen 580 in the list display mode. The search condition column 581 is used to narrow down items to be displayed among the items included in the title. In the item list 582, information on items is displayed as a list in text. In the present embodiment, an item code (item ID and number), step, status, character name, priority, time limit, person in charge, and update date are displayed.

On the title screen 580, a selection box is displayed for each item.
When the selection box is selected and the batch change button is selected, the control unit 21 of the management server 20 executes a batch change support process (Step S109). In this case, the item management unit 212 of the control unit 21 outputs an item editing screen to the display of the client terminal 10. On this item editing screen, a plurality of items can be edited collectively. Note that the batch change button displayed on the title screen can be used. The item edit screen is provided with a setting column for editing a plurality of items collectively. On the item editing screen, there are provided setting columns for editing various information related to the item, for example, step, status, ball, time limit, priority, rarity, character attribute, type, and the like. 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 editing screen.

  When the Gantt chart display button is selected on the title screen, the control unit 21 of the management server 20 executes a 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, a search condition column 591 and a Gantt chart 592 are displayed on the title screen 590 in the Gantt chart display mode. The Gantt chart 592 displays the progress of each step in each item and the deadline. This Gantt chart creation processing will be described later with reference to FIG.

  The item code displayed on the title screen 570 in the thumbnail display mode or the title screen 580 in the list display mode has a link to the item detail screen.

  When this link is selected, the control unit 21 of the management server 20 executes an 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 specifies the check file image with the latest posting date and time, and outputs a thumbnail image to the item image display area 601.

  The item display area 602 displays information on various items for this item. In the present embodiment, an item code, an evolution level, a character name, a character attribute, a rarity, a priority, a status, a step, a deadline, a memo, and the like are displayed. Furthermore, in the term, a start date and a term 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 specifies check file images that have the same item code and different evolution levels. Then, the display control unit 213 specifies, for each evolution level, the check file image with the latest posting date and time, 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 a new order and outputs the rearranged date to the posting list display area 604. In this case, the comment and the image to which the same post ID is assigned are output in association with both.

Further, a return button 605, an edit button 606, a post button 607, and a history display button 608 are displayed on the item detail screen 600.
When the return 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 an item editing process (Step S112). Specifically, the item management unit 212 of the control unit 21 outputs an item editing screen to the display of the client terminal 10. When this item edit screen is used, the item management unit 212 acquires the 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 an item posting process (Step S113). The item management unit 212 of the control unit 21 outputs an item posting screen to the display of the client terminal 10.

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

  As shown in FIG. 18, when the upload button 612 is selected, a type setting column 615 of the image to be uploaded and a path setting column 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 post ID has been assigned in the item management information storage unit 24 in association with the item information D40. I do. In this case, the logged-in poster and the posted date and time are recorded in the comment information D60 and the image information D70. Furthermore, 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 column 614 to the destination set in the destination column 613.

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

(Thumbnail display processing)
Next, the thumbnail display processing will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes a group specifying process (Step S201). Specifically, the display control unit 213 of the control unit 21 specifies, from the item management information storage unit 24, the item for which the output target item ID is set. 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 performs a color coding process for each group (Step S202). Specifically, the display control unit 213 of the control unit 21 specifies display fields to which the same item code is assigned and different evolution levels are set as the same group. Then, when the title screen 570 is adjacent to a display column belonging to another group, the display control unit 213 sets a color scheme different from that of the adjacent display column. Sets the same color scheme as the adjacent display column. For example, it is assumed that display columns of item codes “100” to “102” each including a plurality of evolution levels are sequentially adjacent. In this case, each display column of the item code "100" is a first color (white), each display column of the item code "101" is a second color (blue), and each display column of the item code "100" is a first color. As shown in (white), blue and white are set in stripes for each display column. Thus, for example, when the items are rearranged in the order of the item codes, the items belonging to the same group are displayed adjacently in the same color, and the items in another group adjacent thereto are displayed in a different color. Can be easily grasped. Also, when rearranged according to another condition (for example, item update order), even if they belong to the same group, they are not necessarily displayed adjacent to each other. It will be easier.

  Next, the control unit 21 of the management server 20 executes a process of acquiring the latest posted image (Step S203). Specifically, the display control unit 213 of the control unit 21 acquires, from the image storage unit 25, a posted image with the latest posted date and time for each number and evolution level. 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 a thumbnail generation process (Step S204). Specifically, the display control unit 213 of the control unit 21 outputs the generated thumbnail to each display column.
In FIG. 13, items of the same group are displayed using the same background color (shaded) and different background colors from those of other adjacent groups.

(Gantt chart creation processing)
Next, a Gantt chart creation process will be described with reference to FIG.
First, the control unit 21 of the management server 20 executes a parent item specifying process (Step S301). Specifically, the display control unit 213 of the control unit 21 specifies the item information D40 associated with the 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 a process of specifying a child item of the parent item (Step S302). Specifically, the display control unit 213 of the control unit 21 specifies the step information D90 associated with the item information D40. Then, each step (in the present 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 a process of acquiring the progress information of the child item (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 for the child item on the Gantt chart.

  Next, the control unit 21 of the management server 20 executes a progress display process of the parent-child item (Step S304). Specifically, the display control unit 213 of the control unit 21 calculates the progress rate of the parent item by dividing the sum of the progress rates of the child items by the number of child items.

(Image history display processing)
Next, the image history display processing will be described with reference to FIGS. 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 an item specifying process (Step S401). Specifically, the history display unit 214 of the control unit 21 specifies an item for which a history is to be displayed using the item ID and the number on the item detail screen 600.

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

  Next, the control unit 21 of the management server 20 executes a slide display process (Step S403). Specifically, the history display unit 214 of the control unit 21 arranges the check images in the upload order (post date order). Then, the history display unit 214 outputs a 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 sequentially outputs check files to the image display area 702 in the order of the creation steps on the history display screen in response to a change operation by selecting the page turning button 701. Here, in the image storage unit 25, each check file of rough image (1), rough image (2), line image (1), line image (2), coloring,... If there is, the check file images are output to the image display area 702 in the order of upload. When the page turning button 701 is selected, it is desirable to change the original image and the next image within a time period in which the afterimage effect visually occurs. For example, since the temporal resolution of human eyes is about 50 ms to 100 ms, it is easy to perceive the change by changing the time in a shorter 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 a title creation process (Step S101). Here, the custom field information D15 is obtained. Thereby, common items such as character attributes can be set for the items included in the title.

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

  Further, group information D30 including information on the step group is recorded. Thereby, even when a title includes 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 an item setting process (Step S103). Here, an individual item creation screen 540 and a multiple item creation screen 550 are used. Then, the control unit 21 of the management server 20 executes an empty item generation process (Step S104). As a result, items can be registered individually, or a plurality of items can be registered collectively.

  (4) In the above embodiment, the control unit 21 of the management server 20 executes a title selection process (Step S106). When the normal mode is set, all extracted items are to be displayed. If the name hiding mode is set, the names of other creators are hidden. In the non-display mode, items of other creators are hidden. Thereby, in the normal mode, all information on the item can be shared. In the name hiding mode, information on different creators such as competitors can be hidden. In this case, by seeing items of different creators, consistency (style of world) such as style can be matched even if the creators are different. In the non-display 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 a thumbnail display process (Step S107). Here, the control unit 21 of the management server 20 performs a color coding process for each group (step S202). Thereby, a related image can be accurately grasped in a plurality of items. Further, the control unit 21 of the management server 20 executes a process of acquiring the latest posted image (Step S203). Here, since the items are grouped and displayed according to the evolution level, the status of the item images can be grasped in the related item creation process. Further, in the grouped items, it is possible to grasp the balance of item images (the richness of character images and background images) according to the evolution level.

  (6) In the above embodiment, the control unit 21 of the management server 20 executes a list display process (Step S108). When the selection box is selected and the batch change button is selected, the control unit 21 of the management server 20 executes a batch change support process (Step S109). Thereby, information on a plurality of items can be edited collectively.

  (7) In the above embodiment, when the Gantt chart display button is selected, the control unit 21 of the management server 20 executes a Gantt chart display process (Step S110). In this case, the control unit 21 of the management server 20 executes a process of specifying a child item of the parent item (step S302), a process of acquiring progress information of the child item (step S303), and a process of displaying the progress of the parent item (step S304). I do. This makes it possible to grasp not only the progress information of the 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 an item detail display process (Step S111). The display control unit 213 specifies the check file image with the latest posting date and time, and outputs a thumbnail image to the item image display area 601. Thereby, the creation status of the item image can be grasped. Further, the display control unit 213 displays thumbnail images of this item at other evolution levels. Thereby, the creation status of the related item can be grasped. Further, the display control unit 213 rearranges the posting date and time in the comment information D60 and the image information D70 in a new order and outputs the rearranged date and time to the posting 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 an image history display process (Step S114). Here, the control unit 21 of the management server 20 executes a process of acquiring all check images (step S402). A slide display process is performed (step S403). Thereby, it is possible to grasp the change of the item image in 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 an image changing operation.

The above embodiment may be modified 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 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 an image with the latest posting date and time in each step for all items related to this item. Then, the display control unit 213 outputs a history display screen to the display of the client terminal 10.

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

In the above embodiment, the control unit 21 of the management server 20 executes a thumbnail display process (Step S107). Here, the steps 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 in the thumbnail display mode.
As shown in FIG. 22, the title screen 720 in the thumbnail display mode includes a step display 711 and a status display 712.

  -In the said embodiment, the control part 21 of the management server 20 performs a Gantt chart display process (step S110). In this Gantt chart, a thumbnail image of each item may be output.

  In the above embodiment, the control unit 21 of the management server 20 executes an image history display process (Step S114). In this case, a 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, a status display 704 of the image displayed in the image display area 702 is output. Thereby, 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 repeatedly displayed at a predetermined time interval (for example, one second) a predetermined number of times (for example, five times), and then the next image is displayed. You may make it. The repeated display makes it easy to grasp the changed portion.

  In the above embodiment, in the image history display process, the control unit 21 of the management server 20 executes a process of acquiring all check images (Step S402) and a process of displaying a slide (Step S403). Here, the developer may be able to write a correction instruction (mark 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 post ID to the feedback and records the post ID in the item management information storage unit 24. Further, the control unit 21 of the management server 20 records image information D70 in which an image ID is assigned 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 a correction instruction). Then, in the image history display processing, the pages are turned in the order of the check file image and the check file (with correction instruction) image. Thereby, the correction instruction given in the feedback can be grasped in the image history display processing.

  In the above-described embodiment, in the thumbnail display process, the control unit 21 of the management server 20 performs a color classification process for each group (step S202). Here, when a display column belonging to another group is adjacent, a color scheme different from that of the adjacent display column is set, and when a display column belonging to the same group is adjacent, the same color scheme as the adjacent display column is set. Set. As a result, the image is displayed in a two-color striped pattern in which the background color is alternately changed for each adjacent group. Here, different colors may be set for the items forming the group. For example, when items belonging to different groups are individually adjacent, the control unit 21 of the management server 20 sequentially sets the display column to the first color (white) and the second color (blue). 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 columns of the two to the third color (yellow). This makes it easy to recognize items belonging to the same group even when the background color differs every time depending on the arrangement order at the time of rearrangement.

Next, technical ideas that can be grasped from the above embodiment and other examples will be additionally described below together with their effects.
(A) a system for managing items,
For at least the same base item used in the application, a storage unit that stores mutually related item images,
A control unit connected to the client terminal,
The control unit includes:
Acquiring the item image of the item from the storage unit, generating an image area for displaying the item image, outputting the image area to the client terminal,
An item management system, wherein when a change input is performed, a related item image is changed and output to the image area.
Therefore, according to the invention described in (a), it is easy to grasp a changed portion by comparing mutually related item images.

(B) Each item image is recorded in the storage unit in association with the registration date and time.
The item management system according to (a), wherein the item images are changed and output in the order of registration date and time.
Therefore, according to the invention described in (b), even when a plurality of item images are recorded, it is easy to grasp a changed portion.

(C) The item management system according to (a) or (b), wherein, when the item image is changed and output, the item image is changed within a time period in which an afterimage effect is visually generated.
Therefore, according to the invention described in (c), the difference between the front and rear images can be grasped by the afterimage effect.

(D) In the storage unit, a check image registered by the creator of the item image and a confirmation result of the confirmer for the check image are registered.
The item management system according to any one of (a) to (c), wherein a confirmation result of the item image output to the image area is displayed so as to be identified.
Therefore, according to the invention described in (d), the state of the item image can be grasped.

  Reference Signs List 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 (5)

A system for managing items,
A storage unit configured to store item information in which an item ID, an evolution level, and a step are associated, and step information on a progress rate of the step;
A control unit connected to the client terminal,
The control unit includes:
Items having the same item ID and different evolution levels are specified as parent items,
Each step having the same item ID and the same evolution level is specified as a child item,
From the storage unit, obtain the progress rate of the specified child item,
An item management system characterized in that a progress status of the parent item is specified and displayed based on a progress rate of the child item. The control unit includes:
Calculating the progress rate of the parent item by dividing a value obtained by summing the progress rates of the child items having the same parent ID, the item ID, and the evolution level by the number of the child items;
On the Gantt chart, display a bar according to the progress information of the child item,
2. The item management system according to claim 1, wherein a progress rate of a parent item of the child item is displayed above a progress rate of the child item on the Gantt chart.   The item management system according to claim 2, wherein the control unit displays that a thumbnail image of the child item is output in the Gantt chart. An item management method for a computer system , comprising: a storage unit that stores item information in which an item ID, an evolution level, and a step are associated with each other, step information on a progress rate of the step, and a control unit connected to the client terminal. hand,
The control unit includes:
Items having the same item ID and different evolution levels are specified as parent items,
Each step having the same item ID and the same evolution level is specified as a child item,
From the storage unit, obtain the progress rate of the specified child item,
An item management method comprising: identifying and displaying a progress status of the parent item based on a progress rate of the child item. An item management program for a computer system comprising: a storage unit that stores item information in which an item ID, an evolution level, and a step are associated with each other, step information on a progress rate of the step, and a control unit connected to the client terminal. hand,
The control unit,
Items having the same item ID and different evolution levels are specified as parent items,
Each step having the same item ID and the same evolution level is specified as a child item,
From the storage unit, obtain the progress rate of the specified child item,
An item management program for causing a function of displaying and displaying a progress status of the parent item based on a progress rate of the child item.

Images