Reference no: EM132946635

In this assignment, we'll follow the database design process with a step-by-step example. Your client, Wellness Week is a small, specialized publisher that publishes articles on health and wellness issues. The owner would like to have a small database that would track authors and articles.

Below are some of the findings from the analysis phase
Authors can sometimes simply express interest in submitting an article. So it would be good to have them in the database, even if they haven't submitted anything.
Wellness Week would like to have basic contact information for all authors: name, address, phone number, email.
Wellness Week currently publishes a monthly newsletter only. They do not currently publish online. Each monthly newsletter has a specific theme (title). It is possible that an article might be reprinted in more than one edition of a newsletter.
For each article, they would like to capture the author name, date of publication and length (in words).
Just as an author can exist in the database without an article, in the planning stages of a publication, it would be helpful to have a publication without an article.
The articles can have only one author.

Question?

1. If Wellness Week decided that it would like to allow multiple authors for an article, would this require changing the (underlying) database schema? Why or why not?

2. If Wellness Week decided that it would like to establish an online presence, with some reprints and some new content (articles), would this require adding a new table? Why or why not? Note this does NOT mean we would use the database to store the articles or connect to the Internet. This merely means we would want to keep track of whether an article appeared online or in print or both and when.