| Glossary |
|---|
Recording Proxy Pattern
|
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]
|
MRP
|
REST
|
Metadata
|
Real Time Enterprise
|
Security Token
|
Repository
— "A Repository is a mechanism for encapsulating storage, retrieval, and search behavior which emulates a collection of objects." [smidigtonull:Evans 2003]
|
LAMP
|
Cargo Cult
|
SOA Maturity Models and EDR-MDS
|
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
|
Master Data Service (MDS)
|
Enterprise Domain Repository Pattern
— The Enterprise Domain Repository's main responsibility is to provide unified access to Domain Objects in the Enterprise.
|
lightweight architecture
|
Command Pattern
|
EDR-MDS a SOA Master Data Management Service
|
Service Categories
|
Policy Advisory Board
|
The Cost of reuse versus duplication
|
Replacement project
|
Software Design
— Software design is a process of problem-solving and planning for a software solution.
|
Master Data Management
|
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.
|
Potentially shippable
|
Kanban
— Naked Just-In-Time planning.
|
Application to Application Services
|
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]
|
Identity Management (IdM)
|
SOA
— Service Oriented Architecture
|
Business Intelligence (BI) and Enterprise Search in a Service Oriented Architecture Strategy
|
Enterprise Applications
|
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.
|
Domain-Driven Design (DDD)
|
Extreme Agile
— It's a term we came up with to challenge existing agile practices, or push them to the extreme. We don't recommended that anyone actually try to enforce these practices, they're more like thought-experiments that you might be able to apply.
|
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
|
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.
|
Evolving Service Endpoint Pattern
|
Master Data Management Notes
|
Master Data
|
System Strategy
|
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]
|
Test-Driven Development
— The ever more popular test-first approach.
|
From EA to SOA (and back)
|
Human to Application Services
|
Value Object
— "An object that represents a descriptive aspect of the domain with no conceptual identity is called a VALUE OBJECT." [smidigtonull:Evans 2003]
|
Understandability
|
Enterprise POJO
|
Aggregated Core Servives
|
Constraints and validation
|
Learning circle
|
Enhancement project
|
Smart Service Proxy Pattern
— Simplify usage/reuse of a remote service
|
Service Manifest
|
Entity
— "An Entity is an Object that represents something with continuity and identity. An entity is tracked through different states and implementations."
|
Source Code
|
Core Services
|
Cloud
|
Recording Command Pattern
|
Service Assembly Pattern
— Aggregering av core tjenester inn som aggregated core tjenester
|
Alignment of Enterprise Search Platforms (ESP) and Service-Oriented Architecture
|
Search-driven Business Intelligence
|
Design-Time Governance - SOA Design Rules
|
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.
|
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,
|
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
|
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 Operations
Browse Space