1250results about "Program documentation" patented technology

An automated software production system is provided, in which system requirements are captured, converted into a formal specification, and validated for correctness and completeness. In addition, a translator is provided to automatically generate a complete, robust software application based on the validated formal specification, including user-interface code and error handling code.

A developer can express the logic offered by a Web service, or other network accessible service, using a standard programming language augmented with declarative annotations specifying preferences for exposing that logic as a Web service. At compile time, an enhanced compiler can analyze the annotated source file and automatically generate the mechanisms required to expose its functionality as a Web service or network accessible service. Because the annotations are declarative, they may be easily visualized, created, and modified such as by using a graphical user interface, further simplifying the developer's task. Thus, such an approach decreases the time, knowledge, skill and ultimately cost required to develop the complex support required to proved services in these environments. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Methods and arrangements to manage comment data that is associated with computer executable code are provided. Comment data associated with a line or lines of executable code can be stored, and a tag can be assigned to the comment data or the line(s) of code. When it is desired to locate information about lines of code, tags allow for an improved way to search for the desired lines of code. Thus, in response to a user query for information, a search engine can locate a specific tag or groups of tags and display code and comments associated with the located tag(s).

Provided is a process that includes: determining whether to execute a software asset based on trust records documenting provenance of the software asset published to a blockchain, wherein determining whether to trust the software asset comprises: accessing the trust record, verifying the trust record has not been tampered with subsequent to publishing, verify that a hash digest based on the software asset matches a hash digest associated with the trust record and published to the blockchain; verifying that trust assertions of the trust record are cryptographically signed by trusted entities specified by entity criteria, and verifying that the trust assertions satisfy execution criteria.

Methods and apparatus for analyzing the interface usage and requirements within software applications. In one embodiment, the interfaces comprise application programming interfaces (APIs) used with Java-based software, and the apparatus comprises a computer program that analyzes file paths (or classpaths) containing one or more files comprising Java bytecode. The names of the classes are extracted and placed into a class dictionary. The different classes listed in the dictionaries are broken down into their individual methods. Each method is then dissembled and analyzed for method or field invocations on other classes found in the dictionary. Methods called are added to a “used class” report. The used class report preferably contains the name of the class, method and the instruction information.

Systems, methods, and computer program products are provided for identifying software files, flaws in code, and program fragments by obtaining a software file, determining a plurality of artifacts, accessing a database which stores a plurality of reference artifacts for reference software files, comparing at least one of the artifacts to at least one of the reference artifacts stored in the database, and identifying the software file by identifying the reference software file having the reference artifacts that correspond to the plurality of artifacts. Certain embodiments can also automatically provide updated versions of files, patches to be applied, or repaired blocks of code to replace flawed blocks. Example embodiments can accept a wide variety of file types, including source code and binary files and can analyze source code or convert files to an intermediate representation (IR) and analyze the IR.

A software database system is provided that includes an automatic code analysis and self-documentation program. This program operating on a computer analyzes and fragments input code into constituent code segments and self-documents those segments. A code repository stores the code segments. A code-generating algorithm operating on a microprocessor extracts the code segments from the repository to generate a standard code page that is deployable on a server.

Techniques for binding a data exchange format with a computer program application having source code in a particular language include receiving comment data from a particular file that includes the source code. The comment data includes first data indicating a parameter of the data exchange format. Second data from the particular file is also received. The second data is associated with the comment data and includes a statement that defines a class of data objects in the particular language. Based on the first data and the second data, third data for configuring the data exchange format is generated. When the particular language is Java and the data exchange format is XML, these techniques allow a developer to automatically produce an XML grammar document that is based on Java data objects defined by the developer and that is responsive to the developer's choices for options in the XML grammar. Individual classes or multiple nested classes are handled.

Methods, systems, and media are disclosed for translating comments in code. One embodiment includes checking out, from a code repository, code having the comments, which are in a foreign language. Further, the embodiment includes selecting a desired language for translation of the comments, and then identifying the comments in the code to be translated, which are referred to as “identified comments.” The embodiment also includes translating the identified comments from the foreign language into the language selected for translation, which then results in producing translated comments. Finally, the embodiment includes publishing the translated comments, wherein the publishing may be audio, visual or both.

Metadata describing common Java classes is extracted and utilized to optimize a Java program's performance based on the code requirements of the application. Data mining techniques extract metadata and other information about different sets of JVM byte code written by multiple vendors to determine the design choices and optimizations made by each vendor in implementing their JVM. Then, byte code in a Java application being programmed is analyzed in comparison to each vendor's JVM metadata and information. Based upon the application's requirements (for example footprint, performance, etc.), recommendations are generated that yield a newly compiled rt.jar that combines the best practices of each vendor together or recommends a particular vendor's standard JVM that is best suited for the application.

