EXPERTSMINDS.COM GIVES ACCOUNTABILITY OF YOUR TIME AND MONEY - AVAIL TOP RESULTS ORIGINATED COMP3771 DATABASE DEVELOPMENT ASSIGNMENT HELP SERVICES AT BEST RATES!
COMP3771 Advanced Database - Flinders University
Learning Outcome 1: Design and develop a complex database for a given scenario, with a professional approach to the documentation of the system
Learning Outcome 2: Construct SQL programs using advanced to ensure efficient processing
Learning Outcome 3: Detect and evaluate various key issues which affect database systems and their perfor- mance
Learning Outcome 4: Compare and contrast approaches for improving a database's performance.
ENROL WITH COMP3771 DATABASE DEVELOPMENT ASSIGNMENT HELP AND HOMEWORK WRITING SERVICES OF EXPERTSMINDS.COM AND GET BETTER RESULTS IN COMP3771 DATABASE DEVELOPMENT ASSIGNMENTS!
Database Design and Queries
Question: Find out more about the requirements of each user view so that you can define the type of data needed and the processing needed for the data.
24/7 AVAILABILITY OF TRUSTED COMP3771 DATABASE DEVELOPMENT ASSIGNMENT WRITERS! ORDER ASSIGNMENTS FOR BETTER RESULTS!
1.1 REQUIREMENTS
In this report we are going know about database design and its development. As we know collection of related data is database. And database management is a software designing database, in which all data are related to each other. Here we are going to design a supply chain management system which contains details of products, supplier and their order details. This system has been design to give real time solution to any wholesale store. It also stored detail order and their shipments details. By the use of this system the user can easily develop their business and can check all the details.
The features are the systems designed by us are as follows:
By the use of this system we can store different data in one database and easily retrieve it whenever needed.
This system can be used easily by any user.
By use of this system writing work for order or customer will be reduced.
In this system there multiple options for sell or buy product.
Business Rule of the supply chain management system:
Each customer can buy one or more products.
Each inventory has one or more product quality details
Each order table will have one or more products details.
All shipment will be related to one or more orders.
1.2 FACT FINDING
ER Model i.e. Entity-relationship model which use for representing database in diagrammatic way.t is blue print of any database and its main components are entity set and relational set.
Components of ER Model:
Primary Key:- A primary key is a key in a database which is unique field in the table.
Composite Key: A combination of one or more fields in a table is called composite key of a database.
Foreign Key: A foreign key of each table relate the child table with parent table.
Entity and attribute of the model:
Entity: SUPPLIERS
Attribute: SUPPLIER_ID, SUPPLIER_NAME ,TELEPHONE , ADDRESS , EMAIL ,CONTACT_PERSON
Entity: CATEGORIES
Attribute:CATEGORY_NAME
Entity: COMPONENTS
Attribute:COMPONENT_NAME ,COMPONENT_UNIT, COMPONENT_PRICE ,INSTOCK ,REORDER_THRESHOLD ,STORE_LOCATION
Entity: PURCHASE_ORDERS
Attribute:PURCHASE_ORDER_NUMBER,DATE ,STATUS ,SUPPLIER
Entity: PO_DETAILS
Attribute:PO_NUMBER,PO_LINE,COMPONENT,COMPONENT_CODE,PRICE_PER_UNIT ,QUANTITY , STATUS
Entity: USERS
Attribute:USERNAME,PASSWORD,PHONE ,EMAIL ,LASTLOGIN
Entity: SPONSORS
Attribute:SPONSORS_ID,SPONSOR_NAME,SPONSOR_TELEPHONE ,SPONSOR_ADDRESS,SPONSOR_EMAIL,SPONSOR_CONTACT_PERSON
Entity: GOODS_RECEIVED
Attribute:PO_NUMBER ,PO_LINE ,DATE_RECEIVED ,QUANTITY_RECEIVED
Entity: PROJECTS
Attribute:PROJECT_NAME
Entity: PROJECT_COMPONENTS
Attribute:PROJECT,COMPONENT,DATE,QUANTITY
1.3 REQUIREMENTS COLLECTION AND ANALYSIS
As per the requirement of database we need to create different user for designing the database. And we can the use of each user. If we have created user A1 for inserting and deleting data in Customer table then he can only do these functions.
1.4 DATABASE DESIGN
1.4.1 CONCEPTUAL DESIGN
NO PLAGIARISM POLICY - ORDER NEW COMP3771 DATABASE DEVELOPMENT ASSIGNMENT & GET WELL WRITTEN SOLUTIONS DOCUMENTS WITH FREE TURNTIN REPORT!
1.4.2 LOGICAL DESIGN
PK- Primary key
FK- Foreign Key
Table
|
Attribute
|
Data Type
|
Description
|
Constraint
|
SUPPLIERS
|
Supplier_id
|
NUMBER
|
supplier identification number
|
|
|
SUPPLIER_NAME
|
VARCHAR
|
supplier name
|
|
|
TELEPHONE
|
NUMBER
|
Supplier telephone
|
|
|
ADDRESS
|
VARCHAR
|
Supplier address
|
|
|
EMAIL
|
VARCHAR
|
Supplier email
|
|
|
CONTACT_PERSON
|
VARCHAR
|
Supplier contact person
|
|
CATEGORIES
|
CATEGORY_NAME
|
VARCHAR
|
Category name
|
PK
|
COMPONENTS
|
COMPONENT_NAME
|
VARCHAR
|
Component name
|
PK
|
|
COMPONENT_UNIT
|
NUMBER
|
Component unit
|
|
|
COMPONENT_PRICE
|
NUMBER
|
Component price
|
|
|
INSTOCK
|
NUMBER
|
|
|
|
REORDER_THRESHOLD
|
VARCHAR
|
|
|
|
STORE_LOCATION
|
VARCHAR
|
|
|
|
Sponser
|
NUMBER
|
|
|
PURCHASE_ORDERS
|
PURCHASE_ORDER_NUMBER
|
NUMBER
|
Purchase order number
|
PK
|
|
DATE
|
DATE
|
date of purchase
|
|
|
STATUS
|
VARCHAR
|
Status of purchase
|
|
|
SUPPLIER
|
NUMBER
|
Supplier of component
|
|
PO_DETAILS
|
PO_NUMBER
|
NUMBER
|
Purchase order details
|
PK
|
|
PO_LINE
|
NUMBER
|
|
|
|
COMPONENT
|
VARCHAR
|
|
|
|
COMPONENT_CODE
|
NUMBER
|
|
FK
|
|
PRICE_PER_UNIT
|
VARCHAR
|
|
|
|
QUANTITY
|
NUMBER
|
|
|
|
STATUS
|
VARCHAR
|
|
|
USERS
|
USERNAME
|
VARCHAR
|
User name
|
PK
|
|
PASSWORD
|
VARCHAR
|
|
|
|
PHONE
|
NUMBER
|
|
|
|
EMAIL
|
VARCHAR
|
|
|
|
LASTLOGIN
|
NUMBER
|
|
|
SPONSORS
|
SPONSORID
|
NUMBER
|
Sponsor unique code
|
PK
|
|
SPONSOR_NAME
|
VARCHAR
|
Sponsor name
|
|
|
SPONSOR_TELEPHONE
|
NUMBER
|
|
|
|
SPONSOR_ADDRESS
|
VARCHAR
|
|
|
|
SPONSOR_EMAIL
|
VARCHAR
|
|
|
|
SPONSOR_CONTACT_PERSON
|
VARCHAR
|
|
|
GOODS_RECEIVED
|
PO_NUMBER
|
NUMBER
|
Purchase order recieved
|
FK,PK
|
|
PO_LINE
|
NUMBER
|
|
|
|
DATE_RECEIVED
|
DATE
|
|
|
|
QUANTITY_RECEIVED
|
NUMBER
|
|
|
PROJECTS
|
PROJECT_NAME
|
VARCHAR
|
Project name
|
|
PROJECT_COMPONENTS
|
PROJECT
|
VARCHAR
|
|
FK,PK
|
|
COMPONENT
|
NUMBER
|
Component details
|
FK
|
|
DATE
|
DATE
|
|
|
|
QUANTITY
|
NUMBER
|
|
|
GET ASSURED A++ GRADE IN EACH COMP3771 DATABASE DEVELOPMENT ASSIGNMENT ORDER - ORDER FOR ORIGINALLY WRITTEN SOLUTIONS!
1.4.3 PHYSICAL DESIGN
DROP TABLE IF EXISTS PROJECT_COMPONENTS;
DROP TABLE IF EXISTS GOODS_RECEIVED;
DROP TABLE IF EXISTS PO_DETAILS;
DROP TABLE IF EXISTS PURCHASE_ORDERS;
DROP TABLE IF EXISTS COMPONENTS;
DROP TABLE IF EXISTS SUPPLIERS;
DROP TABLE IF EXISTS SPONSORS;
DROP TABLE IF EXISTS CATEGORIES;
DROP TABLE IF EXISTS USERS;
DROP TABLE IF EXISTS PROJECTS;
CREATE TABLE SUPPLIERS (SUPPLIER_ID int(5) NOT NULL AUTO_INCREMENT,
SUPPLIER_NAME varchar(120),
ADDRESS varchar(255),
EMAIL int(10),
TELEPHONE int(10),
CONTACT_PERSON int(10),
PRIMARY KEY (SUPPLIER_ID));
CREATE TABLE SPONSORS (SPONSORS_ID int(10) NOT NULL AUTO_INCREMENT,
SPONSOR_NAME varchar(100),
SPONSOR_TELEPHONE int(10),
SPONSOR_ADDRESS varchar(100),
SPONSOR_EMAIL varchar(100),
SPONSOR_CONTACT_PERSON int(10),
PRIMARY KEY (SPONSORS_ID));
CREATE TABLE CATEGORIES (CATEGORIES varchar(50) NOT NULL,
PRIMARY KEY (CATEGORIES));
CREATE TABLE USERS (USERNAME varchar(100) NOT NULL,
PASSWORD varchar(100),
PHONE int(10),
EMAIL varchar(100),
LastLoginint(10),
PRIMARY KEY (USERNAME));
CREATE TABLE PROJECTS (PROJECT_NAME varchar(50) NOT NULL,
PRIMARY KEY (PROJECT_NAME));
CREATE TABLE COMPONENTS (Components_IDint(10) NOT NULL AUTO_INCREMENT,
COMPONENT_UNIT varchar(255),
COMPONENT_PRICE int(20),
INSTOCK int(10),
REORDER_THRESHOLD varchar(255),
STORE_LOCATION varchar(100),
CATEGORIES varchar(50) NOT NULL,
SPONSORS int(10) NOT NULL,
USERNAME varchar(100) NOT NULL,
PRIMARY KEY (Components_ID), INDEX (INSTOCK));
CREATE TABLE PURCHASE_ORDERS (PURCHASE_ORDER_NUMBER int(10) NOT NULL AUTO_INCREMENT,
`DATE` date, STATUS varchar(255),
Privacy varchar(20),
UploadDate date,
`View` int(10),
ImagePathvarchar(50),
COMPONENTSCOMPONENT_ varchar(100) NOT NULL,
SUPPLIER_ID int(5) NOT NULL,
PRIMARY KEY (PURCHASE_ORDER_NUMBER));
CREATE TABLE PO_DETAILS (PO_LINE int(10) NOT NULL AUTO_INCREMENT,
COMPONENT varchar(100),
PRICE_PER_UNIT int(10),
QUANTITY int(10),
STATUS varchar(100),
COMPONENT_CODE int(10) NOT NULL,
PO_NUMBER int(10) NOT NULL,
PRIMARY KEY (PO_LINE));
CREATE TABLE GOODS_RECEIVED (PO_NUMBER int(10) NOT NULL,
PO_LINE int(10) NOT NULL,
DATE_RECEIVED date,
QUANTITY_RECEIVED int(10),
PRIMARY KEY (PO_NUMBER));
CREATE TABLE PROJECT_COMPONENTS (PROJECT varchar(50) NOT NULL,
COMPONENT int(10) NOT NULL,
`DATE` int(10),
QUANTITY int(10),
PRIMARY KEY (PROJECT));
ENDLESS SUPPORT IN COMP3771 DATABASE DEVELOPMENT ASSIGNMENTS WRITING SERVICES - YOU GET REVISED OR MODIFIED WORK TILL YOU ARE SATISFIED WITH OUR COMP3771 DATABASE DEVELOPMENT ASSIGNMENT HELP SERVICES!
Listed below some of the major courses cover under our Flinders University Assignment Help Service:-
- COMP1711 Database Modelling and Knowledge Engineering Assignment Help
- COMP1712 Software Engineering Principles and Practice Assignment Help
- COMP2711 Computer Programming Assignment Help
- COMP2781 Computer Mathematics Assignment Help
- COMP2812 Operating Systems Assignment Help
- COMP3712 Computer Programming Assignment Help
- COMP3722 Theory and Practice of Computation Assignment Help
- COMP3732 Enterprise Cloud Systems Assignment Help
- COMP3751 Interactive Computer Systems Assignment Help
- COMP3771 Advanced Database Assignment Help