JP2012164101A - Manual preparation information management device and method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a manual preparation information management device and method, and a program capable of supporting preparation and revision of a manual by managing information on the preparation and revision of the manual.SOLUTION: A manual preparation information management device reads manual document data inserted with a management tag indicating a content identifier relating to content of text specified by a model version and the tag, and generates and stores a data table in which the text specified by the management tag corresponds to the version and the content identifier indicated by the management tag. The manual preparation information management device refers to the data table of each model to generate and store a feature correspondence table in which the content identifier included in each data table corresponds to a model name provided to the data table.

Description

  The present invention relates to a manual creation information management apparatus, method, and program.

  When creating a manual for a general product, manual data of the same model or a similar model is used, and descriptions that can be diverted from the manual are often used to describe the features unique to the model. In recent years, a system for supporting creation and revision of such a manual has been realized.

  For example, Patent Literature 1 discloses a system for creating an editing manual for creating a new manual based on model specification information.

JP 2006-277460 A

  In manual creation and revision, manual data creation and management as well as various information management related to manual creation and revision are required. For example, it is necessary to manage information such as model version, manual version number, revision history, and the like. In addition, if the manual is changed for one of multiple generation models due to model changes or one of the same generation models with multiple variations, it is necessary to change the manual for other related models as well. Yes, management of information for this is also necessary. However, in a system such as Patent Document 1, information relating to manual creation and revision cannot be managed by the system.

  The present invention has been made in view of the above problems, and its purpose is to provide a manual creation information management apparatus, method, and method capable of supporting the creation and revision of a manual by managing information related to the creation and revision of a manual. Is to provide a program.

  The present invention reads manual document data in which a management tag indicating a model version is inserted, and generates a data table in which text specified by the management tag is associated with a version indicated by the management tag. It is a manual creation information management device characterized by storing.

  The present invention reads manual document data in which a management tag indicating a model version is inserted, and generates a data table in which text specified by the management tag is associated with a version indicated by the management tag. This is a manual creation information management method characterized by storing.

  The present invention reads a manual table data in which a management tag indicating a model version is inserted into a computer, and a data table in which text specified by the management tag is associated with a version indicated by the management tag A program for executing a process of generating and storing a program.

  According to the present invention, it is possible to support creation and revision of a manual by managing information related to creation and revision of a manual.

FIG. 1 is a diagram showing a configuration of a manual creation information management apparatus according to the first embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a data list. FIG. 3 is a diagram showing an example of the version number correspondence table. FIG. 4 is a diagram showing an example of the feature correspondence table. FIG. 5 is a diagram illustrating an example of document data of a manual in which a tag is inserted. FIG. 6 is a diagram illustrating an example of a template created by the template creation unit. FIG. 7 is a diagram illustrating an example of a template generated by the manual creation information management apparatus according to the second embodiment. FIG. 8 is a flowchart for explaining a process of creating manual data of another model by the manual creation information management apparatus of the second embodiment. FIG. 9 is a diagram illustrating an example of a feature correspondence table according to the second embodiment. FIG. 10 is a diagram showing an example of the version number correspondence table in the second embodiment. FIG. 11 is a flowchart for explaining a process of generating a revision history by the manual creation information management apparatus of the third embodiment. FIG. 12 is a diagram illustrating an output example of the revision history in the third embodiment.

  Embodiments of the present invention will be described below with reference to the drawings.

