System for portal architecture

• US 20080109276A1
• Filed: 02/08/2007
• Published: 05/08/2008
• Est. Priority Date: 11/03/2006
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture SPA (Accenture PLC)
• Inventors: Ionfrida, Nicola, Cardinale, Paolo
• Granted Patent: US 8,239,830 B2
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/316 Aspect-oriented programming techniques

Abstract

A system for a portal architecture may include a model service component. The model service component may be arranged to connect a presentation device to a business manager component. An aspect oriented architecture may be associated with the model service component. A service oriented architecture may be associated with the model service component, the service oriented architecture being arranged orthogonal to the aspect oriented architecture.

Claims

1. A system for a portal architecture, comprising:

a model service component, the model service component being arranged to connect a presentation device to a business manager component;

an aspect oriented architecture associated with the model service component; and

a service oriented architecture associated with the model service component, the service oriented architecture being arranged orthogonal to the aspect oriented architecture.

2. The system of claim 1 wherein the aspect oriented architecture comprises security, exception handling, logging and caching aspects.

3. The system of claim 1 wherein the service oriented architecture comprises support, order, catalogue, account and customer services.

4. The system of claim 1 wherein the presentation device comprises web and mobile portals.

5. The system of claim 1 further including legacy systems, wherein the business manager component connects to the legacy systems.

6. The system of claim 1 further including a layout database for storing data, wherein the data comprises layout information.

7. The system of claim 6 wherein the layout information comprises information about different portals.

8. The system of claim 6 further comprising a web application, wherein the web application reads the data from the layout database.

9. The system of 6 wherein at least two entities which are located in different locations contribute to the layout database.

10. The system of claim 9 wherein the entities define a state machine to be shared via a dynamic link library.

11. A model service component for connecting different portals to legacy systems, comprising:

an aspect oriented architecture means; and

a service oriented architecture means, the service oriented architecture means being arranged orthogonal to the aspect oriented architecture.

12. The model service component of claim 11 wherein the aspect oriented architecture means comprises security, exception handling, logging and caching aspects.

13. The model service component of claim 11 wherein the service oriented architecture means comprises support, order, catalogue, account and customer services.

14. The model service component of claim 11 further including legacy systems, wherein the aspect oriented architecture means and service oriented architecture means connects the different portals to the legacy systems.

15. The model service component of claim 111 further including a layout database means for storing data, wherein the data comprises layout information.

16. The model service component of claim 15 wherein the layout information comprises information about the different portals.

17. The model service component of claim 15 further comprising a web application means, wherein the web application means reads the data from the layout database means.

18. The model service component of 15 wherein at least two entities which are located in different locations contribute to the layout database means.

19. The model service component of claim 18 wherein the entities define a state machine to be shared via a dynamic link library.