You are on page 1of 5

Read Me First DBM/380 Version 9

READ ME FIRST WEEK ONE


INTRODUCTION This course provides you with an introduction to database architecture and relational databases. The introduction covers the basic concepts of database design and management, focusing on the steps that a database designer should follow when creating a database for use with an application, addressing the basic tasks encountered by a database administrator, and identifying and discussing some of the aspects of ongoing database management. In Week One, you are introduced to a variety of different database architecture types, from data that is stored in flat files and XML, to legacy database architecture such as network and hierarchical structures. You also learn about the widely used relational database architecture and other less-used types including object-oriented and multidimensional architecture. With each architecture, you learn more about how the data is stored and how it is managed. The week concludes by focusing on the specific aspects of the relational database architecture. THIS WEEK IN RELATIONSHIP TO THE COURSE AND THE PROGRAM This first week prepares you for the remaining weeks of the course and introduces what a database is and the different kinds of databases available. This understanding helps you to see databases in the context in which they are used in the industry. HINTS FOR A READING STRATEGY OF THE ASSIGNED MATERIALS It is important for you to recognize the available database architecture. Some of these are not databases at all, in the formal sense. As you read this weeks readings, consider how data is stored and managed in your own organization or in one with which you are familiar. Further, consider the effectiveness of the different databases discussed in the readings. Consider how well data can be managed using the architecture. What are the advantages and disadvantages to data management for the architecture? Finally, when confronted with a problem that requires data storage, which type of database would you use as a part of the solution? SOME QUESTIONS TO ASK AS YOU HONE YOUR CRITICAL THINKING Consider the following questions as you read the assigned material. Why has relational database architecture become so dominant in the world today? What makes this architecture so successful? What are the ramifications for having the majority of our data stored in unstructured methods, such as files and spreadsheets? SUMMARY This weeks topics introduce you to the basic concepts of database architecture, database management systems, and relational databases. This information is fundamental to the remaining weeks of this course and helps you understand the scope of database design and management.

Copyright 2012, 2010 by University of Phoenix. All rights reserved. University of Phoenix is a mark of Apollo Group, Inc. in the United States and/or other countries.

Read Me First DBM/380 Version 9

WEEK TWO
INTRODUCTION Database designers are often tasked with gathering user requirements, translating these requirements into a logical design, and working with the database administration staff to implement the design within the database. This week provides instruction on the basics of this process. The reading assignments provide details about understanding the needs of users and translating those needs into requirements. It continues through the design process to elaborate on the translation of requirements into a logical data model. Identifying business rules and logic during this process is also discussed. These elements of database design are vital to the process of successfully creating a workable database model. THIS WEEK IN RELATIONSHIP TO THE COURSE AND THE PROGRAM During the second week of the course, you begin to apply the information on database architecture, especially the information provided on relational databases, in useful practice. The individual assignment uses the learning from Week One to test your knowledge of database management systems and provide an opportunity for you to elaborate on those systems used within your own workplace. The reading assignments move into the design aspects of database management. While this weeks readings introduce the basics of database design and new concepts are introduced, remember that the concepts of database design continue throughout the remainder of this course, HINTS FOR A READING STRATEGY OF THE ASSIGNED MATERIALS The reading assignment for this week is especially critical to your understanding as you embark on the Learning Team assignments. Because database design is a large part of the Learning Team assignment, as well as some of your individual assignments, be attentive to the steps in the design process and the hints and techniques outlined in the text. A sound understanding of these makes your assignment work more successful. SOME QUESTIONS TO ASK AS YOU HONE YOUR CRITICAL THINKING Understanding user needs and gathering user requirements is an important part of the design process. With this in mind, consider what you can do to make this process more accurate and streamlined. Also consider why there is such difficulty in translating the requirements into a workable data model. What business rules can be found in user requirements? How might these business rules be successfully implemented? SUMMARY Proper database design is critical to creating functional databases. The concepts introduced this week enable you to successfully plan a database for an organization. Learn to identify database architecture types and the strengths and weaknesses of each. With the concept of database design introduced, you are ready to continue learning the next steps in designing a database, namely entity-relationship diagrams (ERD).

Copyright 2012, 2010 by University of Phoenix. All rights reserved. University of Phoenix is a mark of Apollo Group, Inc. in the United States and/or other countries.

Read Me First DBM/380 Version 9

WEEK THREE
INTRODUCTION An important part of any database design is the logical design step. This is often documented using a diagram called an entity-relationship diagram (ERD). During this weeks readings and assignments, you learn how to document the logical design using the ERD. The ERD not only captures the basic entities related to the logical design but also captures, in detail, the relationships the entities share with each other. These include the type of relationships, the attributes, the keys, and more. A diagram with this information is not only used to communicate the design to other parties (like database administrators and users), but also used as a part of the design process itself to identify possible issues and correct them. THIS WEEK IN RELATIONSHIP TO THE COURSE AND THE PROGRAM This weeks material continues the database design process from the initial design steps discussed in Week Two into the logical design of the database. This provides a transition into Week ThreeNormalization. HINTS FOR A READING STRATEGY OF THE ASSIGNED MATERIALS The texts provide you with the details of building an ERD. Be attentive to the specific notation used in the ERD to diagram the various relationships, entity types, cardinalities, and so forth. Follow closely the examples provided later in the chapter. These examples provide you with valuable insight into how to diagram specific scenarios. These scenarios are typical of what you encounter in your Learning Team and individual assignments, as well as in the workplace. SOME QUESTIONS TO ASK AS YOU HONE YOUR CRITICAL THINKING Now that you have studied the steps in the design process, think about how you would follow the process from the beginning up through this point. Consider how you would diagram the user requirements identified last week using an ERD. Also, ask yourself how you would take the logical design diagramed using the ERD and implement it within your Microsoft Access database. Some relationships, such as the many-to-many relationship, are easily diagrammed using the ERD, but cannot be implemented in the same manner. SUMMARY Last week, you learned the first steps of the database design process. This week you cover ERDs. Using the ERD to work out the logical design of the database is a vital aspect of database design. ERDs are an important new tool to assist you as you learn database concepts. In Week Four, you continue learning about database design and normalization.

