JPH09167087A - Software development environment management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To handle various object relative files through easy operation all over various definition information by performing display management control over a common part which is possibly referred to and used by plural layers in hierarchical structure of software. SOLUTION: A development environment information storage part 104 is stored with logical layer-directory structure correspondence information showing the correspondence between the hierarchical structure of software divided logically by designing operation in a high-order process and the hierarchical structure of physical directories structured on an operation computer. A development environment extracting means 105 extracts a physical directory meeting retrieval conditions specified with the logical layer-directory structure correspondence information stored in the development environment information storage part 104. A development information display management control means 106 performs display management control over the correspondence relation between software products obtained in individual operation processes and physical files on the operation computer.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software development environment management system, and more particularly to a software development environment management system in which a person in charge of software development does not need to be aware of locations and names of various related files.

[0002]

2. Description of the Related Art Conventionally, when software is developed using a workstation or a personal computer, a person in charge of software development actually creates various related files (specifications, design, etc.) for development work. Books, source programs, etc.) are often managed.
In such a case, there are the following general methods for managing various related files. The first management method is a hierarchical structure of software that is logically divided in advance in the design work of the upper process based on various design techniques such as a structured design technique and an object-oriented design technique. Hierarchical structures of the physical directories are built on a work computer, and various related files are stored in each directory so as to correspond to the hierarchical structure of the software. The second management method is to construct one physical directory on the work computer and store all the related files in the directory.

In the first management method described above, each person in charge of software development manages various related files while always being aware of the hierarchical structure of the physical directory defined in the OS on the work computer. To do. Therefore, when the logical hierarchical structure of software changes due to design changes or the like, each person in charge of development modifies various related files on the work computer so as to correspond to the new hierarchical structure of software. Will be required. In addition, in the second management method, it is necessary to always manage the correspondence between the logical hierarchical structure of software and various related files separately from the work computer.

[0004]

In the software development using the first management method described above, when the logical hierarchical structure of the software is changed in the upper process, each person in charge of development develops a new software. There has been a problem in that the work of changing the various related files on the work computer according to the hierarchical structure must be consciously executed under the responsibility of the developer. The contents of the specific modification work required at this time are the creation of a new physical directory corresponding to the new software hierarchical structure, and the creation of a new directory of various related files stored under the original directory. Copying and moving files, deleting the original directory and various related files that are no longer needed, and reconfirming the correspondence between the logical hierarchy of the new software and the physical directory hierarchy after the modification work. . In the above description, the names given to the new directories and various related files are restricted by the naming rules peculiar to the OS on the work computer, so that the names desired by the developer cannot always be given.

Common files that may be referenced and used from a logical hierarchy of a plurality of types of software are generally managed collectively under a physical directory dedicated to the common files. is there. Therefore, the person in charge of development asks whether or not the various related files to be referenced and used are common files, and under what directory if they are common files,
There was a problem that the development work had to be done while always being aware of the above. Furthermore, for software products such as programs, specifications, and design documents created by the execution of work processes, names are given according to the contents and types of software products according to predetermined rules, and then appropriate directories are created. Classify below and save,
There was a problem that each person in charge of development must always be aware of the work related to the management of software products. From the above, especially when multiple developers are involved in software development work, various types of definition information determined in advance corresponding to the hierarchical structure of software logically divided in the upper process All the information (information about the hierarchical structure of the physical directory, information about the common files and the directories in which the common files are stored, information about the created software products, etc.) However, there was a problem that the management work to be made known to all employees must be repeated.

The user-specific resource management method disclosed in Japanese Patent Laid-Open No. 1-158548 shares user-specific resources by separately managing user identification information and user-specific resources. It enables flexible management. However, management in this case is limited to individual resource management for each user, and nothing is said about resource sharing and management by logical division in software development in general. Also, it does not mention the management by product that must be defined for each process of software development.

Therefore, an object of the present invention is to solve the above-mentioned problems and to realize a hierarchical structure of a physical directory constructed on a work computer according to a logical hierarchical structure of software and a plurality of kinds of software. Each person in charge of development manages all kinds of definition information such as the location and name of common files that may be referenced and used from a logical hierarchy and the location and name of software products created in the work process. You can handle various related files that are directly referenced and used when executing development work processes without being aware of them with simpler operations than before, and it is also easy to general definition information related to all development work processes. The purpose is to provide a software development environment management system that can be managed by.

[0008]

