Project Schedule Management via Automated Query Templates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current project schedule management systems are cumbersome and error-prone, requiring manual data entry and lack oversight, especially in large-scale software development projects, where complex interdependencies and subjective progress reports complicate the management of master project schedules.

Innovation Solution

A client-server based project schedule management system that generates and executes client-executable code for displaying and managing schedule-related information, using PHP scripts on the server and JavaScript on the client, automating database query generation and task management through class objects that manipulate attributes directly, facilitating centralized control and uniformity across schedules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual data entry and manual aggregation of schedules is used, then flexibility in individual schedule creation is maintained, but error rate increases and time consumption increases

Engineering Contradiction:
Improveerror rateVSAvoidmanual data entry
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The system enables self-service through automated database query generation from editor constant strings. The PHP processor automatically retrieves schedule data without manual intervention, eliminating errors associated with manual data entry while maintaining system flexibility.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-defining editor constant strings that contain database query templates. These templates are prepared in advance with placeholder strings, allowing automated query generation when editors are accessed, thus eliminating the need for manual query construction and reducing errors.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If manual aggregation of individual schedules into master project schedule is performed, then adaptability to individual developer needs is preserved, but productivity decreases and time consumption increases

Engineering Contradiction:
Improveschedule aggregation efficiencyVSAvoidtime for consolidating schedules
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system replaces the mechanical manual aggregation process with automated computer-based operations. The PHP processor automatically consolidates individual developer schedules into the master project schedule by executing database queries and merging data, dramatically improving productivity while reducing the time required for schedule consolidation.

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

Solution Approach 2:

The system introduces an intermediary PHP processor that acts as a mediator between individual developer schedules and the master project schedule. This intermediary automatically retrieves, processes, and consolidates schedule data from multiple sources, eliminating the need for manual aggregation while maintaining data integrity and uniformity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If subjective progress reports by individuals are accepted without oversight, then ease of operation is improved, but measurement precision of actual project status deteriorates

Engineering Contradiction:
Improveaccuracy of project statusVSAvoidsimplicity of progress reporting
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The system implements feedback mechanisms where progress data entered by developers is automatically retrieved, consolidated, and reflected in the master project schedule. This automated feedback loop provides oversight while maintaining ease of operation, as developers simply enter their progress data and the system automatically processes and validates it against the overall project schedule.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The PHP processor serves as an intermediary that objectively processes and validates progress reports from individual developers. It automatically retrieves the data, compares it against project requirements, and consolidates it into the master schedule, providing measurement precision without complicating the reporting process for developers.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of information

If HTML editors are used for schedule creation without automated query generation, then ease of manufacture is improved, but loss of information increases due to manual aggregation errors

Engineering Contradiction:
Improvedata accuracy during aggregationVSAvoidsimplicity of schedule creation
Core Design Contradiction:
Loss of informationVSEase of manufacture

Solution Approach 1:

The system performs preliminary action by pre-defining database query templates within editor constant strings. These templates contain the structure and logic for data retrieval, ensuring that when editors are accessed, accurate and complete information is automatically retrieved and consolidated, preventing data loss while maintaining ease of schedule creation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system replaces manual information aggregation with automated database query execution. The PHP processor automatically retrieves data using pre-defined query templates, eliminating manual copying and pasting operations that cause information loss, while preserving the simplicity of using HTML editors for schedule creation and modification.

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

Data Source

PatentUS8826282B2Project task management system for managing project schedules over a network
Publication Date: 2014.09.02 RICOH CO LTD
  • US8826282B2 patent drawing
  • US8826282B2 patent drawing
  • US8826282B2 patent drawing

AI summary

A client-server based project schedule management system comprises multiple editors accessible through a web browser to perform various scheduling tasks by members of a project. Client-executable code is generated by the server for the client, which is passed to the client along with schedule-related information for populating the respective editors. The client executes the server-generated code to display the respective editor with pertinent information populated therein, and to manage and maintain any new or updated information in response to user interactions with the editor. Rows of tasks are represented by corresponding objects, where editor elements are object attributes which are directly accessible by the respective objects. Database queries are generated by the server based on constant strings containing placeholders which are replaced with information used by the query.