Bead Bar Consulting

Bead Bar Consulting

Bead Bar should implement a distributed enterprise database system, due to the fact that “Bead Bar Onboard” my not be able to access a centralized enterprise database at times, this type of DBMS will also serve to protect the franchises from incurring system downtime in the event of a hardware or software failure at the central location. Administration is more complex with this model due to the number of databases in use, but given the logistics of having a mobile franchise like Bead Bar on Board, the merits outweigh the drawbacks. This DBMS should use the relational model because of its flexibility and ease of use; relationships between table s will need to be established in order for the users to be able to get the outputs they need. For example; the table containing order information will need to be linked to a table containing inventory data as well as a customer data table; this allows Rachel and Suzanne to track inventory levels, Miriam can track what customers are buying, and Julia can track sales. This could also be accomplished with the network model DBMS, but the complexity of the network model makes it more difficult to administer and maintain.

Implementing a data warehouse that stores a history of orders by customer will give Meredith and Miriam the information they need to identify and track sales trends, which in turn gives them the information they need to target a specific customer base through direct mailings and other marketing techniques.

Mitch is a special case; since his only interest is in tracking sales leads he may best be served with having a flat file model database that can be stored on his handheld pc or laptop. Having the capability of “uploading” customer and sales data to the database at the central office would be beneficial for him.