In order to achieve the above object, the software development environment management system of the present invention comprises a hierarchical structure of software logically divided in the design work of a higher step in software development and a work computer. A development environment information storage unit storing logical hierarchy / directory structure correspondence information indicating correspondence with the hierarchical structure of the physical directory constructed above, and based on the information in the development environment information storage unit, the software A hierarchical environment, a hierarchical structure of the directory, each of the logical hierarchy / directory structure correspondence information, and development environment information display management control means for performing display management control of the corresponding relationship, and The development environment information display management control means is based on the information stored in the development environment information storage section. It is obtained to perform the display management control for the common parts that may be referenced and available from a plurality of hierarchies (such as a common file) in the hierarchical structure of the software.

In addition to the above, software product / physical file correspondence information indicating correspondence between software products created in individual work steps in software development and physical files on a work computer, or The software includes a development product information storage unit storing one or both of the work process / physical file correspondence information indicating the correspondence between the work process and the file, and the software based on the information in the development product information storage unit. Display management control for either the product and each of the software product / physical file correspondence information and mutual correspondence or the work process and each of the work process / physical file correspondence information and mutual correspondence. It is configured to include a development product information display management control means.

Further, based on the information in the development environment information storage unit, a physical directory matching the specified search condition is extracted, and the identification information of all the extracted directories is controlled by the development environment information display management control. Based on the information in the development environment information extraction means and the information in the development information storage unit to be passed to the means, a physical file matching the specified search condition is extracted, and the identification information of all the extracted files is used as the development information. And a development product information extraction means to be passed to the information display management control means.

As described above, the hierarchical structure of a physical directory constructed on a work computer according to the logical hierarchical structure of software, the possibility of being referred to and used from the logical hierarchy of a plurality of types of software. Without having to be aware of all the various definition information such as the location and name of a certain common file and the location and name of the software product created in the work process,
Various related files that are directly referenced and used when executing development work processes can be handled with simpler operations than before, and various general definition information related to all development work processes can be easily managed. .

[0012]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of a software development environment management system of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a block diagram showing a schematic configuration of an embodiment of a software development environment management system of the present invention. In the figure, 100 is a set of a plurality of physical files having a directory structure, 101 is a terminal device, and 10 is a terminal device.
2 is a logical hierarchy / directory structure display management control means, 1
Reference numeral 03 is a common part display management control unit, 104 is a development environment information storage unit, 105 is a development environment information extraction unit, 106 is a development product information display management control unit, 107 is a development product information storage unit, and 109 is an operation screen display management control. It is a means. The set 100 of physical files is used on a work computer and is usually stored in an auxiliary storage device such as a hard disk device. The terminal device 101 is for inputting and displaying figures and texts using a mouse and a keyboard. The logical hierarchy / directory structure display management control means 102 performs display management control on the correspondence relationship between the logical hierarchical structure of software and the physical hierarchical structure of directories. The common part display management control means 103 controls the display management of the common part corresponding to the logical hierarchy of the designated software.

The development environment information storage unit 104 shows the correspondence between the hierarchical structure of software logically divided in the design work of the upper process and the hierarchical structure of the physical directory constructed on the work computer. The logical hierarchy / directory structure correspondence information (including information about common portions that may be referenced and used from multiple hierarchies in the software hierarchy) is stored. The development environment information extraction means 105 extracts the logical hierarchy / directory structure correspondence information stored in the development environment information storage unit 104 from
Extract physical directories that match the specified search criteria.

The developed product information display management control means 106 carries out display management control of the correspondence between the software product created in each work process and the physical file on the work computer. The development product information storage unit 107 stores software product / physical file correspondence information indicating correspondence between software products created in individual work processes and physical files on the work computer. The development product information extraction unit 108 extracts a physical file that matches the specified search condition from the software product / physical file correspondence information stored in the development product information storage unit 107.

In addition to the above, the input operation performed by the terminal device 101 is transmitted to the development environment information extracting means 105 and the development product information extracting means 108, and the input operation from the development environment information extracting means 105 and the development product information extracting means 108 is performed. A portion for displaying output information on the terminal device 101 (logical hierarchy / directory structure display management control means 102, common portion display management control means 103, development information display management control means 10
6) is generically defined as operation screen display management control means. Among general computers, those equipped with a window system can easily realize an operation screen display management control means 109 capable of input / output control for inputting information from the screen and displaying information on the screen. can do.

FIG. 2 is a block diagram showing an example of a logical hierarchical structure obtained by dividing the software to be developed by the structured design technique. In the figure, each of 200 to 229 is each module constituting the software and its logical name. That is, 200 is the highest-level main system module “editor”, 210 is the subsystem module “file operation”, 220 is the subsystem module “edit”, 230 is the subsystem module “print”, and 290 is the inter-subsystem common module “ 221 is a basic system module "move", 221 is a basic system module "copy", 223 is a basic system module "delete", 22
Reference numeral 9 is a common module "edit (common part)" between basic systems. The main system module “editor” 200 has a subsystem module “file operation” 210 and a subsystem module “edit” 22.
0, subsystem module “print” 230, inter-subsystem common module “editor (common part)” 290
It is composed of Among these, the inter-subsystem common module “editor (common part)” 290 may be referenced and used by all other subsystem modules. Furthermore, the subsystem module “edit” 220 is the basic system module “move”.
221, a basic system module “copy” 222, a basic system module “delete” 223, and a basic system common module “edit (common part)” 229. Among these, the inter-basic system common module “edit (common part)” 229 may be referred to and used by all other basic system modules in the hierarchy below the subsystem module “edit” 220.

FIG. 3 is a diagram showing an example of a hierarchical structure of a physical directory constructed on a work computer for software to be developed. In the figure, 300-
Reference numerals 360 are physical directories. Under the root directory'C: \ '300, there are six types of directories'EDITOR' 310 and'FILE '32.
0, 'EDIT' 330, 'PRT' 340, 'COM
MON'350 and'EDITCOMMON'360 have been constructed. And further, the directory'EDI
Under T'330, there are three types of sub directories'MO.
VE'331, 'COPY'332,' DELETE '
333 has been built. In this way, a logical hierarchical structure obtained by dividing the software to be developed shown in FIG. 2 by the structured design technique and the OS on the work computer
Although it does not always match the hierarchical structure of the above-mentioned directory defined by, the conventional development work process requires the person in charge of development to carry out the work while always being aware of the corresponding relationship of the above-mentioned hierarchical structure.

FIG. 4 is a diagram showing an example of the logical hierarchy / directory structure correspondence information defined in advance for the "editor" shown in FIGS. In FIG. 4, first, in the system name “editor” 400 (main system module “editor” 200), which is the highest level software logical name, the physical directory “C: \ EDI
TOR "401 (= 'EDITOR' 310) is made to correspond. Next, the directory" C: \ FIL "is added to the subsystem name" file operation "(subsystem module" file operation "210) which is a lower software logical name.
E "(= 'FILE'320) in the directory" C: \ EDIT "(='EDIT'330) in the subsystem name" edit "(subsystem module" edit "220)
To the subsystem name "print" (subsystem module "print" 230) in the directory "C: \ PRT" (=
'PRT' 340) is made to correspond respectively,
At the same level as these subsystems, the keyword "C
OMMON ”402 allows the common directory“ C: ¥ CO ”as a common part of the entire system (inter-subsystem common module“ editor (common part) 290) ”.
The MMON "403 (= 'COMMON' 350) is made to correspond.

In addition, in the subsystem name "edit", the basic system name "move" (basic system module "move" 22
1) In the directory "C: \ EDIT \ MOVE" (=
'MOVE'331), the basic system name "copy"
(Basic system module “copy” 222) directory “C: \ EDIT \ COPY” (= 'COPY')
332) to the basic system name “deletion” (basic system module “deletion 223)” as “C: ¥ DELETE” (=
'DELETE'333) is made to correspond to each other, and the common part in the hierarchy below the subsystem name "edit" (common module between basic systems "edit (common part)"
229), the common directory "C: \ EDITC
OMMON ”(= 'EDITCOMMON' 360) is made to correspond.

In the definition example based on the logical hierarchy / directory structure correspondence information described above, one hierarchy structure is searched for from the keyword “BEGIN” 404 to the keyword “END” 405.
It is expressed by the description up to, and the correspondence of the physical file to be referenced and used as a common part differs depending on the position of the hierarchical structure in which the keyword "COMMON" is defined for the target of the common part. Becomes That is, in the definition example of FIG. 4, from the hierarchical structure of the lower logical software belonging to the subsystem names “file operation”, “edit”, and “print”, “C: ¥ COMMON” is defined in the same hierarchy. 401 can be referenced and utilized as a common part. Similarly,
Based on the hierarchical structure of the lower logical software belonging to the basic system names "move", "copy", and "delete", "C: \ EDITCOMMON" defined in the same hierarchy.
Can be referred to and used as a common part, and "C: \ C" which is a common part in the upper hierarchy.
The OMMON ”401 can also be referred to and used.

