Patent Application
20210209295
This application is based on and claims priority under 35 USC 119 from Japanese Patent Application No. 2020-000869 filed Jan. 7, 2020.
The present disclosure relates to an information processing apparatus and a non-transitory computer readable medium.
Japanese Unexamined Patent Application Publication No. 2016-081185 describes a disclosure of an information processing apparatus. The information processing apparatus includes an acceptance unit, a deployment unit, and an output unit. A relation diagram is created by systematically connecting plural function items in accordance with dependence relations of the function items, each of the plural function items representing a function related to quality function deployment. Among the plural function items, a function item representing a function belonging to any of plural processes in the quality function deployment is provided with attribute information for identifying the process to which the function item belongs. Upon the relation diagram being input, the acceptance unit extracts, from the relation diagram, information for identifying the function item, the attribute information provided for the function item, and dependence information for identifying the dependence relations between the function items and accepts them as raw information. The deployment unit classifies the function items according to the process on the basis of the attribute information in the raw information, creates deployment information used for deploying the classified function items for each process, and deploys, on the basis of the deployment information, the raw information into a deployment chart in which the function items are deployed and in which the processes are axes. The output unit outputs the deployment chart deployed by the deployment unit.
In a typical relation diagram representing logical relations between events, many events are linked in a chained manner and in a crossed manner. In order to grasp all downstream events related to upstream events, it is necessary to track relation lines in the relation diagram one by one.
Aspects of non-limiting embodiments of the present disclosure relate to an information processing apparatus and a non-transitory computer readable medium by which, even if many items representing events are related in a chained manner and in a crossed manner, relations between the events may be grasped more easily than using a relation diagram.
Aspects of certain non-limiting embodiments of the present disclosure address the above advantages and/or other advantages not described above. However, aspects of the non-limiting embodiments are not required to address the advantages described above, and aspects of the non-limiting embodiments of the present disclosure may not address advantages described above.
According to an aspect of the present disclosure, there is provided an information processing apparatus including a processor. The processer is configured to receive relation information generated by systematically connecting plural items representing events in accordance with relations of the items, extract, from the relation information, information for identifying the items and information for identifying the relation for each of the items, arrange the items based on the extracted information for identifying the relation for each of the items to generate a table in which attribute information of the items is allowed to be input, and output the generated table.
An exemplary embodiment of the present disclosure will be described in detail based on the following figures, wherein:
Hereinafter, an example of an exemplary embodiment of the present disclosure will be described with reference to the attached drawings. Note that identical or equivalent components and sections are denoted by the same reference numerals in the drawings. In addition, the dimensional ratios in the drawings may be different from the actual ratios by being exaggerated for convenience of description.
First, the background to the exemplary embodiment of the present disclosure that the inventors have arrived at will be described.
Typically, in a system using complex physical phenomena, many events are linked to each other in a chained manner. For example, an effect, such as a final quality of a product, may be caused by plural events, which are caused by plural other events, and the plural other events are caused by plural still other events. In such a complex system, a large number of qualities need to be assured, and relations between designs and qualities are extremely complex. Accordingly, it is difficult to find a design item that assures a desired quality, and a change in design value for assuring a certain quality may tend to adversely affect the other qualities.
To visualize and organize such complex relations, relation information is used. The relation information refers to information in which items and relations between the items are defined. An example of the relation information is a relation diagram representing relations by connecting plural items to each other via relation lines. Each of the items represents an event and has attributes such as an item name and characteristics. An example of the relation diagram is a logic tree. The relation diagram is suitably used to indicate items representing events serving as effects and items representing events serving as causes of the effects in detail without any missing or overlapping item.
Another example of the relation information is a quality function deployment chart representing relations between events listed on plural axes that intersect with each other, by using symbols or numeric values arranged in a matrix. The quality function deployment chart represents relations in a matrix in which some events are extracted from among many events and arranged on axes. Thus, relations between many events serving as effects and many events serving as causes may be represented simply.
However, if a relation diagram includes too many items representing target events, the diagram becomes excessively complex and large. In addition, the quality function deployment chart is incapable of representing detailed relations including items representing events that are not arranged on axes, and as a result, the items tend to be missing.
In a typical, widely used quality function deployment chart, events serving as causes and events serving as effects are arranged on two axes, the horizontal axis and the vertical axis, and is incapable of including information about the reasons for the indicated relations. However, it is useful to use a multi-axis quality function deployment chart representing overall relations in which three or more axes are arranged to intersect with one another and some causes are extracted and illustrated from among the causes constituting the relations.
From the above description, by using both a relation diagram and a multi-axis quality function deployment chart, it is possible to extract and illustrate relations in detail without any missing or overlapping item, while simply displaying the relations between many events serving as causes and many events serving as effects. However, it is complicated to convert a relation diagram into a multi-axis quality function deployment chart or to convert a multi-axis quality function deployment chart into a relation diagram, and a system that supports the conversion is necessary.
In a case where a two-axis quality function deployment chart is to be displayed by depicting a relation diagram having hierarchical relations between items representing events and selecting a level therefrom, in order to create a hierarchical relation diagram, the relations need to be originally organized in a hierarchical manner. Unless the relations are originally organized in a hierarchical manner, it is difficult to depict hierarchical relations in detail without any missing or overlapping item, which is the purpose of the disclosure. Even if events are classified as hierarchy, display of all events in a selected level in the quality function deployment chart increases the information amount to be displayed, which hinders the purpose to extract and display some events serving as causes.
The disclosure disclosed in Japanese Unexamined Patent Application Publication No. 2016-081185 proposes deployment of a quality function deployment chart after selecting an event corresponding to each axis of the quality function deployment chart on a created relation diagram. In this technique, however, information of the relation diagram is condensed to create a quality function deployment chart. This decreases information of the quality function deployment chart much less than information of the relation diagram. Thus, although it is possible to deploy the quality function deployment chart from the relation diagram, it is difficult in turn to reflect any changes of the quality function deployment chart in the relation diagram.
As described above, the relation diagram and the quality function deployment chart have different roles to visualize the same relations between events. Accordingly, it is desired, not only to use either one or to convert either one into the other in one way, but also to create and view both back and forth while keeping all information of complex event relations.
Accordingly, this exemplary embodiment will describe a technique by which, on the basis of relation information for creating a relation diagram and a quality function deployment chart, information for making it easy to grasp relations between events may be generated and output.
The server 10 is an apparatus that generates and outputs, on the basis of relation information for creating a relation diagram and a quality function deployment chart, information for making it easy to grasp relations between events. Specifically, the server 10 generates and outputs, on the basis of relation information, a table for making it easy to grasp relations between events. In the following description, the table generated by the server 10 will be referred to as a relation table.
The relation information is generated by systematically connecting plural items in accordance with predetermined relations between the items. Each of the items may be a function item indicating a function. The relations between the items may include a dependence relation or a hierarchical relation. Each function item may have attribute information. The attribute information may be a numeric value or a character. The relation information may be a relation diagram representing dependence relations by linking function items via lines. Alternatively, the relation information may be a multi-axis deployment chart, in which processes are arranged on axes, representing dependence relations by deploying function items belonging to any of plural processes.
The exemplary embodiment is applicable to a relation table generation process for performing processing to obtain a relation table from various charts, such as a deployment chart and a two-element chart in quality function deployment. For example, in designing a product or a service, a design quality that satisfies customers is set, and in order to embody the set design quality, quality function deployment is applied to checking of dependence relations with the function items or components. In quality function deployment, it is necessary to check actual dependence relations properly, and thus, in quality function deployment, many function items such as a design quality are set accurately without any missing item (without any omission). In addition, in quality function deployment, one or more processes among a series of related processes are arranged on axes, function items of the processes are displayed systematically in a hierarchical manner, and thereby correspondence relations between the function items are clarified.
The exemplary embodiment is applied to generation of a relation table from a two-element chart representing correspondence relations (dependence relations) between function items in two processes by combining correspondence relations between two related processes (e.g., correspondence relations in a deployment chart in which processes are arranged on axes) for quality function deployment of various cases. The two-element chart in quality function deployment may be any of various charts, such as a required quality deployment chart, a quality element (characteristics) deployment chart, a planned quality setting chart, a design quality setting chart, a function deployment chart, a mechanism deployment chart, a unit/component deployment chart, a method deployment chart, a new idea deployment chart, and a cost deployment chart. The two-element chart may further be any of various charts, such as a cost plan setting chart, a material deployment chart, a fault tree (FT) deployment chart, a reliability plan setting chart, a measurement equipment deployment chart, a measurement method deployment chart, a business function deployment chart, a technique deployment chart, a quality assurance (QA) chart, a quality control (QC) step chart, and an assured item deployment chart. The exemplary embodiment is applied to generation of a relation table from any of these charts. Without limitation to the above, the exemplary embodiment may be applied to generation of a relation table from a two-element chart representing correspondence relations between desired processes.
Furthermore, the quality function deployment according to the exemplary embodiment is applied to generation of a relation table from a diagram for quality function deployment representing correspondence relations between function items in each process by combining correspondence relations between, not only two processes, but also three or more (e.g., three or four) processes. Note that in the following description, a diagram for quality function deployment representing correspondence relations between plural processes will be referred to as “multi-element chart”. That is, in the following description, a multi-element chart representing correspondence relations between two processes is referred to as a two-element chart, a multi-element chart representing correspondence relations between three processes is referred to as a three-element chart, and a multi-element chart representing correspondence relations between four processes is referred to as a four-element chart. In addition, in the exemplary embodiment, a process refers to a series of actions that relate to or act on each other for a target case, such as quality-performance-structure-material. Between related processes, an output of a process serves as an input for another (see, for example, JIS Q 9000).
Each of the user terminals 20A and 20B is an apparatus that is connected to the server 10 via a network 30, such as the Internet or an intranet, to edit relation information or to issue an instruction for generating a relation table from the relation information. The user terminals 20A and 20B are used by different users. Although
As illustrated in
The CPU 11 executes various programs or controls each unit. That is, the CPU 11 reads a program from the ROM 12 or the storage 14 and executes the program by using the RAM 13 as a work area. In accordance with the program recorded on the ROM 12 or the storage 14, the CPU 11 controls the above components and performs various arithmetic processes. In the exemplary embodiment, the ROM 12 or the storage 14 stores a relation table generation program for generating a relation table.
The ROM 12 stores various programs and various kinds of data. The RAM 13 temporarily stores a program or data as a work area. The storage 14 is constituted by a storage device such as a hard disk drive (HDD), a solid state drive (SSD), or a flash memory, and stores various programs including an operating system and various kinds of data.
The input device 15 includes a pointing device, such as a mouse, and a keyboard and is used by a user to input various kinds of information.
The display 16 is, for example, a liquid crystal display and displays various kinds of information. The display 16 may also function as the input device 15 by employing a touch panel.
The communication interface 17 is an interface for communicating with other equipment such as a user terminal 20, and for example, a standard such as Ethernet (registered trademark), Fiber Distributed Data Interface (FDDI), or Wi-Fi (registered trademark) is used.
When executing the above relation table generation program, the server 10 implements various functions by using the above hardware resources. The functional configuration implemented by the server 10 will be described.
Next, the functional configuration of the server 10 will be described.
As illustrated in
The reception unit 101 receives input of relation information from which a relation table is to be generated. The relation information from which a relation table is to be generated is stored in, for example, the storage unit 105. In accordance with a generation instruction for generating a relation table from the relation information received from a user terminal 20, the reception unit 101 acquires the relation information from the storage unit 105.
The generation unit 102 generates a relation table from the relation information received by the reception unit 101. The method for generating a relation table from the relation information will be described later in detail.
The output unit 103 outputs the relation table generated by the generation unit 102. The relation table is output to the user terminal 20 that has transmitted the instruction for generating the relation table. In addition, the output unit 103 stores the relation table generated by the generation unit 102 in the storage unit 105.
The notification unit 104 notifies the user terminal 20 that is displaying the relation table of information about the relation table generated by the generation unit 102. For example, if identical items are present when editing attribute information of an item, the notification unit 104 notifies the user terminal 20 displaying the relation table that identical items are present. In addition, for example, if identical items are present when editing attribute information of an item, the notification unit 104 displays a notification of information about the number of identical items. Examples of the information about the relation table as a notification displayed by the notification unit 104 will be described later in detail.
The storage unit 105 stores various kinds of information about operations of the server 10. In the exemplary embodiment, the storage unit 105 stores information about relation information. For example, if the relation information is a relation diagram, the storage unit 105 stores a relation diagram information table, an item information table, and a relation line information table. Herein, examples of the information about relation information stored in the storage unit 105 will be described.
Note that the tables illustrated in
In addition, the relation information is not necessarily stored in the storage unit 105. The relation information may be stored in an apparatus other than the server 10.
Next, operations of the server 10 will be described.
First, the CPU 11 waits until receiving a relation table generation instruction from a user terminal 20 (step S101).
The CPU 11 waits for the relation table generation process until receiving the relation table generation instruction from the user terminal 20 (step S101; No).
Upon the relation table generation instruction being received from the user terminal 20 (step S101; Yes), the CPU 11 acquires, from the storage unit 105, item names in the relation information from which a relation table is to be generated (step S102). In a case where a relation table is to be generated from a relation diagram, the CPU 11 acquires, from the relation diagram information table 900, recording of a relation diagram ID of the relation diagram from which a relation table is to be generated, and acquires, from the item information table 1000, recording of item IDs in the acquired recording. Then, the CPU 11 acquires the item names in the acquired recording of the item IDs.
Subsequently to step S102, the CPU 11 acquires relations for the acquired item names (step S103). Specifically, in a case where a relation table is to be generated from a relation diagram, the CPU 11 acquires connection item IDs in the recording of the item IDs acquired from the item information table 1000. In addition, the CPU 11 acquires, from the relation line information table 1100, recording of relation line IDs corresponding to lines connecting the item IDs acquired from the item information table 1000 and the connection item IDs.
Subsequently to step S103, on the basis of the acquired relations, the CPU 11 sequentially arranges the acquired item names to generate a relation table (step S104). In a case where the input relation information includes information about processes, on the basis of the acquired relations, the CPU 11 sequentially arranges the acquired item names in accordance with processes to which the acquired items belong.
Subsequently to step S104, the CPU 11 arranges, next to the respective item names, regions in which attribute information for the arranged item names are to be input to generate a relation table (step S105).
An example of the relation table generated in the relation table generation process performed by the server 10 illustrated in
Upon the relation diagram 200 illustrated in
The relation diagram 200 illustrated in
Note that the item “thermal conductivity of heating section” belongs to none of the plural processes. Thus, the CPU 11 does not acquire “thermal conductivity of heating section”.
As illustrated in
Since “cooking efficiency of pot” and “quality A” belong to the process “quality”, the CPU 11 arranges “cooking efficiency of pot” and “quality A” in the column of “quality”. Then, next to (on the right of) “cooking efficiency of pot” and “quality A”, the CPU 11 arranges input cells in which attribute information is to be input. In
Subsequently, since “amount of foodstuffs that may be cooked at once” and “temperature of foodstuffs during heating” belong to the process “function”, the CPU 11 arranges “amount of foodstuffs that may be cooked at once” and “temperature of foodstuffs during heating” in the column of “function”. In this case, referring to relations between the items, “cooking efficiency of pot” is related to “amount of foodstuffs that may be cooked at once” and “temperature of foodstuffs during heating”. Thus, the CPU 11 arranges both “amount of foodstuffs that may be cooked at once” and “temperature of foodstuffs during heating” on the right of “cooking efficiency of pot”. In addition, “quality A” is related to “temperature of foodstuffs during heating”. Thus, the CPU 11 arranges “temperature of foodstuffs during heating” on the right of “quality A”. Then, next to (on the right of) “amount of foodstuffs that may be cooked at once” and “temperature of foodstuffs during heating”, the CPU 11 arranges input cells in which attribute information is to be input. In
Subsequently, the CPU 11 arranges the item names belonging to the process “physics” and the item names belonging to the process “design” in the same manner. Then, next to (on the right of) the arranged item names, the CPU 11 arranges input cells in which attribute information is to be input.
In a case where attribute information is input in the original relation diagram, the CPU 11 generates the relation table 300 reflecting the input attribute information.
In accordance with an operation from a user terminal 20, the CPU 11 may optionally increase or decrease the number of input cells in which the attribute information corresponding to each item is to be input.
In a relation diagram, symbols indicating polarities may be attached to item names. In the relation diagram 200 illustrated in
The relation table generated by the CPU 11 in this manner, in which items belonging to each process are sequentially arranged on the basis of relations, makes it easier to grasp the relations between events than a relation diagram and a deployment chart.
In the relation diagram 200 illustrated in
By contrast, by referring to the relation table 300 illustrated in
Furthermore, the relation table 300 illustrated in FIG. 9 includes cells in which attribute information is input and displayed, the cells not included in the relation diagram 200 illustrated in
In the relation table generated by the CPU 11, identical items may be displayed on plural rows. For example, referring to
In a case where a user selects an item or attribute information thereof in a relation table, if the item is present on other rows, the CPU 11 may notify the user that the same attribute information is present on the other rows in the relation table. In addition, in a case where a user selects an item or attribute information thereof in a relation table, if the item is present on other rows, the CPU 11 may notify the user of the number of pieces of the same attribute information in the relation table.
In the example illustrated in
The server 10 according to the exemplary embodiment is capable of generating a relation table by which it is possible to easily overlook relations between events including attribute information that is set for each item. In addition, the server 10 according to the exemplary embodiment makes it possible to easily organize downstream events in a relation diagram by generating a relation table provided with input cells in which attribute information of identical items may be edited. Furthermore, the server 10 according to the exemplary embodiment notifies a user of the presence of plural input cells in which attribute information of identical items may be concurrently edited, thereby preventing unintended change of attribute information.
Although the exemplary embodiment describes a case where the relation table generation program is stored (installed) in the ROM or the storage in advance. However, the disclosure is not limited to this. The program may be provided by being stored in a storage medium such as a Compact Disk Read Only Memory (CD-ROM), a Digital Versatile Disk Read Only Memory (DVD-ROM), or a Universal Serial Bus (USB) memory. Alternatively, the program may be downloaded via a network from an external apparatus.
In the embodiment above, the term “processor” refers to hardware in a broad sense. Examples of the processor include general processors (e.g., CPU: Central Processing Unit) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, and programmable logic device).
In the embodiment above, the term “processor” is broad enough to encompass one processor or plural processors in collaboration which are located physically apart from each other but may work cooperatively. The order of operations of the processor is not limited to one described in the embodiment above, and may be changed.
The foregoing description of the exemplary embodiment of the present disclosure has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Obviously, many modifications and variations will be apparent to practitioners skilled in the art. The embodiment was chosen and described in order to best explain the principles of the disclosure and its practical applications, thereby enabling others skilled in the art to understand the disclosure for various embodiments and with the various modifications as are suited to the particular use contemplated. It is intended that the scope of the disclosure be defined by the following claims and their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2020-000869 | Jan 2020 | JP | national |
