Abstract: An aspect container being operable to generate an instance of itself at run time is provided. The aspect container comprises logic operable to create an instance of the aspect container by reading configuration information specifying a sequence of one or more aspects from an aspect container configuration file corresponding to the aspect container. The logic is also operable to generate instances of the aspects in the sequence, configure each aspect instance with its configuration information from an aspect configuration file corresponding to the aspect, and chain the aspect instances according to the specified sequence, such that the chain of aspect instances preamble and postamble activities of a class or method.

Abstract: A target shim injected into a target process detects activity in a user interface and sets a target-busy status. A source shim injected into a source process detects the input being sent toward the target process to drive automated testing. The source shim determines that the target-busy status is set, and prevents the source process from sending the input until the status is clear. The target shim clears the status after confirming that a screen capture, accessibility test, localizability test, or other user interlace analysis operation has completed. Multiple source shims and/or multiple target shims may be present. Copies of a single automation shim component may be tailored for use as source shims or as target shims. Security processes and operating system processes may be listed to prevent interference from automation shims. User interface analysis module(s) may be loaded and/or unloaded “hot” while the target process is running.

Abstract: In an embodiment, a test installer is executed that includes woven advice located at join points. The join points are associated with methods in the test installer. When the advice in the test installer is executed, the advice saves identifiers of the associated join points and times of execution. Subsets of the join points are assigned to installation options. Each installation option causes a production installer to execute a combination of methods. In response to receiving an installation option, advice is woven into the production installer at the join points specified by the assigned subset. When the advice in the production installer is executed, the advice reports its join point identifier, and the production installer presents completion progress status based on the time that was saved for the join point identifier during execution of the test installer. In this way, progress status may be provided during the installation of programs.

Abstract: During installing a first computer software product, a computer system advertises a second computer software product other than the first computer software product and demonstrates a feature of the second computer software product. The feature is responsive to said installing but unnecessary to said installing.

Abstract: The present invention teaches a variety of systems, platforms, applications, and methods, and relates to mobile platforms, embedded native applications, Java virtual machines, user interfaces, and the like. The present invention discloses a mobile platform which unifies the worlds of the Java virtual machine and native applications to provide a unified and consistent environment for multitasking both Java and native applications within a mobile device.

Abstract: System and method for converting a statechart from a first statechart development environment to a second statechart development environment. A first statechart may be received. The first statechart may be created in a first statechart development environment. The first statechart may implement a first functionality. The first statechart may be parsed to determine a plurality of elements of the first statechart. A markup language representation of the first statechart may be generated. The markup language representation may represent the plurality of elements of the first statechart. A second statechart may be generated based on the markup language representation. The second statechart may be in a second statechart development environment. The second statechart may implement the first functionality. The second statechart may be stored.

Abstract: A method and apparatus for the manually optimizing the scheduling of code are disclosed. Accordingly, a software development tool with a graphical user interface enables manually ordering the scheduling of operations for architectures that execute multiple instructions/operations per machine cycle, such as very long instruction word (VLIW) processors. Assistance is provided at the instruction scheduling stage of VLIW compilation process to increase instruction level parallelism (ILP). The apparatus provides graphical views of assembly code and related information. An interactive, user friendly method to manipulate the code during or after scheduling is provided. The programmer can temporarily pause the automated scheduling, override decision taken by the scheduler, and then resume scheduling. The method lets the programmer interact graphically with scheduling decisions in a feedback environment.

Abstract: An embedded electronic device includes a display and a user interface system shown on the display. The user interface system includes a plurality of item display modules and item resource modules. Each item display module includes a position sub-module operable to position the item resource module, and a connection sub-module capable of linking to the item resource module. Each item resource module has at least one resource path sub-module to retrieve a resource.

Abstract: Web applications are deployed for execution within the existing framework of Open Services Gateway initiative (OSGi) when they are written in the commonly-employed Java™ (trademark of Sun Microsystems, Inc) 2 Platform, Enterprise Edition (J2EE) language. The intended deployment of J2EE web applications is detected and the J2EE application contents are converted into appropriate OSGi bundles using a provisioner. The provisioner employs its list of available provision providers to create the OSGi bundles that correspond to the J2EE application contents.

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: While optimizing executable code, compilers traditionally make static determinations about whether or not to inline functions. Embodiments of the invention convert dynamic hardware-event sampling information into context-specific edge frequencies, which can be used to make inlining decisions for functions.