If the physical directory defined in the above-mentioned logical hierarchy / directory structure correspondence information is a directory that can be used by the OS on the work computer, there is some special correspondence with the logical hierarchy of software. There is no need to set a limit. In addition, here, the definition example when the software is divided by the structured design technique has been described, but the logical hierarchical structure of the software divided by the object-oriented design technique should also correspond to the physical directory as described above. Can be defined.

FIG. 5 is a flow chart for explaining general display management control based on the logical hierarchy / directory structure correspondence information in the system of FIG. In FIG. 5, first, the logical hierarchy / directory structure correspondence information as shown in FIG. 4 is read (step 500).
Then, the target software logical name is acquired from the read logical hierarchy / directory structure correspondence information (step 501). If it was the startup, step 501
Then, the software logical name set as a default in advance, such as the highest level software logical name and the software logical name at the time of the previous termination, is acquired. Next, of the physical directories built on the work computer, information about the one corresponding to the software logical name acquired above is extracted from the logical hierarchy / directory structure correspondence information (step 502). Then, based on the extracted physical directory information, the physical file information corresponding to the software logical name is output to the logical hierarchy / directory structure display management control means 102, and this information is displayed on the terminal device 101 (step 503). At this time, if there is other directory information corresponding to the software logical name, until all output of the corresponding physical file information to the logical hierarchy / directory structure display management control means 102 is completed, The processing from step 502 is repeated (step 504).

Next, in step 505 and thereafter, processing is performed on directory information that can be referred to and used as a common part among a plurality of software logical structures. At first,
It is confirmed whether the physical directory described by the keyword "COMMON" as a common part exists in the same logical hierarchy as the software logical name of interest (step 5).
05). Then, if there is a common part in the same logical hierarchy (step 505 = Yes), the physical directory information corresponding to the common part is extracted from the logical hierarchy / directory structure correspondence information (step 506) and based on this physical directory information. Then, the corresponding physical file information is output to the common part display management control means 103, and this information is displayed on the terminal device 101 (step 507). At this time, if other directory information corresponding to the keyword “COMMON” exists, the processing from step 506 is repeated until the output of the corresponding physical file information to the common part display management control means 103 is completed. (Step 508). If there is no common part in the same logical hierarchy (step 505 = No), the process jumps to step 509. Finally, if the keyword "COMMON" exists in the upper layer of the software logical name of interest, the keyword "CO" in the corresponding upper layer is used.
With respect to the directory information corresponding to "MMON", the processes from step 506 are repeated until the output to the common part display management control means 103 is completed in the same manner as described above (step 509).

When another software logical name is to be subject to display management control, by searching and inputting that software logical name from the terminal device 101,
With respect to an arbitrary software logical name and common part, it is possible to display the information of the corresponding physical file on the terminal device based on the corresponding physical directory information constructed on the work computer.

FIG. 6 is a diagram showing an example of the definition of the software product / physical file correspondence information regarding the software product created in the work process relating to the software to be developed. When developing software, products such as various specifications, design documents, and source programs are specified in advance, and each of them is installed on an OS on a work computer.
It is common to manage the files in correspondence with the physical files defined in. Here, as software products obtained by software development, "basic specifications" that describe the external specifications of the relevant software, "functional specifications" that describe the software configuration and interface, and the internal logic of the software are described. "Detailed design document", "source program" that describes a computer-recognizable programming language based on these software products. That is, in the definition example of FIG. 6, the physical file corresponding to the “basic specification” 610 is the physical file 611 with the extension “BSL” on the work computer. Similarly, the physical file corresponding to the “functional specification” 620 is the physical file 621 with the extension “FSL”, and the physical file corresponding to the “detailed design document” 630 is the physical file 631 with the extension “DDL”. . In addition, three types of physical files corresponding to the “source program” 640 are defined, and a physical file 641 with an extension “C”, a physical file 642 with an extension “ASM”, and an extension “H”, respectively. 'Physical file 64
3. The correspondence between software products and physical files can be described by not only the extension but also general regular expressions.
The physical file corresponding to 630 is "P01 * .DDL"
As a result, only the physical file with the first three letters “P01” and the extension “DDL” is described in “Detailed design document” 63.
It can also be regarded as 0. Further, although the software product and the physical file are associated with each other in the definition example of FIG. 6, the work steps such as “basic design” and “functional design” may be associated with the physical file.