(First embodiment)
FIG. 1 is a block diagram showing a configuration of a manual creation information management apparatus according to the first embodiment of the present invention. The manual creation information management device includes an input device 1, a data processing device 2, a storage device 3, and an output device 4. The input device 1, the storage device 3, and the output device 4 are connected to the data processing device 2.

  The input device 1 is for inputting data to the data processing device 2. For example, a recording medium reading device that reads data recorded on a recording medium and inputs the data to the data processing device 2, a network such as the Internet or a LAN. A communication control device that receives data via the data processing device 2 and inputs the data to the data processing device 2, and an input device that inputs data corresponding to a user operation to the data processing device 2.

  The data processing device 2 includes a tag reading unit 21, a changed part presentation unit 22, a template creation unit 23, and a tag generation unit 24.

  The tag reading unit 21 reads a tag inserted in manual document data, generates a data list (data table) indicating the structure of the manual, and stores the data list in the structure storage unit 31. The manual data may be configured using a markup language such as XML, for example. The tag in the present embodiment includes a management tag indicating a content identifier related to the version and content of the corresponding model in the manual text.

  The change location presentation unit 22 reads the data list generated by the tag reading unit 21 and stored in the structure storage unit 31, performs analysis processing using the read data list, and stores the analysis processing result in the change history storage unit. 33.

  The template creation unit 23 creates a manual modification template from the data list stored in the structure storage unit 31 and outputs the template to the output device 4.

  The tag generation unit 24 inserts a tag into manual data. The tag may be inserted according to an input operation by the user. Further, the tag generation unit 24 may perform according to a predetermined insertion rule.

  The storage device 3 includes a structure storage unit 31, a version number correspondence storage unit 32, a change history storage unit 33, and a feature storage unit 34.

  The structure storage unit 31 stores data of a data list indicating the structure of the manual. In the data list, the text of the manual text, the corresponding model version, and content identifier information (feature A, feature B, feature C) for identifying the feature of the content may be associated with each other. An example of the data list is shown in FIG.

  The version number correspondence storage unit 32 stores data of a version number correspondence table for each model. In the version number correspondence table, model version, manual update date and time, and manual version number information may be associated with each other. An example of the version number correspondence table is shown in FIG.

  The change history storage unit 33 stores manual change history data.

  The feature storage unit 34 stores data of a feature correspondence table indicating features supported by each model for each model. In the feature correspondence table, a model name and a feature identifier may be associated with each model. An example of the feature correspondence table is shown in FIG.

  The output device 4 includes a display device, a printer, and the like, and displays or prints output data from the data processing device 2.

  Next, the processing operation of the manual creation information management apparatus according to the present embodiment will be described.

First, a description will be given of a case where the document data of a manual that is a major revision is read.
First, the data processing device 2 reads document data such as an initial manual for the model XXXXXX through the input device 1. The reading method is arbitrary, and for example, the document data read from the recording medium by the recording medium reading unit may be read. A tag may be inserted in the read document data in advance, or text data in which no tag is inserted may be read, and the tag generation unit 24 may insert the tag. An example of the document data of the manual in which the tag is inserted is shown in FIG.

  In the example of FIG. 5, 501 corresponds to the notation of the model name, and the model name is described following the tag for identifying the model name. 502 corresponds to the first heading. Reference numeral 503 denotes a tag (management tag) indicating a version and characteristics. Reference numeral 504 corresponds to the second heading. Reference numeral 505 denotes a blank line as a paragraph break. Reference numeral 506 denotes a tag indicating a notice. 507 indicates Ver. 3 to Ver. This is the content described up to 5. Reference numeral 508 denotes a part describing a date. For example, the date and time in the version number correspondence table may be acquired from this portion. Reference numeral 509 denotes an example of a manual text.

  Next, the tag reading unit 21 performs a process of reading the inserted tag for the manual data read via the input device 1. Specifically, when the manual tag data is read from the beginning and a predetermined tag is detected, the character strings (tag character strings) in the delimiters “<” and “>” are supported. The character string of the manual text to be read is read and stored in the corresponding storage area in the data list of the structure storage unit 31 according to a predetermined storage rule. For example, when a management tag indicating the version and characteristics is detected, the character string enclosed by the tag is stored in the corresponding item in the data list, and the content identifier indicated by the management tag is stored in the corresponding item. May be.

  In the example of the data list in FIG. 2, a character string surrounded by management tags indicating versions and features is stored as data of the manual text in the item “content” 201 of the data list, and the management tag. A character string (Ver.3-Ver.5, etc.) representing the version in the item is stored in the item "Version" 202, and a character string (feature A etc.) indicating the feature following "tag:" in the management tag is It is stored in the item “feature” 203.

