The main objective of this part of the project is for your team to get to know each other and start thinking about your application. Specifically, you must complete the following:

1. (0 points)
   Your first step is to identify the domain you would like to manage with your database. It is suggested that you pick an area you will enjoy, since you'll be stuck with it for the semester! In previous years, students who built a database about something they were interested in got the most from this part of the course. Try to pick an area that is relatively substantial, but not too enormous. For example, when expressed in the entity-relationship model, you might want your design to have in the range of seven to ten or so entity sets, and a similar number of relationships. Note that these are ballpark figures only!
    
   
2. (25 points)
   Briefly describe the general nature of the domain, a description of the data that must be stored in the database to support the domain, as well as the interactions between users and the database. Your description should be brief and relatively informal ( 2-3 pages). If there are any unique or particularly difficult aspects in your proposed area, please point them out. Your description will be graded only on suitability and clarity. This document (i.e., project plan) will serve as your road map for the development of your database and give the instructor an overview of what you are trying to do and how difficult it is. Please note that it is ok to deviate from this plan as the semester progresses and you understand the details of your application better. Please submit an updated project plan with your deliverable whenever you make changes.
    
   
3. (25 points)
   A design of the underlying database using the E/R data model discussed in class. Specifically, your data design should support the needs of the application and should contain somewhere between 7 to 10 entity types, each with their associated attributes (3-5). Attributes should be defined over a mixture of simple, composite, and set-valued domains. In addition, you must specify approximately 7-10 relationships among the entity types of your schema. Finally, specify a set of constraints for the domains, entity types, and relationships. Include as many constraints as you need to support the application (and as you can model using E/R constructs). At this point do not worry about how to enforce the constraints in the DBMS. Please use the notation introduced in the lectures or the textbook.

For this part, you need to hand in your project plan as well as your E/R database design. You may use an E/R design tool if you have access to one. Otherwise, paper & pencil is ok, with a clear photo or scan submitted.

Your project plan will be examined quickly to catch major problems before you have to hand in the next deliverable for Part 2.