Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/10—Requirements analysis; Specification techniques

Definitions

• the present invention relates to a design information management method and system for managing the relationship between design information and design information in software development.
• Patent Document 1 a design information identification ID is assigned to the design information described in the software product, the design information identification ID is described on the vertical axis and the horizontal axis, and the intersection of the vertical axis and the horizontal axis is described. A cross-reference table marked manually is created to manage the relationship between design information identification IDs. As a result, the location of the design information identification ID between the upstream design information and the downstream design information is identified and the description location is specified.
• Patent Document 2 when creating a software product from upstream to downstream with the CASE tool, tags with the same number are attached to the design information related to each other, and the relationship between the design information is managed.
• Patent Document 1 Japanese Patent Laid-Open No. 10-105390
• Patent Document 2 Japanese Patent Laid-Open No. 08-147151
• Patent Document 1 since a cross reference is created separately from a software product, If the air product is corrected, the cross reference must also be corrected. If the correction of the cross reference is omitted, the relationship cannot be made and the description part cannot be specified.
• Patent Document 2 when design information is refined from upstream to downstream, the design information is often implemented in a terminal program through branching, merging, etc., as in this example, from upstream to downstream. If the same tag is attached, the downstream design information that is not directly related will be related.
• the object of the present invention is to manage the relationship between design information when software products are corrected in view of the above-mentioned problems of the prior art, and the design information of the upstream process is expanded to the design information of the downstream process. It is to provide a design information management method and system that can surely check whether or not the
• the present invention for solving the above-described problem is that upstream design information, downstream design information, and the relationship between them are created when software is created while design information is broken down step by step upstream.
• a design information identification ID is assigned to a predetermined range in the software product in advance as a description rule of the software product, and further, an upstream design information identification ID related to the software product.
• a design information identification ID is obtained from the predetermined range, and the design information identification ID is upstream of other design identification information IDs.
• the modification not completed is set in the related information of the downstream design identification information ID with respect to the design information identification ID.
• the design information management system of the present invention when creating a software product while stepping down design information from upstream to downstream, creates upstream design information, downstream design information, and their information.
• a product storage unit that stores software products, and a design information identification ID and design information from the software products And upstream software configuration It has a function to extract design information identification IDs that indicate the relationship with fruits, stores design information in software products in units of design information identification IDs, and stores relationships between design information identification IDs in software products. It is characterized by having a design information analysis means.
• the required specification power determined in the upstream process is clearly specified in the software product in the downstream process, and it can be proved that the function has been verified without omission, thereby improving the quality of the software. There is an effect that can be done.
• management based on customer requirements is easy, making it easier to modify and confirm software.
• FIG. 1 shows a system configuration diagram of an embodiment of the present invention.
• the design information management system includes a design information management machine 101 that manages created products, an operation terminal 102 that is operated by a developer, and a network 103 that connects them.
• the design information management machine 101 includes a product storage unit 107 that stores product information 108 of the created product, and a design information storage unit 104 that stores design information 106 extracted from the product and related information 105.
• a request reception unit 114 that receives registration of a product from the operation terminal 102, a product registration unit 109 that stores the product in the product information 108, and design information that extracts design information from the product registered in the product information 108 It consists of an analysis unit 110, design information 106, and a reference unit 111 that references related information 105.
• the operation terminal 102 refers to the registration request unit 112 that requests the design information management machine 101 to register the deliverable, the design information 106 registered in the design information management machine 101, and the related information 105.
• the reference request unit 113 requests the reference unit 111.
• FIG. 2 shows the overall flow of product registration.
• the operator selects (201) the deliverable created according to the description rule on the operation terminal 102, then selects (202) the category of the selected deliverable (S: design, T: verification), and the registration request unit 112 Requests registration (203) of the selected deliverable to the design information management machine 101.
• the request reception unit 114 receives the product requested to be registered from the registration request unit 112 (204).
• the received product is registered in the product information 108 of the product storage unit 107 by the product registration unit 109 (205).
• the Design Information Analysis Department 11 The contents of the deliverable are analyzed by 0 (206), and the analyzed result is registered (207) in the design information 106 and related information 105 of the design information storage unit 104, and the result is returned to the operation terminal 102.
• FIG. 3 shows an example of a product created in accordance with the description rule.
• the design information starts with the keyword & s &, and the block enclosed by & e & is one design information, and the character described after & s & is the design information identification ID for identifying the design information.
• the required specification of the system is described in the required specification 301, and the design information "automatically closes the gate when the signal is turned on” is the design information identification ID "required specification. 1 ”is described as 304.
• the design information identification ID “Required specification 1” 304 is set with the change ID “M1” for linking with the system that manages the content, cause, or countermeasure of the change!
• design information identification ID “Required specification 2” 305 is described as design information identification ID “Required specification 2” 305.
• the design information “Function specification 1” 30 “Design information is confirmed that the controller X signal is turned on and the gate is closed by turning off the Y signal”. Described as 6.
• “Functional specification 1” 306 describes the functional specification with reference to the design information of the design information identification ID “Required specification 1” 304 in the requirement specification 301.
• “Function specification 2” 307 describes the functional specification by referring to the design information identification ID “Required specification 2” 305 of the requirement specification 301.
• design information identification IDs “verification specification 1” 308, “verification specification 2” 309, “verification specification 3” 310, and “verification specification 4” 311 are respectively described.
• Design information identification ID “Verification specification 1” 308 is “Required specification 1” 304
• “Verification specification 2” 309 is “Required specification 1” 304
• “Verification specification 3” 310 is “Required specification 2” 305
• “Verification specification 4” 311 refers to the design information of “Required specification 2” 305 and describes the verification specification.
• the relationship between deliverables is represented as 1: 1, but it is also possible to use l: n.
• FIG. 4 shows data structures of the product storage unit 107 and the design information storage unit 104 managed by the design information management machine 101.
• the product information 108 of the product storage unit 107 is a product ID 401 and product ID for managing the product requested to be registered in the design information management machine 101 from the operation terminal 102 and identifying the product name.
• the version 402 representing the number of times of change is configured as unique information.
• the latest information is available when there are multiple versions 402 of the product name 403 with the full path of the file name indicating the location of the product, the update date 404 that is the date of the product file, and the same product ID 401
• the design information 106 in the design information storage unit 104 manages the design information identification ID extracted from the deliverable by the design information analysis unit 110, and changes the design information identification ID 406 and design information identification ID 406 that represent the design information. Version 407 representing the number of times is configured as unique information. In addition, it has a category 408 (S: design, T: verification) that represents the type of product, and a product ID 409 that represents the product from which the design information identification ID 406 has been extracted. Furthermore, when the design information 411 and the design information 411 corresponding to the product version 410 and the design information identification ID 406 are changed, it is composed of a change ID 412 for linking with the system that manages the contents, cause, or countermeasure of the change.
• “Required specification 1” of design information identification ID 406 includes version 1 and version 2. Version 1 of design information identification ID “Required specification 1” is extracted from version 1 of product ID “S1”, Version 2 of design information identification ID “Required specification 1” is extracted from version 2 of product ID “S1” Design information.
• the related information 105 manages the relation extracted from the product by the design information analysis unit 110, and is created by referring to the design information of the upstream design information identification ID 412 and the upstream design information identification ID 412 of the upstream process. It is configured as the downstream design information identification ID 413 of the process.
• a modification flag 414 indicating that the design information of the upstream design information identification ID 412 has been modified has an ONZOFF value. When ON, it indicates that the design information of the upstream design information identification ID 412 has been modified, and when OFF, it indicates that the design information of the upstream design information identification ID 412 has been modified.
• “required specification 1” of the upstream design information identification ID 412 indicates that it is related to “functional specification 1”, “verification specification 1”, and “verification specification 2” of the downstream design information identification ID 413. Since the design information of “Required specification 1” of upstream design information identification ID 412 has been revised, The identification information ID413 ⁇ Function specification 1 '', ⁇ Verification specification 1 '', ⁇ Verification specification 2 '' design information must be corrected! /, Indicating that the correction flag 414 value is ON! / RU
• the design information identification ID “required specification 1” 406-1 of the design information 106 is expanded to the downstream process using the structure of FIG.
• the design information identification ID “required specification 1” 406-1 is searched from the information identification ID 412.
• the downstream design information identification ID “functional specification 1” 413-1 is acquired from the upstream design information identification ID “required specification 1” 412-1.
• the obtained downstream design information identification ID “functional specification 1” 413-1 is searched for the design information identification ID 406 of the design information 106, and the design information identification ID “functional specification 1” 406-2 information of the design information 106 is obtained.
• the design information identification ID “functional specification 1” 406-2 is S (design)
• the design information identification ID “required specification 1” 406-1 design information is the design information identification ID “functional specification 1”. It is possible to verify that it has been expanded to downstream processes at 406-2.
• the design information identification ID “request” is determined from the upstream design information identification ID 412 of the related information 105.
• the downstream design information identification ID “verification specification 1” 413-2 is acquired from the acquired upstream design information identification ID “required specification 1” 412-2.
• the obtained downstream design information identification ID “Verification specification 1” 413-2 is searched from the design information identification ID 406 of the design information 106, and the information of the design information identification ID “Verification specification 1” 406-3 of the design information 106 is obtained. can get.
• the functional verification of the design information identification ID “Required specification 1” 406-1 is performed by the design information identification ID “Verification specification 1”. It can be verified that it is implemented in 406-3.
• Fig. 5 shows a product registration flow.
• Product registration unit 109 registers product information 108
• the product name to be registered is searched from the product name 403 of the product information 108, and it is determined whether the product to be registered has already been registered in the product information 108 (501).
• the product to be registered does not exist in the product information 108, the product is newly registered in the product information 108 (506), and the version is set to 1 (505).
• the registered product (previous version) is acquired (502). The contents of the obtained deliverable and the deliverable to be registered are compared (503).
• the return value is returned as unregistered (508) without being registered in the deliverable information 108. If the contents do not match, the value of the previous version + 1 (504) is set for the version of the corresponding product, and the product specified in the product information 108 of the product storage unit 107 is registered (506). Return registration (507). When the product is registered in this manner, the product ID 401, the version 402, the product name 403, the update date 404, and the latest flag 405 are set in the product information 108 of FIG.
• FIG. 6 shows a design information analysis flow for analyzing the deliverable.
• the design information analysis unit 110 starts the analysis by specifying the product name and the product category (S: design, T: verification).
• the design information analysis unit 110 opens the designated deliverable (601), and searches for the character (& s &) indicating the design information identification ID according to the description rule shown in FIG. 3 (602).
• the keyword is searched, the character design information identification ID after the keyword is acquired (603), and the design information is registered (604).
• Registration is registered in the design information 106 of the design information storage unit 104 in the specified product category (S: design, T: verification).
• the related information 105 in the design information storage unit 104 is searched to determine whether the design information identification ID acquired in step 603 is registered as the upstream design information identification ID 412 (606). If it is registered as upstream, the design information of the downstream design information identification ID 413 related to the acquired design information identification ID needs to be corrected, so the correction flag 414 of the related information 105 is set to ON ( 607).
• the related information 105 in Fig. 4 as an example, if the design information of the requirement specification 1 that is the upstream design information identification ID is modified, the downstream design information identification ID function specifications 1, verification specifications 1, and verification specifications 2 This indicates that the correction flag in the line is turned ON.
• the upstream design information identification ID is acquired (608) and registered in the related information 105 of the design information storage unit 104. (609). That is, the upstream design information identification ID acquired in the upstream design information identification ID 412 is registered), the design information identification ID acquired in the downstream design information identification ID 413 is registered, and the correction flag 414 is set to OFF by default and registered.
• FIG. 7 shows a flow for registering the design information identification ID in the design information 106 of the design information storage unit 104.
• the design information identification ID extracted in step 603 in FIG. 6 is searched for the design information identification ID 406 of design information 106, and it is determined whether the design information identification ID to be registered is already registered in the design information 106. (701).
• 1 (705) is set to the version of the design information identification ID (603) registered in the design information (106).
• the design information identification ID 603 to be registered is already registered in the design information 106, the design information of the previous purge is acquired (702), and the acquired design information is compared with the contents of the registered design information (703). ) If the contents match, the return value is returned as unregistered (711) without registering in the design information 106. If the contents do not match, the value of the previous version + 1 (704) is set in the version of the extracted design information identification ID. Taking design information 106 in Fig. 4 as an example, when registering requirement specification 1 of design information identification ID 406, requirement specification 1 of design information identification ID is already registered as version 1, so the next version to be registered is Register as 2.
• the product category (SZT) designated when the product registration request is made is determined (706).
• the category to be registered in the design information 106 to 'S' (707)
• the category is the verification process
• the changed design information identification ID can be tracked with respect to the change ID. If the design information identification ID can be specified, the product name can be specified by the product ID 409 and the product version 410 of the design information 106.
• FIG. 8 shows an example of a registration request screen operated on the operation terminal 102.
• the registration request screen It consists of an operation area 801 representing the operation of the operator, a product selection area 802 representing the product structure on the operation terminal side in a tree structure, and a design information extraction area 80 3 representing the result of extracting the design information in the product. .
• the registration request unit 112 requests the registration request unit 114 to register the product created by the operator, and confirms the analysis result by the design information analysis unit 110. The procedure to do is explained.
• the developer extracts design information created by the operation terminal 102 from the product selection area 802. After selecting the deliverable, select the category 805 of the selected deliverable and press the button for registration request 804. When the registration request 804 button is pressed, the name of the selected product and the design information extracted from the product are displayed in the design information extraction area 803. Check the consistency of the relationship between the displayed design information identification ID 808 and the upstream design information identification ID 809. If there is a mistake in the extracted information, correct the deliverable in the operation terminal 102 and request registration. Do.
• design information identification IDs “functional specification 1” 808-1 and “functional specification 2” 808-2 are extracted.
• Design information identification ID “functional specification 1” 808 1 is upstream design information identification ID “required specification 1” 809—1
• design information identification ID “functional specification 2” 808 2 is upstream design information identification ID “request” Spec 2 ”809 2
• FIG. 9 shows an example of the verification screen displayed on the operation terminal.
• the verification screen has a design information identification ID 904 registered in the design information management machine 101 and a design information identification ID selection area 901 for displaying the design information 905. Furthermore, it is composed of a design information identification ID expansion area 902 that indicates that the design information identification ID is expanded downstream, and a verification information area 903 that displays verification contents for the design information identification ID. .
• a procedure for verifying whether the design information identification ID 904 registered in the design information management machine 101 has been developed in the downstream process will be described with reference to FIG.
• the operator selects the design information identification ID 904 displayed in the design information identification ID selection area 901.
• the downstream design information identification ID related to the selected design information identification ID 904 in the design information identification ID expansion area 902 is displayed as an expanded view of the design information identification ID. It can be verified whether it is deployed in downstream processes.
• a mark (*) is given to the design information identification ID.
• the verification information area 903 displays the design information identification ID of the verification process related to the selected design information identification ID, and confirms whether the design information identification ID can be verified. be able to.
• Design information identification ID “required specification 1” 906 design information is expanded to design information identification ID “functional specification 1” 907.
• Design information identification ID “Function Specification 1” 907 design information is assigned to Design Information Identification ID “Processing Specification 1” 908, Design Information Identification ID “Processing Specification 2” 909, Design Information Identification ID “Processing Specification 3” 910, respectively.
• the design information identification ID “required specification 1” 906 may be functionally verified with the design information identification ID “verification specification 1” 911-1 of the verification process and the design information identification ID “verification specification 2” 911 2. I understand.
• FIG. 10 shows an example of a correction instruction screen operated by the operation terminal.
• the correction instruction screen includes a correction instruction display area 1001.
• design information identification ID 1002, design information 1003, and upstream design information identification ID 1004 are displayed in the correction instruction display area 1001, and the design of the upstream design information identification ID “required specification 1” 1005-1 is displayed. Instructs the correction of information.
• Design information identification ID “Verification specification 2” 1002-3 Modify design information.
• FIG. 1 is a functional block diagram of a design information management system according to one embodiment of the present invention.
• FIG. 3 An explanatory diagram showing an example of a deliverable.
• FIG. 8 Screen display of product registration on the operation terminal.
• FIG. 9 A screen shot of the verification of the operation terminal.
• FIG. 10 A display screen view of the operation terminal correction instruction.

Landscapes

• Engineering & Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Software Systems (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Stored Programmes (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Priority Applications (1)

Applications Claiming Priority (2)

Publications (1)

Family

ID=38287428

Family Applications (1)

Country Status (3)

Families Citing this family (5)

Citations (3)

Family Cites Families (7)

• 2006
  • 2006-01-23 JP JP2006013950A patent/JP4920978B2/ja not_active Expired - Fee Related
  • 2006-12-20 WO PCT/JP2006/325362 patent/WO2007083472A1/ja active Application Filing
  • 2006-12-20 CN CN200680051676.7A patent/CN101361040B/zh not_active Expired - Fee Related

Patent Citations (3)

Also Published As

Similar Documents

Legal Events