Entity Relationship Diagram $($ERD$)$

SITUATION:

The BTMA $317$ P$2024$ class has made the decision to launch an online clothing store. We've collectively

agreed that leveraging our group expertise is the most effective approach for this endeavor. Our initial

step will involve developing an Entity Relationships Diagram $($ERD$)$ to model our business rules and data

structure.

The name of our company is The BTMA Extreme Soft Textile $($BEST$).$

BACKGROUND:

This proposed business venture is based on product familiarization with students. Buying clothing

online. Since most students are used to buying product online, hence, online business seems like an

obvious choice. Furthermore, one of our colleagues have managed to secure a secret investor for our

business. This secret investor has extreme high confidence in the class, that we were provided with

enough investments to open up a few stores across Canada from the onset. It was determined we will

re$-$evaluate our business effectiveness after a year of operation.

Interview notes with our investor and BTMA $317$ student

advisors:

Figure $1$: The BEST organization chart.

$1.$ Initially, we would like to have an Enterprise Resource Planner $($ERP$)$ system developed

optimally.

$2.$ Recognizing that our staff are our most valuable assets, we will maintain records of their first

name, last name, title, date of birth, supervisor, and working store locations.

$3.$ Figure $1$: Org$-$chart as suggested by our investor must be modeled into our ERD.

$4.$ We're committed to nurturing this business like a family. Therefore, we offer opportunities to

the children of our staff such as co$-$op$,$ internship, practicum, and summer job programs.

Programs availability and details are yet to be determined. We'll keep parent$-$child relationship

records of this arrangement to ensure staff children will receive job priority and associated

privileges.

$5.$ All store managers and staffs will work at their assigned store within their respective cities. For

starter, there will be one store per city. Store name will be preceded with the City name

followed by $$The BEST$$

$6.$ All BEST executives will work at the head office $($HO$)$ in Calgary, alongside with business analysts

and operation specialists.

$7.$ All BTMA $317$ students will act as external advisors and report directly to the VP Marketing.

$8.$ Membership advantages:

a$.$ Membership purchases are mandatory for all members, like those required by Costco$.$

b$.$ Memberships are offered in various levels, ranging from standard to platinum, catering

to diverse preferences and needs.

c$.$ To ensure that every customer feels valued, each will be assigned a unique customer

identification by our very own marketing department for future potential personalized

service.

$9.$ Payment:

a$.$ The BEST will accept cash and both debit and credit cards at all stores. This payment will

be designed now with the anticipation of other future payment methods such as using

crypto currency.

President

VP Marketing

Business

Analysts

BTMA $317$

student

advisors

Chief

Operating

Officer

Store

Managers

Staffs

Operation

Specialists

$10.$ Fashion:

a$.$ We cater to a diverse customer base with our extensive selection of clothing options.

b$.$ At times, special deals are available on our products to encourage customer loyalty. We

may feature different types of specials. So$,$ it's crucial to keep track of which ones are

currently active and which ones are not.

$11.$ More requirements may be included during the development phase of this MS Access ERP

system.

REQUIREMENTS:

Create an Entity Relationship Diagram $($ERD$)$ for The BEST. The ERD should

$1.$ Define primary $($PK$),$ foreign $($FK$),$ and composite $($CK$)$ keys within your ERD. Ensure all

appropriate keys are used, and composite keys must be minimized and grouped together for

clarity.

$2.$ Be thoughtful in how key names are used to reduce mistakes and misunderstanding. This can

make them easier for automatic ERD creation in Power BI$.$ This ETL $($Extract Transform Load$)$

process or importing process will be part of our assignment $3.$

$3.$ Ensure that all relationships have clear cardinality and participation constraints.

$4.$ Ensure all relationships are pointing between two attributes so it is clear which attributes you

are referring to$.$ Unclear relationships will be graded wrong.

$5.$ You must ensure there are no overlaps if you have multiple relationships pointing to an

attribute. You can add notes if you have multiple relationships pointing to the same one

attribute to provide clarity on cardinalities.

$6.$ The ERD must be in the $3$rd normal form.

SUBMISSION:

$1.$ It is highly recommended that assignment be completed using LucidChart$$ or MS Visio$.$

$2.$ The ERD must be converted to PDF format for submission.

$3.$ PDF File submissions that cannot be open from within D$2$L will be marked wrong.

$4.$ Submit early during UofC IT helpdesk and your ISP business hours, to ensure you can get

technology help as required.

RUBRICS:

$1.$ All ERD st