The change location presentation unit 22 adds a version (“Ver.” In FIG. 3) and a date (for example, a date tag in the manual text) to the version number correspondence table (FIG. 3) of the corresponding model name in the version number correspondence storage unit 32. And the version number of the manual ("Rev." in FIG. 3)) are stored. The version “Ver.” Indicates the association between the changed contents and the file because a file is created every time the manual is changed. In addition, the version number of the manual is increased by one every time it is actually converted into data as a manual. In the example of FIG.
“Ver.1” indicates that the contents are reflected in the manual version 1 301, and “Ver.6” indicates that the contents are reflected in the manual version 2 302.

  In addition, the changed part presentation unit 22 stores information on features corresponding to the model XXXXXX in a feature correspondence table stored in the feature storage unit 34. For example, referring to the `` feature '' item in the model list of model XXXXXX, for each feature included in the `` feature '' item, data indicating that the model XXXXXX is supported is stored in the feature correspondence table. For features not included in the “feature” item, data indicating that the model XXXXXX is not supported is stored in the feature correspondence table.

Next, a scene where the manual is modified based on the manual data stored in the structure storage unit 31 will be described.

  The change location presentation unit 22 performs various processes related to manual modification in cooperation with the template creation unit 23.

  First, the changed part presentation unit 22 reads the latest version of the manual data among the manual data stored in the structure storage unit 31.

  The template creation unit 23 accepts changes such as addition and deletion of the text of the manual for the latest manual data by the editor function. The data to be added is, for example, text data with a tag inserted. The template creation unit 23 corrects a tag or the like for data in which the latest version of manual data is changed. Specifically, for example, the specified new version is “Ver.7”, and a portion surrounded by tags of <Ver.3-Ver.5 tag: feature B> (for example, 307 in FIG. 2) If it is added, as shown in 607 of the manual data illustrated in Fig.6, it is corrected by adding "Ver.7" to the corresponding part tag <Ver.3-Ver.5, Ver.7 tag: Feature B>. As for tag “<Ver.1-tag: feature A>”, it is considered that the new version is included. Further, in order to allow the user to input the portion surrounded by the <date> tag, it is displayed in the form of “()” as shown in FIG. 6 and the input of the edited date is accepted.

  When the editing of the manual is completed, the template creation unit 23 stores the edited manual data in the structure storage unit 31. The tag reading unit 21 generates a data list for the edited manual data and stores it in the structure storage unit 31.

  When the model name of the edited manual is not changed, the change location presentation unit 22 extracts the character string following the <title model name> tag of the manual data as the model name, and the corresponding model name in the version correspondence storage unit 32 In the version number correspondence table (FIG. 3), data of version, date (for example, acquired from the date tag of the manual text), and manual version number are stored. In addition, the changed part presentation unit 22 stores data indicating whether or not the corresponding model in the feature correspondence table stored in the feature storage unit 34 corresponds to each feature.

  In addition, the change location presentation unit 22 refers to the feature correspondence table stored in the feature storage unit 34, and when there is another model having the feature corresponding to the changed part, the latest manual of the model Data is read from the structure storage unit 31 and the same correction is performed. For example, in the case of manual data of model XXXXXX, if the text 709 “Cannot be activated simultaneously with model 2” is added to the part of feature B in FIG. 6, the changed part presentation unit 22 refers to the feature correspondence table and changes to feature B. The other corresponding model is specified, the manual data of the specified model is read out, and the corresponding part of the part specified by the tag of the feature B is corrected to add “cannot be started simultaneously with model 2”. Further, at the time of this correction, the version of the tag of the corresponding part may be corrected together so that the new version is included.

  As described above, according to the first embodiment, it is possible to embed a tag indicating information about a version or revision in manual data, and to manage the version of each model or revision of the manual using this tag. Further, by outputting the tag as invisible to the output device 4, it can be used as a manual as it is.

