IT211-SQL Project: Ronin Arms Inc DB

IT211- Structured Query Language 2011
INFORMATICS COMPUTER SCHOOL
DIT PROJECT
(IT211 Structured Query Language)
< Ronin Arms Inc. Database System>
Student No. Student Name Student Contact No. Class Code Description Centre Code Country Date of Submission
: 0535-0000-7999 : Ma. Carmen N. Lim : 09339731236 (MOBILE) : IT211 : Structured Query Language : 0535 : Philippines : February 8, 2011
RONIN ARMS INC/ CARMEN LIM/ DIT
TABLE OF CONTENTS
CHAPTER 1: INTRODUCTION AND CURRENT SYSTEM 1.1 Current System 1.2 Problems Encountered Due to the Current System 1.3 Proposed System Objectives 1.4 Benefits of the Proposed System 1.5 Organizational Chart
P. 3 P. 3 P. 3 P. 4 P. 4 P. 4
CHAPTER 2: DATABASE DESCRIPTION

2.1 Table Description 2.2 Attributes Description 2.3 Relationships (ER DIAGRAM)
P. 5 P. 6-16 P. 6-16 P. 17 - 25
CHAPTER 3: COMMAND LISTING
P. 26-39
CHAPTER 4: PROGRAM TESTING CHAPTER 5: USER MANUAL CHAPTER 6: CONCLUSION

