EASILY QUERIABLE SOFTWARE REPOSITORIES
First Claim
1. In a repository environment, a method of providing entities the ability to optimally create, manage, and/or store fine-grained metadata, artifacts, or other software related items of a domain by providing a relational model that stores these items in a way that allows rich querying using standard database routines and other tools, the method comprising:
- providing entities with a set of schema guidelines that describe how software related items of a schematized model of a domain are to be categorized in query tables;
based on the set of schema guidelines, allowing the entities to arrange the software related items into a plurality of query tables that provide ease in querying over the software related items, wherein such items typically reside in a universal entity-property-value schema that is versioned on an object-by-object basis; and
storing the plurality of query tables in a software repository, which is a common store that allows tools that use the software related items to be independent of any particular domain model.
2 Assignments
0 Petitions
Accused Products
Abstract
In one embodiment, tables are created in such a way that allows rich querying using standard database routines and other tools. This is accomplished by providing developers and repository users with a set of schema guidelines that describe how the software related items are to be categorized in the tables and how to use such tables for rich querying. For example, one such guideline provides for course-grained versioning of items (e.g., artifacts, metadata, etc.)—as opposed to the fine grained object principle of unit change found in most repository systems such as the entity-property-value scheme. The developers or providers then use these guidelines to optimally categorize, in a natural way, their metadata and other software related items for storing copies thereof in the repository.
-
Citations
20 Claims
-
1. In a repository environment, a method of providing entities the ability to optimally create, manage, and/or store fine-grained metadata, artifacts, or other software related items of a domain by providing a relational model that stores these items in a way that allows rich querying using standard database routines and other tools, the method comprising:
-
providing entities with a set of schema guidelines that describe how software related items of a schematized model of a domain are to be categorized in query tables; based on the set of schema guidelines, allowing the entities to arrange the software related items into a plurality of query tables that provide ease in querying over the software related items, wherein such items typically reside in a universal entity-property-value schema that is versioned on an object-by-object basis; and storing the plurality of query tables in a software repository, which is a common store that allows tools that use the software related items to be independent of any particular domain model. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. In a repository, a method of optimally creating, managing, and/or storing fine-grained metadata, artifacts, or other software related items of a domain by providing a relational model that stores these items in a way that allows rich querying using standard database routines and other tools, the method comprising:
-
identifying a plurality of software related items of a schematized model of a domain; accessing a set of schema guidelines that describe how the software related items are to be categorized in query tables; based on the set of schema guidelines, arranging the software related items into a plurality of query tables that provide ease in querying over the software related items, wherein such software related items typically reside in a universal entity-property-value schema that is versioned on an object-by-object basis; and cataloging the plurality of query tables for storage in a software repository, which is a common store that allows tools that use the software related items to be independent of any particular domain model. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification