Database Administrator for Department Store
Scenario
The department store has expanded in the local region by opening five more bookstores, and the bookstore has launched a series of marketing campaign to increase sales and attract new customers. The objective of this technical report is to develop a plan to create and maintain an enterprise-wide database system that will assist the bookstore to hold the inventory and sales data. The database design will assist the organization to support the new marketing strategy, and align with the product initiatives.
Identification of the Potential Departmental and Sales Transaction to be Store within the Database
In the United States, the enterprise-wide relational database is very critical for the retail bookstore envisaging increasing sales within the contemporary business environment. To design a database to support the accuracy of the business information for the departmental store, there is a need to identify the potential sales transaction. This identification will avoid the redundant data within the enterprise relational database. The principal entities involved in the departmental and sales transactions for the bookstore are as follows:
Customers- They are the people who buy the product from the bookstore. The main attributes for customer's identifications are name, identification number, and address.
Customer History- attributes to identify customer's history are date of delivery, history identification number, and quantity delivered.
Publishers -- These companies supply book stocks to the stores. Main attributes are name, publisher identification number, address, and contact number.
Book- These are the product supplied to the bookstore and which are available for purchase. Main attributes are the ISBN, author, title, and price, amount in the inventory, subject area, and year of publication.
Store -- This is the location or actual premises where the transaction takes place.
Employees -- staff who work in the store and deal with the customers.
Transaction: Process of buying and selling of book product. Main attributes for identification are transaction number, number of books bought and sold, and the amount of money involved in the transaction.
All these makes up of the entities in the database design, and each entity has attributes allotted to them. The table below reveals the attributes for each entity.
Entity
Attribute
Customer
Customer ID
First Name
Last Name
Address
APT
City
Zip
Email
Book
Book ID
Book Number
ISBN
Publication Date
Publisher Name
Type
Price
Quantity
Employee
Employee ID
First Name
Last Name
Address
APT
City
Zip
Email
Hire Date
Term Date
Term Note
Book Author
Author ID
First Name
Last Name
Address
APT
City
Zip
Email
Date of Birth
Order Transaction
Price
Quantity
Total Price
Ship Date
Ship Type
Customer ID
Employee ID
Book ID
Sales
Products
Customer
Employee
Store
Store
Store Name
Address
Publisher
Publisher ID
Address
APT
City
Zip
Email
Web Address
All these attributes provide the information for the successful transactions in the departmental bookstore. The next step is to present the business rules associated with the business transactions as well the storage in the database. Bookstore transaction is similar to the business transaction; however, the department store will organize and store data to facilitate easy transaction.
2. Database Solution and Business Rules for the Sales Transaction
A business rule is a statement that imposes a form of constraint on an aspect of database. The business rules assist the organization to conduct business transactions effectively, and businesses rules provide business solutions for the database. The business rules are important for the database because they provide important method of data modification as well as the method data are created and deleted. The rules assist in determining the structure of the database. The proposed database provides the following business rules for the database design:
Rule 1:
When a customer order a book from the bookstore, the following business process must take place:
An order received from a customer.
An employee checks the inventory for product availability,
Employee confirms the customer's order,
The employees contacts warehouse,
The bookstore ships the product and invoice to the customer.
Rule 2
Department store has 5 stores that sell many books, and this is translated into a field constraint within the dataset. The designated code is also assigned to each store location. In the field, the assigned codes are valid.
Rule 3
A customer is allowed to generate many invoices,
Each invoice could be generated by one customer,
An invoice should contain one or more line, and each line associates with one invoice,
Publisher is allowed to supply many books,
Rule 4:
Each vendor is allowed to supply at least one product. This is represented by the relationship constraint within the database.
3. Evaluation of all Relationships...
Database Administrator, Manager of IT, and the value of a college education As a result of swift distribution of computers and information technology, a necessity for well trained workers to design and promote new hardware and software systems and to integrate new technologies. These workers comprises of computer systems analysts, database administrators, and computer scientists. Based on the choices and procedures of employers and on development of new areas of specialization
Databases and Regulatory Compliance Challenges The advent of technology has increased the popularity of database usage in firms, yet the legislation regulating the field has yet to be finalized. The changing nature of the IT sector, coupled with the legislative traits, creates several situations in which the companies find it difficult to comply with the regulations. This paper recognizes some of those difficulties, and also proposes some solutions. Databases Regulatory challenges for databases No
Design criteria exist at the levels of the technical, system integration aspects of the database to other systems through XML. This integration is critically important to ensure that the applications created can be effectively used over time and not have any scalability issues. There is also the need for designing the databases at the presentation layer to provide for scalability and flexibility of being able to create applications relatively quickly
Building a Database for Use in Scheduling Process The scheduling of various activities can at the moment be with the help of computer programs that implement the methodology of the critical-path method (CPM) (Choo et al.,2008). The requirements for building a database for use in scheduling process are numerous. For instance, each scheduler must have a separate database for storing information persistently. The server administrator and the application scheduler have
Security Issues for a Database System The biggest questions that any database system must check to ensure the proper operations of the system and the security of data within the system can be understood by following the three guidelines. The first question is to check whether the system administrators themselves are following the guidelines that have been established for the proper operations of the system. The second important question is to
They in short link and map ideas that already exist, creating real time answers to questions as they are applied to new and archived knowledge or action plans. According to IDC reports, most data warehouses will be stored in a columnar fashion and not in rows, reporting and data collection problems will be solved with databases that have no formal schema at all, horizontal scalability through clustering will be achieved
Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.
Get Started Now