Abstract: A mechanism for continuous integration in a content repository is disclosed. A method of the invention includes retrieving by a computing system an application from an archive of the computing system and executing at least one test file corresponding to the application in the archive. The method further includes storing the application and results from executing the at least one test file as metadata for the application in the content repository.

Abstract: Described herein are interactive graphical user interfaces that visualize execution behavior of source code together with theoretical execution behavior of the source code together with the source code itself. Structure of the source code is analyzed to determine theoretical execution behavior of the source code. Thereafter, symbolic execution of the source code is undertaken to output an execution trace. The execution trace is shown together with the theoretical execution behavior of the source code.

Abstract: A system and method for collecting instrumentation data in a processor with a pipelined instruction execution stages arranged in an out-of-order execution architecture. One instruction group in a Global Completion Table is marked as a tagged group. Instrumentation data is stored for processing stages processing instructions associated with the tagged group. Sample signal pulses trigger a determination of whether the tagged group is the next-to-complete instruction group. When the sample pulse occurs at a time when the tagged group is the next-to-complete group, the instrumentation data is written as an output. Instrumentation data present during sample pulses that occur when the tagged group is not the next-to-complete group is optionally discarded. Sample pulses are generated at a rate equal to the desired sample rate times the number of groups in the global completion table to better ensure occurrence of a next-to-complete tagged group.

Abstract: A method for software processing includes obtaining change information, which records changes that have been performed in respective locations in software code. The change information is processed so as to assign to at least some of the locations respective priorities, which are indicative of respective likelihoods that the locations contain program faults. The at least some of the locations are presented to a user in accordance with the assigned priorities.

Abstract: Mechanisms are provided for debugging a graphical user interface (GUI) of a computer application code. The mechanisms detect a user interaction with a first renderable object of the GUI during execution of the computer application code. The mechanisms identify one or more second renderable objects of the GUI that are reachable from the first renderable object based on an identity of the first renderable object and a type of the user interaction. Moreover, the mechanisms apply one or more compliance rules to the first renderable object and one or more second renderable objects, the compliance rules specifying requirements for at least one relationship between the first renderable object and the one or more second renderable objects. Additionally, the mechanisms output results of the application of the one or more compliance rules to the first renderable object and one or more second renderable objects.

Abstract: A computer-implemented method for reliably identifying controls invoked during quality-assurance reviews of user interfaces may include: 1) identifying at least one user-interface control invoked during an initial quality-assurance review of a user interface, 2) for each identified user-interface control, identifying an object-tree path that is followed when invoking the user-interface control, 3) storing the object-tree path for the user-interface control in a data structure, and then 4) using the object-tree path during a subsequent quality-assurance review to automatically identify and invoke the user-interface control.

Abstract: Systems, methods, and computer storage media having computer-executable instructions embodied thereon that facilitate static software program analysis using an interactive tool and/or a disassembly integration tool are provided. An interactive tool enables a user to view alternative error paths in association with an error such that the user can identify any valid errors within program code. A disassembly integration tool provides source code that is interleaved with an intermediate representation of such source code.

Abstract: A debugging tool is provided that is capable of recording code paths taken during a program's execution, and along the way capture the memory state at configurable points in time such as function exits or statements. The tool also records interactions with external systems like a database, and captures which statements resulted in interactions with these systems. An analysis of the output of the debugging tool enables a developer to understand which part of the code executed; what the value of relevant variables were at configurable points in time; and which code statements correlate to which interactions with external systems.

Abstract: A method, information processing system, and computer program product integrate a code coverage tool with a debugger. A debugging process is performed on a set of source code for an application program. A set of code coverage information associated with the set of source code is analyzed with respect to a set of debugging information. The set of code coverage information at least identifies a set of instructions that has been executed. A set of source code lines in the set of source code that correspond to the set of instructions that has been executed is identified based on the analyzing. A user is notified through a user interface that the set of instructions associated with the identified set of source code have been executed.

Abstract: In one general aspect, a computer-based software testing method is disclosed that includes presenting to a user an interactive visual user interface of an application under test that includes a plurality of user interface controls, with each of the presented user interface controls having a predefined native interaction mode. The method also includes intercepting normative pointing-device-based user interaction with each of a plurality of the user interface controls, with the normative pointing-device-based user interaction mode being different from the native interaction mode. Interface definitions are built for the application based on results of the steps of intercepting for the plurality of interface controls.