FIG. 7 is a flow chart for explaining general display management control based on the software product / physical file correspondence information in the system of FIG. In the figure, first, the software product / physical file correspondence information as shown in FIG. 6 is read (step 70).
0). Then, the target software product name is acquired from the read software product / physical file correspondence information (step 701). If it was at startup,
In step 701, the software product name set as a default in advance, such as the initially defined software product name and the software product name at the end of the previous time, is acquired. Next, it is confirmed whether the physical file described in the software product / physical file correspondence information corresponding to the software product acquired above exists on the work computer (step 70).
2) If it does not exist (step 702 = No),
All the processes after step 703 are skipped. If it exists (step 702 = Yes), information about the corresponding physical file on the work computer is extracted (step 703), and the physical file information is output to the development product information display management control means 106. , Is displayed on the terminal device 101 (step 704).
At this time, in the software product / physical file correspondence information, if another rule of the physical file corresponding to the software product is defined, to the development product information display management control means 106 of all relevant physical file information. The processing from step 703 is repeated until all the outputs of are completed (step 705).

When another software product is to be subject to display management control, by searching and inputting the software product from the terminal device 101,
For any software product, the information of the corresponding physical file on the work computer can be displayed on the terminal device 101.

8 to 12 are views for explaining the display of the operation screen and the management control when the system of FIG. 1 is operated for the "editor" shown in FIGS. Here, a physical file corresponding to the software product "source program" belonging to the software logical hierarchy "print" is developed based on the logical hierarchy / directory structure correspondence information of FIG. 4 and the software product / physical file correspondence information of FIG. The display of the operation screen and the management control when the person in charge searches will be described.

In the operation screen shown in FIG. 8, reference numeral 800 indicates the name of the software logical layer currently being focused on as a search target, and logical layer designation for selecting and designating a software logical layer belonging to the same level as a new search target. GUI (Graphical User Interface), 810 is an upper migration GUI for selecting and designating the software logical hierarchy belonging to the upper hierarchy as a new search target, and 820 is selecting and designating the software logical hierarchy belonging to the lower hierarchy as a new search target GUI for lower-level movement, 83
0 is a display designating GUI for selectively designating a software product to be displayed on the operation screen, and 840 is a software logical name and a software product corresponding to the selection designating condition in the logical hierarchy designating GUI 800 and the display designating 830. A work file name display unit for displaying the correspondingly extracted physical file name on the work computer, and 850 is referred to as a common part under the selection designation condition in the logical hierarchy designation GUI 800 and the display designation 830. And a common file name display section for displaying a physical file name on a work computer that can be used.

The operation screen of FIG. 8 is the operation screen immediately after the system of FIG.
The highest software logic hierarchy "editor" is selected at 0, and the software product "basic specification" is selectively specified at the display designating GUI 830. Then, as a physical file name extracted from the work computer based on the selection and designation condition, the work file name display unit 84
"MAIN.BSL" is displayed in the common file name display section 8
“EDITCOMMON.BSL” is displayed at 50. That is, by referring to the operation screen at this time, each person in charge of development writes the basic specifications of the main system module "editor", which is currently focused, in the physical file "MAIN.BSL" and between other modules. The basic specifications of the common parts that may be commonly referenced and used in the physical file “ED
ITCOMMON. It is possible to easily understand that each is stored in the BSL ". Further, it is possible to easily find other necessary physical files related to software development work by performing the following display management control operations. Is possible.

FIG. 9 shows an operation screen when the software logical layer to be searched is being changed to "print". When the person in charge of software development gives an instruction operation to the lower movement GUI 820 displayed on the operation screen of FIG. 8 with a pointing device such as a mouse,
A menu selection GUI 821 is newly opened. At this time, in the menu selection GUI 821, the names of the three types of subsystem modules existing in the hierarchy immediately below the main system module “editor” which is currently being focused on according to the software hierarchical structure shown in FIG. "File operation" 821a, "Edit" 821b, "Print" 82
1c is displayed. At this point, the person in charge of development makes a "print" 82
When the selection designation operation is performed for 1c, the menu selection G
The UI 821 is closed, and the software logical layer of interest is changed from "editor" to "print". Accordingly, the display on the GUI 800 for logical hierarchy designation is changed from "editor" to "print", and the display on the work file name display unit 840 is changed from "MAIN.BSL" to "PRINT.BSL", respectively, and the common file is changed. The name display portion 850 displays “EDITCOMMON.
In addition to "BSL", a new "PRTCOMMON. BS
L ”is displayed. As a result, the operation screen shown in FIG. 9 changes to the operation screen shown in FIG.

