Source Object Formatting via Component Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current software development tools are inadequate in accommodating global collaboration among developers who speak different languages and have varying preferences for formatting and viewing source objects, leading to challenges in maintaining software integrity and coordination across different locations and time zones.

Innovation Solution

A system and method that utilize a transformation engine to create a structural representation of source objects, applying rules for personalized formatting and viewing, including identifier tags for real-time component tracking, allowing developers to work on specific components while maintaining software integrity and enabling communication during collaborative development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If developers work on the same source object simultaneously from different locations, then collaboration efficiency is improved, but software integrity and coordination are compromised

Engineering Contradiction:

Improvecollaboration efficiencyVSAvoidsoftware integrity

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The source object is divided into multiple components, each with its own identifier tag. Developers can check out and work on specific components independently without affecting the entire source object, thus maintaining software integrity while enabling simultaneous collaboration.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system provides real-time feedback to developers about which components are currently checked out by whom. This feedback mechanism allows developers to coordinate their work and avoid conflicts, maintaining software integrity while enabling continuous collaboration.

Inventive Principle:

Principle #23Feedback

2Ease of operation

If developers use different formatting preferences for source objects, then ease of operation is improved, but consistency and coordination are worsened

Engineering Contradiction:

Improveformatting preference flexibilityVSAvoidsource object consistency

Core Design Contradiction:

Ease of operationVSStability of the object's composition

Solution Approach 1:

The system applies different formatting rules locally to different portions of the source object based on each developer's preferences. Each developer can view and edit components with their preferred formatting while the underlying source object structure remains consistent and unchanged.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system creates a formatted copy of the source object that reflects the developer's personal preferences. This copy is used for viewing and editing, while the original source object remains unchanged, ensuring consistency across all developers' work.

Inventive Principle:

Principle #26Copying

3Manufacturing precision

If the entire source object is checked out for modification, then modification completeness is improved, but collaboration efficiency is worsened

Engineering Contradiction:

Improvemodification completenessVSAvoidcollaboration efficiency

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The source object is segmented into components with unique identifier tags. Developers can check out only the specific components they need to modify rather than the entire source object, enabling partial modifications while maintaining collaboration efficiency.

Inventive Principle:

Principle #1Segmentation

4Ease of operation

If formatting rules are applied to personalize source object display, then ease of operation is improved, but system complexity is worsened

Engineering Contradiction:

Improvepersonalized viewingVSAvoidformatting rule management

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system uses a universal set of formatting rules that can be applied to any component of the source object. These rules are stored in a rules module and can be selectively applied based on the component type and developer preferences, simplifying the management of formatting complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS7877731B2Formatting and viewing source objects

Publication Date: 2011.01.25 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A system, method, and computer readable storage medium for formatting and viewing a source object that allows software developers to select their own preferences for formatting and/or viewing the same source object.