IP Library Patent Application 11253511
Patent Application
App. No. 11/253,511

Shared schema for software user interface designers and developers

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
11/253,511
Abstract

A method, an apparatus and a system provide a shared schema for software user interface designers and developers. In some embodiments, a system includes a machine-readable medium to store a set of validation rules that are based on rules derived from a designer and rules derived from a developer. The system also includes a validation logic to validate software code from the designer, wherein the validation logic is to validate a version of the software code modified by the developer.

Claims (35)

1 . A system including:

a machine-readable medium to store a set of validation rules that are based on rules derived from a designer and rules derived from a developer; and

a validation logic to validate software code from the designer, wherein the validation logic is to validate a version of the software code modified by the developer.

2 . The system of claim 1 , wherein the software code is for a Graphical User Interface.

3 . The system of claim 1 , wherein rules derived from the designer include a rule that limits a size, a location, or a color of a component of a Graphical User Interface (GUI).

4 . The system of claim 3 , wherein the component of the GUI includes a button, a menu or text.

5 . The system of claim 3 , wherein the rule that limits the size, the location or the color includes a rule that limits the size to a range of sizes.

6 . The system of claim 3 , wherein the rule that limits the size, the location or the color includes a rule that limits the location to less than all but more than one location relative to a number of other components of the GUI.

7 . The system of claim 1 , wherein the validation logic is to validate software code from designers across multiple and essentially independent software projects of a business entity.

8 . The system of claim 1 , wherein the validation logic is to validate software code from developers across multiple and essentially independent software projects of a business entity.

9 . A method including:

receiving software code for a user interface, the software code generated by a software user interface designer;

receiving a schema that includes one or more rules confirmed by the software user interface designer and a software developer;

validating the software code for the user interface based on the schema;

receiving a modified version of the software code that is the software code that has been modified by the software developer; and

validating the modified version of the software code based on the schema.

10 . The method of claim 9 , wherein the schema includes a rule that limits an attribute of a component of the user interface.

11 . The method of claim 10 , wherein the attribute includes a size, a location, or a color.

12 . The method of claim 11 , wherein the component includes a button, a menu or text on the user interface.

13 . The method of claim 11 , wherein the rule that limits the attribute of the component includes a rule that limits the size of the component to a range of sizes.

14 . The method of claim 11 , wherein the rule that limits the attribute of the component includes a rule that limits the color of the component to less than all but more than one color.

15 . The method of claim 9 , further including validating software code for user interfaces, based on the schema, from multiple software user interface designers across multiple and essentially independent software projects of a business entity.

16 . The method of claim 15 , further including validating modified versions of the software code, based on the schema, from software developers across multiple and essentially independent software projects of a business entity.

17 . A method including:

receiving software generated by a software user interface designer of a number of software user interface designers, wherein the number of software user interface designers are designing software for a number of software projects that are essentially independent; and

validating the software based on at least one rule agreed upon by the number of software user interface designers and a number software developers, wherein the number of software user interface designers are developing software for the number of software projects.

18 . The method of claim 17 , further including:

receiving an updated version of the software that has been updated by one of the number of software developers; and

validating the updated version of the software based on the at least one rule.

19 . The method of claim 17 , wherein receiving the software includes receiving software for a Graphical User Interface.

20 . The method of claim 17 , wherein the at least one rule includes a rule that limits an attribute of a component of a Graphical User Interface screen.

21 . The method of claim 20 , wherein the attribute includes a size, a location, or a color.

22 . The method of claim 21 , wherein the component includes a button, a menu or text on the Graphical User Interface screen.

23 . A machine-readable medium that provides instructions which, when executed by a machine, cause said machine to perform operations of claim 9 .

24 . A machine-readable medium that provides instructions which, when executed by a machine, cause said machine to perform operations of claim 17.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 23, 2015
From: EBAY INC.
To: PAYPAL, INC.
Reel/Frame 036163/0469 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 19, 2005
From: HO, YUAN DER; HOOVER, JAMIE; MAESEN, EDWARD; REFFELL, JAMES
To: EBAY INC.
Reel/Frame 017120/0275 →