Conceptual Architecture Layers
Conceptual Architecture Layers: Layers, Technologies, Providers or Standards. -- table to: Framework For Better Decisions
Conceptual Architecture Layers
Layers | Technologies | Providers or Standards |
---|---|---|
Enterprise Application | Enterprise resource planning | SAP, Oracle, AND PeopleSoft and Data Systems |
Content management | EMC (Documentum), Interwoven, and Vignette | |
Mainframe and legacy applications | Fraud-detection systems,telecommunications provisioning applications, etc. | |
Customer-relationship-management and call-center systems | Kana and Siebel | |
Data Services | Application and data systems adapters | Actional, iWay, TIBCO, and WebMethods |
Data model and persistence engines | BEA, IBM (Rational), Sybase, Teradata, and TIBCO | |
Legacy functionality extraction | Microsoft, Oracle, Teradata, and TIBCO | |
Application Services | Messaging | IBM, Sonic, and TIBCO |
Application containers | BEA, Borland, IBM, Microsoft, and Oracle | |
Standard interfaces | Java standards, .NET standards, and web services | |
Metadata repositories | IBM, Oracle, Teradata, TIBCO, and custom repositories | |
Business Services | Business process | Fuego, Fujitsu, IBM, Microsoft, and TIBCO |
Business rules | Ilog, Pegasystems, and TIBCO | |
Human workflow | Fujitsu, IBM, Staffware, and TIBCO | |
Presentation and Interface Services | Web portal | IBM, Microsoft, Novell, Oracle, Plumtree, Sybase,TIBCO, and Vignette |
Mobile devices | WAP, WML, AND Java | |
Standard formats | EDIFACT, ebXML, AND other XML |
Return to: Framework For Better Decisions
About the Author
You May Also Like