Feature Evolution Chronology Using Tagged Issue Closure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional collaboration tools for software development struggle with document proliferation, making it difficult to find relevant documents efficiently, leading to slowed searching processes and reduced motivation due to the burden of navigating through irrelevant results.
Innovation Solution
Applying design change tags and timestamps to issue tracking entries in a feature tracking tool at the time of closure, along with links to pertinent documentation, to construct a feature evolution chronology that allows users to easily access relevant documentation without keyword searches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional collaboration tools are used to share project information, then developers can electronically collaborate and share documents, but the proliferation of documents makes finding critical documents difficult and time-consuming
Solution Approach 1:
The patent segments the large collection of project documents into organized issue tracking entries, each representing a specific feature or bug. Documents are grouped by issue rather than being a flat proliferation, making them searchable and manageable. This segmentation allows developers to navigate to specific issues and their associated documents without searching through all project documents.
Solution Approach 2:
The patent introduces an intermediary system - the issue tracking tool - that sits between the document repository and the developer. This intermediary automatically links documents to issues, manages document organization, and provides structured access paths. The intermediary eliminates the need for developers to manually search through document proliferations by providing direct navigation to relevant documents through issue tracking.
2Measurement precision
If developers perform keyword searches to find documentation, then they can identify relevant documents, but the burden of navigating and reading through search results slows down the searching process
Solution Approach 1:
The patent applies preliminary action by pre-organizing documents into issue tracking entries before developers need to search. Documents are automatically associated with specific issues during the development process, and the system pre-computes the relationships between documents, issues, and features. When developers need information, the structured organization is already in place, eliminating the need for keyword searches and manual navigation through results.
3Quantity of substance
If all issue tracking entries are displayed, then complete tracking information is available, but the chronology becomes difficult to navigate and relevant design changes are hard to identify
Solution Approach 1:
The patent applies local quality by creating different views of the issue tracking data tailored to different user needs. The feature evolution chronology provides a filtered, time-ordered view showing only design change-related issues with documentation links, while the complete issue tracking database remains available for comprehensive searches. Each view has optimized qualities for its specific purpose: completeness for the full database, navigability for the chronology view.
Data Source
AI summary
Techniques are directed to managing feature evolution. Such techniques involve receiving closure commands to close issue tracking entries in an issue tracking tool constructed and arranged to track issues for a feature. Such techniques further involve, in response to the closure commands, applying design change tags and timestamps to the issue tracking entries in the issue tracking tool. The design change tags indicate whether the issue tracking entries identify design changes in the feature. Additionally, the timestamps indicate when the design change tags are applied to the issue tracking entries Such techniques further involve storing, in a repository, the design change tags and the timestamps applied to the issue tracking entries to enable construction of a feature evolution chronology from the design change tags and the timestamps.