# US 2008/0189235 A1 · User-interface architecture for manipulating business models

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0189235 A1
- Document ID: US20080189235A1
- Status: Published application
- Kind: A1
- Application number: 11/670,815
- Filed: 2007-02-02
- Published: 2008-08-07
- Earliest claimed: 2007-02-02
- Assignees: Microsoft Corporation
- Inventors: Vijay Mital; Andrew Robert Miller; Erik Jon Rucker
- Web page: https://patentgrep.com/patent/US20080189235A1

## CPC

- G06F 8/34: Graphical or visual programming
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present invention extends to methods, systems, and computer program products of user-interface architecture for manipulating business models. Embodiments of the invention facilitate efficient generation and extension of business related software applications, including commingled data-centric applications that represent both data elements and business logic in metadata. Modules of the user-interface architecture permit users to enter commands through common metaphors and wizards that abstract underlying (and more complex) modeling commands and data formats from users. The user-interface architecture can automatically search for existing models to provide and extend business related functionality.

## Claims

### Claim 1

At a computer system including user-interface architecture for manipulating commingled data-centric software applications, commingled data-centric software applications commingling data models for data stores with business logic models that include rules for interacting with data entities contained in the data stores, a method for creating a commingled data-centric application, the method comprising:
an act of the user-interface architecture receiving user-entered data commands for creating a data model including at least one or more data fields;
an act of the user-interface architecture receiving user-entered rule commands indicating a business logic rule is to be associated with one or more selected data fields among the one or more data fields;
an act of the user-interface architecture converting the user-entered rule command into a meta-data format that can be associated with the one or more selected data fields in a commingled data-centric application such that user-interface architecture abstracts the meta-data format from the user and thereby relieves the user from having to know the meta-data format; and
an act of the user-interface architecture associating the meta-data format of the business logic rule with the one or more selected data fields to commingle the data model with the business logic rule within a commingled data-centric application.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein the act of the user-interface architecture receiving user-entered data commands for creating a data model including one or more data fields comprises an act of user-entered data commands for creating a business related software application.

### Claim 3 (depends on 1)

The method as recited in claim 1, wherein the an act of the user-interface architecture receiving user-entered rule commands comprises an act of receiving user-entered rule commands indicative of a rule type selected from among data validation, data integrity, synchronized updates, data snapshots, audits and logs, form flow, user authorization, task flow, custom formatting, and conditional formatting.

### Claim 4 (depends on 1)

The method as recited in claim 1, wherein the act of the user-interface architecture receiving user-entered rule commands comprises an act of receiving one or more formulas having syntax supported by an existing spreadsheet and database applications.

### Claim 5 (depends on 1)

The method as recited in claim 1, wherein the act of the user-interface architecture receiving user-entered rule commands comprises an act of receiving a user-selected rule command from a wizard designed to assist users in entering rule commands.

### Claim 6 (depends on 1)

The method as recited in claim 1, wherein the act of the user-interface architecture converting the user-entered rule command into a meta-data format comprises an act of converting the user-entered rule command into a declarative macro.

### Claim 7 (depends on 1)

The method as recited in claim 1, wherein the act of the user-interface architecture associating the meta-data format of the business logic rule with the one or more selected data fields comprises an act of binding a declarative macro to one or more selected fields.

### Claim 8

At a computer system including a display device and a user-interface architecture for manipulating business related software applications, a method for creating a business related software application, the method comprising:
an act of the user-interface architecture receiving user-entered commands for creating a new model, including user-entered commands for at least creating one or more data fields;
an act of the searching existing models for any relevant models having at least a specified level of commonality with the one or more data fields;
an act of the user-interface architecture identifying one or more relevant models having at least the specified level of commonality with the one or more data fields;
an act of the user-interface architecture presenting a list of the identified one or more relevant models at the display device;
an act of the user-interface architecture receiving a user-entered selection selecting one of the relevant models; and
an act of the user-interface architecture automatically adding one or more additional fields from the selected relevant model to the new model to automatically provide the user with the functionality of an existing business related software application and thus relieve the user from having to manually create the functionality.