Abstract: A method of creating computer instructions for transforming inbound instances, being instances of an inbound data format, into outbound instances, being instances of an outbound data format. At least one of the inbound and outbound data formats has a number of segments arranged in a hierarchical manner. The method uses a computing device having at least a processor, a memory, a display device and an input device. The method includes allowing a developer to use the input device to create a graphical representation of the inbound data format on the display device and allowing the developer to use the input device to create a graphical representation of the outbound data format on the display device.

Abstract: A degree of detail calculation required for calculations to process computer graphics data is determined based on input parameters that are varying in certain dimensions. During a detail analysis of a shader, a directed graph is built in such a way that each connection between nodes indicates a dependency among inputs and outputs of calculations and/or input parameters. For each input parameter, variability information about the input parameter is obtained. A lattice or a table representing dimensional variability is used to determine a variability value for each calculation for given input parameters and dependency relationships among other calculations. After a variability value has been determined for each calculation, calculations are grouped into several groups and executed once per the variability value.

Abstract: The present invention provides for debugging a target program with a computer comprising a storage unit and a processing unit. In one aspect, this comprises: storing, in the storage unit, reliability information including the reliability of individual indices of classification items of the program; reading, by the processing unit, the reliability information of the target program from the storage unit and determining a reliable code area and an unreliable code area by using the reliability of the individual indices in the reliability information; and executing debugging of the debug target program only for the unreliable code area while omitting debugging of the reliable code area. A graphical user interface to support debugging of only unreliable code areas is also disclosed.

Abstract: A debugger allows a programmer to select the granularity of a line step function. Using a debugger step statement, the programmer can specify line step, statement step, or automatic selection. When the user specifies line step in the debugger statement, the debugger functions in true line step mode, where a line of source code is executed for each step. When the user specifies statement step in the debugger statement, the debugger functions in statement step mode, where a statement is executed for each step. When the user specifies automatic selection in the debugger statement, the program is analyzed, and a decision regarding whether to use line step or statement step is made based on the characteristics of the program and based on user-specified selection criteria. In this manner the function of the debugger when line stepping can vary according to the programmer's needs.

Abstract: Systems, methods, and computer storage media having computer-executable instructions embodied thereon determine whether an output value of a dependency graph has a particular characteristic. In one embodiment, to make this determination, a dependency graph is generated that illustrates external and internal nodes, in addition to their dependency to one another. External nodes, or those nodes that do not depend on other nodes, are analyzed to determine whether they have a particular characteristic. Depending on the operation associated with the characteristic, it may then be determined whether the output value of the dependency graph also has that characteristic.

Abstract: A workflow module automates and monitors a package review process. A package review module receives a package created by a contributor to be reviewed for compliance with a set of guidelines. The workflow module initiates, monitors, and manages a plurality of package review tasks to be performed on the package. A user interface module provides user interface for creating a package and a user interface for reviewing a package. The workflow module automates review tasks, interfaces with external servers performing review tasks, gathers review task results, determines whether to send a notification regarding the status of a review task, sends notifications regarding the status of a review task and stores successfully review packages in a repository.

Abstract: Computation execution can be visualized and debugged. A computation such as a database query plan graph can be extracted from a database query expression. Trace points can be injected into the database query expression while preserving original behavior. Query graphs can be generated with automatic inserting of mechanisms to connect to trace points, enabling visualization of query execution lifecycle states, collection of data traces across operators, and historical debugging with replay of data sets.

Abstract: Various technologies and techniques are disclosed for providing stepping and state viewing in a debugger application. A start and end breakpoint are assigned. Source code execution begins, and upon reaching the start breakpoint, a logging feature begins storing one or more values that may be impacted upon execution of code between the start breakpoint and an end breakpoint. More lines of source code are executed until the end breakpoint is reached. When the end breakpoint is reached, the debugger is put into break mode. While in break mode, a playback feature is provided to allow a user to play back a path of execution that occurred between the start breakpoint and the end breakpoint. The playback feature uses at least some of the values that were stored with the logging feature to show how each referenced variable changed in value.

