US20070288883A1 - Method for consolidated launching of multiple tasks - Google Patents
Method for consolidated launching of multiple tasks Download PDFInfo
- Publication number
- US20070288883A1 US20070288883A1 US11/450,618 US45061806A US2007288883A1 US 20070288883 A1 US20070288883 A1 US 20070288883A1 US 45061806 A US45061806 A US 45061806A US 2007288883 A1 US2007288883 A1 US 2007288883A1
- Authority
- US
- United States
- Prior art keywords
- launch
- components
- launching
- composite
- description
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3696—Methods or tools to render software testable
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Definitions
- the invention disclosed and claimed herein generally pertains to a method whereby a multiplicity of tasks, each performed by launching a software or other component, are carried out in a pre-specified order or arrangement. More particularly, the application pertains to a method of the above type wherein the launching of one component to perform its task has a pre-specified relationship to the launching of other task components. Even more particularly, the invention pertains to a method of the above type wherein launch descriptions for respectively launching each of the individual components are consolidated, in order to provide a single composite launch description for launching the multiplicity of tasks.
- IDEs Integrated Development Environments
- Eclipse Integrated Development Environments
- These environments support the full development life cycle by combining a rich set of cooperating tools, such as visual user-interface builders, source-code editors, compilers and debuggers.
- IDEs organize software into projects, where a project typically corresponds to a platform-specific software component such as a Web service or its corresponding client.
- IDEs are very useful in developing individual components, they tend to fall short in developing heterogeneous systems consisting of multiple components, such as distributed applications.
- a distributed application contains sub-applications that can run on multiple computational nodes.
- An important aspect of the application development cycle is the ability to launch the developed application for the purposes of testing and debugging. Accordingly, when developing a distributed application having multiple sub-applications, it is important to have the capability of launching the different sub-applications simultaneously, or in some other pre-specified relationship with one another. Such relationships may be provided by specifying launch parameters, which indicate such things as which sub-applications to launch, in what order, on what computers, and under what conditions. Such a specification, also referred to as a launch configuration, usefully should be stored so that it can be applied repeatedly in the development process. Moreover, in order to support structured organization, it would be desirable to provide a launch configuration with a hierarchical structure. This would enable grouping of sub-applications and launch parameters.
- One prior art IDE product provides the ability to launch a distributed application (called a “solution”) and thereby launches its constituent sub-application.
- a solution a distributed application
- Such product has no capability of defining launch configurations independently of a solution, nor does it support hierarchical organization of the launch configuration.
- Such product only lists the sub-applications contained in the solution.
- the parameters of an aggregated launch configuration are very restricted.
- scripts such as shell script are used for launching.
- This approach requires scripting expertise, and lacks the affordances of an IDE, such as a graphical interface. Furthermore, this approach does not provide a generic flexible method for composing launches.
- the invention provides a general purpose mechanism for consolidating the launching of multiple tasks.
- a task is said to be launched, when it or an associated software component is run or executed.
- launch descriptions of the individual tasks are read and parsed.
- Composition parameters are then read, wherein the parameters indicate relationships between the launchings of different tasks, such as launch order, specific timings and synchronizations, delays between tasks, and groupings of tasks.
- a combined or composite launch description is then constructed, wherein the composite description takes into account both the individual launch descriptions and the composition parameters.
- tasks of the composite launch description are launched. For example, if the tasks are software components, they are run in a certain order or arrangement, each with its own parameters.
- a plurality of individual launch descriptions are delivered to a tool, wherein each of the individual launch descriptions is usable to launch a corresponding component to perform a corresponding task.
- the method further comprises providing the tool with a set of launch relationships, wherein a given launch relationship specifies the relationships between launchings of two or more components.
- the tool is then operated to generate a single composite launch description that defines the launching of the components in accordance with the set of launch relationships.
- FIG. 1 is a flow chart depicting steps for an embodiment of the invention.
- FIG. 2 is a schematic diagram illustrating usage of a single or individual launch description.
- FIG. 3 is a schematic diagram illustrating use of a tool in implementing an embodiment of the invention.
- FIG. 4 is a schematic diagram illustrating a hierarchical tree structure for a composite launch configuration in an embodiment of the invention.
- FIGS. 5 , 6 and 7 respectively show screen shots pertaining to an embodiment of the invention.
- FIG. 8 is a block diagram showing a distributed data processing system in which an embodiment of the invention may be used.
- FIG. 9 is a block diagram showing a data processing or computer system for implementing an embodiment of the invention.
- FIG. 1 there is shown a flow chart showing principal steps of a method comprising an embodiment of the invention.
- the method discloses a general purpose mechanism for consolidating the launching of multiple tasks.
- a task, or a software component for performing the task is “launched”, as such term is used herein, when it is run or executed.
- a software component is launched when it is run or debugged.
- a physical task is launched when it is executed.
- FIG. 1 shows that a first step 102 of the method is to read the launch description of each individual task of the multiplicity of tasks. These descriptions need to be in a prescribed format, e.g. XML with a particular schema, so that they can be parsed.
- the result of step 102 is that a list of input launch descriptions is stored in a selected data structure.
- the use of an individual launch description is described hereinafter in further detail, in connection with FIG. 2 .
- the method reads a set of composition launch parameters that have been supplied. These parameters generally relate to how the launches are composed. Parameters may indicate the relationship between the launching of a component, to perform its corresponding task, and the launching of one or more other components. For example, a launch parameter could specify an order or sequence in which different components and their tasks are to be launched, with respect to one another. Another parameter could specify the timing or delay between tasks that are launched successively, or could specify that tasks are to be launched simultaneously or in some other timed or synchronized relationship. Launch parameters could also indicate the number of instances for a launched component, or specify the conditions under which the task would or would not be launched. Further parameters could group tasks into different subsets, or could indicate the computers or other locations for launching respective tasks.
- a representation of the composite or combined launch description is constructed, as shown by step 106 .
- the composite launch description, or composite launch configuration mirrors the nested structure of a composite entity, such as an application having multiple sub-applications.
- a launch of the composite launch description, shown at step 108 acts by delegation. That is, the composite launch is equivalent to the launch of respective constituents that are contained in the composite entity, wherein each constituent has its own specified launch configuration.
- Respective individual constituent launchings occur in accordance with the order, sequence, or other launch relationships that are specified by the composition launch parameters. If the tasks are software components, they are run in a certain order (or in parallel), each with its own parameters. In the case of physical tasks, they may be executed in a particular, prescribed manner, by a person or group of people.
- FIG. 2 is a schematic diagram illustrating an individual launch description 202 that is associated with a software component 204 .
- a launch description interpreter 206 is provided to interpret launch description 202 , and to thus run software component 204 on the appropriate run time environment 208 .
- the launch description would comprise a group of parameters and other related pieces of information. Collectively, these would provide enough information, when presented to launch description interpreter 206 , to launch the software component.
- a small document or the like is provided to be the launch description 202 , in order to launch software component 204 to perform a desired task.
- the IDE is also provided with a software component comprising the launch description interpreter 206 , which responds to the information provided by the launch description to trigger the launch of software component 204 .
- Tool 302 for implementing an embodiment of the invention.
- Tool 302 may, for example, comprise a software based tool that is part of an IDE.
- FIG. 3 shows multiple individual launch descriptions 304 delivered as inputs to tool 302 . As described above, each individual launch description is usable to launch a corresponding component, and to thereby perform a corresponding task.
- FIG. 3 further shows tool 302 being provided with composition launch parameters 306 , as described above in connection with FIG. 1 .
- the tool 302 is then operated to construct a single composite launch description 308 from these inputs, as likewise described above in connection with FIG. 1 .
- the composite launch description defines the launching of respective software components and their tasks, in accordance with a set of launch relationships specified by composition launch parameters 306 .
- a composite launch description comprising a composite launch configuration 400 .
- the configuration 400 could be useful, for example, for consolidated launching of a collection of projects in an IDE. More particularly, the composite launch configuration 400 comprises a collection of projects arranged for launching in a hierarchical tree structure.
- the leaves 402 - 422 comprise projects or other components that are to be launched, and internal nodes 424 - 440 represent hierarchical collections, groupings or subsets of projects.
- leaves 408 - 412 comprise a project subset under node 432
- leaves 402 - 404 comprise a subset under node 424 .
- Arranging related leaf projects in a subset under a common node can be very useful for certain purposes.
- all the projects under node 432 could be launched at the same time, or could be launched using the same computer.
- the hierarchical arrangement is also useful for enabling an application developer to visualize the composite launch configuration, or to select a particular project subset for launch and testing.
- the developer can also rearrange project launches in the over-all configuration, and can specify the launch order of sub-projects within the composite project, to enable various test scenarios.
- FIGS. 5-7 respectively show screen shots of a user interface (UI) 500 , wherein UI 500 may be interconnected with tool 302 described above.
- UI 500 is provided to enable a developer or other user to visualize, manipulate or selectively modify a composite project launch configuration generated by tool 302 .
- FIG. 5 there is shown a window 502 labeled Composite Project Name. This window is used to select or specify the name of a composite project. In FIG. 5 , the name “compJav” has been selected.
- FIG. 6 shows multiple tabs employed for defining the launch configuration.
- the “SubApplications” tab 602 (shown in the center) lists the sub-projects that are to be launched by using checked boxes 604 a - c, in order to indicate whether a sub-project should be launched in the next run.
- the “MoveUp” button 606 and “MoveDown” button 608 enable a user to readily change the launch order. The functionality of this tab can easily be extended to define additional launch parameters such as the number of instances to launch.
- the “Launchers View” tab 610 (shown on the right) shows the entire hierarchy of the launch configuration as depicted in FIG. 7 . In the example shown in FIG. 6 , “jav1” and “jav2” are sub-applications inside CompJav, and “compJavNested” is an internal node.
- FIG. 7 shows a screen shot that visually presents a tree structure as described above in connection with FIG. 4 .
- the top level 702 of the tree “compJav/compJav”
- has a child 704 (compJavNested), which has a child 706 (NoLauncher/jav3).
- Top level 702 also has further children 708 and 710 .
- Distributed data processing system 800 contains a network 802 , which is the medium used to provide communications links between various devices and computers connected together within distributed data processing system 800 .
- Network 802 may include permanent connections, such as wire or fiber optic cables, or temporary connections made through telephone connections, as well as wireless connections such as Wi-Fi (802.11) and Bluetooth.
- a server 804 and server 806 are connected to network 802 along with storage unit 808 .
- clients 810 , 812 , and 814 are connected to network 802 .
- These clients 810 , 812 , and 814 may be, for example, personal computers, network computers or mobile computers such as PDAs and smart phones.
- a network computer is any computer, coupled to a network, which receives a program or other application from another computer coupled to the network.
- server 804 provides data, such as boot files, operating system images, and applications to clients 810 - 814 .
- Clients 810 , 812 , and 814 are clients to server 804 . Additionally, clients 810 - 814 may be clients to server 806 in these examples. Moreover, tool 302 shown in FIG. 3 , together with other computer hardware and software components required to implement embodiments of the invention, may reside in or collectively comprise one of the clients 810 - 814 .
- Distributed data processing system 800 may include additional servers, clients, and other devices not shown.
- network 802 interconnecting system 800 could be the Internet.
- Distributed data processing system 800 also may be implemented as a number of different types of networks, such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN).
- LAN local area network
- WAN wide area network
- FIG. 9 there is shown a block diagram of a generalized data processing system 900 which may be adapted for use as one of the client computers 810 - 814 shown in FIG. 8 .
- Data processing system 900 exemplifies a computer, in which code or instructions for implementing embodiments of the invention may be located.
- Data processing system 900 usefully employs a peripheral component interconnect (PCI) local bus architecture, although other bus architectures such as Accelerated Graphics Port (AGP) and Industry Standard Architecture (ISA) may alternatively be used.
- FIG. 9 shows a processor 902 and main memory 904 connected to a PCI local bus 906 through a Host/PCI bridge 908 .
- PCI peripheral component interconnect
- PCI bridge 908 also may include an integrated memory controller and cache memory for processor 902 . It is thus seen that data processing system 900 is provided with components that may readily be adapted to provide tool 302 as described above, together with other components for implementing embodiments of the invention as described herein.
- LAN local area network
- SCSI small computer system interface
- expansion bus interface 914 respectively connected to PCI local bus 906 by direct component connection.
- Audio adapter 916 , a graphics adapter 918 , and audio/video adapter 922 are connected to PCI local bus 906 by means of add-in boards inserted into expansion slots.
- SCSI host bus adapter 910 provides a connection for hard disk drive 920 , and also for CD-ROM drive 924 .
- the invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements.
- the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.
- the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system.
- a computer-usable or computer readable medium can be any tangible apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
- the medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium.
- Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a USB flash drive, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk.
- Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.
- a data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus.
- the memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
- I/O devices including but not limited to keyboards, displays, pointing devices, etc.
- I/O controllers can be coupled to the system either directly or through intervening I/O controllers.
- Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks.
- Modems, cable modems, Ethernet cards and wireless adapters are just a few of the currently available types of network adapters.
Abstract
Description
- 1. Field of the Invention
- The invention disclosed and claimed herein generally pertains to a method whereby a multiplicity of tasks, each performed by launching a software or other component, are carried out in a pre-specified order or arrangement. More particularly, the application pertains to a method of the above type wherein the launching of one component to perform its task has a pre-specified relationship to the launching of other task components. Even more particularly, the invention pertains to a method of the above type wherein launch descriptions for respectively launching each of the individual components are consolidated, in order to provide a single composite launch description for launching the multiplicity of tasks.
- 2. Description of the Related Art
- Integrated Development Environments (IDEs), such as an open source product known as Eclipse, are currently the tool of choice for complex software development. These environments support the full development life cycle by combining a rich set of cooperating tools, such as visual user-interface builders, source-code editors, compilers and debuggers. IDEs organize software into projects, where a project typically corresponds to a platform-specific software component such as a Web service or its corresponding client. However, while IDEs are very useful in developing individual components, they tend to fall short in developing heterogeneous systems consisting of multiple components, such as distributed applications. A distributed application contains sub-applications that can run on multiple computational nodes. Thus, there is a need to augment IDEs to effectively manage collections of projects or other software components as coherent entities.
- An important aspect of the application development cycle is the ability to launch the developed application for the purposes of testing and debugging. Accordingly, when developing a distributed application having multiple sub-applications, it is important to have the capability of launching the different sub-applications simultaneously, or in some other pre-specified relationship with one another. Such relationships may be provided by specifying launch parameters, which indicate such things as which sub-applications to launch, in what order, on what computers, and under what conditions. Such a specification, also referred to as a launch configuration, usefully should be stored so that it can be applied repeatedly in the development process. Moreover, in order to support structured organization, it would be desirable to provide a launch configuration with a hierarchical structure. This would enable grouping of sub-applications and launch parameters.
- In current IDEs, the notion of a launch configuration is generally well known. However, mechanisms for flexibly composing launch configurations as well as the notion of a hierarchically organized aggregated launch arrangement that encompasses multiple launchings, are generally not known. In the absence of an aggregated launcher, the application developer has to manually perform several launch operations each time that testing and debugging is carried out. This process tends to be cumbersome and error-prone. In addition, when performing certain tests such as stress testing, the developer may want to launch multiple instances of an application, such as one instance of a server and many instances of a client. Again, in current IDEs this needs to be done manually.
- One prior art IDE product provides the ability to launch a distributed application (called a “solution”) and thereby launches its constituent sub-application. However, such product has no capability of defining launch configurations independently of a solution, nor does it support hierarchical organization of the launch configuration. Such product only lists the sub-applications contained in the solution. Moreover, the parameters of an aggregated launch configuration are very restricted.
- In IDEs that support Web tooling, such as Eclipse, there is only a limited notion of distributed launching. That is, when testing a Web application, the IDE launches both an application server and a browser client. However, while this feature may exemplify a “one click” way of launching multiple computational nodes, it is restricted to the Web-based client-server model, and has no notion of hierarchy or flexible composition.
- In a traditional, non-IDE approach to development, scripts such as shell script are used for launching. This approach requires scripting expertise, and lacks the affordances of an IDE, such as a graphical interface. Furthermore, this approach does not provide a generic flexible method for composing launches.
- From the above, it is seen that a flexible method for composing launch configurations is required for advancing the state of the art in modern distributed application development. In particular, providing such a method in an IDE, which also supports hierarchical composition, is particularly valuable. While this will be useful for distributed application development, it is anticipated that such a method would have other useful applications as well, such as in stress testing.
- The invention provides a general purpose mechanism for consolidating the launching of multiple tasks. A task is said to be launched, when it or an associated software component is run or executed. In one embodiment of the invention, launch descriptions of the individual tasks are read and parsed. Composition parameters are then read, wherein the parameters indicate relationships between the launchings of different tasks, such as launch order, specific timings and synchronizations, delays between tasks, and groupings of tasks. A combined or composite launch description is then constructed, wherein the composite description takes into account both the individual launch descriptions and the composition parameters. Finally, tasks of the composite launch description are launched. For example, if the tasks are software components, they are run in a certain order or arrangement, each with its own parameters. In a further embodiment, directed to a method of the above type, a plurality of individual launch descriptions are delivered to a tool, wherein each of the individual launch descriptions is usable to launch a corresponding component to perform a corresponding task. The method further comprises providing the tool with a set of launch relationships, wherein a given launch relationship specifies the relationships between launchings of two or more components. The tool is then operated to generate a single composite launch description that defines the launching of the components in accordance with the set of launch relationships.
- The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
-
FIG. 1 is a flow chart depicting steps for an embodiment of the invention. -
FIG. 2 is a schematic diagram illustrating usage of a single or individual launch description. -
FIG. 3 is a schematic diagram illustrating use of a tool in implementing an embodiment of the invention. -
FIG. 4 is a schematic diagram illustrating a hierarchical tree structure for a composite launch configuration in an embodiment of the invention. -
FIGS. 5 , 6 and 7 respectively show screen shots pertaining to an embodiment of the invention. -
FIG. 8 is a block diagram showing a distributed data processing system in which an embodiment of the invention may be used. -
FIG. 9 is a block diagram showing a data processing or computer system for implementing an embodiment of the invention. - Referring to
FIG. 1 , there is shown a flow chart showing principal steps of a method comprising an embodiment of the invention. The method discloses a general purpose mechanism for consolidating the launching of multiple tasks. A task, or a software component for performing the task, is “launched”, as such term is used herein, when it is run or executed. For example, a software component is launched when it is run or debugged. A physical task is launched when it is executed. -
FIG. 1 shows that afirst step 102 of the method is to read the launch description of each individual task of the multiplicity of tasks. These descriptions need to be in a prescribed format, e.g. XML with a particular schema, so that they can be parsed. The result ofstep 102 is that a list of input launch descriptions is stored in a selected data structure. The use of an individual launch description is described hereinafter in further detail, in connection withFIG. 2 . - At
step 104, the method reads a set of composition launch parameters that have been supplied. These parameters generally relate to how the launches are composed. Parameters may indicate the relationship between the launching of a component, to perform its corresponding task, and the launching of one or more other components. For example, a launch parameter could specify an order or sequence in which different components and their tasks are to be launched, with respect to one another. Another parameter could specify the timing or delay between tasks that are launched successively, or could specify that tasks are to be launched simultaneously or in some other timed or synchronized relationship. Launch parameters could also indicate the number of instances for a launched component, or specify the conditions under which the task would or would not be launched. Further parameters could group tasks into different subsets, or could indicate the computers or other locations for launching respective tasks. - From the individual launch descriptions and the composition launch parameters, a representation of the composite or combined launch description is constructed, as shown by
step 106. The composite launch description, or composite launch configuration, mirrors the nested structure of a composite entity, such as an application having multiple sub-applications. A launch of the composite launch description, shown atstep 108, acts by delegation. That is, the composite launch is equivalent to the launch of respective constituents that are contained in the composite entity, wherein each constituent has its own specified launch configuration. Respective individual constituent launchings occur in accordance with the order, sequence, or other launch relationships that are specified by the composition launch parameters. If the tasks are software components, they are run in a certain order (or in parallel), each with its own parameters. In the case of physical tasks, they may be executed in a particular, prescribed manner, by a person or group of people. -
FIG. 2 is a schematic diagram illustrating anindividual launch description 202 that is associated with asoftware component 204. Alaunch description interpreter 206 is provided to interpretlaunch description 202, and to thus runsoftware component 204 on the appropriaterun time environment 208. For example, for a software component such as a Web application or Java application, the launch description would comprise a group of parameters and other related pieces of information. Collectively, these would provide enough information, when presented to launchdescription interpreter 206, to launch the software component. In an IDE, a small document or the like is provided to be thelaunch description 202, in order to launchsoftware component 204 to perform a desired task. The IDE is also provided with a software component comprising thelaunch description interpreter 206, which responds to the information provided by the launch description to trigger the launch ofsoftware component 204. - Referring to
FIG. 3 , there is shown atool 302 for implementing an embodiment of the invention.Tool 302 may, for example, comprise a software based tool that is part of an IDE.FIG. 3 shows multipleindividual launch descriptions 304 delivered as inputs totool 302. As described above, each individual launch description is usable to launch a corresponding component, and to thereby perform a corresponding task.FIG. 3 further showstool 302 being provided withcomposition launch parameters 306, as described above in connection withFIG. 1 . Thetool 302 is then operated to construct a singlecomposite launch description 308 from these inputs, as likewise described above in connection withFIG. 1 . The composite launch description defines the launching of respective software components and their tasks, in accordance with a set of launch relationships specified bycomposition launch parameters 306. - Referring to
FIG. 4 , there is shown a composite launch description comprising acomposite launch configuration 400. Theconfiguration 400 could be useful, for example, for consolidated launching of a collection of projects in an IDE. More particularly, thecomposite launch configuration 400 comprises a collection of projects arranged for launching in a hierarchical tree structure. The leaves 402-422 comprise projects or other components that are to be launched, and internal nodes 424-440 represent hierarchical collections, groupings or subsets of projects. Thus, leaves 408-412 comprise a project subset undernode 432, and leaves 402-404 comprise a subset undernode 424. Arranging related leaf projects in a subset under a common node can be very useful for certain purposes. For example, all the projects undernode 432 could be launched at the same time, or could be launched using the same computer. The hierarchical arrangement is also useful for enabling an application developer to visualize the composite launch configuration, or to select a particular project subset for launch and testing. The developer can also rearrange project launches in the over-all configuration, and can specify the launch order of sub-projects within the composite project, to enable various test scenarios. -
FIGS. 5-7 respectively show screen shots of a user interface (UI) 500, whereinUI 500 may be interconnected withtool 302 described above.UI 500 is provided to enable a developer or other user to visualize, manipulate or selectively modify a composite project launch configuration generated bytool 302. - Referring to the screen depicted in
FIG. 5 , there is shown awindow 502 labeled Composite Project Name. This window is used to select or specify the name of a composite project. InFIG. 5 , the name “compJav” has been selected. -
FIG. 6 shows multiple tabs employed for defining the launch configuration. The “SubApplications” tab 602 (shown in the center) lists the sub-projects that are to be launched by using checked boxes 604 a-c, in order to indicate whether a sub-project should be launched in the next run. The “MoveUp”button 606 and “MoveDown”button 608 enable a user to readily change the launch order. The functionality of this tab can easily be extended to define additional launch parameters such as the number of instances to launch. The “Launchers View” tab 610 (shown on the right) shows the entire hierarchy of the launch configuration as depicted inFIG. 7 . In the example shown inFIG. 6 , “jav1” and “jav2” are sub-applications inside CompJav, and “compJavNested” is an internal node. -
FIG. 7 shows a screen shot that visually presents a tree structure as described above in connection withFIG. 4 . For example, thetop level 702 of the tree, “compJav/compJav”, has a child 704 (compJavNested), which has a child 706 (NoLauncher/jav3).Top level 702 also hasfurther children - Referring to
FIG. 8 , there is shown a generalized distributeddata processing system 800 comprising a network of computers.System 800 may be used in connection with distributed applications and their development, and may thus be used with embodiments of the invention. Distributeddata processing system 800 contains anetwork 802, which is the medium used to provide communications links between various devices and computers connected together within distributeddata processing system 800.Network 802 may include permanent connections, such as wire or fiber optic cables, or temporary connections made through telephone connections, as well as wireless connections such as Wi-Fi (802.11) and Bluetooth. - In the depicted example, a
server 804 andserver 806 are connected to network 802 along withstorage unit 808. In addition,clients clients server 804 provides data, such as boot files, operating system images, and applications to clients 810-814. -
Clients server 804. Additionally, clients 810-814 may be clients toserver 806 in these examples. Moreover,tool 302 shown inFIG. 3 , together with other computer hardware and software components required to implement embodiments of the invention, may reside in or collectively comprise one of the clients 810-814. - Distributed
data processing system 800 may include additional servers, clients, and other devices not shown. In the depicted example,network 802interconnecting system 800 could be the Internet. Distributeddata processing system 800 also may be implemented as a number of different types of networks, such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN). - Referring to
FIG. 9 , there is shown a block diagram of a generalizeddata processing system 900 which may be adapted for use as one of the client computers 810-814 shown inFIG. 8 .Data processing system 900 exemplifies a computer, in which code or instructions for implementing embodiments of the invention may be located.Data processing system 900 usefully employs a peripheral component interconnect (PCI) local bus architecture, although other bus architectures such as Accelerated Graphics Port (AGP) and Industry Standard Architecture (ISA) may alternatively be used.FIG. 9 shows aprocessor 902 andmain memory 904 connected to a PCIlocal bus 906 through a Host/PCI bridge 908.PCI bridge 908 also may include an integrated memory controller and cache memory forprocessor 902. It is thus seen thatdata processing system 900 is provided with components that may readily be adapted to providetool 302 as described above, together with other components for implementing embodiments of the invention as described herein. - Referring further to
FIG. 9 , there is shown a local area network (LAN)adapter 912, a small computer system interface (SCSI)host bus adapter 910, and anexpansion bus interface 914 respectively connected to PCIlocal bus 906 by direct component connection.Audio adapter 916, agraphics adapter 918, and audio/video adapter 922 are connected to PCIlocal bus 906 by means of add-in boards inserted into expansion slots. SCSIhost bus adapter 910 provides a connection forhard disk drive 920, and also for CD-ROM drive 924. - The invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In a preferred embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.
- Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any tangible apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
- The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a USB flash drive, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.
- A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.
- Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.
- Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems, Ethernet cards and wireless adapters are just a few of the currently available types of network adapters.
- The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/450,618 US20070288883A1 (en) | 2006-06-09 | 2006-06-09 | Method for consolidated launching of multiple tasks |
US12/115,661 US8219991B2 (en) | 2006-06-09 | 2008-05-06 | Consolidated launching of multiple tasks |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/450,618 US20070288883A1 (en) | 2006-06-09 | 2006-06-09 | Method for consolidated launching of multiple tasks |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/115,661 Continuation US8219991B2 (en) | 2006-06-09 | 2008-05-06 | Consolidated launching of multiple tasks |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070288883A1 true US20070288883A1 (en) | 2007-12-13 |
Family
ID=38823396
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/450,618 Abandoned US20070288883A1 (en) | 2006-06-09 | 2006-06-09 | Method for consolidated launching of multiple tasks |
US12/115,661 Active 2029-05-31 US8219991B2 (en) | 2006-06-09 | 2008-05-06 | Consolidated launching of multiple tasks |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/115,661 Active 2029-05-31 US8219991B2 (en) | 2006-06-09 | 2008-05-06 | Consolidated launching of multiple tasks |
Country Status (1)
Country | Link |
---|---|
US (2) | US20070288883A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070294667A1 (en) * | 2006-06-15 | 2007-12-20 | International Business Machines Corporation | Method for moving and copying dependencies along with source code |
US20080153473A1 (en) * | 2006-12-21 | 2008-06-26 | Motorola, Inc. | Method and apparatus for dynamic menuing of applications in a mobile communication device |
US20080209432A1 (en) * | 2006-06-15 | 2008-08-28 | Guruduth Somasekhara Banavar | Computer implemented method and system for sharing resources among hierarchical containers of resources |
US20080250410A1 (en) * | 2006-06-09 | 2008-10-09 | Danny Soroker | Method for consolidated launching of multiple tasks |
EP2107459A1 (en) * | 2008-03-31 | 2009-10-07 | Jatho Investments | A software appliance framework |
US8020108B1 (en) * | 2006-09-29 | 2011-09-13 | Emc Corporation | Separation of presentation and business models for common management platform tasks in a storage area network |
US20130268853A1 (en) * | 2010-09-09 | 2013-10-10 | Option | Mobile terminal comprising a man/machine interface |
US20170139685A1 (en) * | 2014-06-25 | 2017-05-18 | Chengdu Puzhong Software Limted Company | Visual software modeling method to construct software views based on a software meta view |
US9871911B1 (en) | 2016-09-30 | 2018-01-16 | Microsoft Technology Licensing, Llc | Visualizations for interactions with external computing logic |
US20180176086A1 (en) * | 2015-06-02 | 2018-06-21 | Sparkl Limited | Interaction of devices in a networked environment |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9207972B2 (en) * | 2013-03-14 | 2015-12-08 | International Business Machines Corporation | Meta-application management in a multitasking environment |
US10817310B2 (en) * | 2017-09-01 | 2020-10-27 | Ab Initio Technology Llc | Executing graph-based program specifications |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5485615A (en) * | 1992-06-10 | 1996-01-16 | Telefonaktiebolaget L M Ericsson | System and method of interactively developing desired computer programs by using plurality of tools within a process described in graphical language |
US6195659B1 (en) * | 1998-07-14 | 2001-02-27 | Trw Inc. | Method and apparatus for morphological clustering having multiple dilation and erosion of switchable grid data cells |
US6546395B1 (en) * | 1999-08-30 | 2003-04-08 | International Business Machines Corporation | Multi-dimensional restructure performance by selecting a technique to modify a relational database based on a type of restructure |
US20030195898A1 (en) * | 2002-04-15 | 2003-10-16 | International Business Machines Corporation | Multidimensional disk clustering scheme for query processing and maintenance in relational databases |
US6678716B1 (en) * | 2000-06-19 | 2004-01-13 | J. D. Edwards World Source Company | System and method for managing processes |
US6789251B1 (en) * | 1999-07-28 | 2004-09-07 | Unisys Corporation | System and method for managing a suite of data management tools |
US20040205066A1 (en) * | 2003-04-08 | 2004-10-14 | International Business Machines Corporation | System and method for a multi-level locking hierarchy in a database with multi-dimensional clustering |
US20040220972A1 (en) * | 2003-04-29 | 2004-11-04 | International Business Machines Corporation | System and method for space management of multidimensionally clustered tables |
US6938240B2 (en) * | 2000-09-01 | 2005-08-30 | Borland Software Corporation | Methods and systems for improving a workflow based on data mined from plans created from the workflow |
US6966061B1 (en) * | 2001-09-20 | 2005-11-15 | Bellsouth Intellectual Property Corp. | System and method for managing initiative delivery process |
US20060020619A1 (en) * | 2004-07-09 | 2006-01-26 | Microsoft Corporation | Database generation systems and methods |
US20060206496A1 (en) * | 2003-04-18 | 2006-09-14 | Jean-Jacques Aureglia | System and method in a data table managing deletion operations in recursive scalable template instances |
US7272818B2 (en) * | 2003-04-10 | 2007-09-18 | Microsoft Corporation | Creation of an object within an object hierarchy structure |
US7328206B2 (en) * | 1999-10-15 | 2008-02-05 | Microsoft Corporation | Extensions for adding and removing calculated members in a multidimensional database |
US7461049B2 (en) * | 1999-10-08 | 2008-12-02 | Edgenet, Inc. | Automated configuration system and method |
Family Cites Families (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5361357A (en) | 1992-04-02 | 1994-11-01 | Cadence Design Systems, Inc. | Method and apparatus for optimizing computer file compilation |
US5574898A (en) | 1993-01-08 | 1996-11-12 | Atria Software, Inc. | Dynamic software version auditor which monitors a process to provide a list of objects that are accessed |
US5854932A (en) | 1995-08-17 | 1998-12-29 | Microsoft Corporation | Compiler and method for avoiding unnecessary recompilation |
US6263492B1 (en) | 1997-06-06 | 2001-07-17 | Microsoft Corporation | Run time object layout model with object type that differs from the derived object type in the class structure at design time and the ability to store the optimized run time object layout model |
US6031747A (en) * | 1999-08-02 | 2000-02-29 | Lockheed Martin Missiles & Space Company | Interleaved synchronous flyback converter with high efficiency over a wide operating load range |
US6880126B1 (en) * | 1999-08-03 | 2005-04-12 | International Business Machines Corporation | Controlling presentation of a GUI, using view controllers created by an application mediator, by identifying a destination to access a target to retrieve data |
US6684383B1 (en) | 1999-09-29 | 2004-01-27 | Kabushiki Kaisha Toshiba | Method for constructing enterprise system |
US7383320B1 (en) | 1999-11-05 | 2008-06-03 | Idom Technologies, Incorporated | Method and apparatus for automatically updating website content |
EP1290552A1 (en) | 2000-04-21 | 2003-03-12 | Togethersoft Corporation | Methods and systems for identifying dependencies between object-oriented elements |
US6678889B1 (en) * | 2000-05-05 | 2004-01-13 | International Business Machines Corporation | Systems, methods and computer program products for locating resources within an XML document defining a console for managing multiple application programs |
US6598041B1 (en) | 2000-09-07 | 2003-07-22 | International Business Machines Corporation | Method, system, and program for processing modifications to data in tables in a database system |
US6766334B1 (en) | 2000-11-21 | 2004-07-20 | Microsoft Corporation | Project-based configuration management method and apparatus |
US7370315B1 (en) | 2000-11-21 | 2008-05-06 | Microsoft Corporation | Visual programming environment providing synchronization between source code and graphical component objects |
US7152224B1 (en) | 2000-11-21 | 2006-12-19 | Microsoft Corporation | Versioned project associations |
WO2002048866A2 (en) * | 2000-12-11 | 2002-06-20 | Microsoft Corporation | Method and system for management of multiple network resources |
US20040031015A1 (en) | 2001-05-24 | 2004-02-12 | Conexant Systems, Inc. | System and method for manipulation of software |
US7051036B2 (en) * | 2001-12-03 | 2006-05-23 | Kraft Foods Holdings, Inc. | Computer-implemented system and method for project development |
US6804682B1 (en) | 2002-04-29 | 2004-10-12 | Borland Software Corporation | System and methodology providing compiler-assisted refactoring |
US6804686B1 (en) * | 2002-04-29 | 2004-10-12 | Borland Software Corporation | System and methodology for providing fixed UML layout for an object oriented class browser |
US7127707B1 (en) | 2002-10-10 | 2006-10-24 | Microsoft Corporation | Intellisense in project upgrade |
US20040187140A1 (en) | 2003-03-21 | 2004-09-23 | Werner Aigner | Application framework |
US7707566B2 (en) | 2003-06-26 | 2010-04-27 | Microsoft Corporation | Software development infrastructure |
US20050005261A1 (en) | 2003-07-02 | 2005-01-06 | Severin William B. | Component integration engine |
US8645420B2 (en) | 2003-08-05 | 2014-02-04 | Accenture Global Services Limited | Methodology framework and delivery vehicle |
EP1680741B1 (en) * | 2003-11-04 | 2012-09-05 | Kimberly-Clark Worldwide, Inc. | Testing tool for complex component based software systems |
US20050278709A1 (en) | 2004-06-15 | 2005-12-15 | Manjula Sridhar | Resource definition language for network management application development |
US7797293B2 (en) * | 2004-06-24 | 2010-09-14 | Oracle America, Inc. | Adaptive contact list |
US8037056B2 (en) | 2005-02-18 | 2011-10-11 | International Business Machines Corporation | Online repair of a replicated table |
US20060218538A1 (en) | 2005-03-22 | 2006-09-28 | Van Kesteren Tom A | System, method and computer program product for converting a serialized object between different software versions |
US7971198B2 (en) | 2005-06-08 | 2011-06-28 | Unoweb Inc. | Method for global resource sharing having logically linked means and integrated functionality for building solutions |
US7721205B2 (en) | 2005-09-15 | 2010-05-18 | Microsoft Corporation | Integration of composite objects in host applications |
CN101390050B (en) | 2005-12-22 | 2018-04-24 | 艾伦·J·薛比洛 | Reach the apparatus and method of selectivity distribution software resource by subtractive installation |
US7631014B2 (en) | 2006-04-27 | 2009-12-08 | International Business Machines Corporation | Method and apparatus for fast deletion of physically clustered data |
US20070288883A1 (en) | 2006-06-09 | 2007-12-13 | International Business Machines Corporation | Method for consolidated launching of multiple tasks |
US7870536B2 (en) | 2006-06-15 | 2011-01-11 | International Business Machines Corporation | Computer implemented method and system for sharing resources among hierarchical containers of resources |
US8302073B2 (en) | 2006-06-15 | 2012-10-30 | International Business Machines Corporation | Moving and copying dependencies along with source code |
-
2006
- 2006-06-09 US US11/450,618 patent/US20070288883A1/en not_active Abandoned
-
2008
- 2008-05-06 US US12/115,661 patent/US8219991B2/en active Active
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5485615A (en) * | 1992-06-10 | 1996-01-16 | Telefonaktiebolaget L M Ericsson | System and method of interactively developing desired computer programs by using plurality of tools within a process described in graphical language |
US6195659B1 (en) * | 1998-07-14 | 2001-02-27 | Trw Inc. | Method and apparatus for morphological clustering having multiple dilation and erosion of switchable grid data cells |
US6789251B1 (en) * | 1999-07-28 | 2004-09-07 | Unisys Corporation | System and method for managing a suite of data management tools |
US6546395B1 (en) * | 1999-08-30 | 2003-04-08 | International Business Machines Corporation | Multi-dimensional restructure performance by selecting a technique to modify a relational database based on a type of restructure |
US7461049B2 (en) * | 1999-10-08 | 2008-12-02 | Edgenet, Inc. | Automated configuration system and method |
US7328206B2 (en) * | 1999-10-15 | 2008-02-05 | Microsoft Corporation | Extensions for adding and removing calculated members in a multidimensional database |
US6678716B1 (en) * | 2000-06-19 | 2004-01-13 | J. D. Edwards World Source Company | System and method for managing processes |
US6938240B2 (en) * | 2000-09-01 | 2005-08-30 | Borland Software Corporation | Methods and systems for improving a workflow based on data mined from plans created from the workflow |
US6966061B1 (en) * | 2001-09-20 | 2005-11-15 | Bellsouth Intellectual Property Corp. | System and method for managing initiative delivery process |
US7080081B2 (en) * | 2002-04-15 | 2006-07-18 | International Business Machines Corporation | Multidimensional data clustering scheme for query processing and maintenance in relational databases |
US20030195898A1 (en) * | 2002-04-15 | 2003-10-16 | International Business Machines Corporation | Multidimensional disk clustering scheme for query processing and maintenance in relational databases |
US7236974B2 (en) * | 2003-04-08 | 2007-06-26 | International Business Machines Corporation | System and method for a multi-level locking hierarchy in a database with multi-dimensional clustering |
US20040205066A1 (en) * | 2003-04-08 | 2004-10-14 | International Business Machines Corporation | System and method for a multi-level locking hierarchy in a database with multi-dimensional clustering |
US7272818B2 (en) * | 2003-04-10 | 2007-09-18 | Microsoft Corporation | Creation of an object within an object hierarchy structure |
US20060206496A1 (en) * | 2003-04-18 | 2006-09-14 | Jean-Jacques Aureglia | System and method in a data table managing deletion operations in recursive scalable template instances |
US20040220972A1 (en) * | 2003-04-29 | 2004-11-04 | International Business Machines Corporation | System and method for space management of multidimensionally clustered tables |
US20060020619A1 (en) * | 2004-07-09 | 2006-01-26 | Microsoft Corporation | Database generation systems and methods |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080250410A1 (en) * | 2006-06-09 | 2008-10-09 | Danny Soroker | Method for consolidated launching of multiple tasks |
US8219991B2 (en) | 2006-06-09 | 2012-07-10 | International Business Machines Corporation | Consolidated launching of multiple tasks |
US8423956B2 (en) | 2006-06-15 | 2013-04-16 | International Business Machines Corporation | Sharing resources among hierarchical containers of resources |
US20080209432A1 (en) * | 2006-06-15 | 2008-08-28 | Guruduth Somasekhara Banavar | Computer implemented method and system for sharing resources among hierarchical containers of resources |
US8302073B2 (en) | 2006-06-15 | 2012-10-30 | International Business Machines Corporation | Moving and copying dependencies along with source code |
US20070294667A1 (en) * | 2006-06-15 | 2007-12-20 | International Business Machines Corporation | Method for moving and copying dependencies along with source code |
US8020108B1 (en) * | 2006-09-29 | 2011-09-13 | Emc Corporation | Separation of presentation and business models for common management platform tasks in a storage area network |
US7941132B2 (en) * | 2006-12-21 | 2011-05-10 | Motorola Mobility, Inc. | Method and apparatus for dynamic menuing of applications in a mobile communication device |
US20080153473A1 (en) * | 2006-12-21 | 2008-06-26 | Motorola, Inc. | Method and apparatus for dynamic menuing of applications in a mobile communication device |
EP2107459A1 (en) * | 2008-03-31 | 2009-10-07 | Jatho Investments | A software appliance framework |
US20130268853A1 (en) * | 2010-09-09 | 2013-10-10 | Option | Mobile terminal comprising a man/machine interface |
US20170139685A1 (en) * | 2014-06-25 | 2017-05-18 | Chengdu Puzhong Software Limted Company | Visual software modeling method to construct software views based on a software meta view |
US20180176086A1 (en) * | 2015-06-02 | 2018-06-21 | Sparkl Limited | Interaction of devices in a networked environment |
US10601662B2 (en) * | 2015-06-02 | 2020-03-24 | Sparkl Limited | Interaction of devices in a networked environment |
US9871911B1 (en) | 2016-09-30 | 2018-01-16 | Microsoft Technology Licensing, Llc | Visualizations for interactions with external computing logic |
Also Published As
Publication number | Publication date |
---|---|
US20080250410A1 (en) | 2008-10-09 |
US8219991B2 (en) | 2012-07-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8219991B2 (en) | Consolidated launching of multiple tasks | |
O'Kane | A gentle introduction to ROS | |
US9514031B2 (en) | Auto-deployment and testing of system application test cases in remote server environments | |
Gonsalves | Evaluating the mobile development frameworks Apache Cordova and Flutter and their impact on the development process and application characteristics | |
US8166347B2 (en) | Automatic testing for dynamic applications | |
US10409564B2 (en) | Recording and playback of development sessions | |
CN102667730B (en) | Design time debugging | |
US10489274B2 (en) | Using emulation to disassociate verification from stimulus in functional test | |
CN108347358A (en) | The automatic test of cloud connection | |
WO2020061533A1 (en) | Platform-integrated ide | |
US20030167422A1 (en) | Methods and systems for managing an application's relationship to its run-time environment | |
US9965257B2 (en) | Automatic configuration of project system from project capabilities | |
US20140298290A1 (en) | Identification of code changes using language syntax and changeset data | |
US8904346B1 (en) | Method and system for automated load testing of web applications | |
CN109739704A (en) | A kind of interface test method, server-side and computer readable storage medium | |
US20070240131A1 (en) | Application prototyping | |
Thomas et al. | Simulation factory: Taming application configuration and workflow on high-end resources | |
Oliveira | pytest Quick Start Guide: Write better Python code with simple and maintainable tests | |
US8745587B2 (en) | System and method for testing computer programs | |
Milka et al. | Dfuntest: A testing framework for distributed applications | |
Allen | Android for Absolute Beginners | |
US11775293B1 (en) | Deploying a static code analyzer based on program synthesis from input-output examples | |
Versluis et al. | Creating and running tests with xamarin test cloud | |
Bronkhorst et al. | Design Report VEmulate | |
Voncina | Streaming MySQL Database Activity to AWS Kinesis |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SOROKER, DANNY;DIG, DANIEL IRIMIE;CACERES, RAMON;AND OTHERS;REEL/FRAME:017856/0095;SIGNING DATES FROM 20060601 TO 20060605 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |
|
AS | Assignment |
Owner name: MIDWAY TECHNOLOGY COMPANY LLC, MICHIGAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:037704/0257 Effective date: 20151231 |
|
AS | Assignment |
Owner name: SERVICENOW, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MIDWAY TECHNOLOGY COMPANY LLC;REEL/FRAME:038324/0816 Effective date: 20160324 |