As you have learned from the Systems Development Life Cycle, there are many ways to design a system. Given that, adopting from a simple process this assignment allows you to gain a hands-on experience with data modeling of a small and manageable subsystem. In this simple process, there are six steps involved in the assignment: 1) Listing the Output Requirements, 2) Listing the Input Requirements, 3) Normalizing the Entities, 4) Establishing Relationships among Entities, 5) Creating Bridge/Relationship Entities if necessary, and 6) Setting up Foreign Keys to establish physical links among entities. We will go over two sample applications together, i.e., credit memo subsystem and purchase order subsystem. You will then apply these steps to the charge sale invoice subsystem yourself (that is the work for this assignment). You can find an image of the credit memo form on the second page, purchase order form on the third page, and charge sale invoice on the last page of this document. If you have any questions, please post them via the Discussion Board on Blackboard. 

Requirements: 

1. (10%) List the OUTPUT requirements (i.e., all of the data/information). Additional points may be taken away if you skip any significant data items which may affect your work later. 

2. (10%) List the INPUT requirements (i.e., some of the above data needed to be stored in the database). Additional points may be taken away if you skip any significant data items tha may affect your work later. 

3. (40%) Based on the input requirements, create entities and apply database normalization to each of the entities. You must apply 1st, 2nd, and 3rd normal forms “individually” to each one of the entities. Please clearly indicate the requirements of each of the normal forms, specify any violations if there are any, and provide your solutions to the violations. Do not write over your process for each of the database normalization like I did in the class. List the table structures (with all attributes) after each of the normalization processes. It’ll be very easy to lose points if you fail to provide your work and follow these requirements. 

4. (25%) Identify required relationships and specify their types among the entities created previously. You need to specify your assumptions for the relationships if you are going to alter them from the SUA case. If you don’t remember/know or are not sure about the rules used in the SUA case, it’ll be better for you to state your assumptions about the rules. 

5. (5%) Create bridge/relationship tables if they are necessary for the RDBMS and apply the normalization. Make sure that you include previously excluded items if it’s appropriate. 

6. (10%) Establish the physical relationships between entities by creating foreign keys. 

7. Submit your work in MS Word to me via Course Message on Blackboard. Please use your full name and assignment name as the file name, e.g., Wang-TJ-RDB-Design.docx.