Abstract: Computer program product, apparatus, and data processing system for modifying a computer program. According to one embodiment, a new value to replace a value associated with a virtual type in a computer program is received. The new value is received during execution of the computer program by a processor unit. The replacement of the value by the new value modifies the computer program while the computer program is executed by the processor.

Abstract: Various embodiments include at least one of systems, methods, and software to receive input configuring tests within a computing environment to expose users to standard application or website experiences or test experiences. In some embodiments, multiple tests may be configured to run orthogonally within user experiences without affecting the results of one another. Some such embodiments preserve the ability to execute certain tests in a non-orthogonal manner while other tests are allowed to execute orthogonally.

Abstract: Technology is described for debugging in a multi-processor environment. An example system can include a plurality of process icons representing processes executing on compute nodes. A plurality of relationship arc icons between the process icons can represent messages being sent between source processes and destination processes on the compute nodes. A tabular display control can have rows to display attributes for relationship arc icons representing the messages being sent. In addition, a grouping module can be used to identify groups of messages that are related and to highlight relationship arc icons which are part of a group.

Abstract: A system for enabling a developer to concurrently debug parallel activities in a business process or workflow, or other software process. A production server includes a business process, which includes a parallel activity. The production server is operable to receive a request to debug the business process, present a graphical representation of the business process, receive input which indicates where a breakpoint is to be added to the business process, and insert the breakpoint. When a request to debug the business process is received, the production server instantiates the business process and executes the instance, and pauses execution of the instance when a breakpoint is reached and enters debug mode. It can then receive an instruction to perform a parallel-step operation on the parallel activity, execute a plurality of current activities in the parallel activity concurrently, and pause execution before executing a next activity and waits for further input.

Abstract: A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of threads stops execution of only the one thread without concurrently stopping execution of other threads. In the non-stop debugging environment, thread-specific watch event administration includes holding from execution, by the debugger, a thread triggering a watch event; determining, by the debugger, whether the watch event was set for the thread triggering the watch event; if the watch event was set for the thread triggering the watch event, setting, by the debugger, the debug perspective of a GUI to the thread triggering the watch event; and, if the watch event was not set for the thread triggering the watch event: retrieving, by the debugger, watch event information from the thread triggering the watch event; and resuming, by the debugger without user interaction, execution of the thread triggering the watch event.

Abstract: A non-stop debugging environment includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of other threads. In such a non-stop debug environment, impact indication of thread-specific events includes tracking, by the debugger, activity associated with a thread-specific event and displaying, by the debugger in a graphical user interface (GUI), an indication of thread-specific event impact in dependence upon the tracked activity.

Abstract: Event management in a non-stop debugging environment that includes a debugger configured to debug a multi-threaded debuggee, where encountering an event by one of the threads stops execution of only the one thread without concurrently stopping execution of other threads and event management includes: receiving, by the debugger, a user request to establish a dynamically disabled event that is disabled for all threads upon a stop in execution of any thread; establishing, by the debugger, the dynamically disabled event; identifying, by the debugger, a stop in execution of a particular thread; and disabling, by the debugger, the dynamically disabled event for all threads of the debuggee.

Abstract: A method for a network having a network element with an original configuration profile stored therewith which specifies operation of the network element in the network includes connecting a server to the network such that the server is in communication with the network element via the network. The server retrieves the original configuration profile from the network element after the network element has been operating in the network. The server analyzes the original configuration profile for compliance with desired characteristics. If the original configuration profile is not in compliance with the desired characteristics, then the server manipulates the original configuration profile to generate a new configuration profile in compliance with the desired characteristics and forwards the new configuration profile to the network element for the network element to store therewith in place of the original configuration profile.

Abstract: A test generator and methods for generating tests from a hybrid diagram are provided. A hybrid diagram is a diagram that primarily uses one higher-level semantic notation with portions utilizing one or more secondary higher-level semantic notations. Example higher-level semantic notations are statechart notation and data-flow notation. A test generator processes the hybrid diagram without reducing the higher-level semantic constructs to lower-level semantic constructs. The test generator generates test-generation templates as needed based on the higher-level semantic model used in the diagram. The test generator uses the test-generation templates to generate tests for a system-performing device specified by the diagram. The generated tests may be executed automatically by a test driver or manually by a human tester.