(Second Embodiment)
The manual creation information management apparatus according to the second embodiment of the present invention has a function of creating manual data of another model using manual data of a certain model. The manual creation information management apparatus of the second embodiment has the same configuration as that of the first embodiment. Hereinafter, differences from the first embodiment will be described.

  FIG. 7 shows an example of manual data created by the changed part presentation unit 22 and the template creation unit 23 in the manual creation information management apparatus of the second embodiment. FIG. 7 illustrates manual data of the model name CCCCCC created using the manual data of the model name XXXXXX illustrated in FIG. As shown in 707 etc., the tag indicating the version etc. indicates the version and model name of the original model and the version of the new model (for example, <XXXXXX Ver.3-Ver.5 / Ver.1- tag: feature B>) Conversion processing is performed. As a result, it is possible to manage with a new model version in the future. For the portion 707 in FIG. 7, manual data of model CCCCCC is created by diverting the manual data of Ver. 5 of model XXXXXX.

  A process in which the manual creation information management apparatus of the second embodiment creates manual data of another model will be described with reference to the flowchart of FIG. Here, a case where manual data for a successor model is created from manual data for a previous model will be described as an example.

  For example, manual data of a predecessor model as shown in FIG. 5 input from the input device 1 is processed by the tag reading unit 21 and then supplied to the changed part presentation unit 22 (step A1).

  The change location presentation unit 22 acquires information indicating some of the latest version of the previous model from the version number correspondence storage unit 32 (step A2).

  The changed part presentation unit 22 updates the feature correspondence table stored in the feature storage unit 34 (step A3). An example of the updated feature correspondence table is shown in FIG. In the feature correspondence table shown in FIG. 9, information relating to the features of the predecessor model XXXXXX is set to 1001, and in addition, information relating to the features of the successor model CCCCCC is set to 1002.

  The changed part presentation unit 22 stores the version number correspondence table for each model generated for the succeeding model CCCCCC in the version number correspondence storage unit 32 (step A4). An example of the generated version number correspondence table is shown in FIG. In FIG. 10, the data file of the manual for each model that is the diversion source is indicated by 1101 (in the example of this figure, it corresponds to “Ver. 6” described in 302 of FIG. 3). Reference numeral 1102 indicates the correspondence of the first version of the successor model.

  The change location presentation unit 22 determines whether there is a predetermined unconverted tag for the manual data (step A5). This determination method is arbitrary. For example, when a tag with a version or the like is searched from the beginning of manual data and a corresponding tag is detected, whether or not there is a model name in the part indicating the version or the like. You may judge. If an unconverted tag exists (step A5: YES), conversion is performed to indicate the model name of the previous model and the latest version and the first version of the succeeding model (step A6). This unconverted tag conversion process is performed on the entire manual data (step A7).

  Thereby, the manual data of the successor model is created. As described above, the manual data of the successor model is created from the manual data of the predecessor model, which is an example, and the same applies to the case of creating a manual template of a derivative model of the same generation, for example.

  As described above, according to the second embodiment, manual data of another model can be easily created using manual data of a certain model. Further, for example, the relationship between a plurality of models such as the predecessor model and the successor model can be expressed in the feature correspondence table. Also, as shown in the version number correspondence table of FIG. 10, when a change occurs in one manual data by associating manuals of a plurality of models such as the predecessor model and the successor model, for example, a change location presentation unit By referring to the version number correspondence table 22 and the like, the same change can be reflected in the corresponding portion of the manual data associated with the changed manual data. Similarly, when a plurality of manual data are associated with one type of manual data, when a change occurs in one type of manual data, the change location presentation unit 22 associates with the changed manual data. It is possible to reflect changes for a plurality of manual data.

