Unified API Documentation Platform for Dynamic Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current API documentation systems face challenges in unifying documentation across different products, failing to keep pace with dynamic API changes, and lacking a centralized location for API information, leading to inconsistent and time-consuming manual updates.

Innovation Solution

An API documentation platform that generates and dynamically modifies documentation by organizing API electronic documents according to versions, using a document corpus with a document classifier, query formatter, and document generation engine to provide real-time, unified, and customizable API documentation across various formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual updates are used for API documentation, then documentation can be created, but it is time-consuming and cannot keep pace with dynamic API changes

Engineering Contradiction:
Improvedocumentation update speedVSAvoidtime for manual updates
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables self-service by automatically generating and updating API documentation through the document generation engine, which consumes API specifications and code artifacts to produce documentation without requiring manual intervention. This automated self-updating mechanism resolves the contradiction by making the documentation system self-sufficient and continuously synchronized with API changes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-generating documentation from API specifications and organizing it in a structured document corpus before users need it. The document generation engine creates documentation templates and structures in advance, allowing rapid retrieval and customization when users query for specific API documentation, thus eliminating time-consuming manual updates.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If separate documentation is maintained for different products, then product-specific details are preserved, but unified access and consistency across products is lost

Engineering Contradiction:
Improveaccess to unified documentationVSAvoidproduct-specific documentation details
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system applies universality by creating a unified document corpus that serves multiple product lines through a single centralized structure. The document generation engine can generate documentation for different products using the same underlying framework and templates, allowing users to access unified documentation across products while maintaining product-specific details through parameterized content generation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system segments documentation into modular components organized by product, API version, and functionality within the unified document corpus. This segmentation allows the system to maintain product-specific details as distinct, retrievable units while presenting them through a unified access point, resolving the contradiction between unity and specificity.

Inventive Principle:
Principle #1Segmentation

3Reliability

If documentation is updated dynamically to reflect API changes, then accuracy is improved, but system complexity increases

Engineering Contradiction:
Improvedocumentation accuracyVSAvoidsystem complexity for dynamic updates
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback by continuously monitoring API specification changes and automatically triggering documentation regeneration through the document generation engine. When APIs evolve or new APIs are released, the system detects these changes and feeds them back into the documentation generation process, ensuring accuracy while managing complexity through automated change detection and response mechanisms.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system manages dynamic updates by changing parameters such as API version identifiers, documentation templates, and code artifact references rather than restructuring the entire system. The document generation engine responds to parameter changes in API specifications by automatically adjusting the generated documentation, maintaining reliability while minimizing system complexity through parameter-based adaptability.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10761838B2Generating unified and dynamically updatable application programming interface documentation from different sources
Publication Date: 2020.09.01 DELL PROD LP
  • US10761838B2 patent drawing
  • US10761838B2 patent drawing
  • US10761838B2 patent drawing

AI summary

A method in one embodiment comprises generating a document corpus comprising a plurality of application programming interface electronic documents, wherein the plurality of application programming interface electronic documents are organized according to one or more application programming interface versions, receiving a query from one or more users seeking information corresponding to one or more application programming interfaces, generating a subset of the plurality of application programming interface electronic documents from the database in response to the query using one or more code artifacts, retrieving data corresponding to the one or more application programming interface versions, dynamically modifying one or more of the plurality of application programming interface electronic documents in the subset of the plurality of application programming interface electronic documents based on the retrieved application programming interface version data, and transmitting the subset of the plurality of application programming interface electronic documents to the one or more users.