Abstract: An object code generating system includes: a storage unit configured to store a first source file; and an object code generating section. The object code generating section is configured to read the first source file, generate function data indicating an arrangement address and size of each of the functions in the first source file, generate an execution format file for the first source file; and read a second source file obtained by modifying at least one of the functions as a specific function in the first source file, and the function data from the storage unit, generate a dummy function corresponding to the modified specific function when the modified specific function is discovered in the second source file, arrange the dummy function at an arrangement address different from the arrangement addresses of the functions, and arrange a branch command to the dummy function at the different arrangement address.

Abstract: The present invention defines a method for assembling software components using an application controller. The application controller provides a conduit through which calling client modules can access functionality provided by various handlers in a manner that results in greater flexibility when additional functionality is required. Additional functionality can be provided to the clients by adding additional handlers to the application controller without the need to modify any of the individual clients. The client will continue invoking the application controller in the same manner as it did previously, whilst the application controller provides additional functionality by accessing the additional handlers. Indeed, the only changes that are required are to an agent, which in preferred embodiments includes a relatively straightforward to modify XML configuration file.

Abstract: A software development production management system having a processor, which is enhanced in reliability by reducing a different between an evaluation of an actual development and a formed plan. A management database holds both development process component data necessary to model a development process of software and estimation parameter data used to estimate a development plan of the software. The software development production management device compares and evaluates, upon completion of the software development, an actually performed development process and the previously created software development plan, and makes a correction to the estimation parameter data as needed to feed details of the actually conducted software development back to the next development plan.

Abstract: A method for developing a software project includes identifying business cases and goals for the software project, defining a common interface architecture through which components of the software project are to be integrated, identifying software project components to be integrated over the common interface, defining high level requirements of the project components, elaborating the component interfaces and defining detailed component requirements, implementing the project components, testing the project components individually, defining integration tests for testing integrated components, and executing the integration tests on a set of integrated components.

Abstract: An application development system for developing an application with application components is described. The system application development includes a modeling tool. The modeling tool imports the application components in a comparable component definition format, and defines a data relation between data, screens, and operations embodied in the application components in an application model. The application model has a static structural characteristic, a dynamic behavioral characteristic and an implementation characteristic. The static structural characteristic defines parts of the application. The dynamic behavioral characteristic defines responsiveness of the application to events or actions, and the implementation characteristic describes elements required for deploying the application. The modeling tool updates the cross-component mapping.

Abstract: In an embodiment, a code generator receives input code having a plurality of functional elements, such as blocks, nodes, statements, commands, etc. The input code processes a data set, such as an image file. The code generator further receives one or more criteria for the generated code. The functional elements of the input code are provided with one or more parameters regarding the block sizes that the respective functional elements can process, such as an available block size and a preferred block size. The code generator queries the functional elements of the input code to obtain their available and preferred block sizes, and builds an intermediate representation (IR) of the input code. The code generator re-organizes and modifies the IR so that it achieves the one or more criteria. Output code that meets the one or more criteria is generated from the reorganized and modified IR.

Abstract: A system for tracking the testing of a set of software modification projects in an install plan provides a centralized project database where the testers can update their progress of testing software modification projects as they perform the tests. The central database advantageously eliminates the need to contact individual testers of each and every project every time a status report needs to be generated. Instead, a manager can automatically generate status reports which contain the testing progress of particular projects in real-time to more accurately monitor what projects are on track and what projects may be falling behind schedule.

Abstract: A customized distribution, e.g. of Linux software, is built using only packages that satisfy a customer's individual requirements. The packages are verified, at build time, to be interoperable at run-time. Also, the distribution is verified to ensure all package dependencies are included. In cases where no package already exists that meets a user requirements, a new package can be created for this purpose. The packages in the distribution customized for the user can be tracked, so that as updates to the packages are released, the customer can be notified about those updates (without being notified about packages not in the customer's customized distribution). Finally, once the distribution has been built for the user, it can then be offered as a general-purpose distribution for future customers.

Abstract: An automated software testing system allows automated test script generation with fully parameterized scripts, execution, and result correlation. A software Application Under Test (AUT) includes a process having Graphical User Interface (GUI) windows, objects and data elements. A test thread tree is generated corresponding to these windows, objects and data elements. A data structure is generated to enumerate test cases indicative of the windows, objects and data elements. Also generated is a parameterized script implementing the test cases and having string values instead of hard-coded data. A global change manager automates modifying in the data structure, data object attributes across multiple scripts. A Scenario view or data generation member generates Test Descriptions, automatically documenting the test cases. The script is executed to apply each of the test cases to the AUT and receive responses.