A method,
system and program product 100
usable by domain developers having any experience level in creating domain models. A representation of
domain model knowledge is derived from
a domain specification. The domain specification includes multiple potential domain objects, e.g., tables of APIs functional arguments, and each of the potential domain objects include one or more attributes. Potential domain objects are selected one at a time 102 from the specification and offered to the developer. The developer decides 104 whether or not to include the potential domain object in the
domain model. If the developer decides to include the potential domain object 106, then the
system provides a default name 108, i.e., the table name or argument name, and allows the developer to
rename the selected domain object 110. Then, after having selected the object, potential attributes 112, e.g., table columns 1122, are selected from the object and offered to the developer 116. If the developer decides to include a potential attribute, then a default name, i.e., the column name or name extracted from an API function, is offered 1126 for the selected attribute and the developer is allowed to
rename attributes 1128. Once all the potential domain objects have been offered 118 to the developer and the developer has either decided to include the potential objects or not, the
system checks the
domain model for nesting structure 200. If domain objects include attributes that are shared with other domain objects 2006, then those domain objects may be reorganized such that some domain objects include instances of identically named attributes from other domain objects.