| Glossary |
|---|
Master Data Management
|
Master Data Service (MDS)
|
Master Data
|
EDR-MDS a SOA Master Data Management Service
|
SOA Maturity Models and EDR-MDS
|
Real Time Enterprise
|
Enhancement project
|
MRP
|
Potentially shippable
|
Replacement project
|
LAMP
|
Cloud
|
REST
|
Enterprise Applications
|
Enterprise POJO
|
Constraints and validation
|
Understandability
|
Metadata
|
SOA
— Service Oriented Architecture
|
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
|
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
|
Core Services
|
Application to Application Services
|
Identity Management (IdM)
|
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.
|
Service Categories
|
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.
|
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.
|
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,
|
Aggregated Core Servives
|
Security Token
|
Policy Advisory Board
|
From EA to SOA (and back)
|
Software Design
— Software design is a process of problem-solving and planning for a software solution.
|
Alignment of Enterprise Search Platforms (ESP) and Service-Oriented Architecture
|
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 fint 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.
|
Master Data Management Notes
|
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
|
Human to Application Services
|
Source Code
|
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.
|
System Strategy
|
Cargo Cult
|
Test-Driven Development
— The ever more popular test-first approach.
|
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.
|
Kanban
— Naked Just-In-Time planning.
|
Recording Proxy Pattern
|
Recording Command Pattern
|
Command Pattern
|
Business Intelligence (BI) and Enterprise Search in a Service Oriented Architecture Strategy
|
Service Manifest
|
Service Assembly Pattern
— Aggregering av core tjenester inn som aggregated core tjenester
|
Smart Service Proxy Pattern
— Simplify usage/reuse of a remote service
|
Search-driven Business Intelligence
|
Evolving Service Endpoint Pattern
|
Enterprise Domain Repository Pattern
— The Enterprise Domain Repository's main responsibility is to provide unified access to Domain Objects in the Enterprise.
|
Design-Time Governance - SOA Design Rules
|
Browse Space