(Third embodiment)
A manual creation information management apparatus according to the third embodiment of the present invention has a function of managing the version number and history of a manual using tags present in manual data. The manual creation information management apparatus of the third embodiment has the same configuration as that of the above-described embodiment. Hereinafter, differences from the first embodiment will be described.

  A process of generating a revision history by the manual creation information management apparatus of the third embodiment will be described with reference to the flowchart of FIG.

  The change location presentation unit 22 extracts the first version number from the version number correspondence table stored in the version number correspondence storage unit 32 for the designated model (step B1). The version number is represented by “Rev.”. In addition, here, the data list corresponding to the first edition is also taken out.

  Next, the changed part presentation unit 22 determines whether the version number next to the version number extracted in step B1 exists in the version number correspondence table (step B2).

  When the next version number exists (step B2: YES), the changed part presentation unit 22 takes out the data list corresponding to the next version number (step B3), and compares it with the data list of the previous version. The difference is searched (step B4). For example, manual data may be used in the difference detection process. Further, the content of the difference detection process is arbitrary. For example, it may be determined whether each row in one data list matches the other data list in order from the top, and addition or deletion of a row may be determined based on the determination result.

  When the change location presentation unit 22 detects a difference (step B4: YES), the change location presentation unit 22 extracts the difference and stores it as a revision history in the change history storage unit 33 (step B5).

  When the extraction of the difference from the previous version in step B5 is completed or when the difference from the previous version is not detected in step B4, the process returns to step B2 and the difference extraction is repeated until the latest version. If it is determined in step B2 that there is no next version (step B2: NO), the revision history stored in the change history storage unit 33 is output to the output device 4 (step B6). As for the revision history of the first version, data indicating that it is the first version may be generated, stored, and output.

  An output example of the revision history is shown in FIG. In FIG. 12, 1201 indicates the version number and date of revision, 1202 indicates the name of the paragraph, 1203 indicates the content of the text, and 1204 indicates the reason for the revision. The format of the revision history can be arbitrarily set. For example, when a sentence is added to an existing feature, the changed part presentation unit 22 describes an additional part after the description “add the following sentence”. May be. When a sentence is deleted for an existing feature, the deleted part may be described in the description “delete the following sentence”. In addition, when a new feature is added, the changed part presentation unit 22 may include a description “addition of description because of feature X”. When a feature is deleted, a description “deletion of feature X” may be included, or a description that is deleted may be included.

  As described above, according to the third embodiment, a revision history can be automatically generated and expressed by analyzing a tag. In addition, by combining the third embodiment with the first embodiment or the second embodiment, it is possible to output the revised part and the template shown in FIGS. 6 and 7 to the output device 4 for presentation. Revision work for other models such as successor models is also facilitated.

  Although the present invention has been described with reference to the preferred embodiments, the present invention is not necessarily limited to the above-described embodiments, and various modifications can be made within the scope of the technical idea.

  The manual creation information management apparatus according to the embodiment of the present invention described above may be realized by a CPU (Central Processing Unit) reading and executing an operation program or the like stored in a memory, or configured by hardware. May be. Only some functions of the above-described embodiments can be realized by a computer program.

  A part or all of the above-described embodiment can be described as in the following supplementary notes, but is not limited thereto.

(Appendix 1)
Reading manual document data in which a management tag indicating the model version is inserted, and generating and storing a data table in which the text specified by the management tag is associated with the version indicated by the management tag. A featured manual creation information management device.

(Appendix 2)
The management tag further indicates a content identifier related to the content of the text specified by the management tag,
In the generation of the data table, the text specified by the management tag is stored in association with the version and content identifier indicated by the management tag,
A feature correspondence table in which a content identifier included in each data table is associated with a model name assigned to the data table is generated and stored with reference to the data table for each model. Manual creation information management device described in 1.

(Appendix 3)
When the manual document data is corrected, the content identifier corresponding to the corrected part is acquired, the model corresponding to the acquired content identifier is specified with reference to the feature correspondence table, and the manual document data of the specified model is specified. Correct the part corresponding to the content identifier of
The manual creation information management apparatus according to appendix 2, characterized by:

(Appendix 4)
When creating manual document data of another model based on manual document data of a certain model, the version and model name of the certain model and the above-mentioned separate tag for the management tag inserted in the manual document data of the certain model Convert to show the model version of
The manual creation information management device according to any one of appendices 1 to 3, characterized in that:

(Appendix 5)
5. A version number correspondence table in which a manual version number and a version number of a model corresponding to the manual are associated with each other is generated and stored for each model. Manual creation information management device.

(Appendix 6)
A process of extracting the difference by comparing the data table corresponding to a certain version number and the next version number is performed from the first version to the latest version, and the extracted difference is stored as revision history information.
The manual creation information management device according to appendix 5, characterized in that:

(Appendix 7)
Reading manual document data in which a management tag indicating the model version is inserted, and generating and storing a data table in which the text specified by the management tag is associated with the version indicated by the management tag. A featured manual revision management method.

(Appendix 8)
The management tag further indicates a content identifier related to the content of the text specified by the management tag,
In the generation of the data table, the text specified by the management tag is stored in association with the version and content identifier indicated by the management tag,
The feature correspondence table in which the content identifier included in each data table is associated with the model name assigned to the data table is generated and stored with reference to the data table for each model. Manual creation information management method described in 1.

(Appendix 9)
When the manual document data is corrected, the content identifier corresponding to the corrected part is acquired, the model corresponding to the acquired content identifier is specified with reference to the feature correspondence table, and the manual document data of the specified model is specified. Correct the part corresponding to the content identifier of
The manual creation information management method according to appendix 8, which is characterized by the above.

