Create few tables that are related to everything with Quiz.(Ex: firstName, Id} and fulfill the requirements above.

Thanks!!! Thumb up!!!

1. Requirements - What are the high level capabilities of the system and how should it look to the end user? This corresponds roughly to the "Data Collection" chapter in the case study, except that instead of looking at things like existing reports, or interviewing existing users, you are the "customer" who will decide what is needed. As a starting point, I'll propose the following set of requirements. You can change this list if you feel its appropriate by adding, deleting, our modifying the requirements, but you should have state clearly what you are changing, and your reasons for doing so. In general, I would like people to think about how to come up with a design that meets these requirements: 1. Support an arbitrary number of quizzes, not just 1 2. Support quizzes with a varying number of questions. (All quizzes do not have to have the same number of questions.) 3. It will be possible to add or remove a question from a quiz 4. It will be possible to print a quiz with a particular student's answers (a finished quiz), or without the answers (a blank quiz for someone to take) 5. It will be possible to answer each question with a single answer or list of answer (such as types of music, or operating systems). 6. It will be possible to store information about a student (such as name and academic level), and about a quiz (such as the date of the quiz) 2. Design - This corresponds roughly to the "Data Naming" chapter in the case study. This is where you should be thinking about a Conceptual Model with your "entities," their "attributes," and the "relationships" between them. I would suggest not showing specific database tables at this stage, but just describe them conceptually. Using graphics (like Entity-Relationship Diagrams) would be a great way show these ideas. 1. Requirements - What are the high level capabilities of the system and how should it look to the end user? This corresponds roughly to the "Data Collection" chapter in the case study, except that instead of looking at things like existing reports, or interviewing existing users, you are the "customer" who will decide what is needed. As a starting point, I'll propose the following set of requirements. You can change this list if you feel its appropriate by adding, deleting, our modifying the requirements, but you should have state clearly what you are changing, and your reasons for doing so. In general, I would like people to think about how to come up with a design that meets these requirements: 1. Support an arbitrary number of quizzes, not just 1 2. Support quizzes with a varying number of questions. (All quizzes do not have to have the same number of questions.) 3. It will be possible to add or remove a question from a quiz 4. It will be possible to print a quiz with a particular student's answers (a finished quiz), or without the answers (a blank quiz for someone to take) 5. It will be possible to answer each question with a single answer or list of answer (such as types of music, or operating systems). 6. It will be possible to store information about a student (such as name and academic level), and about a quiz (such as the date of the quiz) 2. Design - This corresponds roughly to the "Data Naming" chapter in the case study. This is where you should be thinking about a Conceptual Model with your "entities," their "attributes," and the "relationships" between them. I would suggest not showing specific database tables at this stage, but just describe them conceptually. Using graphics (like Entity-Relationship Diagrams) would be a great way show these ideas