ERD [entity relationship diagram] project application

Description

IMPORTANT: CHECK ADDITIONAL MATERIALS FOR COMPLETE STEP 2 … RAN OUT OF SPACE

Base this on the docx for the idea: https://1drv.ms/b/s!AmHjYBj31LB4gVV7fjQlEdUH0JIm

The idea for this project can be found in the docx and company of choice is DELL, which is mentioned in the docx for part 2, and the text highlighted in RED are the proposed table for the ERD diagram required for step 2, you can add some and improve upon the idea for the ERD diagram if need be. This not supposed essay or a big write-up, for step one just get to the point and answer whats required and brief.

For step Dedicate 1.5 pages (more if need be) for step 1 and the rest is for step 2 (this not write-up mostly ERD diagram for step 2)
Step 1): Discuss information requirements for the database application, addressing the following points.
Discuss background of the company (mentioned in docx included) and the industry they are in.

Discuss problems with the current way of doing business or with the current system, problems with obtaining timely and accurate vital information. Your database may not be able to resolve all problems identified here. Specify the problems your database is trying to solve (i.e.; scope of your solution) (should be very brief).

Provide detailed descriptions of business operations that will need or generate data for which you are designing the database. The write up here serves as the natural language description of data requirements. This is not the place to describe your tables or what the attributes are for the tables. This is where you describe business processes and business rules .

Use the four sentence templates to describe detailed data requirements that mostly match the data requirements descriptions in the last bullet. The sentences should start with Database needs to store. For cardinality of each relationship, start the two sentences with each. See the third bullet below. The descriptions of data requirements should be such that another person (say, someone in Operation Management Dept) can draw an ERD based on your descriptions. You may want to use bulleted statements to clearly state data requirements. Provide an example instance of each entity as well as for attributes of relationships. Here are some examples:
o (For entities, attributes, and primary keys). Database needs to store information about each Order. For each order, database needs to store OrderId, OrderDate, and Total dollar amount. OrderId is unique to each Order. Order example: Order1234 ordered on 3/1/2015, with a dollar amount of $540.

o (For relationships) Database needs to store information about what products are being ordered in each order.

o (For relationship cardinalities): Each order can contain multiple products. Each product can appear in multiple orders. For example, Order1234 ordered SKU78 and SKU72; Order34 ordered SKU72 and SKU83.

o (For relationship attributes): Database needs to store quantity and price of each product ordered in each order. (Or, for each product ordered in each order, database needs to store quantity and price.) For example, Order 1234 ordered Product SKU78 at $78/unit for 5 units. Order1234 also ordered SKU72 at $60/unit for 9 units.

Provide sample data for all data requirements as part of the submission. If the application environment uses any paper forms to collect data, fill out a set of forms with fictitious information as sample data and attach those forms as part of the submission. If the application environment does not use paper forms, provide screen captures or otherwise provide sample data (made up data are fine). If your project is made up, provide made up forms or data.

RAN OUT OF SPACE CHECK ADDITIONAL MATERIAL FOR STEP 2 (complete instructions)

RAN OUT OF SPACE CHECK ADDITIONAL MATERIAL FOR STEP 2 (complete instructions)

1
Base this on the docx for the idea: https://1drv.ms/b/s!AmHjYBj31LB4gVV7fjQlEdUH0JIm
The idea for this project can be found in the docx and company of choice is DELL, which is mentioned in the docx for part 2, and the text highlighted in RED are the proposed table for the ERD diagram required for step 2, you can add some and improve upon the idea for the ERD diagram if need be. This not supposed essay or a big write-up, for step one just get to the point and answer whats required and brief.
For step Dedicate 1.5 pages (more if need be) for step 1 and the rest is for step 2 (this not write-up mostly ERD diagram for step 2) Step 1):Discuss information requirements for the database application, addressing the following points. Discuss background of the company (mentioned in docx included) and the industry they are in.
Discuss problems with the current way of doing business or with the current system, problems with obtaining timely and accurate vital information. Your database may not be able to resolve all problems identified here. Specify the problems your database is trying to solve (i.e.; scope of your solution) (should be very brief).
Provide detailed descriptions of business operations that will need or generate data for which you are designing the database. The write up here serves as the natural language description of data requirements. This is not the place to describe your tables or what the attributes are for the tables. This is where you describe business processes and business rules.
Use the four sentence templates to describe detailed data requirements that mostly match the data requirements descriptions in the last bullet. The sentences should start with Database needs to store. For cardinality of each relationship, start the two sentences with each. See the third bullet below. The descriptions of data requirements should be such that another person (say, someone in Operation Management Dept) can draw an ERD based on your descriptions. You may want to use bulleted statements to clearly state data requirements. Provide an example instance of each entity as well as for attributes of relationships. Here are some examples: o (For entities, attributes, and primary keys). Database needs to store information about each Order. For each order, database needs to store OrderId, OrderDate, and Total dollar amount. OrderId is unique to each Order. Order example: Order1234 ordered on 3/1/2015, with a dollar amount of $540.
o (For relationships) Database needs to store information about what products are being ordered in each order.
o (For relationship cardinalities): Each order can contain multiple products. Each product can appear in multiple orders. For example, Order1234 ordered SKU78 and SKU72; Order34 ordered SKU72 and SKU83.
2
o (For relationship attributes): Database needs to store quantity and price of each product ordered in each order. (Or, for each product ordered in each order, database needs to store quantity and price.) For example, Order 1234 ordered Product SKU78 at $78/unit for 5 units. Order1234 also ordered SKU72 at $60/unit for 9 units.
Provide sample data for all data requirements as part of the submission. If the application environment uses any paper forms to collect data, fill out a set of forms with fictitious information as sample data and attach those forms as part of the submission. If the application environment does not use paper forms, provide screen captures or otherwise provide sample data (made up data are fine). If your project is made up, provide made up forms or data.
Step 2):Draw an E-R (ERD) diagram to represent your application according to your descriptions provided in Step 1), including the mapping ratios for relationships. The ERD you draw here should match your descriptions in Step 1, Bullet 4. Clearly identify attributes of entities and relationships. Each entity must have a primary key and necessary attributes. To save on diagramming effort, you may want to list all attributes of an entity inside the box for that entity. For each entity, underline or otherwise indicate the primary key. If writing out the attributes inside the box crowds the diagram, list the attributes for each entity separately, beneath the diagram if there is room, or on a separate page. If the meaning of an attribute is not self-explanatory, add explanations.
Example of ERD diagram: https://1drv.ms/i/s!AmHjYBj31LB4gVTMqSwDELKYf4Qf Make sure to point out the cardinality and when linking them whether 1 to 1 or 1 to many and so on ..

 
"Looking for a Similar Assignment? Get Expert Help at an Amazing Discount!"