Research Paper on:
Internet Integration and Database Design

Unformatted Sample Text from the Research Paper:
They were certain that the new structure of computer use would move computers out of businesses and into society at large. Obviously, they were correct in their predictions.  The accelerating and ongoing technological improvements in microprocessors, information transfer modalities, and application upgrades cause computer systems to quickly become obsolete. In fact, it is difficult to maintain an overall  system that can be kept up to the minute (or up to the second) in terms of such continual advancements. But in terms of designing a database that best suits  an individual organizations needs and goals, certain factors will always remain the same. After all, accuracy, availability, and ease of use will always be important features, regardless of how fast  they are made available or how many bells and whistles they might have. Furthermore, the concept of "one size fits all" will never be applicable in database design and  integration. Creating a unified system to move data has tremendous advantages for the management of virtually (pun intended) organization. For example, Wawrzyniak (2000) points out that there has been a  steady reduction in product life cycles even though design cycles have increased (pp. 20). "It matters little how powerful or integrated the part is if the very complex design now  possible with SOC [system on a chip] takes nine months to complete and the product life cycle is only eight months long" (pp. 20). As a result, many organizations have  found that the best possible means of dealing with the problem is to develop a system that allows for constant maintenance and service that continually upgrades individual computers and networks  to assure that the system is not obsolete before its full potential can be reached. The same holds true with database management. The Fundamentals Designing any database requires an