Abstract: The present invention monitors usage of an operating system at an application program interface (“API”) level and monitors changes in API functionality associated with an upcoming release to manage the version change process. A computer system is configured to track a collection of API functions associated with a first version operating system currently installed and to record the subset of API functions that have been called by applications during operation of the first version operating system. The computer system is further configured to manage the subset of API functions and generate a comparison between the subset and a list of API functions that have changed between a second version and the first version operating system. Finally, the computer system is configured to report the result of the comparison back to the user.

Abstract: An indication of a change to at least one source file associated with a software build is received via a processor. A set of test levels of a level-based testing suite are sequentially processed, where each test level subsequently processed includes tests with decreasing qualitative testing information relative to tests associated with previously-processed test levels. For each processed test level, at least one test is selected that tests the change to the at least one source file associated with the software build, test coverage relative to a target risk level for the software build is determined for each selected test, and test selection is terminated upon determining that the test coverage for the selected tests at least meets the target risk level for the software build.

Abstract: An indication of a change to at least one source file associated with a software build is received via a processor. A set of test levels of a level-based testing suite are sequentially processed, where each test level subsequently processed includes tests with decreasing qualitative testing information relative to tests associated with previously-processed test levels. For each processed test level, at least one test is selected that tests the change to the at least one source file associated with the software build, test coverage relative to a target risk level for the software build is determined for each selected test, and test selection is terminated upon determining that the test coverage for the selected tests at least meets the target risk level for the software build.

Abstract: Debugging a graphics application executing on a target device. The graphics application may execute CPU instructions to generate graphics commands to graphics hardware for generation of graphics on a display. A breakpoint for the graphics application may be detected at a first time. In response to detecting the breakpoint, one or more graphics commands which were executed by the graphics hardware proximate to the first time may be displayed. Additionally, source code corresponding to CPU instructions which generated the one or more graphics commands may be displayed.

Abstract: A method and a non-transitory computer readable medium for evaluating a configuration change of a cable television network, the method may include: receiving, a model of a cable television network, the cable television network comprises multiple service groups, multiple transmitters and at least one session management unit; wherein each service group comprises multiple user devices; receiving or generating, viewers' activity information about viewing patterns of viewers that belong to the multiple service groups; receiving a request to perform a requested change in a current configuration of the cable television network; simulating, by a simulator, based on the model, the viewers' activity information and the requested change, a provision of services to the multiple service groups given the requested change to provide simulation results that represent an effect of the requested change, prior to a deployment of the change in the cable television network.

Abstract: A method and system for creating and modifying computer applications using an application description language based on a markup language is provided. An engine creates, connects, and initializes objects corresponding to entities, and specified by entity tags. A factory may be specified by an entity tag and used to create a plurality of entities. Applications are specified in a plaintext descriptive language using a markup language such as XML, enabling applications to be easily developed using object oriented techniques and abstraction. Altering preexisting applications is also simplified. Finally, an application may be dynamically reconfigured when the application's data changes. Type checking and conditional creation of entities is supported.

Abstract: A debugger allows a programmer to select the granularity of a line step function. Using a debugger step statement, the programmer can specify line step, statement step, or automatic selection. When the user specifies line step in the debugger statement, the debugger functions in true line step mode, where a line of source code is executed for each step. When the user specifies statement step in the debugger statement, the debugger functions in statement step mode, where a statement is executed for each step. When the user specifies automatic selection in the debugger statement, the program is analyzed, and a decision regarding whether to use line step or statement step is made based on the characteristics of the program and based on user-specified selection criteria. In this manner the function of the debugger when line stepping can vary according to the programmer's needs.

Abstract: An apparatus and methods for hardware-based performance monitoring of a computer system are presented. The apparatus includes: processing units; a memory; a connector device connecting the processing units and the memory; probes inserted the processing units, and the probes generating probe signals when selected processing events are detected; and a thread trace device connected to the connector device. The thread trace device includes an event interface to receive probe signals, and an event memory controller to send probe event messages to the memory, where probe event messages are based on probe signals. The probe event messages transferred to memory can be subsequently analyzed using a software program to determine, for example, thread-to-thread interactions.