By referring to the operation screen shown in FIG. 10, each person in charge of development confirms that the basic specifications of the subsystem module "print", which is currently under consideration, is the physical file "PRIN".
T. In BSL ", the basic specifications of common parts that may be commonly referenced and used with other modules are stored in the physical file" EDITCOMMON.
BSL "and" PRTCOMMON. It is possible to easily grasp that each is stored in the BSL ". Then, by performing another instruction operation for these physical files, it is possible to start the development work according to the physical files.

FIG. 11 shows the operation screen when the software product displayed on the operation screen is about to be changed to the "source program". The person in charge of software development uses a pointing device such as a mouse to display the image shown in FIG.
When an instruction operation is performed on the display designating GUI 830 displayed on the operation screen of FIG.
Opens anew. GUI 831 for menu selection at this time
Contains four types of definition item names “basic specification” 831a, “functional specification” 831b, “detailed design” 831c, and “source” described in the software product / physical file correspondence information shown in FIG. The program "831d" is displayed. At this point, the person in charge of development is "source program" 83
When the selection designation operation is performed for 1d, the menu selection G
The UI 831 is closed and the software product displayed on the operation screen is changed from the "basic specification" to the "source program". According to this, G for display designation
The display on the UI 830 is changed from “basic specifications” to “source program”, and the work file name display section 840 is displayed.
Instead of "PRINT.BSL", "PRT1.
C "," PRT2. C "," PRT. H ”,“ PRT.
"ASM" is displayed in the common file name display area 850 as "PRT".
COMMON. "EDITCOMM" instead of "BSL"
ON. H "," EDITCOMMON. C ”,“ PRT
COMMON. H ”,“ PRTCOMMON. C "is
Displayed respectively. As described above, the operation screen shown in FIG. 11 is changed to the operation screen shown in FIG.

By referring to the operation screen shown in FIG. 12, each person in charge of development finds that the source program of the subsystem module "print" which is currently under consideration is the physical file "PR".
T1. C "," PRT2. C "," PRT. H "," P
RT. The source program of the common part, which may be commonly referred to and used in other modules in the ASM, is a physical file "EDITCOM" as a common file.
MON. H "," EDITCOMMON. C "," PR
TCOMMON. H ”,“ PRTCOMMON. C "
It is easy to understand that they are stored in each.
By performing another instruction operation on these physical files, the development work corresponding to the physical files can be started.

In the above embodiment, the names of the physical files to be subject to display management control are displayed on the work file name display section 840 and the common file name display section 850. However, physical files belonging to different logical layers are displayed. Can be displayed at once with a hierarchical structure corresponding to the software logical hierarchy shown in FIG. 2, and display management control can be performed. Also, by sharing the logical hierarchy / directory structure correspondence information and software product / physical file correspondence information among multiple developers in charge of the same project or development team, they can be used jointly. It is possible to unify various definition items in many software logical hierarchies, common parts, and software products. In this way, if any changes are made to the software logical hierarchy, common parts, software products, etc., the manager who supervises the project, development team, etc. handles the logical hierarchy / directory structure correspondence information and software products / physical file correspondence. Only by rewriting the information contents to new ones, it becomes possible to make detailed information about the changed parts known to all developers.

As described above, it is possible to refer to and use from the hierarchical structure of the physical directory constructed on the work computer according to the logical hierarchical structure of software, and the logical hierarchy of plural kinds of software. There is no need for each person in charge of development to execute a development work process without being aware of all the definition information such as the location and name of a common common file and the location and name of software products created in the work process. Various related files to be directly referenced and used can be handled with simpler operations than before, and various definition information related to all development work processes can be easily managed.

[0038]

As described above in detail, according to the software development environment management system of the present invention, the hierarchical structure of the physical directory constructed on the work computer according to the logical hierarchical structure of the software, Development of various definition information such as location and name of common file that may be referenced and used from logical hierarchy of multiple types of software, location and name of software product created in work process, etc. The person in charge can handle various related files that are directly referenced and used when executing the development work process without being conscious of everything with a simpler operation than before, and various definition information related to all development work processes. The effect of being able to easily manage the whole is also obtained.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a schematic configuration of an embodiment of a software development environment management system of the present invention.

