|
Glossary |
|
--- |
|
Page: Replacement project |
|
Page: Core Services |
|
Page: Application to Application Services |
|
Page: Aggregated Core Servives |
|
Page: Human to Application Services |
|
Page: Metadata |
|
Page: Alignment of Enterprise Search Platforms (ESP) and Service-Oriented Architecture |
|
Page: Cargo Cult |
|
Home page: EDR-MDS a SOA Master Data Management Service |
|
Page: Master Data Service (MDS) |
|
Page: SOA Maturity Models and EDR-MDS |
|
Page: Real Time Enterprise |
|
Page: System Strategy |
|
Page: Security Token |
|
Page: Enterprise Domain Repository Pattern — The Enterprise Domain Repository's main responsibility is to provide unified access to Domain Objects in the Enterprise. |
|
Page: Evolving Service Endpoint Pattern |
|
Page: Software Design — Software design is a process of problem-solving and planning for a software solution. |
|
Page: Enterprise Applications |
|
Page: Source Code |
|
Page: Architecture — The software architecture of a program or computing system is the structure or structures of the system, which comprise software components, the externally visible properties of those components, and the relationships between them. |
|
Page: The Cost of reuse versus duplication |
|
Page: lightweight architecture |
|
Page: Master Data |
|
Page: Understandability |
|
Page: Service Categories |
|
Page: Command Pattern |
|
Page: Service Assembly Pattern — Aggregering av core tjenester inn som aggregated core tjenester |
|
Page: Smart Service Proxy Pattern — Simplify usage/reuse of a remote service |
|
Page: Recording Proxy Pattern |
|
Page: Recording Command Pattern |
|
Page: CS — Core Services is basically data services. Typically they evolve to become the master repository for the most important business objects in the enterprise. Typical examples are Customer and Product. You will also find that it often makes sense to split a service for a domain object into a CRUD (master) service and a accompanying Query Service to keep the complexity to a manageable level, and to allow a more feature rich query interface. |
|
Page: ACS — Aggregated Core Services is extensions to Core Services. ACS is usually either context-specializing (CustomerCustomer and VendorCustomer) or aggregations from several Core Services like in CustomerDashboard which aggregates from Customer Service, Order Service and possibly more services |
|
Page: H2A — Human 2 Application Services is services involving key user interaction components with one or more humans to fulfill some activity/workflow. For example a booking process or a manual shipment process, |
|