Abstract: A system and method for creating and using configuration diagrams for configuring distributed systems. The methods described herein may be used for various types of operations in configuring distributed systems, including creating programs, managing programs in the distributed system, deploying programs to various distributed devices, configuring remote execution or inter-operation of distributed programs, and executing distributed applications. Embodiments of the invention utilize graphical iconic-based techniques for performing the above operations. The configuration diagram may include device icons which represent devices and program icons which represent programs. Device icons and program icons may be associated with each other to accomplish various program creation and deployment operations. Device icons and program icons may also interact with graphical program nodes or icons. Context sensitive device connections and/or program connections are displayed.

Abstract: A system for computer-based testing for producing a test and delivering the test to an examinee includes a storage device that has a first storage location, which stores a first segment of a test definition language, and a second storage location, which stores a second segment of the test definition language, a validation expansion module that validates the first segment and the second segment of the test definition language, a test packager that amalgamates the first storage location and the second storage location and transmits the amalgamated segment to the validation expansion module such that the validation expansion module can determine whether the amalgamated segment forms a complete and valid set, and a test driver that has an executable code that controls functionality that enables the test driver to deliver the test to an examinee.

Abstract: A computer-implemented method for focusing product testing based on areas of change within the product is described. A link between resource files of a product and test cases associated with the product is created. The resource files of a first build of the product are compared with the resource files of a second build of the product. A report that comprises which resource files changed between the first build of the product and the second build of the product is generated. The resource files that have changed and the test cases linked to the changed resource files are displayed. The test cases linked to the changed resource files are executed.

Abstract: Systems, methods, and computer-readable media provide for updating a firmware image during a debugging sequence using a firmware debugger application without re-flashing each updated firmware image on a non-volatile memory device. Embodiments include a debugger application operating on a host computer system and a debugger driver located within a firmware image undergoing the debugging sequence on a target computer system. The debugger application and debugger driver may communicate and transfer data between one another. Upon detecting an error in a firmware image, the debugger driver notifies the debugger application. The debugger application sends an updated firmware image to the debugger driver on the target computer system. The debugger driver loads the updated firmware image and passes control to an entry point of the updated firmware image for continued debugging from the new entry point.

Abstract: Integrating compiler warnings into a debug session including: receiving, by a debugger for a debug session of a debuggee from a compiler, compiled source code for execution and compiler warning data describing one or more compiler warnings generated at compile time of the debuggee, each compiler warning resulting from a source code variable statement in the debuggee source code; receiving, by the debugger, a request to evaluate a variable; determining, from the compiler warning data, whether evaluating the variable is dependent upon a source code variable statement resulting in a compiler warning; and, if evaluating the variable is dependent upon a source code variable statement resulting in a compiler warning, returning, by the debugger responsive to the request along with a result of the evaluation, a compiler warning indicator.

Abstract: A business process component based framework enables test automation to be automated using a component generator and a script generator. The framework is implemented as a two-layer structure. A test script on the top layer is a test case with action description of each step. A component on the bottom layer is a representative of an autonomous GUI interface unit, such as a window. The component can execute any actions on any GUI objects on what it represents. In such a framework, each test case becomes a sequence of calling components. Each called component becomes a slave executing the actions. Both script and component become simple enough to be automated. In an exemplary embodiment, a script generator and a component generator are developed to automatically generate test scripts and components, which are implemented with QuickTest Professional, using test cases and GUI repository of components as their input, respectively.

Abstract: The present invention extends to methods, systems, and computer program products for visualizing thread state during program debugging. A tooltip can present a visual summary of the execution state of the application threads, what the values are, and patterns in the values, during debugging. As such, a developer debugging a parallel application can see the status of threads within a thread block. A visual tooltip (or other presentation mechanism) can be activated by hovering (e.g., placing a mouse pointer) over a user interface element. A visual tooltip can be presented by hovering over a status rollup visualization of the thread states or by hovering over an icon that appears in the code gutter for a code segment. Accordingly, developers can get a concise visual summary of thread states, variables, and values during debugging.

Abstract: Event management in a non-stop debugging environment that includes a debugger configured to debug a debuggee, the debuggee including a number of threads of execution, where encountering an event by one of threads stops execution of only the one thread without concurrently stopping execution of other threads and event management includes: encountering, by a first thread, an event that stops execution of the first thread; while execution of the first thread is stopped, encountering, by each of one or more other threads, an event stopping execution of the other thread; queuing, by the debugger, the events stopping execution of the other threads; receiving, by the debugger from a user, an indication to flush one or more events from the queue; and flushing, by the debugger, the one or more events from the queue.