(Appendix 10)
When creating manual document data of another model based on manual document data of a certain model, the version and model name of the certain model and the above-mentioned separate tag for the management tag inserted in the manual document data of the certain model Convert to show the model version of
10. The manual creation information management method according to any one of appendices 7 to 9, characterized in that:

(Appendix 11)
11. A version number correspondence table in which a manual version number and a version number of a model corresponding to the manual are associated with each other is generated and stored for each model. Manual creation information management method.

(Appendix 12)
A process of extracting the difference by comparing the data table corresponding to a certain version number and the next version number is performed from the first version to the latest version, and the extracted difference is stored as revision history information.
The manual creation information management method according to Supplementary Note 11, wherein:

(Appendix 13)
On the computer,
A process of reading manual document data in which a management tag indicating a model version is inserted, and generating and storing a data table in which the text specified by the management tag is associated with the version indicated by the management tag; A program characterized by being executed.

(Appendix 14)
The management tag further indicates a content identifier related to the content of the text specified by the management tag,
The process of generating the data table includes a process of storing the text specified by the management tag in association with the version and content identifier indicated by the management tag,
Referring to the data table for each model, the computer executes a process of generating and storing a feature correspondence table in which the content identifier included in each data table is associated with the model name assigned to the data table The program according to appendix 12 or 13, characterized in that:

(Appendix 15)
When manual document data is corrected in the computer, a content identifier corresponding to the correction location is acquired, a model corresponding to the acquired content identifier is specified with reference to the feature correspondence table, and the specified model 15. The program according to appendix 14, wherein a process for correcting a portion corresponding to the content identifier of the manual document data is executed.

(Appendix 16)
When creating manual document data of another model based on manual document data of a certain model in the computer, the version and model name of the certain model for the management tag inserted in the manual document data of the certain model The program according to any one of appendices 13 to 15, wherein a process of converting to indicate a version of the different model is executed.

(Appendix 17)
From the appendix 13, wherein the computer is caused to generate and store a version number correspondence table that associates the version number of the manual with the version number of the model corresponding to the manual for each model. The program according to any one of 16 above.

(Appendix 18)
The computer compares the data table corresponding to a certain version number and the next version number, extracts the difference from the first version to the latest version, and executes the process of storing the extracted difference as revision history information The program according to appendix 17, characterized in that:

DESCRIPTION OF SYMBOLS 1 Input device 2 Data processing device 3 Storage device 4 Output device 21 Tag reading part 22 Change location presentation part 23 Template preparation part 24 Tag generation part

Claims (8)

Reading manual document data in which a management tag indicating the model version is inserted, and generating and storing a data table in which the text specified by the management tag is associated with the version indicated by the management tag. A featured manual creation information management device. The management tag further indicates a content identifier related to the content of the text specified by the management tag,
In the generation of the data table, the text specified by the management tag is stored in association with the version and content identifier indicated by the management tag,
The feature correspondence table in which the content identifier included in each data table is associated with the model name given to the data table is generated and stored with reference to the data table for each model. The manual creation information management apparatus according to 1 or 2. When the manual document data is corrected, the content identifier corresponding to the corrected part is acquired, the model corresponding to the acquired content identifier is specified with reference to the feature correspondence table, and the manual document data of the specified model is specified. Correct the part corresponding to the content identifier of
The manual creation information management device according to claim 2. When creating manual document data of another model based on manual document data of a certain model, the version and model name of the certain model and the above-mentioned separate tag for the management tag inserted in the manual document data of the certain model Convert to show the model version of
The manual creation information management apparatus according to any one of claims 1 to 3, wherein 5. The version number correspondence table in which the version number of the manual and the version number of the model corresponding to the manual are associated with each other is generated and stored for each model. 5. Manual creation information management device described. A process of extracting the difference by comparing the data table corresponding to a certain version number and the next version number is performed from the first version to the latest version, and the extracted difference is stored as revision history information.
The manual creation information management apparatus according to claim 5, wherein: Reading manual document data in which a management tag indicating the model version is inserted, and generating and storing a data table in which the text specified by the management tag is associated with the version indicated by the management tag. Characteristic manual creation information management method. On the computer,
A process of reading manual document data in which a management tag indicating a model version is inserted, and generating and storing a data table in which the text specified by the management tag is associated with the version indicated by the management tag; A program characterized by being executed.

Images