Cookbook Framework for Software Development Process Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for representing and managing development processes are often haphazard, inflexible, and incomplete, failing to capture significant issues and stages, relying on intuitive assessments prone to institutional memory limitations and lacking a durable machine-readable record for quantitative analysis.

Innovation Solution

The development of a systematic approach using a 'cookbook' framework that provides structured task descriptions, including inputs, outputs, and instructions, organized by phases and tracks within a development process, allowing for flexible management and representation of development processes across various aspects, including evaluation, development, delivery, and maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If conventional systems use flowcharts with basic step classifications, then the representation is simple and easy to create, but the system is incomplete and fails to capture significant issues and stages

Engineering Contradiction:
Improvesimplicity of representationVSAvoidcompleteness of process representation
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent segments the development process into multiple standardized phases (initiation, planning, execution, monitoring, closing) with specific task types for each phase. This segmentation allows comprehensive coverage of all significant issues and stages while maintaining structured organization, resolving the contradiction between simplicity and completeness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces additional parameters and attributes to task descriptions beyond basic classifications, including inputs, outputs, dependencies, resources, and metrics. This parameter enrichment captures significant issues and stages comprehensively while maintaining a systematic framework that remains manageable and structured.

Inventive Principle:
Principle #35Parameter changes

2Ease of operation

If conventional systems rely on intuitive assessments and institutional memory, then the system is easy to operate, but the system is inflexible and subject to employee turnover and insufficient information exchange

Engineering Contradiction:
Improveease of useVSAvoiddurability of process record
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent creates durable machine-readable copies of process knowledge in standardized formats that can be stored, retrieved, and exchanged systematically. This copying approach preserves institutional memory externally, making it independent of employee turnover while maintaining ease of operation through standardized access methods.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent develops a universal framework that can represent various development processes across different contexts and organizations. This universal system enables consistent information exchange across departmental and site boundaries while remaining easy to operate through standardized procedures and formats.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Device complexity

If conventional systems provide only rudimentary classification of activities, then the system is simple to implement, but the system lacks the capability for quantitative data analysis

Engineering Contradiction:
Improvesimplicity of system implementationVSAvoidcapability for quantitative analysis
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent introduces quantitative parameters and metrics to task descriptions, including time estimates, resource requirements, dependency relationships, and performance measures. These additional parameters enable quantitative data analysis while maintaining a structured framework that remains systematic and manageable.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent adds dimensional depth to process representation by incorporating multiple attributes and parameters for each task, transforming the flat classification system into a multi-dimensional framework. This enables quantitative analysis capabilities while maintaining systematic organization through structured data models.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Device complexity

If conventional systems are directed only to specific kinds of development processes, then the system is focused and manageable, but the system lacks adaptability to diverse industries and customer needs

Engineering Contradiction:
Improvemanageability of systemVSAvoidadaptability to diverse needs
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal framework with standardized phases and task types that can be applied across diverse development processes in different industries. The system maintains manageability through consistent structure while achieving versatility through configurable parameters and customizable task selections within the standardized framework.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent enables dynamic adaptation of the standardized framework to specific needs through configurable parameters, optional task types, and customizable phase structures. This dynamic approach allows the system to maintain its manageable standardized core while adapting to diverse industries and customer requirements.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7810067B2Development processes representation and management
Publication Date: 2010.10.05 SAP SE
  • US7810067B2 patent drawing
  • US7810067B2 patent drawing
  • US7810067B2 patent drawing

AI summary

Systems and techniques to manage and represent development processes. In general, in one implementation, the technique includes a method for managing a software development process. The method includes providing a cookbook describing tasks in a framework of the development process and managing performance of the development process with the cookbook. A first task description identifies an activity in the development process, an input for performance of the activity, an output consequential of performance of the activity, and instructions for performance of the activity. Managing performance of the development process with the cookbook includes assigning activities in the development process to different participants in accordance with the activities identified in the task descriptions, exchanging information between participants in accordance with the inputs and outputs identified in the task descriptions, and instructing the participants in accordance with the instructions identified in the task descriptions.