### Claim 9 (depends on 8)

The method as recited in claim 8, wherein the act of the user-interface architecture receiving user-entered commands for creating a new model comprises an act of receiving field or entity names or rule names for creating business logic rules.

### Claim 10 (depends on 9)

The method as recited in claim 9, wherein the act of searching existing models for any relevant models comprises an act of searching for models that have field names that match the received field names or for models that have business logic rules that match received business logic rule names.

### Claim 11 (depends on 9)

The method as recited in claim 9, wherein the act of the user-interface architecture identifying one or more relevant models comprises an act of identifying one or more relevant models that have field names that match the received field names or identifying one or more relevant models that have rule properties matching received rule names.

### Claim 12 (depends on 8)

The method as recited in claim 8, wherein the act of the user-interface architecture presenting a list of the identified one or more relevant models comprises an act of presenting a list of models, each model configured to provide different business related functionality.

### Claim 13 (depends on 8)

The method as recited in claim 8, wherein the act of user-interface architecture receiving a user-entered selection selecting one of the relevant models comprises an act of selecting a commingled data-centric application.

### Claim 14 (depends on 8)

The method as recited in claim 8, wherein the act of the user-interface architecture automatically adding one or more additional fields from the selected relevant model to the new model to automatically provide the user with the functionality of an existing business related software application comprises an act of adding functionality from a commingled data-centric application to the new model.

### Claim 15

At a computer system including a display device and a user-interface architecture for manipulating business related software applications, a method for extending a business related software application, the method comprising:
an act of the user-interface architecture accessing a current model for a business related software application, the model configured to provide a first business related function;
an act of the user-interface architecture receiving user-entered criteria indicative of a desire to extend the functionality of the business related software application by adding a further second business related function to the business related software application;
an act of the user-interface architecture automatically searching existing models for any relevant models having at least a specified level of commonality with the received criteria;
an act of the user-interface architecture identifying one or more relevant models having at least the specified level of commonality with the received criteria, the identified relevant models having an increased likelihood of being configured to provide the second business related function relative to other unidentified models accessible to the user-interface architecture;
an act of the user-interface architecture presenting a list of the identified one or more relevant models at the display device;
an act of the user-interface architecture receiving a user-entered selection selecting one of the relevant models;
an act of the user-interface architecture receiving a user-entered connection command indicating how the selected relevant model is to be connected to the current model to add the second business related function to the business related software application; and
an act of the user-interface architecture connecting the selected relevant model to the current model in accordance with the user-entered connection commands to add the second business related function to the business related software application.

### Claim 16 (depends on 15)

The method as recited in claim 15, wherein the user-interface architecture receiving user-entered criteria indicative of a desire to extend the functionality of the business related software application comprises an act of receiving search terms for searching existing models.

### Claim 17 (depends on 15)

The method as recited in claim 15, wherein the user-interface architecture receiving user-entered criteria indicative of a desire to extend the functionality of the business related software application comprises an act of ser-entered criteria indicative of a desire to extend the functionality of commingled data-centric application, the commingled data-centric application including one or more business logic rules.

### Claim 18 (depends on 15)

The method as recited in claim 15, wherein the act of the user-interface architecture identifying one or more relevant models having at least the specified level of commonality with the received criteria comprises an act of identifying one or more relevant models that have properties matching search terms that were received at the user-interface module.

### Claim 19 (depends on 15)

The method as recited in claim 15, wherein the act of the user-interface architecture receiving a user-entered connection command indicating how the selected relevant model is to be connected to the current model comprises an act of receiving a command indicating how to connect a first commingled data-centric application to a second commingled data-centric application.

### Claim 20 (depends on 15)

The method as recited in claim 15, wherein the act of the user-interface architecture connecting the selected relevant model to the current model in accordance with the user-entered connection commands comprises an act of connecting a first commingled data-centric application to a second commingled data-centric application.
