Scenario-Driven UI Effort Estimation System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for estimating effort and time required for accessibility design and development projects rely on ballpark approximations and past experiences, leading to inaccurate estimates, cost overruns, and delays due to the lack of visualization of the target system and reliance on expert opinions.

Innovation Solution

A scenario-driven method and system for standard-compliant user interface design and development that allows users to select and modify web components based on business requirements, storing workflows in a repository for effort estimation and generating reports across development stages, enabling more accurate effort estimation without the need for extensive visualization or expert involvement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If ballpark approximations and past experiences are used for effort estimation, then the estimation process is simple and quick, but the accuracy of the estimate deteriorates

Engineering Contradiction:
Improveestimation speedVSAvoidestimation accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The system performs preliminary actions by automatically generating UI prototypes and visualizing the target system during the estimation phase. This allows accurate effort estimation to be conducted before detailed design begins, eliminating the need for rough approximations while maintaining quick estimation through automation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces the mechanical system of manual expert assessment with an automated computer-based system that generates UI prototypes and calculates effort estimates algorithmically. This substitution maintains high productivity through automation while improving accuracy by eliminating human bias and inconsistency.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Device complexity

If expert opinions and past experiences are relied upon for estimation, then the estimation process requires minimal visualization, but the reliability of the estimate deteriorates due to lack of objective basis

Engineering Contradiction:
Improvevisualization requirementVSAvoidestimation reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system creates preliminary visual representations of the UI during the estimation phase itself, rather than requiring detailed visualization later. This preliminary action provides an objective basis for estimation while keeping the overall process relatively simple.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary automated system that acts as a mediator between requirements and effort estimation. This intermediary generates standardized UI prototypes and applies consistent estimation algorithms, providing objective reliability without requiring complex manual visualization processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If detailed UI screens are developed before estimation, then the estimation accuracy improves, but the time and cost required before project initiation increases

Engineering Contradiction:
Improveestimation accuracyVSAvoidpre-project development time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary UI prototyping and effort estimation in parallel during the early project phase, rather than sequentially. This allows accurate estimation to be achieved without requiring complete UI development beforehand, reducing time loss while maintaining precision.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies partial action by creating simplified but sufficient UI prototypes that are adequate for estimation purposes, rather than developing complete detailed screens. This partial prototyping provides enough information for accurate estimation while minimizing the time and resources required before project initiation.

Inventive Principle:
Principle #16Partial or excessive action

4Device complexity

If manual expert assessment is used for effort estimation, then the system complexity remains low, but the productivity of the estimation process deteriorates due to lack of automation

Engineering Contradiction:
Improvesystem complexityVSAvoidestimation productivity
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent replaces manual expert assessment with an automated computer-based system that generates UI prototypes and calculates effort estimates. This substitution dramatically improves productivity through automation while keeping system complexity manageable by using standardized algorithms and templates.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system performs self-service by automatically generating UI prototypes and calculating effort estimates without requiring manual intervention from experts. This automation improves productivity significantly while maintaining relatively low system complexity through rule-based algorithms.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9886168B2Method and system for scenario-driven standard-compliant user interface design and development for effort estimation
Publication Date: 2018.02.06 INFOSYS LTD
  • US9886168B2 patent drawing
  • US9886168B2 patent drawing
  • US9886168B2 patent drawing

AI summary

Embodiments of the present invention provide a method and system for scenario-based conceptualization and visualization of web-based user interface for effort estimation. The method includes providing user-selectable scenarios on said web-based user interface. A plurality of web components is provided on pre-populated screen to display existing number of screens, further user can modify the screen by adding new functionality based on business requirement. After modification, a workflow is stored in a repository for proposing it as pre-populated screen to new users. An effort is estimated by an effort estimation processor based on said modified user-selectable scenarios and compliance standard, and a report is generated for each stage of the development cycle.