Abstract: An analysis engine is described for performing static analysis using CEGAR loop functionality, using a combination of forward and backward validation-phase trace analyses. The analysis engine includes a number of features. For example: (1) the analysis engine can operate on blocks of program statements of different adjustable sizes; (2) the analysis engine can identify a subtrace of the trace and perform analysis on that subtrace (rather than the full trace); (3) the analysis engine can form a pyramid of state conditions and extract predicates based on the pyramid and/or from auxiliary source(s); (4) the analysis engine can generate predicates using an increasingly-aggressive series of available discovery techniques; (5) the analysis engine can selectively concretize procedure calls associated with the trace on an as-needed basis and perform other refinements; and (6) the analysis engine can add additional verification targets in the course of its analysis, etc.

Abstract: An architecture for streaming data from a sending endpoint to a receiving endpoint which are connected to each other by multiple networks is provided. Each of the sending endpoint and the receiving endpoint has multiple physical interfaces each for interfacing to a respective one of the multiple networks. The architecture is implemented on both of the endpoints. The architecture includes a traffic monitor for gathering performance characteristics of each of the multiple physical interfaces, and a software library for controlling sending and receiving of the data stream between the endpoints. The traffic monitor and the software library communicate information to each other. The software library instantiates a plurality of bondable virtual interfaces for splitting the data stream into multiple data sub-streams and for combining the multiple data sub-streams into the data stream, and a data organizer for designating one of the plurality of bondable virtual interfaces.

Abstract: A system for detecting security vulnerabilities in computer software, including a cryptographic API identifier configured to identify a cryptographic API among the instructions of a computer software application, a path-to-source tracer configured to trace an information flow path among the instructions between the cryptographic API and a source that directly or indirectly provides data that are input to the cryptographic API, where a cryptographically-sensitive information carrier lies along the information flow path, a path-to-sink tracer configured to trace an information flow path among the instructions from the cryptographically-sensitive information carrier to a sink, and a security vulnerability identifier configured to provide a notification that the information flow path between the cryptographically-sensitive information carrier and the sink represents security vulnerability if the information flow path between the cryptographically-sensitive information carrier and the sink does not pass through a

Abstract: A debugger allows a programmer to select the granularity of a line step function. Using a debugger step statement, the programmer can specify line step, statement step, or automatic selection. When the user specifies line step in the debugger statement, the debugger functions in true line step mode, where a line of source code is executed for each step. When the user specifies statement step in the debugger statement, the debugger functions in statement step mode, where a statement is executed for each step. When the user specifies automatic selection in the debugger statement, the program is analyzed, and a decision regarding whether to use line step or statement step is made based on the characteristics of the program and based on user-specified selection criteria. In this manner the function of the debugger when line stepping can vary according to the programmer's needs.

Abstract: Described are systems and methods for generating interactive in memory objects from stored program failure data. An anomalous condition related to a program failure is detected. Data is captured regarding the anomalous condition. The captured data is stored. The stored data is converted into at least one in-memory object. A runtime environment is reproduced about a region of code related to the program failure from the at least one in-memory object.

Abstract: Systems and methods for identifying a target position on a computer display are provided. A system receives computer display data indicative of contents of a computer display and identifies a first area of interest within the computer display. Identifying the area of interest includes receiving a first image and searching the computer display for the first image. Upon finding a match for the first image, a location of the match for the first image is identified as a first point. A second image is received and searched for on the computer display. Upon finding a match for the second image, the location of the match is identified as a second point. The first point and the second point are used in defining an area of interest. A target position is located within the area of interest.

Abstract: A system and method for dynamically determining a plurality of possible or valid parameter values and automatically including one of the parameter values in a software program. In one embodiment, the plurality of possible parameter values may be dynamically determined based on a hardware configuration of a computer system. A graphical user interface for selecting a parameter value may be displayed. The graphical user interface may visually indicate the plurality of dynamically determined possible parameter values and may allow a user to easily select one of the possible parameter values for inclusion in the software program. User input may be received to the graphical user interface to select a first parameter value from the plurality of possible parameter values. The first parameter value may be programmatically included in the software program in response to the first parameter value being selected.