Technology
Guide: Selection Criteria
|
|
|
Related Topics 7 Levels of Application Integration Related Links |
Contents System Selection Considerations Consider also its Architecture |
System Selection Considerations
The
expense to deploy a configuration, the ongoing expense, and the marginal
expense to increase the performance of the configuration by adding additional
servers
System
throughput, user response time, or service rates.
Ability
for a system to increase performance capacity with the addition of more
server machines (to cater for larger and larger processing demands).
Ability for a system to maintain predictable behaviour, maintain transactional integrity, resist failures and keep running.
The
practice of developing new software, understanding it, maintaining it, and
augmenting it.
The
practice of administrating software, keeping it secure, installing it, and
upgrading it. |
|
|
|
Hardware Considerations
|
|
|
Consider also its Architecture While product solution selection should primarily be based on its functionality, its architecture should be a key consideration in your decision. Architecture examines how products are built, how they’re deployed, how they can be customised, and how they can be integrated with external applications. You should select a solution product primarily on its functionality, but its architecture should be a significant influence on your decision. For example, the examination of architecture will let you understand: how well a solution product will fit easily into your existing environment, whether it uses well-proven and widely-used technologies, how easy it is to customise, and what it takes to integrate with your existing business systems and the business systems of your customers and suppliers. Here is a time proven approach that considers six areas of architecture. The approach has demonstrated the ability to identify differences among products, and those differences are the key to helping selection decisions. The six areas are: • Environments, which are the user interface (Web servers), server platforms, and databases that a solution product supports. • Organisation, which identifies a product’s major components and the interfaces between them. (Interfaces are always between two components) • Infrastructure, which is the set of runtime services that support request handling, application processing, and database access. • Structure, which is what’s inside the product’s major components, particularly the user interface (Web pages), application logic, and database. • Customisation, which is the adaptation of the components to address site-specific requirements. • Integration, which complements and completes processing with the functionality of external applications. |
Home | Network | Security | Software | Solutions | Products
Updated on Sept 05, 2002
© Copyright 2002 Allan Low. All rights reserved. Reproduction of
this Web Site, in whole or in part, in any form or medium without express
written permission from the author is prohibited.