Automated Defect Logging System for Software Development Lifecycle
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In complex large-scale software projects, manual defect logging in tracking systems often results in missed technical information and human errors due to numerous fields with long lists of valid values, leading to incomplete defect analysis.
Innovation Solution
A system and method for automatically creating and submitting defect information by identifying originating and assignment teams, collecting details from data sources, and generating descriptions for defect tickets, ensuring all mandatory fields are populated and presented in a user-selectable format.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual defect logging is used, then users can populate defect fields, but human errors occur and important technical information is missed
Solution Approach 1:
The defect tracking system automatically collects defect information from multiple data sources without requiring manual user input. The system self-populates defect tickets by retrieving data from version control systems, issue tracking systems, and other integrated sources, eliminating human errors while maintaining high reliability of defect information
Solution Approach 2:
The patent replaces the manual mechanical process of defect logging with an automated electronic system. Instead of users manually typing and populating defect fields, the system uses automated data collection, parsing, and population mechanisms to substitute the manual process, thereby eliminating human errors and improving information accuracy
2Loss of information
If many fields with long lists of valid values are required, then comprehensive defect tracking is achieved, but time spent on defect logging increases
Solution Approach 1:
The system performs preliminary actions by pre-configuring data sources, validation rules, and field mappings before defect logging occurs. Defect information is automatically collected and validated in advance, with default values pre-populated where applicable, significantly reducing the time required for actual defect logging while maintaining comprehensive defect details
Solution Approach 2:
The defect tracking system implements a universal data collection mechanism that automatically handles multiple field types and data sources through a single automated process. The system can populate various defect fields from different sources simultaneously, achieving comprehensive defect tracking without requiring separate manual operations for each field, thus reducing overall logging time
3Adaptability or versatility
If mandatory fields are not set up, then flexibility in defect logging is maintained, but important information is missing
Solution Approach 1:
The system implements feedback mechanisms where defect information completeness is automatically validated and verified. The automated collection process continuously checks for required information, and the system provides feedback loops to ensure all necessary defect details are captured, maintaining both flexibility and information completeness without requiring rigid mandatory field configurations
Data Source
AI summary
A system, method, and computer program product are provided for automatically creating and submitting defect information associated with defects identified during a software development lifecycle to a defect tracking system. In use, creation of a defect ticket is initiated for an identified defect for submission to a defect tracking system, the identified defect being identified during a software development life cycle. Additionally, a list of potential originating teams from which the identified defect was potentially identified is presented, the list of potential originating teams being presented in a user selectable format. Further, a list of teams in which to assign the identified defect is presented, the list of teams in which to assign the identified defect being presented in a user selectable format. Furthermore, a user selected originating team and a user selected team in which to assign the identified defect is identified. Additionally, details associated with the identified defect are collected from one or more data sources. Further, a description associated with the identified defect is generated utilizing the details associated with the identified defect. Moreover, the defect ticket is generated for the identified defect utilizing the identified user selected originating team, the identified user selected team in which to assign the identified defect, and the generated description associated with the identified defect.


