IP Library Granted Patent US 9,317,640
Granted Patent B2
US 9,317,640 · App. 12/122,425 · Granted Apr 19, 2016

System and method for the electronic design of collaborative and validated architectures

View Patent ↗
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 9,317,640
App. No.
12/122,425
Granted
Apr 19, 2016
Kind
B2
Abstract

One aspect of the invention is a method for the electronic design of collaborative and validated architectures. The method for the electronic design of an architecture includes storing architecture elements created by users in a centralized database. The creation of an architecture model is initiated in response to a request of a user of a client system. The centralized database is accessed to retrieve the architecture elements and a selection of an architecture element for inclusion in the architecture model is received from the user. The architecture model including the selected architecture element is included in the centralized database.

Claims (83)

1. A method for electronic design of an architecture, comprising:

storing a plurality of architecture elements created by a plurality of users in a centralized database;

initiating creation of a first architecture model in response to a request of a first user of a first client system;

accessing, by at least one computer, the centralized database to retrieve the plurality of architecture elements and a plurality of architecture stacks that include a physical stack having a hardware element and a software element, and a process stack that includes a grouping of processes;

receiving, by the at least one computer, a selection from the first user of at least one architecture element and at least one of the architecture stacks for inclusion in the first architecture model; and

storing, by the at least one computer, the first architecture model comprising the at least one selected architecture element and the at least one architecture stack in the centralized database.

2. The method of claim 1 , wherein initiating the creation of the first architecture model comprises presenting a template to the first user.

3. The method of claim 1 , wherein initiating the creation of the first architecture model comprises presenting a plurality of layers to the first user, each layer comprising a logical sub-group of architecture elements selected by the first user.

4. The method of claim 3 , further comprising:

receiving a user selection of a selected one of the plurality of layers; and

presenting, to the first user, a listing of architecture elements that are suitable for inclusion in the selected one of the plurality of layers.

5. The method of claim 1 , wherein storing the first architecture model in the centralized database comprises:

storing the first architecture model as a whole; and

storing the architecture elements making up the first architecture model individually.

6. The method of claim 1 , wherein each of the architecture stacks comprises a logical grouping of architecture elements related to one another by a logical function.

7. The method of claim 6 , wherein each architecture element in an architecture stack is dependent on at least one other architecture element in the architecture stack.

8. The method of claim 6 , wherein at least one of the plurality of architecture stacks includes an embedded architecture stack, the embedded architecture stack comprising a logical sub-grouping of architecture elements.

9. The method of claim 1 , further comprising:

at the request of a second user, accessing the first architecture model stored in the centralized database; and

allowing the second user to modify the first architecture model.

10. The method of claim 1 , further comprising:

at the request of a second user, accessing the first architecture model stored in the centralized database;

creating a mirror copy of the first architecture model; and

allowing the second user to modify the mirror copy of the first architecture model.

11. The method of claim 1 , further comprising:

receiving selection of a grouping of architecture elements from the first user; and

saving the grouping of architecture elements as one of the architecture stacks in the centralized database.

12. The method of claim 1 , further comprising:

determining if the first architecture model is compliant with one or more technical rules; and

validating the first architecture model if the first architecture model is compliant with the one or more technical rules.

13. The method of claim 1 , wherein storing the first architecture model in the centralized database comprises:

storing the first architecture model with a status identifying the first architecture model as a draft;

receiving approval of the first architecture model from a reviewer; and

changing the status of the first architecture model to a production status.

14. The method of claim 1 , wherein after accessing the centralized database to retrieve the plurality of architecture elements, the method further comprises:

filtering the plurality of architectural elements based on a type of the first architecture model; and

presenting, based on the filtering, only the architectural elements that are suitable for the type of the first architecture model.

15. The method of claim 1 , further comprising linking the first architecture model with one or more stored business rules or technical requirements.

16. The method of claim 1 , further comprising linking the first architecture model with a second architecture model.

17. The method of claim 16 , wherein the linking is performed by providing an integration stack bridging the first and second architecture models, where the integration stack contains components that tie together parts of the first and second architecture models.

18. The method of claim 1 , wherein the architecture stacks further include a logical stack that includes a grouping of logical components.

19. A system for electronic design of collaborative and validated architectures, comprising:

a centralized database storing a plurality of architecture elements created by a plurality of users;

a network to couple the centralized database to a plurality of client systems; and

