WO2006135607A2 - Procede et systeme pour le deploiement et le developpement rapide de logiciel d'application et d'essai et de documentation - Google Patents

Procede et systeme pour le deploiement et le developpement rapide de logiciel d'application et d'essai et de documentation Download PDF

Info

Publication number
WO2006135607A2
WO2006135607A2 PCT/US2006/021917 US2006021917W WO2006135607A2 WO 2006135607 A2 WO2006135607 A2 WO 2006135607A2 US 2006021917 W US2006021917 W US 2006021917W WO 2006135607 A2 WO2006135607 A2 WO 2006135607A2
Authority
WO
WIPO (PCT)
Prior art keywords
providing
generating
module
imported
functional
Prior art date
Application number
PCT/US2006/021917
Other languages
English (en)
Other versions
WO2006135607A3 (fr
Inventor
Dennis H. Edwards
Timothy B. Alosi
Carter R. Bayly
Terry J. Seanard
Jason D. Cummings
Original Assignee
New England Controls, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New England Controls, Inc. filed Critical New England Controls, Inc.
Publication of WO2006135607A2 publication Critical patent/WO2006135607A2/fr
Publication of WO2006135607A3 publication Critical patent/WO2006135607A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/73—Program documentation
    • G06F11/3664—

Definitions

  • the present invention generally relates to application and test software systems and methods, and more particularly to an improved method and system for rapid deployment and development of application and test software and documentation.
  • a system, method, and computer program product for deployment and development of application and test software and documentation.
  • the system, method, and computer program product can include at least one of converting exported control system data files and populating a database with the converted information, and generating a report on imported objects and logging import errors; providing a graphical user interface module, including at least one of providing a graphical representation of unit operation, allowing modification of imported data, providing a playback function for displaying a process step through phases, providing a step-by-step function, providing an auto-step function, providing an edit function for changing a configuration, providing a go-to function to jump to a selected phase and step, displaying operations and unit procedures, entering data in place of using imported code, and importing graphical information from a computer-aided design (CAD) drawing; providing a functional requirement specification module, including at least one of generating a functional requirement specification for a unit class, and generating a functional requirement specification change log; providing a free
  • FIG. 1 illustrates an exemplary process for application development on control systems
  • FIG. 2 illustrates an exemplary system for rapid deployment and development of application and test software and documentation
  • FIG. 3 illustrates an exemplary project entry user interface screen
  • FIG. 4 illustrates an exemplary import utility user interface screen
  • FIG. 5 illustrates an exemplary Functional Requirements Specification (FRS) generation user interface screen
  • FIG. 6 illustrates an exemplary auto test utility user interface screen
  • FIG. 7 illustrates an exemplary main program user interface screen
  • FIG. 8 illustrates an exemplary file selection user interface screen
  • FIG. 9 illustrates an exemplary discrepancy log form
  • FIG. 10 illustrates an exemplary explorer type map user interface screen
  • FIG. 11 illustrates an exemplary step editor user interface screen
  • FIG. 12 illustrates another exemplary step editor user interface screen.
  • CSRPT Prototype Tool
  • process engineers use Piping and Instrument Drawings (P&ID's) 104 as a vehicle, for example, to visualize the operation of a plant. They also use Process descriptions 106 to define overview functionality and process ranges.
  • the visualization from the P&ID's 104 is recorded in a Functional Requirements Specification (FRS) 108.
  • FRS Functional Requirements Specification
  • a process control engineer performs a quality check and reviews the FRS 108, the P&ID's 104 and an Instrumentation list 110 to check for consistency between and within each document. Any inconsistencies are flagged and the FRS 108 is revised.
  • step S 106 from the documents that pass through the quality check, a detail design is developed. This design is recorded in the Detailed Design Specification (DDS) 112.
  • step S108 application code is developed from the DDS 112.
  • step SI lO internal testing is conducted on the completed Code 114. This can include various types of tests, such as a structural test that verifies that the application code 114 works, a functional test that verifies that the code 114 does what the FRS 108 requested, and the like.
  • step Sl 12 validation testing can be conducted to confirm that the code 116 follows the FRS 108.
  • FIG. 2 illustrates an exemplary system 200 for rapid deployment and development of application and test software and documentation, and can include various modules used to enter, manage, use, and the like, the data that defines the application, and as further described.
  • an import module 202 can convert exported control system data files 204 (e.g., .fhx export file(s) for DeltaV, other file formats for other control systems, etc.), and populate a database 206 with this information.
  • the importing can write the data for the 1 st time, and if the data is already there, the operator can be requested to approve the replacement.
  • a report 208 on the objects imported and errors encountered can be generated and logged. For example, the following exports 204 in a DeltaV control system implementation can be imported, as shown in the following Table 1.
  • a graphical user interface (GUI) module 210 can be configured to provide a graphical representation of unit operation.
  • the graphical user interface 210 can be configured to allow engineers to modify data that was imported.
  • a playback function is available to allow the process engineer to see the process step through the phases.
  • a Step-by- Step function is available as well as an auto-step function.
  • An edit function is available to change the configuration. This function is available during the Step-by-Step function.
  • a goto function is available to jump to a given phase and step.
  • Operations and Unit Procedures can be displayed, for example, in SFC format, and the like.
  • the graphical interface module can also be used to enter data in place of using the imported code, and graphical information can be imported from a computer-aided design (CAD) drawing (e.g., AutoCAD, etc.), and the like.
  • CAD computer-aided design
  • a Functional Requirement Specification (FRS) module 212 can be configured to generate a FRS 214 for the unit class, and a FRS Change log 216.
  • the format of the FRS 214 can be changed to meet a customer's needs, advantageously, without changing the structure of the underlying data or the logic in the module 212. Data needed to generate the FRS 214 can be stored in the database 206.
  • a Free format report module 218 can be configured to generate a variety of paper reports on the database 206. These reports include the Functional Requirements Specification 214, Design Documents 22O 5 functional test protocols 222, structural test protocols 224, and the like, for the control system application, without changing the structure of the underlying data or the logic in the module 218.
  • An auto test module 226 can be configured generate a report 228 of discrepancies between an imported validation log 230 and the data used to generate the FRS.
  • the format of the report 228 can be changed to meet a customer's needs without changing the structure of the underlying data or the logic in the module 226.
  • the auto test module 226 can generate an import log 232 and can be used for functional phase testing, and the like.
  • the exemplary embodiments can be configured to provide various reporting features, for example, including a .fhx Import Log, a Validation Log, an Import Log, a Discrepancy Log, Functional Requirements, a FRS Change Log, and the like.
  • the Validation Log 230, the Import Log 232, and the Discrepancy Log 228 can be associated with the auto test module 226.
  • the validation log 230 can be generated by the application logic for the current customer. Many customers may not have a validation log 230, in which case an additional module can be provided to generate the validation log 230.
  • the Graphic Interface Module 210 can be used by Process and Process
  • the Process engineer can use the module 210 to establish a sequence of operations.
  • the process control engineers can use the tool 210 to define Continuous Control and organize the sequence of events into phases, operations, unit procedures, and the like.
  • the Validation engineers can use Compare functions.
  • the .fhx import function can be used by the process control engineer.
  • Applications data can be collected in the relational database 206 for use by the described and future modules.
  • the database 206 can be populated by the current DeltaV code.
  • Functional requirements can be modified through the graphical user interface 210.
  • the interface 210 can allow the user to see the process function.
  • An import function is provided to collect the Validation log 230 generated by the execution of the phases with the validation flag on.
  • the operation of the system 200 can employ validated DeltaV code for the application.
  • the application code for the employed unit can be exported.
  • the .fhx files generated by the export are imported into the CSRPT system 200. Errors generated during the import can be resolved before continuing.
  • the graphical interface module 210 can be used to replay the sequence logic and to make modifications. Once the modifications are complete, a new FRS 214 can be automatically generated.
  • the printed FRS 214 can be approved by the applications group and the customer. Once approved by the customer, the DDS 112 and application code 116 can be manually or automatically generated. After the code 116 is manually or automatically generated, the structural testing can be run on the target control system.
  • the sequence logic can be executed and the resulting validation log 230 can be imported into the CSRPT database 206. Once imported into the database 206, the discrepancy report 220 can be run. Discrepancies can be fixed and the appropriate steps above can be repeated.
  • the exemplary embodiments provide interfaces with other software systems and its users for input and output, and the like.
  • the user interface 210 can include an Import Module.
  • the import function can be accessed, for example, from an operating system, such as Windows, Macintosh, Linux, and the like. After import is selected, a pop-up can be displayed to allow the user to select one or more of the corresponding files to be imported (e.g., .fhx file(s) for DeltaV, other file formats for other control systems, and the like).
  • a list of objects to be imported can be displayed. By default all objects can be selected, wherein 'Un-select AU' and a 'Select All' buttons are available.
  • AU or some of the objects can be selected.
  • the selected objects can be imported into the database 206. If an imported object is already in the database 206, a pop-up widow can be displayed and the user can be allowed to replace, skip, replace all, or skip all.
  • a log can be generated that, for example, can list objects that were imported, the status of that import (e.g., whether the import is successful or not), if the import caused the creation of the object in the database 206 or a replacement of an object, and the like.
  • the Graphical Interface Module 210 can be opened from the operating system.
  • the display used for the interface 210 can be different for each unit operation and can be imported from a computer-aided design (CAD) file, and the like, and can include a schematic representation of the process.
  • Instruments on the unit display can have touch targets associated with them that can display a submenu when the target is selected.
  • Each instrument can be assigned to an existing library module. This assignment can determine the contents of the submenu described above.
  • the submenu can include actions that can be taken through the assigned library module. These actions can be segregated by type (e.g., alarm actions can be grouped together, etc). For submenu items that employ additional data, a pop box can be displayed to enter the additional data. Status information for the instruments can be indicated on the display.
  • Additional actions not associated with a library module can also be entered. Editing of the sequence and inserting steps can be allowed. Editing of the operations and unit procedures can be accomplished directly through an edit function in the database 206. Editing these need not but can be done through the Graphical Interface module 210. An automatic replay function is provided. This replay can be set up, for example, to execute a phase, an operation, an entire unit procedure, and the like.
  • the Functional Requirements Specification Module 212 can be accessible through the operating system. For example, a unit class name and destination, and the like, can be entered into a pop-up box. The FRS 214 for the requested unit class can be automatically written and stored to the destination entered above.
  • the Auto Test Module 226 can be accessible through the operating system.
  • a selection can be provided to import the validation log 230.
  • the log 230 can be saved from the DeltaV event journal as a text file.
  • a pop-up box can prompt the user, for example, for the location of the source file, the location of the output file (e.g., the Discrepancy Log 228), the name of the unit class and the unit procedure tested, and the like.
  • another pop-up can be displayed that includes, for example, a list of phases for that selected unit class and unit procedure, and the like. The user can select the phases that are present in the imported validation log 230. Once the phases- are selected, the discrepancy report 228 can be generated and stored in the defined output file location.
  • the data flow diagram of FIG. 1 describes exemplary interrelationships between the modules described with respect to FIG. 2 and the data exchanged between them.
  • the CSRPT database 206 can be populated by the Import Module 202 using data 204 exported from the control system (e.g., such as DeltaV; models CS-3000, CS-1000, Gentium CS, Gentium XL 5 and Micro XL from Yokogawa; model Crisp from Crisp; models RS3 and Pro vox from Emerson; model TDC-3000 from Honeywell; models IA and Spectrum from Foxboro; PLC models from Allen Bradley; PLC models from Modicon; PLC and DCS models from Siemens, and the like) or via the Display Interface module 210.
  • the control system e.g., such as DeltaV; models CS-3000, CS-1000, Gentium CS, Gentium XL 5 and Micro XL from Yokogawa; model Crisp from Crisp; models RS3 and Pro vox from Emerson; model TDC-3000
  • a log 208 of the data imported is generated.
  • the imported data is then used to drive a replay function in the Display Interface Module 210.
  • Imported data is modified via the Display Interface Module 210.
  • the Display Interface Module 210 can also be used to enter data into the system 200 in place of the import module 202.
  • a log of all suitable changes made is then generated.
  • Modified data is then used by the Functional Requirements Specification Module 212 to generate an FRS 214 for the unit class.
  • the modified data is used by the Auto Test Module 226 and compared to the validation log 230 and the discrepancy log 228 is generated.
  • Control System Rapid Prototyping Tool provides a novel suite of utilities that specify, design, implement, test, and the like, for example, process control application software, advantageously, automating the repetitive parts of the process.
  • the software of the exemplary embodiments advantageously, reduces, to a minimum, the time from concept to validated software.
  • the CSRPT can include, for example, the ability to import existing DeltaV phase logic into the functional database 206, modify the functionality of the phase logic (e.g., graphically and non-graphically), generate a revised Functional Requirement Specification 214 of the phase in the corresponding format and document as an existing FRS 214, provide automatic comparison of the validation log 230 generated from the revised code (e.g., code manually modified to match the revised functionality) and the revised functionality, and the like.
  • the CSRPT can include, for example, the ability to graphically define the functionality, graphically modify the functionality regardless of how the functionality is initially populated in the database 206, automatically generate continuous control logic on the DeltaV system, automatically generate phase logic on the DeltaV system, import continuous Control Logic, generate the entire FRS 214 automatically, revise sections of the FRS 214 automatically, capture actions for the devices associated with a unit (e.g., which be used in place of the validation log 230), handle various libraries, such as GROCK, and the like, perform the functions above on various control systems, and the like.
  • a unit e.g., which be used in place of the validation log 230
  • various libraries such as GROCK, and the like
  • the PC system configuration can include an
  • the Control System Rapid Prototyping Tool can be configured as a Windows application that includes several components that allow the user to perform the functionality of the exemplary embodiments from a single unified application. Navigation through the application can be via tabs on the main window and the menu keys at the top of the screen. For example, the user can select the Customer, Site and Project from the Project tab of the CSRPT main screen. These selections can be passed to the other tabs to reduce the re-selection of this data in every tab. From this tab, the user can also create a new project, a new site, a new customer, and the like. During this definition, the library and control system can be defined for a given project.
  • the Project Tab 300 is the starting point for the project. It allows the user to select a project by selecting Customer 302, Site 304, Project 306, and the like. The list for each selection can be built based on the previous selections.
  • a File Menu 308 can include a New menu item 310 that allows, the operator to create a new Customer 312, Site 314, Project 316, and the like.
  • a window can be configured to pop up to allow entry of information for the creation of the selected item from the New menu item 310.
  • a Save menu item 318 saves modified information for the project.
  • An Exit menu item 320 exits the CSRPT system.
  • a Help menu item 322 provides the user with options to view general help information, contact info, the about box, and the like.
  • An Import Tab 400 is provided, for example, as shown in FIG. 4, and can allow for a user to import areas, unit classes, unit instances, phases, phase classes, modules, operations, unit procedures, procedures, and the like, into the CSRPT database 206.
  • FIG. 4 there are provided various sections for the import functionality, allowing, for example, preparing the .fhx (e.g., the DeltaV export file) file for conversion to XML, converting the .fhx data to XML, loading the XML file into the CSRPT import utility, importing applicable objects into the database while prompting the user as needed, generating and saving a log file that records imported items and user decisions, and the like.
  • .fhx e.g., the DeltaV export file
  • a function toolbar 402 can include various functions, for example, for importing data into the CSRPT database, a button to clear the log, and the like.
  • an Open FHX button 404 can take the desired .fhx file and prepare it for XML conversion. When the user clicks this button, they can be presented with a standard Windows Open File dialog. Once a file has been selected, the import utility can open, encode and clean the .fhx file (e.g., see corresponding summary 406). The output of this function is a .clean file and its progress is indicated in the summary box.
  • a .clean file is an .fhx file that has been re- encoded in ANSI and has had troublesome, unnecessary, and the like, node types removed.
  • a Convert XML button 408 can load the user specified .clean file and convert it into XML.
  • the output of this function is an .xml file, for example, including the information of the .clean input, except in XML format, and summary information in the summary text box.
  • An Open XML button 410 can prompt the user for an XML file using a standard Windows Open File dialog. Once selected, the desired XML file can be loaded into memory. The output of this section is a summary in the summary dialog box.
  • An Import button 412 can import all applicable nodes from the XML file residing in memory, as further described. Conflicts can be resolved by issuing a prompt to the user.
  • the product of this function is the import of the applicable/chosen data to the CSRPT database and a summary in the summary text box.
  • a Save Log button 414 can save the text in the summary box 406 to a log file.
  • a Clear Log button 416 can clear the text in the summary text box 406.
  • the summary dialog 418 is a running log of what has happened during the course of the import utility process.
  • the log 418 can be saved at any suitable point using the Save Log button 414 and it can also be cleared at any suitable point using the Clear Log button 416.
  • a Progress Bar 420 can show the progress of the currently running function.
  • An FRS Generate Tab 500 can be used to display the FRS Generation GUI
  • user interface for example, as shown in FIG. 5, and can include controls to select phases from unit classes, generate the associated FRS phase logic content, and the like.
  • a Unit Class Selection List Box 502 can be populated by the database 206 and show the unit classes represented in the database 206 for a given project.
  • One Unit Class can be selected at a time.
  • a Phase Class Selection List Box 504 can be populated with the phases associated with the unit class selected in the Unit Class Selection List Box 502. Multiple Phase Classes can be selected in the list box 504.
  • a Select All Phases Button 506 selects all phase classes in the Phase Class Selection List Box 504.
  • a Deselect All Phases Button 508 deselects all selected phase classes in the Phase Class Selection List Box 504.
  • FRS Generation is provided via an Output File Selection button 510, for example, which allows the selection of the existing Microsoft Word FRS Document per standard windows file selection interface.
  • An Update FRS Sections Button 512 updates the existing FRS sections selected with the information from the CSRPT database 206.
  • An Auto Test Tab 600 can be used to display the Auto Test utility 226, for example, as shown in FIG. 6, and which allows the user to generate a report comparing steps in the FRS 214 with the validation log 230.
  • a Menu Bar 602 can include a File Menu 604 that allows the user to save the program settings, print reports, and exit the program.
  • a Save Settings item 606 saves the current settings (e.g., file directories).
  • a current settings e.g., file directories.
  • Print Validation Report item 608 displays a print dialog box. For example, with this dialog box, the user can select the printer and the printer options, initiate the printing of the report, and the like.
  • a Print Discrepancy Forms item 610 displays the print dialog box. With this dialog box, the user can select the printer and the printer options, initiate the printing of the discrepancy forms, and the like.
  • An Exit item 612 exits the program and saves the current settings.
  • a Help Menu item 614 provides the user with options to view general help information, contact info, the about box, and the like. For example, when Help 614 is selected, a dialog window with general information on the operation of the program is displayed. Contact Information, when selected, displays a dialog window with technical support contact information. About, when selected, displays the about dialog window.
  • a Main Tab 700 can be used to display the main program window, for example, as shown in FIG. 7, and which is split into various areas.
  • a files area 702 displays names and locations of the validation log file, the report file, the discrepancy form files, the FRS database 206, and the like. These items can be changed by a user and stored in the current settings file using the "Save Settings" menu option previously described.
  • a validation area 704 can include a button 706 to initiate the validation, report options 708, a status text box 710, and the like.
  • the directories, and files employed for the validation can be viewed and selected by a user.
  • a Validation Log Location Text Field 712 specifies the directory and file name of the validation log generated during testing, and which is displayed in this field. To change this field, the user selects the ellipsis defined button 714. The user then selects the corresponding file from a file selection dialog box 800 (e.g., implemented via a Microsoft window, and the like), as shown in FIG. 8.
  • a Report Location Text Field 716 displays the directory and file name of the report produced by the program. To change this field, the user selects the ellipsis defined button 718 and selects the file from a file selection dialog box, as previously described.
  • a Discrepancy Forms field 720 displays the directory and file name of the discrepancy forms produced by this program. To change this field, the user selects the ellipsis defined button 722 and selects the file from a file selection dialog box, as previously described. The names of the discrepancy files can be appended with the discrepancy number.
  • the Initiate Validation Area 704 can be used to initiate the validation report and provide the user with the status of the program, for example, as the report is being generated.
  • the Initiate Report Button 706 can be used to start the validation report and the discrepancy form generation.
  • the output generated when the button 706 is selected depends on check boxes 724 and 726. For example, if the Validation Report Check Box 724 is selected, the validation report is generated when the Initiate Report button 706 is selected. If the Discrepancy Forms Check Box 726 is selected, the discrepancy forms are generated when the Initiate Report button 706 is selected.
  • the Program Status Field 710 displays the status of the program, for example, as the report is being generated.
  • the following logs and reports can be generated by the CSRPT.
  • the Import Log utility 202 can generate a .clean file, .xml file, import data into the CSRPT database 206, create a log file, and the like.
  • the log file can be a direct copy of the summary text box information 418 described above.
  • the Validation Log report file is generated when the Validation Report button 706 is selected and the validation report check box 724 is checked.
  • this file includes a line-by-line comparison between the validation log and the corresponding FRS database 206.
  • This file can be in tabular format and in chronological order, for example, as shown in Table 2, which defines the report columns.
  • the Discrepancy Log form files are generated when the Validation Report button 706 is selected and the discrepancy forms check box 726 is checked. These forms provide the information provided in the validation report, wherein an individual form is created for each instance a FRS action differs from a validation log action.
  • the form includes areas for a user to provide information, such as corrective actions, specific information about the discrepancy, and the like.
  • An exemplary form 900 is shown in FIG. 9.
  • the following Table 3 describes the discrepancy form fields and the data provided by this program or manually entered at a later time.
  • the Functional Requirements Specification Log can include a revision log
  • the Control System Rapid Prototyping Tool can read the contents of files, folders, DeltaV export files, DeltaV event journal export files, and the like, and generate the corresponding output files, as described herein.
  • the CSRPT interface can include an explorer type map 1000 with multiple windows into the database 206, as shown in FIG. 10. From the explorer, a pull down menu 1002 allows the user to open any of the modules as a new tab. These tabs can be detached and moved away from the interface window to other places on the screen or other screens in a multi-display system.
  • tabs for a given module can be opened. Each instance of the tab can still be related to the other open tabs.
  • the animated P&ID for a CP skid, a CIP header and a vessel to be cleaned can be opened for a given project and a procedure can be stepped through as the engineer watches the process, and the like.
  • a process engineer can step through the process watching the Graphical interface, while the process control engineer monitors the step editor. Both views remain in sync and changes made in either view are reflected in the other.
  • a step editing module allows another view of the database 206 and facilitates the entry or changing of functionality.
  • the step editor has two views of the functionality.
  • the first view 1100 shown in FIG. 11 , displays details 1102 of each step of the process.
  • the view 1100 allows the user to step through the phase functionality, insert sequences 1104, add actions 1106, create assignments 1108, insert If/Then/Else constructs 1110-1112, remove actions, enter/modify values, change action aliases, and the like.
  • the second view 1200 allows the user to access the history of actions taken during the procedure. When used with the graphical interface, this view provides the Process Control Engineer with additional information.
  • the view displays all possible action for a given alias and which actions have been taken previously and which are currently being taken. Possible actions 1202 can be either hidden or viewed, as selected with check marks 1204.
  • the view 1200 allows the user to step through the phase functionality, insert sequences 1206, add actions 1208, create assignments 1210, insert If/Then/Else constructs 1212-1214, remove actions, and the like.
  • the above-described devices and subsystems of the exemplary embodiments can include, for example, any suitable servers, workstations, PCs, laptop computers, PDAs, Internet appliances, handheld devices, cellular telephones, wireless devices, other devices, and the like, capable of performing the processes of the exemplary embodiments.
  • the devices and subsystems of the exemplary embodiments can communicate with each other using any suitable protocol and can be implemented using one or more programmed computer systems or devices.
  • One or more interface mechanisms can be used with the exemplary embodiments, including, for example, Internet access, telecommunications in any suitable form (e.g., voice, modem, and the like), wireless communications media, and the like.
  • employed communications networks or links can include one or more wireless communications networks, cellular communications networks, G3 communications networks, Public Switched Telephone Network (PSTNs), Packet Data Networks (PDNs), the Internet, intranets, a combination thereof, and the like.
  • PSTNs Public Switched Telephone Network
  • PDNs Packet Data Networks
  • Internet intranets, a combination thereof, and the like.
  • the devices and subsystems of the exemplary embodiments are for exemplary purposes, as many variations of the specific hardware used to implement the exemplary embodiments are possible, as will be appreciated by those skilled in the relevant art(s).
  • the functionality of one or more of the devices and subsystems of the exemplary embodiments can be implemented via one or more programmed computer systems or devices.
  • a single computer system can be programmed to perform the special purpose functions of one or more of the devices and subsystems of the exemplary embodiments.
  • two or more programmed computer systems or devices can be substituted for any one of the devices and subsystems of the exemplary embodiments. Accordingly, principles and advantages of distributed processing, such as redundancy, replication, and the like, also can be implemented, as desired, to increase the robustness and performance of the devices and subsystems of the exemplary embodiments.
  • the devices and subsystems of the exemplary embodiments can store information relating to various processes described herein. This information can be stored in one or more memories, such as a hard disk, optical disk, magneto-optical disk, RAM, and the like, of the devices and subsystems of the exemplary embodiments.
  • One or more databases of the devices and subsystems of the exemplary embodiments can store the information used to implement the exemplary embodiments of the present inventions.
  • the databases can be organized using data structures (e.g., records, tables, arrays, fields, graphs, trees, lists, and the like) included in one or more memories or storage devices listed herein.
  • the processes described with respect to the exemplary embodiments can include appropriate data structures for storing data collected and/or generated by the processes of the devices and subsystems of the exemplary embodiments in one or more databases thereof.
  • All or a portion of the devices and subsystems of the exemplary embodiments can be conveniently implemented using one or more general purpose computer systems, microprocessors, digital signal processors, micro-controllers, and the like, programmed according to the teachings of the exemplary embodiments of the present inventions, as will be appreciated by those skilled in the computer and software arts.
  • Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the exemplary embodiments, as will be appreciated by those skilled in the software art.
  • the devices and subsystems of the exemplary embodiments can be implemented on the World Wide Web.
  • the devices and subsystems of the exemplary embodiments can be implemented by the preparation of application-specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be appreciated by those skilled in the electrical art(s).
  • the exemplary embodiments are not limited to any specific combination of hardware circuitry and/or software.
  • the exemplary embodiments of the present inventions can include software for controlling the devices and subsystems of the exemplary embodiments, for driving the devices and subsystems of the exemplary embodiments, for enabling the devices and subsystems of the exemplary embodiments to interact with a human user, and the like.
  • software can include, but is not limited to, device drivers, firmware, operating systems, development tools, applications software, and the like.
  • Such computer readable media further can include the computer program product of an embodiment of the present inventions for performing all or a portion (if processing is distributed) of the processing performed in implementing the inventions.
  • Computer code devices of the exemplary embodiments of the present inventions can include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, Common Object Request Broker Architecture (CORBA) objects, and the like. Moreover, parts of the processing of the exemplary embodiments of the present inventions can be distributed for better performance, reliability, cost, and the like.
  • the devices and subsystems of the exemplary embodiments can include computer readable medium or memories for holding instructions programmed according to the teachings of the present inventions and for holding data structures, tables, records, and/or other data described herein.
  • Computer readable medium can include any suitable medium that participates in providing instructions to a processor for execution.
  • Non-volatile media can include, for example, optical or magnetic disks, magneto-optical disks, and the like.
  • Volatile media can include dynamic memories, and the like.
  • Transmission media can include coaxial cables, copper wire, fiber optics, and the like. Transmission media also can take the form of acoustic, optical, electromagnetic waves, and the like, such as those generated during radio frequency (RF) communications, infrared (IR) data communications, and the like.
  • RF radio frequency
  • IR infrared
  • Computer-readable media can include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other suitable magnetic medium, a CD-ROM, CDRW, DVD, any other suitable optical medium, punch cards, paper tape, optical mark sheets, any other suitable physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other suitable memory chip or cartridge, a carrier wave or any other suitable medium from which a computer can read.
  • a floppy disk a flexible disk, hard disk, magnetic tape, any other suitable magnetic medium, a CD-ROM, CDRW, DVD, any other suitable optical medium, punch cards, paper tape, optical mark sheets, any other suitable physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other suitable memory chip or cartridge, a carrier wave or any other suitable medium from which a computer can read.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Library & Information Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Debugging And Monitoring (AREA)

Abstract

Système, procédé et programme informatique pour le déploiement et le développement de logiciel d'application et d'essai et de documentation, y compris la fourniture de module d'importation, et au moins l'une des fonctions ci-après, à savoir conversion de fichiers de données de système de contrôle exportées, population de base de données avec l'information convertie, production d'un rapport sur les objets importés et journalisation d'erreurs d'importation; fourniture d'un module d'interface utilisateur graphique, et au moins l'une des fonctions ci-après, à savoir fourniture de représentation graphique d'opération d'unité, possibilité de modifier des données importées, fonction de lecture pour l'affichage d'étape de processus à travers des phases, fonction étape par étape, fonction d'étape automatique, fonction d'édition pour la modification d'une configuration, fonction de passage vers un élément pour passer à une phase et une étape spécifiques, affichage d'opérations et de procédures d'unité, saisie de données au lieu d'utiliser un code importé, et importation d'information graphique depuis un dessin en CAO; fourniture d'un module de spécification de besoin fonctionnel pour une classe d'unité, et production de journal de modification de spécification correspondante; fourniture de module de rapport de format libre, et au moins production de plusieurs types de rapports, entre autres au moins l'un des types ci-après, à savoir spécification de besoin fonctionnel, documents de conception, protocoles d'essai fonctionnel, et protocoles d'essai structurel, pour une application de système de contrôle; et fourniture de module d'essai automatique, et au moins l'une des fonctions ci-après, à savoir production de rapport de différences entre un journal de validation importé et des données utilisées pour la production d'une spécification de besoin fonctionnel, production de journal d'importation, et conduite d'essai de phase fonctionnelle.
PCT/US2006/021917 2005-06-09 2006-06-06 Procede et systeme pour le deploiement et le developpement rapide de logiciel d'application et d'essai et de documentation WO2006135607A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US68873105P 2005-06-09 2005-06-09
US60/688,731 2005-06-09

Publications (2)

Publication Number Publication Date
WO2006135607A2 true WO2006135607A2 (fr) 2006-12-21
WO2006135607A3 WO2006135607A3 (fr) 2009-04-16

Family

ID=37532783

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/021917 WO2006135607A2 (fr) 2005-06-09 2006-06-06 Procede et systeme pour le deploiement et le developpement rapide de logiciel d'application et d'essai et de documentation

Country Status (1)

Country Link
WO (1) WO2006135607A2 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9644396B2 (en) 2013-01-14 2017-05-09 Kiosk Information Systems, Inc. Systems and methods for modular locking
US10127027B2 (en) 2016-10-31 2018-11-13 General Electric Company Scalable and secure analytic model integration and deployment platform
US10296296B2 (en) 2016-10-31 2019-05-21 General Electric Company Integrated development environment for analytic authoring
US10459774B2 (en) 2016-10-31 2019-10-29 General Electric Company Self-aware and self-registering software and analytics platform components
US10481874B2 (en) 2016-10-31 2019-11-19 General Electric Company System architecture for secure and rapid development, deployment and management of analytics and software systems
CN111090460A (zh) * 2019-10-12 2020-05-01 浙江大学 一种基于最近邻算法的代码变更日志自动生成方法
CN111858533A (zh) * 2020-07-23 2020-10-30 山东浪潮商用系统有限公司 一种基于多线程技术的数据导入方法及系统
CN113900953A (zh) * 2021-10-28 2022-01-07 南京华飞数据技术有限公司 一种基于反射机制的软件自动化测试架构方法
CN115037663A (zh) * 2022-05-26 2022-09-09 深圳前海微众银行股份有限公司 一种应用系统更新测试方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
No further relevant documents disclosed *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9644396B2 (en) 2013-01-14 2017-05-09 Kiosk Information Systems, Inc. Systems and methods for modular locking
US10127027B2 (en) 2016-10-31 2018-11-13 General Electric Company Scalable and secure analytic model integration and deployment platform
US10296296B2 (en) 2016-10-31 2019-05-21 General Electric Company Integrated development environment for analytic authoring
US10459774B2 (en) 2016-10-31 2019-10-29 General Electric Company Self-aware and self-registering software and analytics platform components
US10481874B2 (en) 2016-10-31 2019-11-19 General Electric Company System architecture for secure and rapid development, deployment and management of analytics and software systems
CN111090460A (zh) * 2019-10-12 2020-05-01 浙江大学 一种基于最近邻算法的代码变更日志自动生成方法
CN111090460B (zh) * 2019-10-12 2021-05-04 浙江大学 一种基于最近邻算法的代码变更日志自动生成方法
CN111858533A (zh) * 2020-07-23 2020-10-30 山东浪潮商用系统有限公司 一种基于多线程技术的数据导入方法及系统
CN113900953A (zh) * 2021-10-28 2022-01-07 南京华飞数据技术有限公司 一种基于反射机制的软件自动化测试架构方法
CN115037663A (zh) * 2022-05-26 2022-09-09 深圳前海微众银行股份有限公司 一种应用系统更新测试方法及装置
CN115037663B (zh) * 2022-05-26 2023-07-18 深圳前海微众银行股份有限公司 一种应用系统更新测试方法及装置

Also Published As

Publication number Publication date
WO2006135607A3 (fr) 2009-04-16

Similar Documents

Publication Publication Date Title
WO2006135607A2 (fr) Procede et systeme pour le deploiement et le developpement rapide de logiciel d'application et d'essai et de documentation
US8881105B2 (en) Test case manager
CN1961314B (zh) 修正过程控制数据的方法及装置
CA2777443C (fr) Developpement automatise de logiciel d'entreprise
US7496890B2 (en) Generation of configuration instructions using an abstraction technique
US6308146B1 (en) System and method for simulating user input to control the operation of an application
US6560776B1 (en) Software installation verification tool
US5428791A (en) Configuration mechanism for a computer system having generic user interface and component-specific builder modules
US20160170719A1 (en) Software database system and process of building and operating the same
US20020199168A1 (en) Automatic program generation apparatus
CN116627418B (zh) 一种基于递归算法的多级表单界面可视化生成方法及装置
WO2022073981A1 (fr) Extraction de données dans des systèmes d'automatisation industriels
US20070136333A1 (en) Method of inspection and a user interface for a business measure modeling tool
US20080281455A1 (en) Materials, Operations and Tooling Interface and Methods for Managing a Remote Production Facility
GB2278468A (en) Configuring computer programs.
CN112949018B (zh) 一种直流输电控保平台模型创建与测试验证的系统与方法
JP4995009B2 (ja) Ｐｏｄ画面生成装置、そのプログラム
US20080022258A1 (en) Custom database system and method of building and operating the same
JP3373129B2 (ja) プログラム開発支援方法
US20100070954A1 (en) Custom database system and method of building and operating the same
KR100269172B1 (ko) 하드디스크 마스터 제작시스템을 위한 스크립트 파일 작성기
JP2002287964A (ja) 画面入出力仕様設計システムと方法およびプログラム
CN117743144A (zh) 一种基于自动化测试的测试用例筛选方法及装置
Series Model Navigation
CN117632114A (zh) 一种基于文件分析的fmu文件的导入方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06784600

Country of ref document: EP

Kind code of ref document: A2