Database Design Paper
“A database is a structured collection of records or data that is stored in a computer system. In order for a database to be truly functional, it must not only store large amounts of records well, but be accessed easily. In addition, new information and changes should also be fairly easy to input.” (tech-faq.com); to ensure usefulness over the long-term, databases should be built with high data integrity and the ability to recover data if the hardware fails. Information that has been corrupted or destroyed serves no purpose within a business structure. Being the Armed Forces is like being a field value in one giant database. Everything from the gear we are issued to how we are identified as an “individual” (ssn#) is a scannable number to be coded, referenced, and utilized by anyone with proper clearance. “The database architecture is the set of specifications, rule, and processes that dictate how data is stored in a database and how data is accessed by components of the system.” (wingenious.com) Database architecture type s can be broken down into three broad categories, each of which can have several subcategories: One Tier, Two Tier- client/server, and “N” Tier- client/server. The One Tier architecture is best suited to the single user and relatively small amounts of data. It runs on the user’s local machine and references a file that is stored on that machine’s hard drive, thus using a single physical resource to access and process information. For multiple users and small scale applications Two Tier client/server architecture would be better suited than One Tier architecture. Users interact through a GUI (graphical user interface) to communicate with the database server across a network via SQL (structured query language. For the large scale applications, “N” Tier client/server architecture must be adopted. The client/server model expands to include a middle (or business) tier, which is an application server that houses the...
Please join StudyMode to read the full document