ACKNOWLEDGEMENTS
P. 40-87 P. 88-100 P. 101 P. 102
IT211- Structured Query Language 2011 INTRODUCTION & CURRENT SYSTEM 1.1 Current System The Ronin Arms Inc. is known for supplying, distributing and trading weaponries and other materials relevant to the kind of merchandise they have. They have existed throughout the years even before the advent of technology so this would show that they were only relying on manual filing of these records after all these years. It took them until now to have the opportunity to obtain a desktop with the latest Operating System that holds programs that could write applications in all types including database publishers like MS ACCESS, They have been opened to this database publishing program so they wont be putting up with their old record storing ways for as long as they want.
1.2 Problems Encountered Due to the Current System Given the fact that Ronin Arms Inc. is manually storing company files, it posed plenty of difficulties and disadvantages on their behalf. These difficulties are in the form of disorganization & misplacement of files, tedious searching of files and sorting them got troublesome plus security risks for manually filing records means openness to human error. Security in Manual file storing is moderate to minimal and unstable which is a downer for Ronin Arms Inc. cause most of their records are classified because these records are what keep the relationship between their firearms products from their customers and the movements in the workplace. With all those problems getting out of hand the company acknowledged having an automated database system for their shop using SQL.
IT211- Structured Query Language 2011 1.3 Proposed System Objectives
A Database System that could contain and secure all the crucial information and details of Ronin Arms Inc. is the fitted system for proposition in this project. Since they are an armaments shop that would render that theyll need High & Tight Security for their information, MS ACCESS with SQL can answer to that with their administrative controls. This Database will be written using Structured Query Language by its encryptions that would be shown later on in this documentation. All in all, Ronin Arms Inc. will have a database that the company can entrust the essence of their work flow.
1.4 Benefits of the Proposed System
There are a handful of benefits from constructing the proposed system for Ronin Arms Inc. that are mentioned over and over again as you were reading this, if you noticed? To mention the data organization offered by making a database in MS ACCESS, the much more convenient manipulation and searching of these records in a database, A tough security system natural in the MS ACCESS program, which always asks for consent when opening a database. Easy editing and transpositions of these data records, and maybe more that arent realized yet the company would definitely much favored with this concept. 1.5 Organizational Chart
Gun Licensing Exchanges RONIN ARMS INC. FOUNDER/ OWNER/ MANAGER Camp Crame Q.C. Authority/ Gun Licenser
Various Weapons Manufacturers
Affiliates/ Contributors
ASST. MANAGER
STORE CLERK
DATABASE DESCRIPTION Tables are necessary in a Database especially when electronically schemed in MS Access through Structured Query Language for they are somewhat like a body for databases that holds data items in an organized and systematic manner. Without tables a database cant stand alone and keep records filed accordingly. In Ronin Arms Incs Database they have a table for each of the crucial elements in their company in terms of products and services. There are as many as six tables in their database that orderly gives them a spreadsheet view of their merchandise and five tables that interpret to them the activities that revolve around their shop. The tables in this database would center in our patron shops nature which is supplying and dealing firearms for Law Enforcers & Lawful Citizens for them to take advantage of against crime and anomalies. As this chapter of the documentation proceeds it will provide detailed information about the tables that were used in this database and how each of them contribute and function, from the storage of data to the administration of it. They will also be illustrated and scrutinized meticulously. To begin the analysis of every table present within the Ronin Arms Inc. database we should turn to the next page it will be exemplified as it should. The tables will be interpreted accordingly by their table classes, categories and columns. This chapter will also provide an Entity Relationship Diagram at the end.
IT211- Structured Query Language 2011 2.1 2.2 TABLE & ATTRIBUTES DESCRIPTIONS MERCHANDISE TABLES TABLE I: HANDGUNS
The Purpose of this table is to catalog & provide details about the Handgun Products stocked in Ronin Arms Inc. and a record of their dealings. TABLE COLUMNS & THEIR PURPOSE: HandGunID(PK): Gives Identification to handgun items in Ronin Arms Inc. HandGunModel: This names the Handgun Items stocked in Ronin Arms Inc. HandGunDescription: gives specifics on the Handgun Items stocked in Tonin Arms Inc. HandGunType: individually exacts the type of Handgun item listed. Price: puts value on the listed Handgun Item. ManufacturerID(FK): indicates the Handguns manufacturer this column is expandable through relations for elaborations. Status: shows the status of the Handgun in stock it will indicate its actuations. CustomerID(FK): associates the handgun item to a person who availed it is also expandable through relations. TABLE DATA TYPES & WIDTH: Number: QTY (3) Sized Double Text: QTY (4) Sized 225 each Currecy: Auto Sized
IT211- Structured Query Language 2011 TABLE II: LONGGUNS
The Purpose of this table is to catalog & provide details about the Longgun Products stocked in Ronin Arms Inc. and a record of their dealings. TABLE COLUMNS & THEIR PURPOSE: LongGunID(PK): Gives Identification to Longgun items in Ronin Arms Inc. LongGunModel: This names the stock of Longgun Items of our patron shop LongGunDescription: gives specifics on the Longgun Items stocked in Ronin Arms Inc. LongGunType: individually exacts the type of Longgun item listed. Price: puts value on the listed Longgun Item. ManufacturerID(FK): indicates the Longguns manufacturer this column is expandable through relations Status: shows the status of the Longgun in stock it will indicate its actuations. CustomerID(FK): associates the handgun item to a person who availed can be expanded through relations.
DATA TYPES & WIDTH: Number: QTY (3) Sized Double Text: QTY(4) Sized 255 Currency: AutoSized
IT211- Structured Query Language 2011 TABLE III: MELEE ARMS
The purpose of this table is to catalog & specify details about the Melee Armaments Avalable in Ronin Arms. Inc. Actuations of this product should also be shown in here. TABLE COLUMN & THEIR PURPOSE: WeaponID(PK): gives Identification to the Melee Weapon stocked in Ronin Arms Inc. WeaponName: gives a name to address the stocked Melee Weapon Item in Ronin Arms Inc. WeaponDescription: implies specifications and details about the Melee Weapon Item Listed. WeaponType: exacts what type of Melee Weapon Item is listed. ManufacturerID(FK): Elaborates the manufacturer for the melee weapons stocked in Ronin Arms Inc. InStock: gives a count of Melee Weapons available in Ronin Arms Inc. Sold: counts the number of Melee Weapons Sold. DATA TYPE & WIDTH: Number: QTY (4) Double Sized Text: QTY (3) Size 255 Currency: Auto Sized
IT211- Structured Query Language 2011 TABLE IV: ACCESSORIES
The Purpose of this table is to catalog and produce exact details about the Accessories for Armaments in Ronin Arms Inc. Actuations of this product category should be shown here.
TABLE COLUMNS & THEIR PURPOSE: AccessoryID(PK): Gives Identification for the FireArm Accessory Item in Ronin Arms Inc. AccessoryName: names the Accessory Item stocked in Ronin Arms Inc. AccessoryDescription: Gives specifics about the Firearm Accessory Item listed. AccessoryType: states what type of firearm accessory is listed. Price: Indicates the cash value of the Accessory Item listed. ManufacturerI(FK)D: Elaborates the manufacturer for the Firearm Accessories listed. InStock: Counts the number of Firearm Accessories available in Ronin Arms Inc. Sold: Counts the number of Firearm Accessories Sold in Ronin Arms Inc.
DATA TYPES & WIDTH: Number: QTY (4) Double Sized Text: QTY (3) Size 255 Currency: Auto-Sized
IT211- Structured Query Language 2011 TABLE V: EQUIPMENTS
The Purpose of this table is to catalog and give out precise details on Equipment Stocks and sales in Ronin Arms Inc.
TABLE COLUMNS & THEIR PURPOSE: EquipmentID(PK): serves as Identification for Firearm Equipment Products of Ronin Arms. Inc. EquipmentName: Addresses the FireArm Equipment Item listed. EquipmentDescription: Implies specifics about the Firearm Equipment Item listed. EquipmentType: Indicates the type of Firearm Equipment that is Listed ManufacturerID(FK): will provide elaborate details on the manufacturer of the Firearm Equipment Product Listed InStock: Counts the stock of Firearm Equipment Products available in Ronin Arms Inc. Sold: Counts the number of FireArms Equipments Products sold.
DATA TYPE & WIDTH: Number: QTY (4) Double Sized Text: QTY (3) Size 255 Currency: Auto-Sized
10
IT211- Structured Query Language 2011 TABLE VI: AMMOS
This tables purpose is to catalog and provide detailed information & sales regarding Ronin Arms Inc. Ammunition Products.
TABLE COLUMN & THEIR PURPOSE: AmmoID(PK): Identifies the Ammo Item in the AMMOS Table. AmmoBrand: Shows the brand of the Ammo Item Listed. AmmoType: Indicates the type of Ammo Item Listed. Price: Shows the monetary value of the Ammo Item Listed. InStock: counts the number of AMMO Item boxes in Ronin Arms. Incs stock. Sold: counts the number of AMMO Item boxes sold in Ronin Arms Inc. LicenseID shows the License of dealership of the Ammo Products Listed.
DATA TYPE & WIDTH: Number: QTY(3) Double Sized Text: QTY (3) Size 255 Currency: Auto Sized
11
IT211- Structured Query Language 2011 COMPANY BODIES & ACTIVITIES TABLE TABLE I: MANUFACTURERS
This tables purpose is to, of course, list down the manufacturers that are associated with the dealings of Ronin Arms Inc. and also give out enough description about them too. This table relates to other tables in the Ronin Arms Inc. database that rely on this piece of information.
TABLE COLUMN & THEIR PURPOSE: ManufacturerID(PK): Gives out an Identity to the Manufacturer present in this table. Manufacturer: Presents the name of the manufacturer present in the table. Details: Gives important piece of information about the manufacturer listed. LicenseID(FK): States what kind of license do these manufacturers posses regarding firearms, this field is expandable for further information through relation.
DATATYPE & WIDTH: Number: Double Sized Text: Size 255
12
IT211- Structured Query Language 2011 TABLE II: CUSTOMERS
The purpose of this table is to keep a tight record of the customers & their particulars who visit and purchase from the shop. Most of the customers listed here however are the ones who make gun transactions.
TABLE COLUMN & THEIR PURPOSE: CustomerID(PK): gives identification for each recorded Customer. SurName: Shows the Customers Surname or Last Name. ForeName: Shows the Customers First and Forename. Gender: determines if a Customer is Male or Female Age: States the age of the Customer Recorded ContactNumber: Provides the Customers contact details. Email: Gives the customers Email Address. HomeAddress: Shows the Customers residence and location for mailing and security matters. DistinguishingFeatures: Gives the unique physical features of the Customer in case of problems. HandGunID(FK)/ LongGunID(FK)/ WeaponID(FK)/ AmmoID(FK) /LicenseID(FK): These fields show the product purchase and ownership of the customers. These fields are expandable and can give more information through table relations.
13
IT211- Structured Query Language 2011 TABLE III: EMPLOYEES
This Tables Purpose is to have a listing of employees that work an run the company this is just to monitor the employees standings in the company for evaluations and the like.
TABLE COLUMN & THEIR PURPOSE: EmployeeID(PK): Gives Identification to the store Employees of Ronin Arms Inc. FullName: Shows the fullname of Employees in Ronin Arms Inc. Age: Specifies the age of the Employee in the shop. Gender: determines whether an Employee is Male or Female ContactNum: Gives out the contact info of the Employee HomeAddress: Shows the current residence and location of the employee. Position: Shows the Job Position of the Employee Salary: Records the amount of income the employees earn. LicenseID(FK): Elaborates information about the Employees type of license regarding firearms.
DATATYPE & WIDTH: Number: QTY (3) Double Sized Text: QTY (5) Size 255 Currency: Auto Sized
14
IT211- Structured Query Language 2011 TABLE IV: EMPSCHED
This tables purpose is to act as the Work Schedule Table of employees that are working in Ronin Arms Inc and be a basis if anyone is late or on time.
TABLE COLUMN & THEIR PURPOSE: EmpSchedID(PK): Represents the Identification of a work schedule row. WorkDay: The specific Day an Employee should report to work in the shop this is based on the days of the week format (MTWThFStSn) TimeIn: The Time an Emplioyee is expected to start working in the shop TimeOut: The Time an Employee is expected to close and leave the shop EmployeeID(FK): This distinguishes the Employee that logged in a certain date and timeline.
DATATYPE & WIDTH: Text: Size 255 Date: Not Specified Time: Not Specified Number: Double Sized
15
IT211- Structured Query Language 2011 TABLE V: LICENSESHIP
The purpose of this table is to show further details on firearm licensing in Ronin Arms Inc. This table provides much specifics on licenses. It relates to other table that rely on this type of information.
TABLE COLUMN & THEIR PURPOSE:
LicenseID: Gives Identification to a certain firearm license present in the Table. LicenseType: Specifies the type of firearm license listed in the table Details: Gives out important details and information regarding on the specific firearm license present in the table.
DATA TYPE & WIDTH: TEXT: QTY (3) size 255
16
IT211- Structured Query Language 2011 1.3 Relationships Description ENTITY RELATIONSHIP DIAGRAM (FOR THE TABLES IN RONIN ARMS INC. DATABASE) Heres a graphic representation of the table relations in the Ronin Arms Inc. Database. As you can see, every primary key assigned in this table holds one-to-many relationship with their foreign keys from other tables, this is so
because these PKs records correspond to the exact same records which are known as Foreign Keys of its fellow tables. Each Primary Key (PK) relates as one-to-many to all of the records it has likeness with that also exists in its co-tables which are referred to as Foreign Key (FK)
17
IT211- Structured Query Language 2011 *The following relationships were coded in this format*
ALTER TABLE CUSTOMERS ADD CONSTRAINT CUSTOMERS_HandGunID_FK Foreign Key(HandGunID) REFERENCES HANDGUNS(HandGunID)
we shall breakdown our ER Diagram in this portion by each of the tables in our database individual relations to the other.
HANDGUNS Table Relations
The image you are seeing at the left of this text is depicting every relationship of our
HANDGUNS table.
Its Primary Key is set as the HandGunID Field and links to the CUSTOMERS table as a Foreign Key there, this
relationship results as One-Is to-Many. HANDGUNS relationship to the CUSTOMERS table is important because it shows its interaction with the customers and both ways.
HANDGUNS is also related to the MANUFACTURERS table since it has the field ManufacturerID in it as the foreign key for MANUFACTURERs table. This relationship shows as One-to-Many HANDGUNS and MANUFACTURERS table will indicate what handgun product is associated with a manufacturer.
18
LONGUNS Table Relationships
Our LONGGUNS table is related with the and
CUSTOMERS
MANUFACTURERS table.
LONGGUNS
table
has
the LongGunID field as its Primary Key, this key is a foreign key in
CUSTOMERS table and expresses the long gun
products relationship with the customers in that
table and vice versa.
LONGGUNS is also related to the MANUFACTURERS table since it has the field ManufacturerID in it as the foreign key for MANUFACTURERs table. This relationship shows as One-to-Many LONGGUNS and MANUFACTURERS table will indicate what longgun product is associated with a manufacturer.
19
MELEE ARMS table Relations
The MELEE ARMS table is associated with CUSTOMERS the and
MANUFACTURERS Table and its with
relationship each MANY. is
ONE-TO-
It
has
WeaponID
field as its Primary key it relates to THE CUSTOMERS table as an indication of its interaction with the records in that table.
It is related with the MANUFACTURERS table as to identify the products listing from the MELEE ARMS table with the records in the related table mentioned.
20
AMMOS Table Relations
The (short
AMMOS for
ammunitions) table Is related with the
CUSTOMERS and LICENSESHIP tables as ONETO-MANY.
It
has
the
AmmoID field as its Primary Key. And relates this as key a
foreign key to the CUSTOMERS table to indicate its interaction with the records there.
This table is related with the LICENSEHIP table with LicenseID field the so the AMMOS table can recognize the license of its items using the LICENSESHIP table.
21
ACCESSORIES table relations
As you can see, our ACCESSORIES table is only related with the
MANUFACTURERS table it is not related with the customers as these tools are not required much monitoring since these harmless when purchased without armaments. It is products related are with
MANUFACTURERS as ONE-to-MANY via the Foreign key ManufacturerID this relationship indicates who manufactured the product records in the ACCESSORIES table.
EQUIPMENTS table relataions
the
EQUIPMENTS
table is related with the MANUFACTURERS table basing on the picture on the left. The primary ManufacturerID key in
MANUFACTURERS table connects with the ManufacturerID foreign key in the EQUIPMENTS table only to indicate what manufactured the items in the EQUIPMENTS table.
22
IT211- Structured Query Language 2011 CUSTOMERS Table Relations
CUSTOMERS table is related with HANDGUNS, LONGGUNS, LICENSHIP, MELEEARMS, and AMMOs as ONE-TO-MANY. These relationships show the interaction of the customers in the records of the related table. The LICENSESHIP table shows what license the entities in the customers table posses. (Im not sure why the CUSTOMERS table duplicated in the table relationships panel and I couldnt correct it, I was trying however.)
23
EMPLOYEES table & EMPSCHED table relations
EMPLOYEES
table
is
related
with
EMPSCHED table and LICENSESHIP table as ONE-TO-MANY.
EMPSCHED is related to EMPLOYEES table alone and expresses the schedule being followed by the EMPLOYEES in Ronin Arms Inc.
EMPLOYEES
is
linked
with
LICENSESHIP via the field LicenseID key. To identify what license the employee records are under in.
MANUFACTURERS table relations
MANUFACTURERS
table
stretches to HANDGUNS, LONGGUNS, ARMS, MELEE
ACCESSORIES, LICENSESHIP,
EQUIPMENTS one to many.
table
as
It is linked to all those table only to describe the
manfucaturer of records in tables it is related to.
for the
24
LICENSESHIP Table Relations
Table LICENSESHIP table relates to EMPLOYEES, CUSTOMERS, AMMOS, MANUFACTURERS table as ONE-TO-MANY and describes the Licenship of each of the records in the relative tables via the LICENSESHIP tables primary key and the other tables primary key which shares the LicenseID key field
COMMENT: realized that Primary Key and Foreign keys arent just markers and identifier s in a table they are the main element for relating tables.
25
IT211- Structured Query Language 2011 SQL COMMAND LISTING
Of course, A database with tables in MS Access, most probably, wont work on its own without the help of Statements, Syntaxes, clauses, functions, and keywords brought by Structured Query Language. These are like the building blocks of an entire Database, It acts out as a fastener that binds the elements of the contents in a database. As for the Ronin Arms Inc. database there were bundles of these codes, which behaved as commands, which were applied to keep up with the complexity of the design which was formed with the idea of firmness, stability, accuracy, reliability and trustiness. In the making of the project, it was realized that this codes has their own unique purpose and abilities that affects a database. Their differences resulted into the grouping of them to categories as some of these codes executes as, either, for authoring, editing, searching and retrieval. These codes are the ones that bring action to a database. There were as many as possible codes that were incorporated in this database so that it would work precisely in accord with the standards of the Ronin Arms Inc. Firearms Shop. The codes and encryptions in these databases performs as commands and they will be listed down in this chapter in ordinance and by categories based on how these commands affect the database. There are three of these categories that the maker of this database came up with and those are Authoring which are codes that form and shape up the database, Editing Which makes insignificant and singular changes in the database and Functional those codes that allows the access and manipulation of the
databases contents. The listing of these commands will begin at the next batch of pages.
26
AUTHORING COMMANDS These are the commands that were used for the construction and formation of this Database.
CREATE TABLE COMMAND The SQL coding used to construct tables for the Ronin Arms Inc. Database.
The manner of coding used to create a new table in MS ACCESS with SQL. This coding is responsible for all the tables contained in the Ronin Arms Inc. Database.
INTO COMMANDS
Recreating A New Table The SQL coding used to make a table duplicate itself in the form of another table using the INTO command. This type of SQL coding is actually of full use for BACKING UP your tables.
Copying Certain Fields To A New Table This SQL coding creates another table where copies of distinct fields called in the SELECT statements will be placed there. Necessary for backing up a selected few fields as desired.
27
IT211- Structured Query Language 2011 Copying A Single Row To A New Table This SQL coding will duplicate a specified row into a new table.
ALTER COMMAND
ADD These are SQL keyword used to ADD a column in an existing table in the Ronin Arms Inc. Database.
DROP This is the SQL keyword I used to drop or remove a certain column in a Table.
COLUMN This SQL Keyword was used to change the Data Type of a certain field into another Data Type desired.
INSERT INTO COMMAND This is a standard SQL Coding for imputing records in a Table within a database in MS Access. I Used this for Ronin Arms Inc.s behalf.
28
IT211- Structured Query Language 2011 EDITING COMMANDS These are SQL Commands that makes changes in a Table that doesnt entirely influence its structure and the database. This only makes slight changes depending on specific positions in a database table.
UPDATE COMMANDS Updating a Single Row in a Field Its label says it all, this SQL coding SETs a new value to a specific field row in a Table.
Updating All Rows in a Field This SQL coding SETs a new value to a whole field specified. FUNCTIONAL AND ACCESSIBILITY COMMANDS SELECT COMMANDS Selecting all Fields in a Table This SQL Statement is used to display all fields in a specified table in a database.
Selecting a Single Field in a Table This SQL Statement is used to display a single field in a specified table in a database.
Selecting Several Fields in a Table This SQL Statement is used to display Several fields in a table depending on how many fields you want to show.
29
ARITHMETIC OPERATORS These are Mathematical Symbols used for numerical data calculations in SQL. The usual (+) sign for addition, minus (-) sign for subtraction, Slash (/) for division and Asterisk (*) for multiplication.
Operator Precedence Arithmetic Operators in SQL follow the MDAS precedence where the command will calculated for the Multiplication first then go for Division then Addition and Subtraction at last.
Parenthesis in Arithmetic Operators Equations in a parenthesis are prioritized by these SQL Operators disregarding the precedence.
30
IT211- Structured Query Language 2011 ALIAS KEYWORD Is that code that gives another name to a column with the AS keyword Aliasing Table Fields With Spacing If we are going to name a table with word spacing we will put the new name for the field inside a bracket. Aliasing Table Fields Without Spacing If we are going to give a new name that doesnt need spacing like say the word NAME to a column we wouldnt use brackets we will just type a name straight beside the AS keyword. DISTINCT COMMAND This SQL keyword shows a specified column without redundant rows. WHERE COMMAND The WHERE SQL Statements are useful in locating records in a database it gives a records exact position in a table. This command is helpful in searching a database.
31
IT211- Structured Query Language 2011 Conditional WHERE Statement This is an SQL Clause where in its function is to present the condition between a table record and a value given whether they are equals, one is lesser or greater than the other. LOGICAL OPERATORS AND The AND logical operator expresses verification between two records in certain columns. Both records will be true.. OR The OR logical operator verifies one of the two records being options in given columns. Either one of the records will be true.. ORDER BY COMMAND The ORDER BY command can sort table records in a given column by Column Name, Ascending (first to last order) or Descending order (from last
to first order).
32
IT211- Structured Query Language 2011 TOP COMMAND This Command is to display the TOP records in your table by the value entered or by percentage. In the Image, only 5 records are being asked to be displayed.
LIKE COMMAND This COMMAND is mostly used in advanced searches for records in table
columns.
IN COMMAND This SQL Keyword is also used for accurate searching of more than one record. BETWEEN COMMAND This command displays all records that is between two given records in a field.
33
IT211- Structured Query Language 2011 NOT BETWEEN COMMAND Shows records that are not between two records. JOINS Inner Join Only returns rows that has a match from table to table.
Left Join Return all rows from the left table, even if there are no matches in the right table
Right Join Return all rows from the right table, even if there are no matches in the left table
UNION COMMAND Distinctive Union Shows union between two sets of Columns from different tables that could be distinct or redundant in mode.
34
AVG COMMAND The AVG function stands for the average value of the numeric records in a table.
SUM COMMAND This functions totals the numeric records in a whole field that is specified.
ROUND COMMAND This functions rounds of records in a certain numeric column by the decimal asked for it.
COUNT COMMAND Count Records In a Specific Column This function counts records in a certain column.
Count All records in a Table This function counts records in all fields.
35
IT211- Structured Query Language 2011 FIRST FUNCTION
Shows the very first record in a column. LAST FUNCTION This function shows the very last record in a column
MAX COMMAND Shows the record with the highest value in a specific numerical column.
MIN COMMAND Shows the record with the lowest value in a specific numerical column.
UCASE COMMAND This Command turns records in a specific field into all capital letters.
LCASE COMMAND This Command turns records in a specific field into lower case lettered.
36
IT211- Structured Query Language 2011 MID COMMAND Shows the characters in the middle part of all records in a certain field.
LEN COMMAND This command counts the number of characters that are in each record in an entire column. GROUP BY This Command groups certain rows by the given column.
CONCATENATION This syntax is used to merge columns in a table by using the ampersand (&) symbol. LITERALS This coding is used to put a label or add a word description beside the record values in a column. These codes are entered with single quotes ()
37
INSTR COMMAND This command gives out the number and position of a single character amongst records in columns. STRCONV COMMAND
This command converts record strings into: 1 ALL CAPS; 2-LOWER CASE; 0-Default.
MOD COMMAND This code performs the Dividend and Divisor method in a record in a column.
TRIM This clause is used to print out a message on your table and reduce spacing in your record cells.
38
IT211- Structured Query Language 2011 NZ Function
This Command lets you return a value when a variant is null.
PARAMETERS Parameter codes are used for a much more precise and direct search of tables and filtering datas:
SUBQUERIES
a query that is nested inside a SELECT, INSERT, UPDATE, or DELETE statement or inside another subquery.
Those were the whole of the commands that were used in the Ronin Arms Database System which are going to be commonly used by authorized personnel in the company. There are yet to be commands that would be added as this table will continue to develop, Like NULL, DATE & TIME FUNCTIONS, & CASES This table is designed to expand along with the companys growth.
39
IT211- Structured Query Language 2011 PROGRAM TESTING Test Plan The components of this database system would be tested accordingly by their significance on the database contents. Test Cases and Results The Testing of the programs will go like: Test Case Objective : : 1 To see whether the code for creating tables does its job. ( using CUSTOMERS Table as our standard) Test Data :
Expected Test Result
: It should produce a table named customers in the navigation bar.
Actual Test Result :
Conclusion well without errors.
the table code format used for all tables worked
40
Test Case Objective
: :
2 To see whether the code for inserting data values into tables does its job. ( using CUSTOMERS coding as our standard)
Test Data
: the data records should be imputed in our
Sample Customers Table. Which we made in test case 1.
Conclusion
the insert into code to put records in our table
worked as expected without errors.
41
Test Case Objective
: :
3 To check if the SELECT ALL code indeed displays
all fields in an opted TABLE.
Test Data
: The code should display all fields in the opted table when ran.
Conclusion
the code works properly without errors
42
Test Case Objective
: :
4 To check if the code for SELECT SINGLE FIELD
indeed displays one specified field in an opted TABLE.
Test Data
: The code should display a field in the opted table when ran.
Conclusion
43
Test Case Objective
: :
5 To check if the code for SELECT MORE THAN
ONE FIELD indeed displays one specified fields in an opted TABLE.
Test Data
: The code should display specified fields in the opted table when ran.
Conclusion
44
Test Case Objective
: :
6 To check if the code for Division Arithmetic
Operator does divide values in a numerical field in an opted table.
Test Data
: The code should divide values in a numerical table field and shows its quotient as an expression.
Conclusion
the code computed for the quotient of the
numerical table field called in this table and outputted it as Expr1002 with no errors.
45
Test Case Objective
: :
7 To check if the code for Division Arithmetic
Operator does multiply values in a numerical field in an opted table.
Test Data
: The code should multiply values in a numerical table field and shows its product as an expression.
Conclusion
the code computed for the product of the
numerical table field called in this table and outputted it as Expr1002 without errors
46
Test Case Objective
: :
8 To check if the code for addition Arithmetic
Operator does add values in a numerical field in an opted table.
Test Data
: The code should add values in a numerical table field and shows its sum as an expression.
Conclusion
the code computed for the SUM of the numerical
table field called in this table and outputted it as Expr1002 without errors
47
Test Case Objective
: :
9 To check if the code for Subtraction Arithmetic
Operator does subtract values in a numerical field in an opted table.
Test Data
: The code should subtract values in a numerical table field and shows its difference as an expression.
Conclusion
the code computed for the difference of the
numerical table field called in this table and outputted it as Expr1002 without errors
48
IT211- Structured Query Language 2011 Test Case Objective : : 10 To check if the Alias Keywords for spacing in our
table does change a column name of a field in the opted table.
Test Data
The code should compute the values of a
numerical table field in MDAS precedence. Actual Test Result :
Conclusion
the code did change the name of the column name
in the third to the right field of our model table.
49
IT211- Structured Query Language 2011 Test Case Objective : : 11 To check the ALIAS keyword without spacing does
change the name of a column name in a word without spaces.
Test Data :
: the code should change the name of a column in a word without spaces.
Conclusion without spacing.
the code did change a column name into words
50
Test Case
12
Objective
to see whether our DISTINCT clause shows a field
in a opted table without any key or record duplicates!
Test Data
: the code should not display the duplicate keys or records in a field of the opted table.
Conclusion
the code did compute for the value in the
numerical table field inside the parenthesis first then the outer equation, Error free!
51
IT211- Structured Query Language 2011 Test Case : 13
Objective
to test if the WHERE clause for conditioning really
does compare a fieldname and a value in the table
Test Data
: the code should only display field records in the EMPLOYEES table that is lower than 50,000.00
Conclusion
the
code
compared the field
name
values
successfully without errors.
52
Objective
to test if the WHERE clause that uses a single
quote for searching character values in a table works.
Test Data
: the code should only display a table record value of F for the gender of the customers since F is what is being looked for in the WHERE clause
Conclusion
the code only did display those entities in the
customers table that has the gender F
53
Objective
to test if the WHERE clause that doesnt use
quotations for searching numeric values in a table works.
Test Data
: the code should only display a table record value of all entities in the CUSTOMERS table that is aged 45.
Conclusion
the code only did display those entities in the
customers table that has the age of 45.
54
Test Case
16
Objective
to test if the AND logical operator does verify the
values of two records in a table.
Test Data
: the AND operator in the code should show that both record values being compared is TRUE.
Conclusion
the code worked successfully and showed both
values are true in a table row.
55
Test Case
17
Objective
to test if the OR logical operator does verify either
values of the two records in a table.
Test Data
: the OR operator in the code should show that one of the two record values being compared is TRUE.
Conclusion
the code worked successfully and expressed that
two table rows has either values that are true.
56
Test Case
18
Objective
to test if the ORDER BY command sorts values in
the table by its assigned fieldname.
Test Data
the ORDER BY command should sort table
records by the assigned fieldname it wants it to be organized.
Conclusion
the code worked successfully and ordered the
table records by the assigned field name.
57
Test Case
19
Objective
the table in ASCENDING order.
Test Data
records in Ascending order alphabetically starting from A.
Conclusion
the code worked successfully and ordered in
ascending order without errors.
58
Test Case
20
Objective
the table in Descending order alphabetically from the last letter.
Test Data
records in Descending order alphabetically starting from the last letter of its sequence.
Conclusion
the code worked successfully and ordered in
descending order without errors.
59
Test Case
21
Objective
to test if the LIKE Keywords precisely searches for
a table record that start with letter S for our sample.
Test Data
: the command should show all table records that starts with the letter S
Conclusion
the command did show all table records that
begins with the letter S like it was asked to.
60
Test Case
22
Objective
a table record that ends with letter S for our sample.
Test Data
: the command should show all table records that ends with the letter S
Conclusion
the command did show all table records that ends
with the letter S like it was asked to.
61
Test Case
23
Objective
a table record that has with letter that follow a certain pattern.
Test Data
: the command should show all table records that has the letter pattern nage
Conclusion
the command did show all table records that has
with the letter pattern nage like it was asked to.
62
Test Case
24
Objective
to test if the IN Keyword shows the values being
asked for it like the surname in the customers table shown in the image below.
Test Data
the command should display the customer
surname being asked in our code.
Conclusion
the command worked successfully without errors.
63
Test Case
25
Objective
to test if the BETWEEN with logical operator AND
Keyword shows the values being asked for it
Test Data
: the command should display the values being asked in our code.
Conclusion
64
Test Case
26
Objective
to test if the NOT BETWEEN with logical operator
AND Keyword shows the values being asked for it
Test Data
: the command should display the values being asked in our code.
Conclusion
65
Test Case
27
Objective
to test if the INNER JOIN COMMAND does link
tables with internally.
Test Data
: the command should link the tables being asked for this.
Conclusion
66
Test Case
28
Objective
to test if the AVG Function gets the average of the
numerical data of a field being asked for in the code.
Test Data
: the command should average the numerical field data asked for.
Conclusion
67
Test Case
29
Objective
to test if the COUNT Function counts the number
of rows in a table.
Test Data
: the command should count the number of rows in a table.
Conclusion
the command worked successfully and found 15
rows in the opted table it had no errors.
68
Test Case
30
Objective
to test if the COUNT ALL Function counts the
number of rows in a table.
Test Data
Conclusion
the command worked successfully and found the
number of rows present in the opted table it had no errors.
69
Test Case
31
Objective
to test if the COUNT ALL Function counts the
number of rows in a table.
Test Data
Conclusion
the command worked successfully and found the
number of rows present in the opted table it had no errors.
70
Test Case
32
Objective
to test if the FIRST Function shows the first data in
a specified fieldname.
Test Data
: the command should show the first data of the fieldname being searched.
Conclusion
71
Test Case
33
Objective
to test if the LAST Function shows the last data in
Test Data
: the command should show the last data of the fieldname being searched.
Conclusion
72
Test Case
34
Objective
to test if the MAX Function shows the highest data
in a specified fieldname.
Test Data
: the command should show the highest data of the fieldname being searched.
Conclusion
73
Test Case
35
Objective
to test if the MIN Function shows the lowest data in
Test Data
: the command should show the lowest data of the fieldname being searched.
Conclusion
74
Test Case
36
Objective
to test if the SUM Function shows the lowest data
in a specified fieldname.
Test Data
: the command should show the total the numeric values of the fieldname being asked.
Conclusion
75
Test Case
37
Objective
to test if the UCASE Function displays strings in a
field into all capital letters.
Test Data
: the command should show display strings in a field or table into all capital letters.
Conclusion
76
Test Case
38
Objective
to test if the LCASE Function displays strings in a
field into all small letters.
Test Data
: the command should show display strings in a field or table into all small letters.
Conclusion
77
Test Case
39
Objective
to test if the MID Function displays strings
characters in the middle of records in a specified field.
Test Data
: the command should display characters in the middle of strings that are in a field.
Conclusion
78
Test Case
40
Objective
to test if the LEN Function shows the number of
characters there is in each of the records in a field.
Test Data
the command should show the count of
characters in the records of a field.
Conclusion
79
Test Case
41
Objective
to test if the ROUND Function rounds of records to
its assigned decimal.
Test Data
: the command should round-off numeric values in a field to its nearest decimal
Conclusion
80
Test Case
42
Objective
to test if the CONCATENATION code merges
fields together.
Test Data
the command should merge fields using the
ampersand symbol &
Conclusion
81
Test Case
43
Objective
to test if the Literals code does add labels or
messages to field records in a field.
Test Data
the command should merge fields using the
ampersand symbol &
Conclusion
82
Test Case
44
Objective
to test if the GROUP BY command groups field
items and functions by an assigned field.
Test Data
the command group a field and a aggregate
function by the assigned field name.
Conclusion
83
Test Case
45
Objective
to test if the NZ Function runs the way it should.
Test Data
Expected Test Result variant is null.
: the NZ Function should return a value when a
Conclusion
84
Objective
to test if the PARAMETER for this database runs
and gets values to be search for.
Test Data
: The PARAMETER should ask for a value that you should type in it to find it.
Conclusion
85
Test Case
47
Objective
to if the PARAMETER for filtering data in our DB
works properly
Test Data
: the PARAMETER here should filter out data that you wished it would.
Conclusion
86
Test Case
48
Objective
to test if the TRIM command reduces spacing or
prints a message in your database.
Test Data
: the TRIM command should show a message on your database and modify spacing.
Conclusion
87
USER MANUAL
Here is a helpful guide on how to open and start up our database system that we built for Ronin Arms Inc. just read through this chapter.
We will first look for the MS ACCESS 2003 or 2007 program before we open our Ronin Arms Inc. database system. This is how we will carry that out. Ahkei STEP 1: locate the START button at the bottom left of your desktop.
CLICK THE BUTTON!
Once youve located the START Button give it a click.
88
STEP 2: When you clicked the START button you were led to this panel, now, mouse over the ALL PROGRAMS pane.
Youll be then shown another panel that contains programs in your PC System.
Look for Microsoft Office there among the list of programs in your programs panel, just like in the image below.
89
IT211- Structured Query Language 2011 STEP 3: when we found MS Office within the program panel, we now click on
MS ACCESS 2003/2007. For our manual we have 2007. Click! WELCOME!! You have now opened MS ACCESS 2007 =)
The directives on how to operate and explore within the program lies at the pages ahead, read along.
90
IT211- Structured Query Language 2011 Let us first identify the STARTING Graphic User Interface of MS ACCESS 2007 =p
A. MS OFFICE BUTTON- This is where you go for the main controls of your program which offers to create a NEW MS Access File, OPEN an MS Access File, SAVE an MS Access File and others to explore. B. QUICK ACCESS TOOLBAR- This is what youll use to quickly control the activity of your MS Access Creations, You can Save, Undo and Redo here. C. TEMPLATE CATEGORY This is where the design templates for your MS ACCESS work are listed and you can choose them here it has ASSETS, CONTACTS, ETC. ETC. youll fine when you explore the area. D. ONLINE TEMPLATES SELECTION This is where they have the list and options for the Online Templates offered by MS Access 2007 E. NEW BLANK DATABASE this is where you go for creating a new database. F. NEW DATABASE ICON Click if you want to make a new DATABASE. G. QUICK OPEN PANEL Click any file here that you wish to open instantly.
91
IT211- Structured Query Language 2011 USING MS ACCESS 2007 TO OPEN OUR DATABASE We will now open RONIN ARMS INC Database System, Read instructions below. STEP 1: Spot the OFFICE BUTTON (shown in our figure in the previous page) then click it you will then be shown a panel of options.
Click OPEN Option! to load an MS ACCES Document. An window for this will pop up showing you files and folders you can open in my documents path since it is where MS Access 2007 save documents by default. In this project we would like to open the Ronin Arms Inc. Database Systems well now look for it by double- clicking the Carmzi22 folder you see on the window.
92
IT211- Structured Query Language 2011 STEP 2: Once we have opened our Carmzi22 Folder youll be shown another set of folders to search into for our RONIN ARMS DATABASE INC. we will now double-click VALUABLE DOCUMENTS Folder.
STEP 3: When we opened the VALUABLE DOCUMENTS FOLDER there are another set of folders to search into once again we will now go for the STRUCTURED QUERRY LANGUAGE Folder, Double-click it.
93
IT211- Structured Query Language 2011 STEP 4: We have opened the STRUCTURED QUERRY LANGUAGE Folder and saw that this is our path folder since we found our Ronin Arms Inc Database System mdb file here click it once then, press the OPEN button at the bottom left of this window near the CANCEL Button.
WALLAH!! We are now seeing the visual of our RONIN ARMS Inc. Database System. If you noticed, there is a security warning on the screen looking like an azure film lining under your ACCESS ribbon. Yknow? Which tries to block us from viewing our Ronin Arms Inc. Database.
Click OPTION button amid this security warning. To configure our security matters.
94
IT211- Structured Query Language 2011 When we have clicked the OPTION in the Security Warning bar weve opened its menu window. We can configure our security in two ways here. We can either enable viewing the content being filtered or set a security that could authorize your database system. If you chose to Enable viewing the MS Access content being filtered, just click the radio button of the Enable the Content Its the last of the two radio buttons you see there.
CLICK OK! Your database system for Ronin Arms Database Inc will be accessible now and can be openly manipulated but this not the Ideal option because this means youll have lowered security for your database system. The Recommended option is to set a security VIEW NEXT PAGE for the How-Tos in setting our security
95
IT211- Structured Query Language 2011 If you chose to set a security configuration for your database, click the Open the Trust Center Link at the lower left side of the SECURITY OPTION WINDOW.
When you opened the Trust Center youll see its CONTROLS window. you can assign trusted publishers, locations, Macro Settings, Privacy Options. Its main panel is the Message Bar. Just read the tutorial for this on the net.
MS ACCESS 2007 SECURITY CONFIGURATIONS GUIDE: http://msdn.microsoft.com/en-us/library/bb421308%28v=office.12%29.aspx
96
IT211- Structured Query Language 2011 We already chose a security configuration for our Ronin Arms Inc. Database now we are lead to its Environment. Lets first identify its parts.
A. NAVIGATION BAR DROP DOWN MENU- This is what you will be utilizing when you wish to view different elements of your database. B. RIBBON this where youd most likely go for the functions of MS Access for your project files or creations. You have the HOME ribbon for common project and creation controls , CREATE Tools for creating objects for your project file or creation and EXTERNAL DATA & DATABASE TOOLS these are like properties for your Database. C. NAVIGATION BAR- This is where you explore & view the elements of your database.
97
IT211- Structured Query Language 2011 VIEWING TABLES FOR OUR DATABASE Here are directives on how to view tables for our Ronin Arms Inc. Database System. STEP 1: Click the NAVIGATOR BAR DROP DOWN MENU then set Navigate To Category to OBJECT Type.
NAVIGATION BAR DROP DOWN MENU
Then Set the Filter By Group to TABLES.
You will now see the LIST of Tables created on your Navigation Bar.
To open and view a table simply double-click a desired table on the list.
98
VIEWING COMMANDS IN OUR DATABASE To view Commands or Syntaxes for our database we click the NAVIGATION BAR DROP DOWN MENU. Set the Navigate To Category to Object Type And the Filter By Group to querries.
Youll now see the list of Syntaxes and Commands for your database in the Navigation Bar.
99
IT211- Structured Query Language 2011 To View the SQL commands in your table. Right click on a query in the Navigation Bar then choose DESIGN VIEW.
To run your SQL syntax simply click on the red exclamation mark on your Design ribbon
100
CONCLUSION
Now, We have pieced up all the crucial information and directives of our Ronin Arms Inc. Database System for our SQL Documentation, This is where we end our write up.
For a closing statement Id like to part with the realizations I encountered during the making of this project documentation. When writing this up, I realized that Structured Query Language is the most reliable Database Publisher among its kind. It had so many features in terms of administering our database. They have tools in creating databases like query design tools, SQL Design editors and compilers. Acute search for database items is possible through the SELECT statements held by SQL.
Security and Authorization configurations are also available in the SQLs program which is MS ACCESS program and there are so much more yet to be discovered.
By the end of the Project Documentation I found a sense of trust in Structured Query Language with all its beneficial features. It also had very comprehensive and convenient coding scheme that I adored completely.
All in all Structured Query language is worthy of being the standard database and spreadsheet language preferred by ANSI.
101
ACKNOWLEDGEMENTS
THANKS BE TO GOD for His gifts! INFORMATICS FESTIVAL Alabang For being the Academe. Ms. Josha Lamitar for being an effective lecturer. My Parents for sponsoring my studies Microsoft and TOSHIBA for the technical areas. Google for keeping me informed with some of the terms here in SQL. PISONG PRINTING beside UPHR Las-Pinas
Special thanks to Everything =D
102