an architecture creator system including a computer and coupled to the network and operable to access the centralized database via the network, the architecture creator system to:

initiate creation of a first architecture model in response to a request of a first user of a first client system;

access the centralized database to retrieve the plurality of architecture elements and a plurality of architecture stacks that include a physical stack having a hardware element and a software element, and a process stack that includes a grouping of processes;

receive a selection from the first user of at least one architecture element and at least one of the architectural stacks for inclusion in the first architecture model; and

store the first architecture model comprising the at least one selected architecture element and the at least one architectural stack in the centralized database.

20. The system of claim 19 , wherein the architecture creator system is to initiate the creation of the first architecture model by presenting a template to the first user.

21. The system of claim 19 , wherein the architecture creator system is to initiate the creation of the first architecture model by presenting a plurality of layers to the first user, each layer comprising a logical sub-group of architecture elements selected by the first user.

22. The system of claim 21 , wherein the architecture creator system is to:

receive a user selection of a selected one of the plurality of layers; and

present, to the first user, a listing of architecture elements that are suitable for inclusion in the selected one of the plurality of layers.

23. The system of claim 19 , wherein when storing the first architecture model in the centralized database, the architecture creator system is to:

store the first architecture model as a whole; and

store the architecture elements making up the first architecture model individually.

24. The system of claim 19 , wherein each of the architecture stacks comprises a logical grouping of architecture elements related to one another by a logical function.

25. The system of claim 24 , wherein each architecture element in an architecture stack is dependent on at least one other architecture element in the architecture stack.

26. The system of claim 24 , wherein at least one of the plurality of architecture stacks includes an embedded architecture stack, the embedded architecture stack comprising a logical sub-grouping of architecture elements.

27. The system of claim 19 , wherein the architecture creator system is further to:

at the request of a second user, access the first architecture model stored in the centralized database; and

allow the second user to modify the first architecture model.

28. The system of claim 27 , wherein the architecture creator system is further to:

at the request of a second user, access the first architecture model stored in the centralized database;

create a minor copy of the first architecture model; and

allow the second user to modify the mirror copy of the first architecture model.

29. The system of claim 27 , wherein the architecture creator system is further to:

receive selection of a grouping of architecture elements from the first user; and

save the grouping of architecture elements as one of the architecture stacks in the centralized database.

30. The system of claim 19 , wherein the architecture creator system is further to:

determine if the first architecture model is compliant with one or more technical rules; and

validate the first architecture model if the first architecture model is compliant with the one or more technical rules.

31. The system of claim 19 , wherein when storing the first architecture model in the centralized database, the architecture creator system is to store the first architecture model with a status identifying the first architecture model as a draft, the architecture creator system further to:

receive approval of the first architecture model from a reviewer; and

change the status of the first architecture model to a production status.

32. The system of claim 19 , wherein after accessing the centralized database to retrieve the plurality of architecture elements, the architecture creator system is further to:

filter the plurality of architectural elements based on a type of the first architecture model; and

present, based on the filtering, only the architectural elements that are suitable for the type of the first architecture model.

33. The system of claim 19 , wherein the architecture creator system is further to link the first architecture model with one or more stored business rules or technical requirements.

34. The system of claim 19 , wherein the architecture creator system is further to link the first architecture model with a second architecture model.

35. The system of claim 34 , wherein the linking is performed by providing an integration stack bridging the first and second architecture models, where the integration stack contains components that tie together parts of the first and second architecture models.

36. The system of claim 19 , wherein the architecture stacks further include a logical stack that includes a grouping of logical components.

Assignments (9)
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0577 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC)
Reel/Frame 063560/0001 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
CHANGE OF NAME Recorded Aug 8, 2019
From: ENTIT SOFTWARE LLC
To: MICRO FOCUS LLC
Reel/Frame 050004/0001 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ENTIT SOFTWARE LLC; ARCSIGHT, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0577 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 9, 2017
From: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
To: ENTIT SOFTWARE LLC
Reel/Frame 042746/0130 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2015
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 037079/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 25, 2009
From: ELECTRONIC DATA SYSTEMS, LLC
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 022449/0267 →
CHANGE OF NAME Recorded Mar 24, 2009
From: ELECTRONIC DATA SYSTEMS CORPORATION
To: ELECTRONIC DATA SYSTEMS, LLC
Reel/Frame 022460/0948 →