he following business scenario, create a Crow’s Foot ERD using a specialization hierarchy if appropriate for this case study.   Our website manages software projects for downloads to users. Each software project has a unique project id (8 characters long), can be assigned one or more categories (the categories are A, B ,C and D), has a status (D or P), and has a description (text of at most 256 characters). Some projects may depend on other projects and we keep track of the dependency. Each project is developed and owned by a single developer (who is our subscriber), and uploaded to our website in one or m

Given the following business scenario, create a Crow’s Foot ERD using
a specialization hierarchy if appropriate for this case study.

Our website manages software projects for downloads to users. Each
software project has a unique project id (8 characters long), can be assigned one or
more categories (the categories are A, B ,C and D), has a status (D or P), and has a
description (text of at most 256 characters). Some projects may depend on other
projects and we keep track of the dependency. Each project is developed and owned by
a single developer (who is our subscriber), and uploaded to our website in one or more
transactions.
Our users are identified by name (at most 20 characters), email (at most 20 characters),
and a unique user id (8 characters long). They can be either guest users or subscribed
users (subscribers for short). The subscribers have passwords (at most 8 characters) and
we keep the date of the subscription. They need the password to access our website tofile bug reports or upload software projects or update patches. A user can download any
project, the number of downloads per user per project is recorded. The subscribers can
file bug reports for any project. Every bug identified has an id (a positive integer) and a
description (text of at most 256 characters). The bug id’s must be unique for all bugs
concerning the same project. The date of filing of a bug report is recorded. Each bug
report deals with a single project and can report a single bug. Each bug report is made
by a single subscriber.
Some of our subscribers are developers. They develop the software projects and also
software updates for their own projects. Each update for a project has an id (8
characters long), a name (at most 20 characters), a status (P or U), a description (text of
at most 256 characters), and is assigned a particular type (the type are 1, 2 and 3). Each
update for a project is created by a single developer, the one who originally created the
project. Each update patch is uploaded to our website in a transaction.
Each transaction has an id (6 characters long) and a date when it took place. The
transaction id’s must be unique for all transactions concerning the same project.