Software Requirements Recording via User Interaction Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The software development process faces challenges in generating complete requirements due to the complexity of software being developed and interdisciplinary communication issues among stakeholders, leading to costly errors if errors occur in the requirements phase.
Innovation Solution
A software development system that records user interactions with an existing software product to generate requirements for a new product, using a user-action recorder and requirements editor to create an action list and define requirements based on concrete representations, thereby simplifying the process and minimizing perspective and terminology differences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If requirements are generated from scratch through interdisciplinary communication, then the requirements can be tailored to specific needs, but the process becomes complex and error-prone due to communication challenges among stakeholders
Solution Approach 1:
The patent copies requirements from an existing software product by recording user interactions with the old product. The user-action recorder captures actual usage patterns, and the requirement editor extracts requirements from these recordings, eliminating the need for complex interdisciplinary communication while maintaining requirements relevance to specific needs.
Solution Approach 2:
The existing software product serves itself by having its own usage data recorded and converted into requirements. The system uses the product's actual operation data to generate requirements for the new product, making the process self-sufficient without requiring extensive external communication.
2Reliability
If complete requirements are generated through thorough analysis, then requirement completeness improves, but the time and resources required increase significantly
Solution Approach 1:
The system performs preliminary action by recording user interactions with the existing software product before generating requirements. This recording phase captures all necessary usage data in advance, and the requirement editor then efficiently extracts requirements from this pre-collected data, reducing overall time requirements.
Solution Approach 2:
The patent replaces the mechanical process of manual requirement gathering through communication and analysis with an automated system that records user interactions and electronically extracts requirements. This substitution dramatically reduces time and resource requirements while maintaining completeness.
3Measurement precision
If requirements are derived from concrete user interactions with existing software, then accuracy and completeness improve, but the system complexity increases due to recording and processing mechanisms
Solution Approach 1:
The patent introduces an intermediary approach by using a user-action recorder as a mediator between user interactions and requirement generation. The recorder captures concrete interaction data, and the requirement editor acts as another intermediary to translate this data into requirements, improving accuracy while managing system complexity through modular design.
Data Source
AI summary
User interactions with an existing software product are recorded so as to generate a list of actions performed by or triggered by the interaction. The list of actions is then used to generate requirements for a new software product under development.