Label: pattern

All content with label pattern.
Related Labels: glossary

Page: Automate releases (KM: Agile Software Release Strategies)
every release has a large chance of error due to clumsy operators or bad documentation, releasing frequently becomes suicidal. Make sure that the release process open for a little human error as possible. First, make sure the documentation and routines are simple ...
Page: Command Pattern (KM: Service Oriented Architecture (SOA))
Problem Context Forces Solution Resulting Context Rationale Extensions / Advanced Scenarios
Other labels: glossary
Page: Customer by customer (KM: Agile Software Release Strategies)
Problem/Context In a Replacement project where the existing system is based around customer accounts. Solution Develop just enough features to be able to migrate a small number of customer accounts. Migrated accounts should be of the same type. More customers are migrated ...
Page: Data Mapping in EDR (Open Source: EDR - Enterprise Domain Repository)
Definition: Mapping data between Provider Objects and a Domain Object. Data Mapping should also be able to reverse, from the Domain Object to the Provider Object. Reason: A clear statement on how data should be mapped will ease the implementation of EDR. This statement ...
Page: Duplicate input (KM: Agile Software Release Strategies)
Problem/Context In a replacement project the existing system handles a pipline of transactions. Solution Duplicate incoming transactions so that both the new and the existing system can handle them. Strengths Weaknesses
Page: EDR - Moderator (Open Source: EDR - Enterprise Domain Repository)
Moderator Extension for EDR !edrmoderator1.jpg thumbnail! Responsibility Log Differences in data between providers Notify moderator to verify data. Keep list of updates awaiting moderator aproval Notify Controller if a domain object should be flaged dirty. Dependent on Provider ...
Page: Enterprise Domain Repository Pattern (KM: Service Oriented Architecture (SOA))
Problem Most enterprises have several systems which own parts of a domain object. The data from these systems might be disjoint, as well as overlapping. The data quality and SLA requirements for each system are often of diversified quality. We need a standardized ...
Other labels: glossary
Page: Evolving Service Endpoint Pattern (KM: Service Oriented Architecture (SOA))
Problem Core Services will over time aquire a large number of clients in the Enterprise. Changes to the Core Service contract will increase in cost for every new client if the service cannot take responsibility for supporing the legacy clients and new clients concurrently behind ...
Other labels: glossary
Page: Facilitate switching (KM: Agile Software Release Strategies)
Problem/Context Many of the patterns used in replacement projects lead to a transitional period where at least some user groups will use both the existing and the new system in parallel. In these cases users will appreciate any steps taken that make it easier for them ...
Page: Limited releases (KM: Agile Software Release Strategies)
Problem/Context The risk or cost of rolling out a release to the whole user group is large. Solution Identify a small group of users that can be used as pilot users. As few as 68 users can be representative for a whole user group. Deploy a release ...