Patent US6091893A successfully refreshed from Google Patents.
US6091893A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method for performing operations on informational objects by visually applying the processes defined in utility objects in an IT (information technology) architecture visual model
Assignee: Square 1 Bank
•
Filing: 1997-03-10
•
Granted: 2000-07-18
•
Expires: 2017-03-10
Abstract
Abstract A computer implemented method of building an architecture visual model is disclosed. A plurality of architecture visual components are created each having a container. Each container includes a plurality of objects. Each of the objects are of a particular type. Each type of object has operations associated therewith for intra-container relationships and inter-container relationships. Each object is linked to at least another object in the same or another container and each object inherits properties from linked objects depending upon the operations associated with the linked objects. At least a portion of the architecture visual model is displayed which includes visual objects and linkages.
Inventors
- 👤 Robert P. Fintel
- 👤 Julian C. Hope
- 👤 Dag Karlsen
- 👤 Laila Rabe Osnes
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-01 03:45
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/30; G06F8/34; G06F9/00; G06F9/06; G06F9/44; G06F9/451
Claims Analysis
Total Claims: 25
Claim 1
Independent Claim
147 words
A computer implemented method of building an architecture visual model to be used as a business strategy model, comprising: creating a plurality of architectural visual components each having a container, each container including a plurality of objects, wherein the plurality of architectual visual components include a business alignment component, an information technology architecture component, a transition planning component and an architecture management component; each of the objects being of a particular type, each type having operations associated therewith for intra-container relationships and inter-container relationships, each object being linked to at least another object in the same or another container and each object inheriting properties from linked objects depending upon the operations associated with the linked objects; and visually displaying at least a portion of the architectural visual model including visual objects and linkages wherein the architectural visual model is to be used as a business strategy model.
Claim 2
Dependent Claim
147 words
A computer implemented method of building an architecture visual model to be used as a business strategy model, comprising: creating a plurality of architectural visual components each having a container, each container including a plurality of objects, wherein the plurality of architectual visual components include a business alignment component, an information technology architecture component, a transition planning component and an architecture management component; each of the objects being of a particular type, each type having operations associated therewith for intra-container relationships and inter-container relationships, each object being linked to at least another object in the same or another container and each object inheriting properties from linked objects depending upon the operations associated with the linked objects; and visually displaying at least a portion of the architectural visual model including visual objects and linkages wherein the architectural visual model is to be used as a business strategy model.
Claim 3
Dependent Claim
48 words
The method of claim 1, wherein the type of objects in the business alignment container can include a business question type, a business requirement type, a CSF type environmental factor type, a goal type, an objective type, a strategy type, a success factor type, and a vision type.
Claim 4
Dependent Claim
95 words
The method of claim 2, wherein the operations for each object for the business alignment container can include a create object operation, a create feature operation, a create and associate object operation, a create modeling container operation, a create utility container operation, an associate using list box operation, an associate using select operation, an edit operation, a modify structure operation, a navigate operation, an analyse operation, an attribute group on current operation, an attribute group on selected operation, attribute group on type operation, an export content operation, an import content operation and a utility operation.
Claim 5
Dependent Claim
34 words
The method of claim 3, wherein the objective type objects can be intra-container linked to the strategy type object, the business question type object, the environmental factor type object and the goal type object.
Claim 6
Dependent Claim
43 words
The method of claim 1, wherein the type of objects in the information technology architecture container can include a business s/w sub-model type, a conceptual network type, a conceptual network type, a functional technology layer type, an IT-system type, and a location type.
Claim 7
Dependent Claim
93 words
The method of claim 5, wherein the operations for each object in the information technology architecture can include a create object operation, a create feature operation, a create modeling container operation, a create utility container operation, an associate using list box operation, an associate using select operation, an edit operation, a modify structure operation, a navigate operation, a view operation, an analyse operation, an attribute group on current operation, an attribute group on selected operation, an attribute group on type operation, an export content operation, an import content operation and a layout operation.
Claim 8
Dependent Claim
29 words
The method of claim 6, wherein the wide-area network type object can be linked to the IT-system type object, the conceptual network type object and the location type object.
Claim 9
Dependent Claim
26 words
The method of claim 1, wherein the types of objects in the transition planning container include a transition milestone type and a transition planning initiative type.
Claim 10
Dependent Claim
21 words
The method of claim 8, wherein the operations for each object in the transition planning container include a transition planning initiative.
Claim 11
Dependent Claim
29 words
The method of claim 1, wherein the type of objects in the architecture management container includes an AMP issue/barrier, an AMP milestone, an AMP process and an AMP rationale.
Claim 12
Dependent Claim
101 words
The method of claim 10, wherein the operations for each object for the architecture management container include a create object type, a create feature type, a decompose object type, a create and associate object type, a create modeling container type, a create utility container type, an associate using list box type, an associate using select type, an edit type, a modify structure type, a navigate type, a view type, an analyse type, an attribute group on current type, an attribute group on selected type, an attribute group on type, an export content type, an import content type and a layout type.
Claim 13
Dependent Claim
12 words
The method of claim 1, wherein each of the linkages is weighted.
Claim 14
Dependent Claim
170 words
A computer implemented method of building an architecture visual model to be used as a business strategy model, comprising: creating a business alignment container, an information technology container, a transition planning container and an architecture management container; establishing a plurality of objects within each container, each object being of a particular type and having operations associated therewith for intra-container relationships and inter-container relationships, each object being linked to at least another object in the same or another container and each object inheriting properties from linked objects depending upon the operations associated with the linked objects and wherein the type of objects in the business alignment container can include a business question type, a business requirement type, a CSF type environmental factor type, a goal type, an objective type, a strategy type, a success factor type, and a vision type; and visually displaying at least a portion of the architectural visual model including visual objects and linkages wherein the architectural visual model is to be used as a business strategy model.
Claim 15
Dependent Claim
170 words
A computer implemented method of building an architecture visual model to be used as a business strategy model, comprising: creating a business alignment container, an information technology container, a transition planning container and an architecture management container; establishing a plurality of objects within each container, each object being of a particular type and having operations associated therewith for intra-container relationships and inter-container relationships, each object being linked to at least another object in the same or another container and each object inheriting properties from linked objects depending upon the operations associated with the linked objects and wherein the type of objects in the business alignment container can include a business question type, a business requirement type, a CSF type environmental factor type, a goal type, an objective type, a strategy type, a success factor type, and a vision type; and visually displaying at least a portion of the architectural visual model including visual objects and linkages wherein the architectural visual model is to be used as a business strategy model.
Claim 16
Dependent Claim
95 words
The method of claim 13, wherein the operations for each object for the business alignment container can include a create object operation, a create feature operation, a create and associate object operation, a create modeling container operation, a create utility container operation, an associate using list box operation, an associate using select operation, an edit operation, a modify structure operation, a navigate operation, an analyse operation, an attribute group on current operation, an attribute group on selected operation, attribute group on type operation, an export content operation, an import content operation and a utility operation.
Claim 17
Dependent Claim
34 words
The method of claim 14, wherein the objective type objects can be intra-container linked to the strategy type object, the business question type object, the environmental factor type object and the goal type object.
Claim 18
Dependent Claim
43 words
The method of claim 13, wherein the type of objects in the information technology architecture container can include a business s/w sub-model type, a conceptual network type, a conceptual network type, a functional technology layer type, an IT-system type, and a location type.
Claim 19
Dependent Claim
93 words
The method of claim 16, wherein the operations for each object in the information technology architecture can include a create object operation, a create feature operation, a create modeling container operation, a create utility container operation, an associate using list box operation, an associate using select operation, an edit operation, a modify structure operation, a navigate operation, a view operation, an analyse operation, an attribute group on current operation, an attribute group on selected operation, an attribute group on type operation, an export content operation, an import content operation and a layout operation.
Claim 20
Dependent Claim
29 words
The method of claim 17, wherein the wide-area network type object can be linked to the IT-system type object, the conceptual network type object and the location type object.
Claim 21
Dependent Claim
26 words
The method of claim 13, wherein the types of objects in the transition planning container include a transition milestone type and a transition planning initiative type.
Claim 22
Dependent Claim
21 words
The method of claim 19, wherein the operations for each object in the transition planning container include a transition planning initiative.
Claim 23
Dependent Claim
29 words
The method of claim 13, wherein the type of objects in the architecture management container includes an AMP issue/barrier, an AMP milestone, an AMP process and an AMP rationale.
Claim 24
Dependent Claim
101 words
The method of claim 21, wherein the operations for each object for the architecture management container include a create object type, a create feature type, a decompose object type, a create and associate object type, a create modeling container type, a create utility container type, an associate using list box type, an associate using select type, an edit type, a modify structure type, a navigate type, a view type, an analyse type, an attribute group on current type, an attribute group on selected type, an attribute group on type, an export content type, an import content type and a layout type.
Claim 25
Dependent Claim
12 words
The method of claim 13, wherein each of the linkages is weighted.
References Cited (Backward Citations)
US5481740A
Cited
US4914568A
Cited
US5019961A
Cited
US5790116A
Cited
US5727175A
Cited
US5355472A
Cited
US5740444A
Cited
US5432903A
Cited
US5528735A
Cited
US5603025A
Cited
US5671427A
Cited
US5694594A
Cited
US5752245A
Cited
US5535325A
Cited
US5838973A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-07-18 | 2004-01-17 | 2004-07-18 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-07-18 | 2008-01-17 | 2008-07-18 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-07-18 | 2012-01-17 | 2012-07-18 | $7700.00 | Window Closed / Lapsed |