Copyright 2012, 2010 by University of Phoenix. All rights reserved. University of Phoenix is a mark of Apollo Group, Inc. in the United States and/or other countries.

Read Me First DBM/380 Version 9

WEEK FOUR
INTRODUCTION An often-used aspect of logical design is normalization. Normalization is a step-based approach to organizing entities and attributes during database design. A well-normalized database reduces duplication of data standardized table relationships and improves the performance of queries used in transaction-based applications. There are seven different normal forms or steps that build on each other to further standardize the design. Although not all of these levels are commonly used, gaining a basic understanding of each helps you to see the value and better decide what normal form is appropriate for the situation. THIS WEEK IN RELATIONSHIP TO THE COURSE AND THE PROGRAM A sound understanding of the ERD discussed last week helps you normalize your design. The normalization process is a part of logical design, especially when designing databases for transactional applications. This step is absolutely necessary in the design process. It represents one of the final steps in design. Once the design is completed, the physical design or implementation of the design into tables can be completed. HINTS FOR A READING STRATEGY OF THE ASSIGNED MATERIALS The readings for this week focus on discussing the details of normalization. The definition of each normal form is provided and an example of how to convert an entity into the normal form is presented. Be attentive to the differences among the normal forms. Understanding how they build on each other, from the first through the last, is vital to understanding how to normalize. Also, review closely the examples and explanations that are provided. These examples help to put each normal form into perspective. SOME QUESTIONS TO ASK AS YOU HONE YOUR CRITICAL THINKING Fully comprehending the process of normalization requires critical thinking. Often the difference between one normal form and the next is subtle and hard to understand. As each normal form is presented, ask what is different about this normal form and what entity needs this normal form applied to it. Further, ask yourself why each normal form is needed within the database design. Not all normal forms are necessary for a successful database design. A valuable part of design is understanding what an appropriate level of normalization is. SUMMARY Normalization is an important concept of database design, and is often used as a part of logical design. Using normalization can improve the performance of database queries, reduce duplication of data and storage, and can help to maintain the integrity of the database. It is important that you completely understand this concept. Now that you have studied database design, you can move into database implementation and management in Week Five.

Copyright 2012, 2010 by University of Phoenix. All rights reserved. University of Phoenix is a mark of Apollo Group, Inc. in the United States and/or other countries.

Read Me First DBM/380 Version 9

WEEK FIVE
INTRODUCTION With the design of the database completed, you can now focus on implementing the design within the database and managing the database. One step to implementation of the database is converting the logical entities and relationships diagramed using the ERD in physical tables, fields, keys, indexes, and so forth within the database. The implementation of table relationships often requires you to create additional tables and add foreign keys to these tables. Once the tables are created, you must also apply security strategies to limit and control access to the data. Further, can you manage concurrent requests to the same data and ensure that the integrity of the data is maintained at the same time that data is returned to requesting applications? Finally, consider strategies for data backup and recovery to keep the data available when the business needs it. THIS WEEK IN RELATIONSHIP TO THE COURSE AND THE PROGRAM This week concludes the discussion on database design by providing information on implementing the design within the database. This is part of the progression from the design discussion in previous weeks. Additionally, this week discusses several basic concepts of database management that are important once the database has been implemented. HINTS FOR A READING STRATEGY OF THE ASSIGNED MATERIALS Of the topics in the assigned readings this week, one of the most challenging you may encounter is concurrency. Concurrency is the ability of the database to process multiple requestsqueries, inserts, updates, or deletesat the same time. As you read through this section, be attentive to the facilities that the relational database management system (RDBMS) provides to manage concurrency. While none of these tools are completely foolproof, they do a good job of dealing with the problem. As you read through the text, consider the advantages and disadvantages of each of these concurrency tools and how you might use them within your own application. SOME QUESTIONS TO ASK AS YOU HONE YOUR CRITICAL THINKING Consider the following questions as you go through this week. Why are the tools provided by the RDBMS to manage concurrency necessary? Why should the database not allow all requests to be handled without regard to concurrency? Considering the advantages of using cursors in a database, why would this technique not be used for all data requests? With the large number of applications that use an object-oriented language for development, why do you think that objectoriented databases have not become more popular? SUMMARY The final week of this course discusses the implementation of database design and identifies some basic maintenance that should be performed to keep the database running smoothly. Administering databases requires that you know how to design and implement them as well as manage them on a daily basis. Successfully completing this course provides you with the tools and knowledge to work with databases being used in a variety of organizations.

Copyright 2012, 2010 by University of Phoenix. All rights reserved. University of Phoenix is a mark of Apollo Group, Inc. in the United States and/or other countries.

You might also like