Abstract: A conversion system includes a build manager, a file storage device to store original files associated with computer code or data of a project build, a compiler, a cache to store converted files, and an interceptor to provide requested files to the compiler. The interceptor includes one or more processors and memory storing instructions that cause the processor(s) to receive a plurality of file requests for files from the compiler during compilation between a starting and an ending of at least a portion of the project build, examine the cache to determine whether a requested file is stored in the cache for each of the file requests received between the starting and ending of the portion of the project build, and provide the requested file to the compiler.

Abstract: A development system with improved methodology for creation and reuse of software assets is shown and described. In one embodiment, for example, in a development system, a method is described for facilitating creation of a reusable application, the method comprises steps of: during development of the application, capturing knowledge and intent of the application's original developer alongside source code created for the application; producing an archival module storing the source code for the application together with metadata capturing the knowledge and intent of the original developer, the metadata including at least one script guiding subsequent developers in use and modification of the source code for the application; and consuming the archival module by a follow-on developer, including executing the at least one script for facilitating creation of a reusable version of the application.

Abstract: Methods and systems are disclosed for tracking change data in a database. A database, stored at a computer system, is accessed with a plurality of data written to fields in the database, wherein each data in the fields comprises a record header. Data is changed in at least one field of the plurality of data in the database via the computer system, wherein the changing the data changes the record header for the at least one field. A transaction identification (ID) is stored in the record header for each change to the at least one field. A flag is created in the record header signaling the change to the at least one field. Successive versions of the database are linked together such that a subscriber accessing the database can automatically view a current version of the database with the change by accessing the record header and identifying the flag.

Abstract: System and methodology automating delivery, licensing, and availability of software products are shown and described.

Abstract: A development system with improved methodology for creation and reuse of software assets is shown and described. In one embodiment, for example, in a development system, a method is described for facilitating creation of a reusable application, the method comprises steps of: during development of the application, capturing knowledge and intent of the application's original developer alongside source code created for the application; producing an archival module storing the source code for the application together with metadata capturing the knowledge and intent of the original developer, the metadata including at least one script guiding subsequent developers in use and modification of the source code for the application; and consuming the archival module by a follow-on developer, including executing the at least one script for facilitating creation of a reusable version of the application.