Mock-up Test Script Creation for Parallel Software Development
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The traditional sequential approach to software application development and testing prolongs the life cycle of an application, as testing typically begins only after development is complete, leading to increased time and resource allocation.
Innovation Solution
Concurrent creation of a mock-up test script and application development using a mock-up GUI that mirrors the actual GUI but lacks functional logic, allowing for parallel testing and development stages, thereby shortening the application life cycle.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If testing is performed sequentially after development is complete, then testing can be thorough and comprehensive, but the application life cycle is prolonged and time to market is delayed
Solution Approach 1:
The patent applies preliminary action by creating a mock-up GUI and test scripts during the development phase before the actual application is complete. This allows testing activities to begin early in the lifecycle rather than waiting for development completion, thereby reducing overall time while maintaining testing effectiveness through iterative refinement.
Solution Approach 2:
The patent segments the testing process into multiple phases: initial testing with mock-up GUI, intermediate testing with partial application functionality, and final testing with complete application. This segmentation allows testing to occur concurrently with development at different stages rather than as a single sequential phase, reducing total lifecycle time while ensuring thoroughness.
2Ease of manufacture
If testing begins only after development is complete, then resource allocation is simplified, but time and resources are increased due to sequential processing
Solution Approach 1:
The mock-up GUI and test scripts are created preliminarily during development, enabling parallel resource utilization. Development resources work on the actual application while testing resources work with the mock-up, maximizing productivity without complicating resource allocation through automated mock-up generation.
Solution Approach 2:
The patent creates a copy (mock-up GUI) that mimics the structure and interface of the final application without requiring full functionality. This copy enables testing activities to proceed in parallel with development, improving productivity while keeping resource allocation manageable through automated generation and synchronization mechanisms.
3Loss of time
If a mock-up GUI is created for parallel testing, then the application life cycle is shortened, but additional complexity is introduced in managing mock-up and actual GUI synchronization
Solution Approach 1:
The mock-up GUI is created preliminarily with automated generation from development specifications, reducing manual management complexity. The system automatically synchronizes the mock-up with the actual application as development progresses, minimizing the burden of maintaining parallel structures while achieving lifecycle reduction.
Solution Approach 2:
The patent implements feedback mechanisms where the system automatically detects changes in the actual application and updates the mock-up GUI accordingly. This feedback loop maintains synchronization between mock-up and actual GUI without requiring manual intervention, reducing management complexity despite the added structural element.
4Loss of time
If testing is performed in parallel with development, then time is reduced, but the ability to perform comprehensive testing may be compromised
Solution Approach 1:
The testing process is segmented into phases that evolve with development: initial structural testing with mock-up GUI, functional testing as components are completed, and integration testing with the full application. This segmentation ensures comprehensive testing coverage is achieved progressively without extending the overall timeline, as each phase builds on previous work.
Solution Approach 2:
Testing activities are performed preliminarily with the mock-up GUI to validate design and structure before full implementation. This preliminary testing identifies issues early when they are easier and faster to resolve, ensuring comprehensive coverage is achieved efficiently through iterative refinement rather than requiring all testing to occur simultaneously with complete functionality.
Data Source
AI summary
The life cycle of an application can be shortened by initiating the creation of a mock-up test script before the development of an application is complete. The concurrent creation of the mock-up test script and the application can reduce a time associated with the life cycle of an application. Mock-up test script creation is based on the user interface (UI) specification and a mock-up graphical user interface (GUI) without business logic. Test script creation can include associating a functional specification and a UI specification with a proposed application and creating a mock-up GUI for testing based on the UI specification. Test script creation can include developing an application based on the proposed application that includes a logic based on the functional specification and a GUI based on the UI specification and creating a mock-up test script based on the mock-up GUI and not based on the logic, the functional specification, and the GUI.