IT211-SQL Project: Ronin Arms Inc DB

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

IT211-SQL Project: Ronin Arms Inc DB

Enviado por

Direitos autorais:

Formatos disponíveis

IT211- Structured Query Language 2011

INFORMATICS COMPUTER SCHOOL

(IT211 Structured Query Language)

< Ronin Arms Inc. Database System>

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011

CHAPTER 2: DATABASE DESCRIPTION

CHAPTER 3: COMMAND LISTING

CHAPTER 4: PROGRAM TESTING CHAPTER 5: USER MANUAL CHAPTER 6: CONCLUSION

P. 40-87 P. 88-100 P. 101 P. 102

RONIN ARMS INC/ CARMEN LIM/ DIT

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 1.3 Proposed System Objectives

1.4 Benefits of the Proposed System

Various Weapons Manufacturers

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011

RONIN ARMS INC/ CARMEN LIM/ DIT

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE II: LONGGUNS

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE III: MELEE ARMS

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE IV: ACCESSORIES

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE V: EQUIPMENTS

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE VI: AMMOS

RONIN ARMS INC/ CARMEN LIM/ DIT

DATATYPE & WIDTH: Number: Double Sized Text: Size 255

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE II: CUSTOMERS

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE III: EMPLOYEES

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE IV: EMPSCHED

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011 TABLE V: LICENSESHIP

TABLE COLUMN & THEIR PURPOSE:

DATA TYPE & WIDTH: TEXT: QTY (3) size 255

RONIN ARMS INC/ CARMEN LIM/ DIT

RONIN ARMS INC/ CARMEN LIM/ DIT

HANDGUNS Table Relations

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011

LONGUNS Table Relationships

Our LONGGUNS table is related with the and

CUSTOMERS table and expresses the long gun

products relationship with the customers in that

table and vice versa.

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011

MELEE ARMS table Relations

The MELEE ARMS table is associated with CUSTOMERS the and

MANUFACTURERS Table and its with

relationship each MANY. is

RONIN ARMS INC/ CARMEN LIM/ DIT

IT211- Structured Query Language 2011

AMMOS Table Relations

ammunitions) table Is related with the

CUSTOMERS and LICENSESHIP tables as ONETO-MANY.

AmmoID field as its Primary Key. And relates this as key a

RONIN ARMS INC/ CARMEN LIM/ DIT