 |
Access Integration
Overview
The Access Integration pattern describes those recurring designs that enable access to one or more Business patterns. In particular, this pattern enables access from multiple channels (devices) and integrates the common services required to support a consistent user interface.
What's Next
If you're not yet sure that your business problem can be solved by the functionality enabled through an Access Integration solution design, the Access Integration general guidelines page provides additional information on choosing this Integration pattern. Business and IT drivers, the e-business context appropriate for this solution type, and additional solution details are discussed here.
If you've determined that the Access Integration pattern can provide an appropriate solution design for your business need, the next step is to select an Application pattern. The Access Integration pattern can be implemented using one of three Application patterns, providing solution flexibility so that the determined Integration pattern can address the specific needs of the business process being automated.
|
|
|
Patterns for e-business naming conventions
The Patterns for e-business naming conventions can be seen here.
|
|
Feasibility: This material will help you determine the high-level shape of an Access Integration system, and ensure your approach looks similar to other successful sites. Reuse of prior approaches can be an effective way to begin most major projects. Obviously, modifications will be needed for any unique requirements of a given site. This pattern provides a drill-down from high-level architecture to lower-level designs and guidance.
Risk: Basing new projects on prior designs and ideas helps to lower the risk of failure. Creating or inventing designs for each project tends to result in a lower success rate. Frequently, projects begun "from scratch" simply do not work and have major exposures in such areas as security, performance, availability, undefined requirements, and cost over-run.
Cost-benefit: By starting with reasonably complete architectures you save considerable development time and obtain assurance that the end solution will have a much higher chance of success. Actual savings will vary, but project teams have realized a 10% to 50% reduction of work effort in their design and architecture phases alone.
|
|
If you haven't already joined our mailing list to be notified when we make updates or add new patterns, subscribe today.
|
|
Discuss the patterns with your peers. Visit our newsgroup for patterns.
|
|
