Hitachi, Ltd.

Hitachi Software Engineering Company, Ltd.

Hitachi Microcomputer Engineering, Ltd.

Hitachi Computer Engineering Co., Ltd.

Hitachi Keiyo Engineering Co., Ltd.

Hitachi Chubu Software, Ltd.

Hitachi Seibu Soft Ware Co., Ltd.

Hitachi System Engineering, Ltd.

Hiroyuki Maezawa

Ichiro Naito

Kazumasa Saito

Masakazu Kobayashi

Shinobu Koizumi

Yoshihiko Futamura

Hirokazu Mimura

Junko Sakata

Noriyuki Takahashi

Kazuo Takaragi

Ryoichi Sasaki

Hiroshi Matsumoto

Takahiko Kobayashi

Tetsuo Tanaka

Hiroshi Koike

Seiichi Susaki

Hirofumi Danno

Hiroshi Tsukino

Koichi Yamano

Singi Domen

Gunji Tsukuda

Akiko Fukuya

Hidetosi Katumata

Hidehiro Oomae

Kaori Kondoh

Koichi Taguchi

Masashi Amano

Hideo Kamiko

Kazutoshi Tamura

Hiroshi Isobe

Toshio Kinoshita

Takanobu Shimono

Junko Yamaguchi

Takeshi Oshio

Ryoji Eguchi

Yoshimitsu Shindo

Masato Takadachi

Mihoko Iwasaki

A reverse engineering method for supporting software reuse in generating an upper level software product from a lower level software product allowing the reuse of some software product's among multi-level software products ranging from an upper level data flow to a lower level job flow. The method includes the steps of: generating an upper level software product using a lower level software product; generating relational information between the lower and upper level software products; inputting a request for changing the upper level software product via an input/output interface; changing the upper level software product in response to the change request; and detecting a reusable field of the lower level software product which is not to be changed, in response to a change of the upper level software product. A pair of the lower level software product and the upper level software product comprise an internal design and an external design which is higher in level than coded programs and an external design and detailed requirements a user supplied. Information representative of a reusable field with no change and a field that is not reusable which requires a change of the lower level software product, may be provided. The information is obtained by comparing the upper level software product with the lower level software product.

Method and apparatus for detecting a lower level software reusable

A slip processing method for simplifying a processing of a job which uses a form of a predetermined format at a frequency of once a long term such as month, quarter or year and in which an input form is changed at a frequency of once per several times of use. The method comprises storing format information of an input form and data information in one file, providing a format of the input form including a plurality of tables each comprising a plurality of items (cells), storing data in corresponding ones of the items, executing a retrieval of the items and a totalization of data in the items with referencing a file which stores the format information and the data of the input form and storing the format information and the data of the input form and the processed information in a form which is transmittable through a network.

Slip processing method processing data from slips with varying formats

In a terminal which received an electronic document with at leastone digital signature, when a user changes the contents of the received electronic document, a new digital signature is produced by enciphering signature data by using a secret key of the user, the signature data including a hash total of the document of a new version, personal information of the user (signatory), and version management information necessary to restore an electronic document of a former version from the electronic document of the new version. The new digital signature and the new version electronic document version are transmitted together with the received digital signature to a next person on a document circulating route.

Electronic document processing system and method of forming digital

A design supporting method having a specification edit function in an information processing system having a computer and an interactive terminal is disclosed. Items to be described in a specification are correlated among specifications so that when an item described in the specification is modified, a portion which is possibly affected by the modification can be analyzed.

Software design supporting method for classifying portions possibly

Disclosed herein is a data edition supporting method in an information processing system having a computer, interactive terminals and a clock. The method comprises the steps of finding from the clock the time at which a data item was edited; of storing the obtained time in relation to its corresponding data item; of checking to see whether, during data editing by use of an interactive terminal, the data editing time comes before or after a certain time; and of determining the type of editing in accordance with the results of the judgment made in the preceding step.

Method and system for editing data by limiting current operations in

A display method in an information processing device for use in software development support includes the steps of analyzing a software product before change and a software product after change. Respectively forming structure information before change and structure information after change, which consist of software element informations correlated with each other, in accordance with the respective structures of the software products. Forming structure information that forms a union set of the before-change structure information and said after change structure information, which includes all the software element informations before and after change, and appending identification information representative of the manner of change in each software element to the union set structure information. Converting at least a part of the union set structure information into its graphic format so as to be produced together with the representations of the change manners represented by the identification information.

Display method in software development support system

A support method of and apparatus for making/editing a formatted document including a plurality types of formatted documents having a mutual relation therebetween. An input device inputs beforehand a relation between document forms before a formatted document is made, the inputted relation is stored in a storage device, and a relation between formatted documents is automatically generated by referring to the relation stored in the storage device.

Method and apparatus for supporting of making formatted document

A program change effect indicating method for use in a computer system designed to support the determination of parts to be changed in a program. Change steps associated with the method include; the steps of generating analyzed program information by analyzing a program, the analyzed program information representing attributes of respective statements in the program which constitute the program as well as connections between the statements; generating, in accordance with predetermined program intention determining rules, program intention information representing the intentions of the respective statements in the program from the analyzed program information. Inputting change designating information designated by a user which represents a statement to be changed and the contents of the changes; Further change steps associated with the method includes generating, in accordance with predetermined change detail determining rules, change effect information which identifies statements to be changed in association with the change designated by the user and the contents of the required changes from the program intention information, the information representing the relationship between the statements, and the change designating information; and outputting the change effect information.

Method and system for outputting program change effect information to a

A data name standardizing/unifying system for standardizing the names of data belonging to data items having different names and transferred or compared among data files so as to be unified for programs. For standardizing the data names, names of data items assumed to have same contents are gathered and a table indicating data names to be replaced are generated to be displayed together with prompting for entry of the standard data name to replace. From this table, standardization for data names is accomplished by this replacement of the data name in the programs. For identifying the standardized data names created for the different files, different file names or different and upper file names are added to a division of program which refers to the files.

Data name standardizing system

According to the present invention, using a display terminal for conversation, a module structure diagram (schemata expressive of the connectional relations among respective program modules) is created, and a processing flow diagram (a kind of processing flow chart), an internal data definition diagram (schemata for specifying the formats etc. of data for use in processes) and an interface data definition diagram (schemata for specifying the formats etc. of arguments, common data between the modules, etc.) are created for each module, the created contents being stored in a memory. Further, the schematic information items of the module structure diagram, processing flow diagram, internal data definition diagram and interface data definition diagram are read out from the memory for each module and have stereotyped sentences and symbols added thereto, to generate the individual sentences of a source program. These sentences are edited according to the rules of a language, to complete the source program. If necessary, the various diagrams are printed out and utilized as program specifications.

System and method of generating a source program from inputted schematic

Method of generating a source program from inputted schematic information

A diagrammatic method is disclosed of testing a program in a data processing system equipped with a display terminal for interactive operations. Program specification inputs are given in a diagrammatic form through interactive operations and are edited into diagrammatic specifications. Those diagrammatic specifications are then translated into a source program described in, for example, FORTRAN, in which are interspersed comment statements each of which indicates a diagrammatic specification corresponding to the associated statement of the source program. In the course of a test the diagrammatic specification corresponding to a process under execution is retrieved and displayed according to a comment statement, and the portions corresponding to executed operations are displayed distinctively, for example, in a special color, while the resultant values of variables are also displayed.

Diagrammatic method of testing program

Growing community of inventors

Tama, Japan

Hiroyuki Maezawa