Capability test programs are generated implementing the capability test test cases for the components, wherein component developers use the capability test programs to test components during the development and coding of the components. Documentation is generated describing component abstract test cases incorporating information on capability test test cases. Component test programs are generated implementing the component abstract test cases for the components and utilizing capability test programs, wherein each component test program tests one component for at least one test case specified in the component abstract test case documentation for the component. The capability test programs and component test programs are stored in a shared repository. A software development program is deployed to enable the developers and testers to execute groups of component test programs in the shared repository to test the components during different phases of the development of the software product.

Provided is a process that includes: calling a program executed on a decentralized computing platform configured to persist state to a blockchain, the call requesting the program to release the software asset to the production environment, wherein: respective instances of the program are configured to publish release documentation by which provenance of the software asset is verifiable to the blockchain, respective instances of the program are configured to verify a cryptographic signature associated with the software asset, the cryptographic signature establishes that the software asset being released has not been tampered with subsequent to signing, the cryptographic signature establishes that the releasing entity or a proxy of the releasing entity has access to a cryptographic key by which the cryptographic signature was formed, and the decentralized computing platform is configured to reach a consensus verification determination among verification results from the replicated instances of the program.

The invention provides a gray releasing method and system. The method comprises the following steps: customizing a gray rule and generating a gray rule file; introducing the gray rule file when an access request of an initial page of a user is received by a client-side and configuring a gray flag bit in cookie of the user according to the gray rule in the gray rule file and returning the cookie tothe client-side; and respectively calling gray services or formal services according to the gray flag bit in cookie of the user when the request to services of the user is received by the client-side.

Exemplary embodiments employ a mapping among entities that are related to each other. The entities may include a graphical model, generated code, a generated report, a requirements document and/or an intermediate representation. The mapping may facilitate graphical identifications between parts of one entity that maps to part of another entity. The graphical identification may occur based on a selection of a part in one of the entities.

A software application includes a document generator. A user can download from an upgrade website documentation (e.g., release notes) describing the differences in operation between a post-upgrade version of the application that would result if a target upgrade is implemented and a pre-upgrade version of the application, e.g., the one available on the user computer system. The document generator can generate full documentation for the post-upgrade version from the pre-upgrade documentation and the upgrade documentation. The post-upgrade documentation has a revision display mode and a non-revision display mode, the former showing the changes from the operation of the pre-upgrade version to the operation of the post-upgrade version.

Methods and systems are disclosed for developing a software application through requirements specification, design, effort estimation, assigning and tracking work items, development, testing, collaboration and project management. The system is structured as an integrated software development system allowing for structured, systematic and user friendly set up of requirements specification (including workflow, user interface, business rules and integrations), technical design for UI features and integrations using design patterns, automated effort estimation, automated story card and task creation. The system also provides a novel, audio-video playback capability for workflow visualization. Further, the system provides visual depiction of defects and changed items side-by-side with requirements, as well as predictive modeling of defects that allows for forecasting of defect completion rate. In the preferred embodiment, the system is delivered as a multi-tenant Software as a Service.

The present disclosure includes a system and method for learning (or discovering and extracting) business knowledge from a collection of source code. The collection of source code is abstracted to generate an abstracted data stream, which is then transformed to an Extensible Markup Language (XML) format. The transformed data in XML format can be further converted to target formats or processed to satisfy different needs such as software system documentation, migration, impact analysis and security analysis. The disclosure also includes an implementation and operation for a pattern abstraction engine configured to receive an input data stream and format it for abstraction into a standard format using a pattern matching mechanism. The disclosure also includes an implementation and operation for a contextual pattern decoder engine configured to extract knowledge attributes and contextual taxonomy from classified blocks of an input data stream.

Previous attempts to provide systems or processes for enabling the review of the development of information stored in an electronic file are difficult to use effectively and require a user to take active steps to ensure that versions and annotations are created at regular intervals. By contrast, provided by aspects of the present invention there are systems, methods and computer program products for tracking and viewing changes to information stored in a data structure. In some embodiments the systems, methods and computer program products can be combined or integrated with software providing a visual editing environment so that changes are detected, sorted and monitored in a manner that is transparent to the user. In more specific embodiments the changes are grouped according to type, and optionally sub-type, so that a user can use the types to filter which changes in the development history of the information to review according to a particular current desire to locate specific information. In other specific embodiments, the changes are grouped in time providing temporal groups that provide “snapshots” of the development history of the information stored in a data structure at various respective points in the past.