Vous êtes sur la page 1sur 7

For each of the below scenarios, design an appropriate normalized relational database (RDB).

Specifically, include an entity-relationship diagram (ERD) and a database design outline, as


indicated in the lecture notes.
For this assignment, please use the simple elements for text boxes and lines available in this
Google Doc to draw your ER Diagrams. Please include your outlines as normal text.

Q1. Your firm provides a platform for companies to find on-demand talent for short- and mid-term jobs on
their projects, and for independent contractors to find work. For each placement obtained through your
platform, you receive a small percentage of the job price from both the contractor and the company (e.g.
0.2% and 1%, respectively). The contractors fee is universally 0.2%, but you negotiate the companys fee
with each company separately. However, each company pays its negotiated fee for all of the placements
filled on your platform.
Each contractor has a unique license number, its expiration date, a registered DBA company name, and
standard contact information that needs to be stored. Companies also have a name, address information,
a phone number, and the name of a point of contact that should be stored. Additionally, each company
has a portfolio of projects, each of which with a name and description.
Each job consists of a single contractor working on a single project. For quality assurance and to mitigate
service disputes, your system needs to track a description of each job, the jobs price, its projected
projected and actual start and end times, and of course, the contractor and company.
Assume that you DO have access to a zip code table containing city, state, and zip code attributes.
Design a database (ER Diagram and Outline), and create the DB in Access using reasonable datatype for
all attributes.

Q2. You have a large investment portfolio, and want to set up a database to keep track of your holdings.
You do businesses with multiple brokerage firms, and you have more than one account with some of

these firms (for example, one for your IRA and another for day trading). For each brokerage firm, you
want to store a name and standard contact information. For this problem, assume that you do NOT have
access to a zip code table. For each account, you want to keep track of its account number, date opened,
cash balance, and type (for example, ``401(k)" or ``regular").
In addition to cash, each account may contain one or more holdings of securities: for example, 1000
shares of IBM and 500 shares of APPL. You want to track all of your holdings, i.e., the number of shares,
the ticker symbol of the security, the date you acquired the shares, and their cost basis. Shares in some
securities (such as mutual funds) may be fractional. Securities are identified by a ticker symbols
consisting of up to 8 characters (for example, CSCO for Cisco Systems or VZ for Verizon). Assume you
have access to a table giving a name and description for each ticker symbol that appears in your portfolio.

Firm(FirmID, Name, Description, Street Address, City, State, Zip, Phone Number)
FirmID is primary key.
Account(AccountNumber, Date Created, Cash Balance, Account Type, FirmID, HoldingID)
FirmID is foreign key to Firm
HoldingID is foreign key to Holdings
Holdings(HoldingID, Number of Shares, Ticker Symbol, Date Acquired, Cost Basis)
HoldingID is primary key
Ticker Symbol is foreign key to Ticker
Ticker(TickerSymbol, Description)

Q3. Pick any one of the apps on your phone that you like and use every single day. Design a database to
support its core functionality; i.e., your database should be able to support whatever it is you do on the
app every day. (If you cant decide on an app from your phone, pick one of the following applications
instead: Amazon, Facebook, LinkedIn, Twitter, Pinterest, StumbleUpon, Spotify, Uber, AirBnB,
Wealthfront, CrunchBase, AngelList, Evernote, Dropbox, Netflix, Hulu, Upace, Yelp, MeetUp, Craigslist,
BlackBoard, Sakai.) Note: Be sure to indicate which app you are designing.

Vous aimerez peut-être aussi