Abstract:
According to one aspect of the present disclosure, a process for analyzing components related to a software application in a software development environment is disclosed. The process includes obtaining metadata information for each of a plurality of components from the software development environment, and generating an entry including extracting attribute information from the obtained metadata information for each component for use by a developer of the software application.
Abstract:
Systems and methods are disclosed for receiving a first specification that identifies program code behavior associated with a plurality of documents. The specification includes an input-output pair with a first data entity and a second data entity. The systems and methods further include identifying one or more documents, within the plurality of documents, that are configured to (i) use at least a portion of the first data entity as an input to program code associated with particular ones of the documents, and (ii) provide at least a portion of the second data entity as output associated with the program code, wherein the particular ones of the documents correspond to a positive matching between one or more constraints associated with each document and one or more constraints associated with the specification, and generating search results comprising the identified one or more documents.
Abstract:
The subject disclosure relates to capturing window definitions of an executing user interface application and/or website and generating an editable model representation. A starter storyboard or screens can be generated quickly by recording a manipulation of an existing application or website. States associated with a multitude of user interface control hierarchies of a target application are captured, stored in a generic user interface model, and used for generation of mockups, code, and so forth. In an aspect, an indication is received that an application or website is be captured. Thereafter, the state of the website or application window and subsequent windows are observed and captured. For each of the subsequent windows traversed in a live control hierarchy, basic information about each item is captured. The information gathered for a given window and its control hierarchy can be serialized into a simple XML representation.
Abstract:
Methods, systems, and techniques for role-based modernization of legacy applications are provided. Example embodiments provide a Role-Based Modernization System ("RBMS"), which enables the reorganization of (menu-based) legacy applications by role as a method of modernization and enables user access to such modernized applications through roles. In addition the RBMS supports the ability to enhance such legacy applications by blending them with non-legacy tasks and functions in a user-transparent fashion. In one embodiment, the RBMS comprises a client-side javascript display and control module and a Java applet host interface and a server-side emulation control services module. These components cooperate to uniformly present legacy and non-legacy tasks that have been reorganized according to role modernization techniques.
Abstract:
Systems (30) to provide automated testing of a markup software application, program product (47), and methods are provided. An example of a system (30) can include a network (31), at least one computer including memory and a processor, and application testing program product stored in the memory of the at least one computer. The application testing program product can include instructions that when executed by the processor of the respective computer causes the respective computer to perform various operations to include receiving a user selection identifying a target element (65) of an application; determining a command describing an action being performed; identifying a translator (54) responsive to a captured command (52); and generating at least one of the following: an abstract script describing the action being performed by the target element, a context-sensitive verification available for the target element, or a context sensitive synchronization available for the target element.
Abstract:
Methods and systems consistent with the present invention (Fig. 2, 200, 202, 204, 206, 208) provide an improved software development tool that allows a developer to determine which elements in source code are at most a given number of links away from a selected element (Fig. 20A, 2000, 2002, 2004, 2006, 2008, 2010, 2012, 2014, 2016 & FIG. 20B, 2018, 2020, 2022, 2024, 2026, 2028). Moreover, the software development tool allows the developer to specify the types of links connecting the elements from the selected element (Fig. 23, 2300, 2302, 2304).
Abstract:
Methods and systems consistent with the present invention (FIG.2,200, 202, 204, 206, 208) provide an improved software development tool that represents multiple dependencies between a dependent node and a defining node (Fig. 22A, 2202, 2203, 2204, 2206, 2208, 2210, 2212, 2214, Fig. 22B, 2216, 2218, 2220, 2222) in a project as a single dependency link. Figs. 22A and 22B, depict a flow diagram illustrating an exemplary process performed by a software development tool to graphically represent multiple dependencies between two nodes in a project as a single dependency link, as disclosed on page 32 of the specification. Moreover, methods and systems consistent with the present invention also identify and display details regarding each dependency in a project upon request by the user (Fig. 28A, 2802, 2804, 2806, 2808, 2810, 2812, 2814, 2816, 2818, 2820, Fig. 28B, 2822, 2824, Fig. 28C, 2826, 2828, 2830, 2832, 2834, 2836, 2838, 2840). Figs. 28A, 28B, and 28C, depict a flow diagram illustrating an exemplary process performed by the software development tool to identify and display the specific elements and usage that result in each dependency between a dependent node and a defining node, as disclosed on page 38 of the specification.
Abstract:
Methods and system consistent with the present invention (FIG.2, 200, 202, 204, 206, 208) provide an improved software development tool which allows a developer to receive an identification of a data structure with an attribute field in a database (FIG.24, 2400, 2402, 2404), determine whether an attribute field of the data structure is associated with an attribute in the source code, and if the attribute field is not associated with the attribute in the source code, generate the attribute in the source code from the attribute field (FIG.36A, 3602, 3604, 3606, 3608 & FIG.36B, 3612, 3613, 3614, 3616, 3618, 3619, 3620, 3622, respectively).
Abstract:
An item to be processed is received and scanned. The scan identifies any functions or procedures in the item being processed, and extracts actual code representing those functions or procedures. Any invoking functions, which invoke the identified function, are, themselves, identified. Actual code for the invoking function is extracted as well. An output documentation file is generated that includes a name of the identified function or procedure, as well as actual code for the function or procedure, and actual code from at least one example of an invoking function.