| 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,
|
Page:
Policy Advisory Board
|
Page:
Access Manager (AM)
— Access Manager is identity and access management solution to extend security for Web,Microsoft and Java applications to federated environments and Web services security
|
Page:
Identity Management (IdM)
|
Page:
Kanban
— Naked Just-In-Time planning.
|
Page:
Extreme Agile
— When you take agile practices to the extreme. Sandbox for new practices.
|
Page:
Potentially shippable
|
Page:
Domain-Driven Design (DDD)
|
Page:
Design-Time Governance - SOA Design Rules
|
Page:
From EA to SOA (and back)
|
Page:
Service Manifest
|
Page:
MRP
|
Page:
Aggregate
— "An AGGREGATE is a cluster of associated objects that we treat as a unit for the purpose of data changes. External references are restricted to one member of the Aggregate, designated as the root. A set of consistency rules applies within the Aggregate's boundaries." [smidigtonull:Evans 2003]
|
Page:
Value Object
— "An object that represents a descriptive aspect of the domain with no conceptual identity is called a VALUE OBJECT." [smidigtonull:Evans 2003]
|
Page:
SOA
— Service Oriented Architecture
|
Page:
Entity
— "An Entity is an Object that represents something with continuity and identity. An entity is tracked through different states and implementations."
|
Page:
Factory
— "A Factory is a mechanism for encapsulating complex creation logic and abstracting the type of a created object for the sake of a client." [smidigtonull:Evans 2003]
|
Page:
Repository
— "A Repository is a mechanism for encapsulating storage, retrieval, and search behavior which emulates a collection of objects." [smidigtonull:Evans 2003]
|
Page:
Domain Service
— "A SERVICE is an operation offered as an interface that stands alone in the model, without encapsulating state, as ENTITIES and VALUE OBJECTS do." [smidigtonull:Evans 2003]
|
Page:
LAMP
|
Page:
Data Warehouse (DW) and Business Intelligence (BI)
— In this context we are defining traditional Business intelligence as [Data Warehouse (DW) and Business Intelligence (BI)] to separate this form Business Intelligence referred to by search platforms
|
Page:
Search-driven Business Intelligence
|
Page:
A2A
— Application 2 Application Services is services which orchestrates services from several applications, typically asynchronous and workflow-backed. I.e. a Auction type request against a set of suppliers or an booking/order/delivery process.
|
Page:
Enterprise Architecture (EA)
— Enterprise architecture is a term used to describe the practice of documenting the elements of business strategy, business case, business model and supporting technologies, policies and infrastructures that make up an enterprise.
|
Page:
Enhancement project
|
Page:
Master Data Management
|
Page:
Constraints and validation
|
Page:
Master Data Management Notes
|
Page:
Test-Driven Development
— The ever more popular test-first approach.
|
Page:
Business Intelligence (BI) and Enterprise Search in a Service Oriented Architecture Strategy
|
Page:
Enterprise POJO
|
Page:
REST
|
Page:
Learning circle
|
Page:
PAB
— Policy Advisory Board is a specialized Center of Excellence organ, focusing on the round trip of keeping the design-time governance policies aligned with the company goals, people and competences.
|
