Framework for domain-independent archetype modeling

• US 20030128214A1
• Filed: 09/12/2002
• Published: 07/10/2003
• Est. Priority Date: 09/14/2001
• Status: Abandoned Application

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Schloegel, Kirk, Oglesby, David, Bhatt, Devesh, Engstrom, Eric
• Application Number:
  US10/242,201
• Publication Number:
  US 20030128214A1
• Time in Patent Office: Days
• US Class Current: 345/473
• CPC Class Codes: G06T 17/00 Three dimensional [3D] modelling, e.g. data description of 3D objects

Abstract

A framework provides for the creation, use, and management of archetypes as a basic building block for graphical model-based development environments. Archetypes are user-definable, domain-independent modeling entities that can contain one or more domain-specific models as well as archetype-specific operations, such as code generation. Archetypes may contain portals that are the explicit application programming interfaces of archetypes. Users define archetype definitions (including visual representations, portals, implementations, and operations) and they or others can then instantiate instances of defined archetypes into different modeling notations. The semantic interpretation of the archetype instances via archetype- and implementation-specific operations provide support for high-level operations such as code generation, model transformations, and model analyses.

Claims

1. A framework for use of archetypes for graphical model-based development environments, the framework comprising:

a plurality of archetype definitions;

a plurality of implementations for each archetype definition; and

a plurality of domain-independent archetype instance modeling entities derived from each archetype definition.

2. The framework of claim 1 wherein an archetype is a representation of a solution to a problem in a context.

3. The framework of claim 2 wherein selected archetype definitions have user-defined attributes.

4. The framework of claim 3 wherein selected archetype definitions have user-defined operations.

5. The framework of claim 4 wherein an archetype instance is adapted by the values of its attributes to reference a specific implementation.

6. The framework of claim 5 and further comprising portals that are application programming interfaces to archetypes.

7. The framework of claim 6 wherein an archetype instance is a node or arc on a graph having internal details accessible through the portals.

8. The framework of claim 7 wherein selected portals have user-defined attributes.

9. The framework of claim 8 wherein portal attribute values may be derived from other portals or modeling entities.

10. The framework of claim 9 wherein selected archetype instances are components of domain-specific modeling entities.

11. The framework of claim 1 wherein the archetypes support domain-level reuse by archetype instantiation.

12. The framework of claim 1 wherein implementations are comprised of sets of subdiagrams.

13. The framework of claim 12 wherein the implementation may have userdefined attributes and operations.

14. The framework of claim 13 wherein the sets of subdiagrams, operations, and attributes may overlap between implementations.

15. The framework of claim 14 wherein the implementation is adapted by the values of its attributes.

16. The framework of claim 15 and further wherein multiple archetype instances may reference the same implementation.

17. The framework of claim 16 wherein changes in an implementation affect all instances that reference the implementation.

18. The framework of claim 14 wherein the subdiagram is a domain specific model.

19. The framework of claim 18 and further wherein subdiagrams contain portals that correspond to a user-definable subset of the portals that are defined on its archetype definition.

20. The framework of claim 18 wherein a subdiagram is a domain specific visual representation of an aspect of a system or solution.

21. A framework for use of archetypes for graphical model-based development environments, the framework comprising:

means for representing archetype definitions;

means for providing a plurality of implementations of each archetype definition; and

means for providing a plurality of domain-independent archetype instance modeling entities for each archetype definition.

22. The framework of claim 21 and further comprising means for deriving archetype instances from archetype definitions.

23. The framework of claim 22 and further comprising portals acting as application programming interfaces to archetypes.

24. The framework of claim 23 wherein an archetype is a node or arc on a graph having internal details accessible through the portals.

25. The framework of claim 21 and further comprising a subdiagram of an implementation that is a domain specific visual representation of an aspect of a system or solution.

26. A method of programming comprising:

developing one or more archetype definitions;

instantiating one or more archetypes in one or more models;

generating source code from the models.

27. The method of claim 26 wherein at least one archetype instance contains a portal.

28. The method of claim 27 wherein at least one portal is connected to a native modeling entity or another portal by an arc.

29. The method of claim 28 wherein at least one portal or archetype instance has user-defined attributes.

30. The method of claim 29 wherein at least one attribute value is set.

31. The method of claim 30 wherein the result of the generated code is determined by the values of the set and unset attributes.

32. A method of programming related to a problem context, the method comprising:

representing archetypes by graphic images;

implementing a plurality of context-relevant archetype definitions; and

providing a plurality of context relevant subdiagrams, operations, and attributes for each archetype implementation.

33. The method of claim 32 and further comprising:

instantiating one or more archetypes in one or more models;

generating source code from the model.

34. A method of creating a model for programming in a domain, the method comprising:

creating archetype definitions;

providing visual representations of the archetypes;

creating instances of archetypes having domain specific implementations; and

providing portals on the archetypes and archetype instances to access implementations while hiding complexity.