FIG. 2 is a block diagram showing an example of a logical hierarchical structure obtained by dividing software to be developed by a structured design technique.

FIG. 3 is a diagram showing an example of a hierarchical structure of a physical directory constructed on a work computer for software to be developed.

FIG. 4 is a diagram showing an example of logical hierarchy / directory structure correspondence information defined in advance for the “editor” shown in FIGS. 2 and 3;

5 is a flowchart for explaining general display management control based on logical hierarchy / directory structure correspondence information in the system of FIG.

FIG. 6 is a diagram showing an example of definition of software product / physical file correspondence information regarding a software product created in a work process relating to software to be developed.

7 is a software product of the system of FIG.
9 is a flowchart for explaining general display management control based on physical file correspondence information.

FIG. 8 is a diagram (No. 1) for explaining display of an operation screen and management control when the system of FIG. 1 is operated for the “editor” shown in FIGS. 2 and 3;

FIG. 9 is a diagram (No. 2) for explaining display of an operation screen and management control when the system of FIG. 1 is operated for the “editor” shown in FIGS. 2 and 3;

FIG. 10 is a diagram (part 3) for explaining display of operation screens and management control when the system of FIG. 1 is operated for the “editor” shown in FIGS. 2 and 3;
It is.

FIG. 11 is a diagram (part 4) for explaining display of an operation screen and management control when the system of FIG. 1 is operated for the “editor” shown in FIGS. 2 and 3;
It is.

FIG. 12 is a view for explaining display of operation screens and management control when the system of FIG. 1 is operated for the “editor” shown in FIGS. 2 and 3 (Part 5).
It is.

[Explanation of symbols]

 100 a set of physical files having a directory structure 101 terminal device 102 logical hierarchy / directory structure display management control means 103 common part display management control means 104 development environment information storage section 105 development environment information extraction means 106 development product information display management control means 107 Development product information storage unit 108 Development product information extraction unit 109 Operation screen display management control unit 800 Logical hierarchy designation GUI 810 Upper migration GUI 820 Lower migration GUI 830 Display designation GUI 840 Work file name display unit 850 Common file name display Department

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Kiyomi Iwashita, 216 Totsuka-cho, Totsuka-ku, Yokohama, Kanagawa, Ltd.Hitachi, Ltd., Information & Communication Division (72) Inventor, Yoshimi Saito, 216 Totsuka-cho, Totsuka-ku, Yokohama, Kanagawa Bunka Co., Ltd.Hitachi, Ltd., Information & Communication Division

Claims (5)

[Claims] 1. A logical hierarchy directory showing a correspondence between a hierarchical structure of software logically divided in the design work of a high-order process in software development and a hierarchical structure of a physical directory constructed on a work computer. A development environment information storage unit in which structure correspondence information is stored, and based on the information in the development environment information storage unit, the hierarchical structure of the software, the hierarchical structure of the directory, the logical hierarchy / directory structure correspondence information, and each other. A software development environment management system comprising: a development environment information display management control means for performing display management control of correspondence relationships. 2. The development environment information display management control means,
Based on the information stored in the development environment information storage unit, display management control is performed for a common portion that may be referenced and used from a plurality of layers in the hierarchical structure of the software. The software development environment management system according to claim 1. 3. Software product / physical file correspondence information indicating correspondence between software products created in individual work steps in software development and physical files on a work computer, or the work steps and the above 3. The software development environment management system according to claim 2, further comprising: a development product information storage unit that stores one or both of work process / physical file correspondence information indicating correspondence with a file. 4. Each of the software product and the software product / physical file correspondence information and the corresponding relationship based on the information in the development product information storage section,
Alternatively, it is configured to include a development product information display management control means for performing display management control for each of the work process, each of the work process / physical file correspondence information, and mutual correspondence relations. Item 3. A software development environment management system according to item 3. 5. A physical directory matching the specified search condition is extracted based on the information in the development environment information storage unit, and identification information of all the extracted directories is used as the development environment information display management control means. Based on the information in the development environment information extraction unit and the development environment information extraction unit to be passed to, the physical files that match the specified search conditions are extracted, and the identification information of all the extracted files is the development information. 5. The software development environment management system according to claim 4, further comprising: a development product information extraction unit that is passed to the display management control unit.