You must use Crows Foot notation in Visio For your model

Read the following narrative and translate it into a conceptual database model for Julia that can be implemented in a relational database. You will test your design by creating an Access database that implements your design, enters sample data and produces a report to test its functionality. Business Narrative: Customers contact Julia when they are interested in a deploying a new or redesigned web site. Julia would like to track standard information about the customer (name, address, primary contact info). Additionally, Julia would like to know how the customer learned about her company (which internally she calls the "Business Source" and that currently could have these values: Internet Search, Word of Mouth, Radio Ad or Direct Mail Solicitation, though additional sources could be added. A signed contract between the customer and Julia authorizes "Julia's Designs" to start the project. Julia would like to track data about each Project including: the Project Name, a description of the project, a concise statement of work to be performed, the Contract Date, the project start date, an estimate of work required to complete the project (in hours), estimated completion date, and the Project Status (Not Started, Planning, Active, On-Hold, Closed). As the project is planned out, Tasks are identified that must be performed to complete the work. Julia would like to track data about the tasks. Each task has a description, a WBS number, an estimate of the work in hours), a planned start and finish date, the actual work performed (also in hours) and an assigned resource. Julia has several resources (people) in her company that do the work. She would like to track some data about those resources: name, skill, and max availability (which reflects the amount of time per week the resource is available to work on project tasks versus other administrative or operational tasks). Julia identified the following business rules for you: A customer can contract for 1 to many projects, but each project is contracted by one and only one customer. A customer has one and only one business source, though each business source may result in O to many customers. A project has 1 to many tasks and each task belongs to one and only one project. A task is assigned to O to many resources and a resource is assigned to o to many tasks. When a resource is assigned to a task - it is called an assignment. The assignment should A customer can contract for 1 to many projects, but each project is contracted by one and only one customer. A customer has one and only one business source, though each business source may result in 0 to many customers. A project has 1 to many tasks and each task belongs to one and only one project. A task is assigned to O to many resources and a resource is assigned to O to many tasks. When a resource is assigned to a task - it is called an assignment. The assignment should also store data about the estimated work (in hours) assigned to that resource and the actual work performed in hours). A resource has 1 to many skills and skills are held by O to many resources, Use the concepts you have learned thus far to design a database for Julia. Make reasonable choices for primary key selections. Use good design techniques as you consider the attributes needed for each table. Be sure to use simple versus composite attributes and single value versus multi-value attributes. Consider what fields should be required to have a value and carefully analyze the business rules to understand the relationship types, direction and connectivities. Once designed, use Microsoft Visio to draw the ER diagram that can be used to communicate the design to Julia and a DBA. Seek clarification on constraints if necessary. Your ERD must include entities, attributes, relationships (descriptively named), primary keys, foreign keys, and reflect the proper connectivities and cardinalities. Identify the strong and weak relationships and entities by properly setting those properties in Visio. You MUST use Crow's Foot notation for your model