I need help with finishing this discussion question, PLEASE NO PLAGIARISM: 

"Database Design and Implementation"  

Please respond to the following:

• Now that you have learned the concepts of database models and you have practiced creating entity relationship diagrams, let us focus on the implementation of that design into a Database Management System (DBMS).
  • Based on the example of the business function /operation that you described within the Weeks 1-3 discussions, describe the queries that you would need to create in order to support the business function /operation in question.
  • Based on the database model described in the Week 2 and Week 3 discussions for your business function /operation, determine the major /minor issues that might arise when creating these queries.

(Below is an attachment including the week 1-3 discussion questions and answers to use in assisting you to complete this assignment. As the instructions state, your response must be based on the functions/operations I have already described in the week 1-3 discussions. Thank you!)

PLEASE USE GOOD GRAMMAR AND PUNCTUATION. AGAIN, NO COPYING, THE ASSIGNMENTS ARE PLAGIARISM CHECKED BY TEACHER AND MYSELF. DOESN'T HAVE TO BE LONG JUST WHATEVER ANSWERS THE QUESTIONS (THIS IS NOT AN ESSAY). 

 

 

Week 1 Discussion 2 "Business Rules in Data Modeling" Please respond to the following: Per the text, when databases are developed, they are modeled around business
rules, so they accurately support a business function or operation.
Based on your experiences, identify one (1) example of a business function /
operation. Explain the business function / operation in the context of business data models.
Identify the business rules associated with your selected business function /
operation. Explain the manner in which such business rules would impact the design of a
database. RE: Week 1 Discussion COL LA PS E Overall Rating: 1 2 3 4 5 Hi Class,
I am going to take a shot at this but I don't think I fully understand what I read.I've worked
on many freight teams including Target, Babies 'R' Us, Petsmart, Dollar General, WIS
Inventory, and others. At most of these businesses a complete inventory control system was
utilized consisting of a POS system accompanied by RF scanners or the like. The database
for the inventory system held information for the products sold by the business. This
information included quantity on hand, quantity sold, where the items should be located in
the store, item descriptions and pricing, etc. The system was pretty much automatic as I
never had to order anything for the weekly truck to bring in because the system tells the
warehouse exactly what is being sold and how frequently. The warehouse in turn sent out
what was forecast by the system. When the truck arrives every week, we stock the floor
accordingly using the FIFO method. The products are sold and each item scanned at the
register sends a message to the inventory database that there is that many less in stock and
marks that product for refilling. Then the cycle repeats.
The business rules that go along with inventory control are knowing your start, update, be
cautious, and proper communication. Most businesses have automatic inventory tracking
and some are manual. In either instance, you need to know how much inventory is needed
at the start. For automatic systems, that number or forecast needs to be preprogrammed.
For manual inventory keepers, the business inventory should be kept up-to-date frequently.
For technical systems, the inventory will be kept updated each time an item is sold. Even
though our systems kept up automatically, though, we still did a manual inventory of the
entire store once a year. Being cautious involves looking out for theft from customers as well
as employees. This rule is of great importance because it directly effects the accuracy of the
system. When items are misplaced or stolen, the count for the inventory is thrown off.
Meaning that your system will display inventory counts that do not actually exist.
Communication is important, especially if more than one person is doing the inventory. So when inventory changes occur and are noticed that information should be shared. For
example, at the Dollar General I had access to see the quantities of all the products while I
stocked it. I did not have the access to manually make corrections to the counts shown,
though. So when the system showed that there were an amount on hand that was incorrect I
had to communicate that to the general manager so that they could verify and make the
necessary changes. These rules not being followed can affect the store in that we may have
too much or too little of products needed by our customers. That either affects the business
by customers choosing to go elsewhere or having too much product that doesn't sell,
resulting in possible wastes or overstocks of products we can't sell. Week 2 Discussion 1 "Relational Database Model" Please respond to the following: In the Week 1 discussion, you identified one (1) example of a business function or
operation and the business rules associated with that business function / operation. You will
build upon that discussion as you describe the main entities or objects of that business
function / operation in question, as well as the manner in which they relate to one another.
Describe the main entities or objects of the business function / operation.
Specify the attribute that would be the primary key for each entity, and provide a rationale
for why you selected such an attribute.
Determine whether the relationships between each of the chosen entities are
one-to-one, one-to-many, or many-to-many relationships. Justify your response.
Explain the key manner in which the business function / operation and the
business rules associated with that business function / operation support the relationships
mentioned above. Also, explain the fundamental ways in which the relationships could
change, based on the interpretation of the given business rules. RE: Week 2 Discussion 2 3 4 5 Hi Class, In our last discussion, I used Inventory control at the place of work as my operation and gave
what I think are rules that applied to it, some written and some implied. Some of the entities
I associated with this task, from start to end, are ORDERS, SHIPMENTS, ITEMS, INVENTORIES,
AND STORAGE.
The attributes are as follows (with the keys underlined): ORDER - Order Date, Order No.#, and Date Required.
SHIPMENT - Shipment Date and Shipment No.#.
ITEM - Item Name, Item No.#, Bar Code, and Item Description.
INVENTORY - Quantity, Item ID, Item Name, and Inventory ID.
STORAGE - Item Name, Position, Stategic Network Optimization(SNO#). The relationships between each of the entities are: ORDERS prepare SHIPMENTS - (One-to-One) Each order sent to a vendor yields one
shipment and vice versa.
SHIPMENTS deliver ITEMS - (One-to-Many) A shipment brings many items ordered but
each item ordered is brought on one shipment.
ITEMS provide INVENTORIES - (Many-to-Many) Many items mean various inventories
for the store and vice versa.
INVENTORIES replenish STORAGE - (One-to-Many) The storage/warehouse of a
business is stocked with many inventory items but each inventory is stored in one storage. I believe that the function and rules, we discussed in my first post on inventory control,
support the relationships I provide here by creating a system of checks and balances, so to
speak, that aid in the prevention of unwanted disruptions within the organization. Rules such
as no fraternization between certain levels of employees and specific roles given to
management alone, constant updates, caution, and communication ensure that the products
keeping the business alive continue to make it from the shipments to sales. I am sorry that
was a run-on, wasn't it? If these rules were not in place or were changed, I believe it could
lead to the cause of major issues involving missing stock, acts of favoritism, lawsuits, and
perhaps even the fall of a company. This would more than likely come as a result of
manager/employee relations/misconduct and neglected or poorly delegated responsibilities,
such as lower level employees handling manager responsibilities. Week 3 Discussion 1 2 "Entity Relationship Modeling" Please respond to the following: As explained throughout this course, entity relationship modeling is a critical element
of database design. If the database is not properly modeled, it is unlikely that the database
will be properly developed. Using this knowledge, explain the key reasons why entity
relationship modeling is important, and determine at least (1) way in which it impacts the
overall development of the database.
Analyze the key ways that entity relationship modeling helps database developers
overcome potential design challenges and conflicting goals.
For the database that you described in the Week 1 and Week 2 discussions,
determine the major / minor challenges that might exist when you are creating an entity
relationship diagram (ERD) for the business function / operation. RE: Week 3 Discussion 2 3 4 5 Entity relation modeling is of great importance. It provides a perfect tool of
communication that is used mostly to put business requirements together and provide
direction from the system design to the software development. It also helps in saving time
during the data gathering process as the database is being designed. It acts as a prototype,
so to speak, capturing all the semantics of the database in an easy and comprehensible way.
In this way, the entity relationship modeling proves to be an important step for database
design.
ER modeling has a significant impact on the database design. First, it makes the
database conceptualization easy. It helps give a clear understanding regarding the system
about to be designed. This is because it gives a graphical view into what you are required to
have as an end-result. It also helps in clearly viewing the relationship among entities in the
database.
ER modeling helps the developer in overcoming challenges in developing since it helps in
ensuring that all the required tables are included. It also helps the development team to
understand the database data structure and to make improvements to the system as opposed to designing the system without modeling. This helps the design team to clearly
design all the required entities and have the database run more effectively. It helps the team
to understand what to expect at the end of the system design. It finally helps the developers
to avoid leaving anything out any necessary values.
In developing an entity-relation diagram, it is not possible to show an entity to have
another instance, but the only instance it supports is that of record or objects being an
instance of entity types. Therefore, it gives the developer a problem to show this. Secondly,
a developer also faces a challenge since one cannot show a subtype relationship between an
entity and an instance which happens in the real time development. This way we cannot say
that designing an entity model is a walk in the park or it will give you all the requirements on
the system requirement. However, some challenges need to be taken care of to avoid
leaving some relationship in the database that might lead to failure of the entire database or
fail to meet the requirements of the database.

• 1493867636-CIS 111 Discussions wks 1-3 QnA.docx

ComputerScienceExpert

(11)

Status NEW Posted 04 May 2017 03:05 AM My Price 11.00

-----------

Attachments

file 1493867637-Solutions file 2.docx preview (51 words )

H-----------ell-----------o S-----------ir/-----------Mad-----------am ----------- Th-----------ank----------- yo-----------u f-----------or -----------you-----------r i-----------nte-----------res-----------t a-----------nd -----------buy-----------ing----------- my----------- po-----------ste-----------d s-----------olu-----------tio-----------n. -----------Ple-----------ase----------- pi-----------ng -----------me -----------on -----------cha-----------t I----------- am----------- on-----------lin-----------e o-----------r i-----------nbo-----------x m-----------e a----------- me-----------ssa-----------ge -----------I w-----------ill----------- be----------- qu-----------ick-----------ly -----------onl-----------ine----------- an-----------d g-----------ive----------- yo-----------u e-----------xac-----------t f-----------ile----------- an-----------d t-----------he -----------sam-----------e f-----------ile----------- is----------- al-----------so -----------sen-----------t t-----------o y-----------our----------- em-----------ail----------- th-----------at -----------is -----------reg-----------ist-----------ere-----------d o-----------n -----------THI-----------S W-----------EBS-----------ITE-----------. ----------- Th-----------ank----------- yo-----------u -----------

Not Rated(0)

• Buy Answer