Database Design & Development | Bikash Dhakal

Contents
Task 1/ P1...................................................................................................................................................3
Design a relational database system using an appropriate design tools and techniques, containing at
least four tables, with clear statements of user and system requirements.............................................3
1.1Introduction:.....................................................................................................................................3
ER diagram..........................................................................................................................................3
1.2Entity Relationship Diagram (ER Diagram)..................................................................................6
Relationship Diagram............................................................................................................................7
1.3 Data dictionary:...............................................................................................................................8
1.4 Justification Table.........................................................................................................................10
Conclusion............................................................................................................................................10
References............................................................................................................................................11
Task 4/P2 Develop the database system with evidence of user interface, output and data validations,
and querying across multiple tables.......................................................................................................12
Introduction.........................................................................................................................................12
Constraints:..........................................................................................................................................12
1. NOT NULL...............................................................................................................................12
2. Unique Constraints....................................................................................................................13
3. Primary Key...............................................................................................................................13
4. Foreign key................................................................................................................................14
5. Default constraints.....................................................................................................................14
User Interface and Output:.................................................................................................................15
Data Validation:...................................................................................................................................18
Joins......................................................................................................................................................20
a) Inner joins..................................................................................................................................20
b) Left(Outer) Joins........................................................................................................................21
c) Right join...................................................................................................................................23
d) Full join.....................................................................................................................................24
Conclusion............................................................................................................................................25
References............................................................................................................................................26
Task 6 / P3................................................................................................................................................27
Implement a query language into the relational database system.......................................................27
Introduction.........................................................................................................................................27

P a g e 1 | 58
 Database Design & Development | Bikash Dhakal

DML commands (data manipulation language)................................................................................27

1 INSERT.....................................................................................................................................27
2 UPDATE...................................................................................................................................30
3 SELECT....................................................................................................................................33
4 DELETE....................................................................................................................................35
Conclusion:..........................................................................................................................................39
References............................................................................................................................................39
Task 8/P4..................................................................................................................................................40
Test the system against user and system requirements........................................................................40
Introduction.........................................................................................................................................40
1) Integration Test..........................................................................................................................40
2) Unit Test....................................................................................................................................41
3) Stress Test..................................................................................................................................41
Conclusion............................................................................................................................................50
References............................................................................................................................................50
Task 11[P5]..............................................................................................................................................51
Produce a technical and user documentation........................................................................................51
Introduction.........................................................................................................................................51
Overview..............................................................................................................................................51
Constraint/Risk....................................................................................................................................51
Assumption..........................................................................................................................................52
User Manual.........................................................................................................................................52
Conclusion............................................................................................................................................57

P a g e 2 | 58
 Database Design & Development | Bikash Dhakal

Task 1/ P1

Design a relational database system using an appropriate design tools and techniques,
containing at least four tables, with clear statements of user and system requirements.
1.1Introduction:
The newly opened Jaguar International Departmental store is located in Bharatpur, Chitwan.
Since the departmental store is in the initial phase, the store is maintaining all the information
using a traditional concept i.e., the operations of the store are manual the store has decided to
develop a database, so in this assignment I am going to help them as a database operator.

In order to meet the criteria of this task based on the scenario I have done lots of research and
studied about required content. As per task requirement, I have design the ER diagram and Data
Dictionary based on the scenario as I am required to deliver my concepts and ideas to design a
relational database system using an appropriate design tools and techniques, containing at least
four tables according to the requirement of the user and my works on this task are as follows:

ER diagram
Entity Relational Diagram simply ER diagram is the relational diagram that shows the
relationship of entities that are set to be stored in database. It illustrates logical structure of
databases.

“An entity-relationship diagram (ERD) is a graphical representation of an information system

that shows the relationship between people, objects, places, concepts or events within that
system. An ERD is a data modeling technique that can help define business processes and can be
used as the foundation for a relational database.” ER diagram as developed by Peter Chen in
1976 A.D. After its development Charles Bachman and James Martin have added slight change
in principle of ER diagram. (SearchDataManagement, 2018)

Types of ER Diagram:

1. One-to-One (1: 1)- only one entity of one table associated to one entity of another table
2. One-to-Many (1: N)- each entity of one table is associated with at most one entity in
another table but each entity in another table is associated with many entities in one table

P a g e 3 | 58
 Database Design & Development | Bikash Dhakal

3. Many-to-Many (M: N)- each entity of one table is associated with many entities of
another table.

Entity diagram notations

Entity

Entity: Entity in ER diagram is represented in a rectangle.

Actions, which are represented by diamond shapes, show how two entities share information in
the

database.

Relationship

Attributes, which are represented by ovals.

Attributes

Information Engineering style shows the relationship between two entities whether they are
connected one to one, one to many or many to many it shows the relationship types.

P a g e 4 | 58
 Database Design & Development | Bikash Dhakal

Information Engineering Style:

Before designing database following things should be identified:

a. Entities – the types of information that are saved in the database are called entities.
b. Relationship- the connection between the entities are relationship.
c. Attributes-the data elements of each entity is attributes. (Lucidchart, 2018)

Advantages of ER diagram

P a g e 5 | 58
 Database Design & Development | Bikash Dhakal

 Designing E-R diagram is too simple.

 Designing E-R diagram for a database application, the relational representation of data
model becomes straightforward.
 Converting E-R diagram to other data model is easy.
 Gives better understanding from graphical representation as it represents various entitles,
theirs attributes and relationship.

Disadvantages of ER diagram

 Lack any company for development of E-R diagram.

 It is only popular for high level design.
 There is limitation in representing relationship.
 No representation of data manipulation. (EDUGRABS, 2018

P a g e 6 | 58
 Database Design & Development | Bikash Dhakal

1.2Entity Relationship Diagram (ER Diagram)

Fig: ER Diagram
In above figure I have managed four entity and nineteen attributes along with relations. These
relations are shown briefly with the help of SQL server along with primary key and foreign key
references below:

Relationship Diagram

P a g e 7 | 58
 Database Design & Development | Bikash Dhakal

Fig: Entity Relationship Diagram

In the above Relationship Diagram, I have created Six Table with their attributes each as per the
requirement of the task. Here, in the Customer table I have given a primary key to the Customer
Id with the data type integer and Customer Name, Customer Address, Customer contact,
customer email with data type Varchar, Varchar, varchar, varchar respectively.

1.3 Data dictionary:

Data dictionary is the collection of different types of names, attributes that we use in SQL query
while creating tables. Such as int, date etc. Through data dictionary we can recognize what type
of value is used for creating the table. So below are some examples that I have used in above
Jaguar billing system. (SearchMicroservices, 2018)

P a g e 8 | 58
 Database Design & Development | Bikash Dhakal

Table 1: customer table

SN Column Data Type Key Status Description

Name
1 cus_ID integer Primary key Unique id of a customer.
2 Cus_Name Varchar Name of customer.
(50)
3 Cus_Add Varchar Address of customer.
(50)
4 Cus_Contact Varchar Contact number of customer.
(20)
5 Cus_Email Varchar Email address of customer.
(50)

Table 2: Product table

S Column Data Type Key status Description

N Name
1 Pro_ID integer Primary key Unique id of product.
2 Pro_Name varchar Name of product.
3 Pro_price money Price of product.
4 Pro_MFG Date Manufacturing date of product.
5 Pro_EXP Date Expiry date of product.

Table 3: Invoice table

S Column Name Data Type Key status Description

N
1 Inv_ID Integer Primary key Unique id of invoice.
2 Cus_ID Integer Foreign key Unique id of customer.
3 Inv_Date Date Date of invoice.
4 Inv_Name Varchar Name of invoice
5 Pro_ID integer Foreign key Unique id of product

Table 4: sale table

P a g e 9 | 58
 Database Design & Development | Bikash Dhakal

S Column Name Data Type Key Status Description

N
1 Sale_ID Integer Primary key Unique id of sale.
2 Agent_ID Integer Unique id of agent.
3 Quantity Integer Quantity of sale
4 Pro_ID Integer Foreign key Unique id of product.
5 Agent_Name varchar Name of sale’s agent.

Table 5: Category table

SN Column Name Data type Key status Description

1 Cat_ID Integer Primary key Unique id of category.
2 Cat_Name varchar Name of category.
3 Pro_ID Integer Foreign key Unique id of product.
4 Cat_type varchar Type of category.

Table 6: Login table

S Column Data type Key status Description

N
1 Log_ID Integer Primary key Unique id of login.
2 Cus_ID Integer Foreign key Unique id of customer.
3 Pro_ID Integer Foreign key Unique id of product
4 Pro_Name Varchar Name of product.

1.4 Justification Table

S Client Row My justification status

N
1 Customer As per scenario, I have created a customer
table in which we have to store the details of Accepted
the customers that are found on our
Departmental Store.
2 product According to the scenario, I have created a
Product table in which we have to store the Accepted
P a g e 10 | 58
 Database Design & Development | Bikash Dhakal

details of the products that are found on our

Departmental Store.
3 Invoice In this database, I have created Invoice table
where we can store all information of Accepted
Invoice.
4 Sale For this table, I have created all the details of
sale of a Products as per the requirements of Accepted
the Scenario.
5 Category According to scenario demand, I have created
table name Category where we can make a Accepted
different category for each product.
6 Login In the login table, I have created User Login
where user have to login to get access by Accepted
using Name and the password as per the
requirements.

Conclusion
In this task I have created the ER diagram as well as data dictionary and I have included all the
contents according to demand of the clients and at last I have created the justification table which
briefly describe the client requirements along with justification and status.

Hence, I have concluded that I have done this task successfully.

References
SearchDataManagement. (2018). What is entity relationship diagram (ERD)? - Definition from
WhatIs.com. [online] Available at:
https://searchdatamanagement.techtarget.com/definition/entity-relationship-diagram-ERD
[Accessed 25 Apr. 2018].

SearchMicroservices. (2018). What is data dictionary? - Definition from WhatIs.com. [online]

Available at: https://searchmicroservices.techtarget.com/definition/data-dictionary [Accessed 25
Apr. 2018].

Lucidchart. (2018). Entity-Relationship Diagram Symbols and Notation. [online] Available at:
https://www.lucidchart.com/pages/ER-diagram-symbols-and-meaning [Accessed 27 Apr. 2018].
P a g e 11 | 58
 Database Design & Development | Bikash Dhakal

EDUGRABS. (2018). Advantages and Disadvantages of ER Model in DBMS - EDUGRABS.

[online] Available at: http://www.edugrabs.com/advantages-and-disadvantages-of-er-model/
[Accessed 27 Apr. 2018].

P a g e 12 | 58
 Database Design & Development | Bikash Dhakal

Task 4/P2 Develop the database system with evidence of user interface, output and data
validations, and querying across multiple tables.

Introduction
As per scenario demand, on this task I am going to explain about database constraints, user
interface, data validation and different types of SQL joins in this task.

Constraints:
Constraints are the guidelines enforced on the facts columns of a desk. These are used to
restriction the type of information that can pass right into a desk. This ensures the accuracy and
reliability of the data within the database.

Constraints could be both on a column stage or a table stage. The column stage constraints are
implemented only to at least one column, whereas the table level constraints are applied to the
complete table. (www.tutorialspoint.com, 2018)

The following constraints are mostly used in SQL.

1. NOT NULL
It is the constraints that ensures that column cannot have null value. It means that when we
specify the nut null constraints, then it cannot have null value in the column. Let’s take example
of not null constraints.

P a g e 13 | 58
 Database Design & Development | Bikash Dhakal

The above query will declare that the (cus_contact) field of customer table will not take NULL
value.

2. Unique Constraints
The column or set of columns which has a restrict inside a table, that all the values in that
column should be unique. The column having a unique constraint cannot have a replica cost in
that table.

3. Primary Key
Primary key uniquely identifies the row or record in the database table. It must have unique
values and cannot contain null value in it. Let’s take example of Primary key constraint.
(Lifewire, 2018)

The above query created the primary key in the Pro_ID. Pro_Id will have unique value.

4. Foreign key
Foreign Key is used to relate two tables. FOREIGN KEY constraint is also used to restrict
actions that would destroy links between tables. Let’s take example of foreign key constraint.

P a g e 14 | 58
 Database Design & Development | Bikash Dhakal

In above table pro_ID is the foreign key which is primary key on product table which is
mentioned on example of primary key above.

5. Default constraints
The value that are provided by the SQL Server automatically where there is no value during the
time of inserting in the table. It can be null, Constant or a function. (www.tutorialspoint.com,
2018)

User Interface and Output:

P a g e 15 | 58
 Database Design & Development | Bikash Dhakal

Query: Create database Jaguar_assignment

This Query creates database name Jaguar_assignment.

Query: Use database Jaguar_assignment.

This Query uses database name Jaguar_assignment.

Query: Create table Customer

This Query is use to create table name customer where we input data related with the Customer.

P a g e 16 | 58
 Database Design & Development | Bikash Dhakal

Query: Create table Product

So, this query creates Product Table where we can input the data of different products of a
Jaguar_assignment.

Query: Create table Invoice

This query creates table name Invoice where we can input all the information of a invoice.

P a g e 17 | 58
 Database Design & Development | Bikash Dhakal

Query: Create table Category

In this query we create table name category where we input data according the need of table.

Query: Create table Sale

This query is use to create Sale table where all the information of the product that are bought by
the Customer can be placed.

P a g e 18 | 58
 Database Design & Development | Bikash Dhakal

Data Validation:
Table User interface and out put Remar
Names ks
It is
seen
that the
fields
are
Custom same
er in both
tables
and
form

Product It is
seen
that the
fields
are
same
in both
tables
and
form

P a g e 19 | 58
 Database Design & Development | Bikash Dhakal

Categor Here
y we can
see that
both in
Table
as well
as in
Interfa
ce the
Entity
are
same
Invoice It is
seen
that the
fields
are
same
in both
tables
and
form

Sale Here
we can
see that
both in
Table
as well

P a g e 20 | 58
 Database Design & Development | Bikash Dhakal

as in
Interfa
ce the
Entity
are
same.

Joins
Join is also another type of retrieve query that gives the output after joining two tables which
have

connection with each other. Following are the types of joins. (W3schools.com, 2018)

a) Inner joins
Returns records that have matching values in both tables

Select all records from Table 1 and Table 2, where the join condition is met.

P a g e 21 | 58
 Database Design & Development | Bikash Dhakal

Above pictures show the inner join between customer and product table.

b) Left(Outer) Joins
Select all records from Table 1, along with records from Table 2 for which the join condition I
met

(if at all).

P a g e 22 | 58
 Database Design & Development | Bikash Dhakal

Above screen shots show the left join between category and product table.

P a g e 23 | 58
 Database Design & Development | Bikash Dhakal

c) Right join
Select all records from Table 1, along with records from Table 2 for which the join condition is
met

(if at all).

P a g e 24 | 58
 Database Design & Development | Bikash Dhakal

Above pictures are the example of right join.

d) Full join
Select all records from Table 1 and Table 2, regardless of whether the join condition is met or
not.

P a g e 25 | 58
 Database Design & Development | Bikash Dhakal

In above screenshots we can see full join.

Conclusion
In this task I described about SQL constraints and some types of SQL joins which I have used in
my database management.
P a g e 26 | 58
 Database Design & Development | Bikash Dhakal

References

www.tutorialspoint.com. (2018). SQL Constraints. [online] Available at:

https://www.tutorialspoint.com/sql/sql-constraints.htm [Accessed 28 Apr. 2018].

W3schools.com. (2018). SQL Joins. [online] Available at:

https://www.w3schools.com/sql/sql_join.asp [Accessed 28 Apr. 2018].

Lifewire. (2018). Learn What a Primary Key in a Database Is and What Makes a Good Key.
[online] Available at: https://www.lifewire.com/primary-key-definition-1019179 [Accessed 28
Apr. 2018].

www.tutorialspoint.com. (2018). SQL Constraints. [online] Available at:

https://www.tutorialspoint.com/sql/sql-constraints.htm [Accessed 28 Apr. 2018].

P a g e 27 | 58
 Database Design & Development | Bikash Dhakal

Task 6 / P3

Implement a query language into the relational database system.

Introduction
Database is to store your data. After storing data, you may need to retrieve that data but if we
want data it gives haphazardly we want specific data so we have to write a specific query for
specific data to view it.

DML commands (data manipulation language)

DML is Data Manipulation Language to retrieve our data from database.

“DML is abbreviation of Data Manipulation Language. It is used to retrieve, store, modify,

delete, insert update data in database. Examples: SELECT, UPDATE, INSERT statements. DDL
is abbreviation of Data Definition Language. It is used to create and modify the structure of
database objects in database.” (DML, 2018)

following are the types of DML command.

1 INSERT

INSERT is key used to INSERT the data in our table

To insert a data in a table this is the syntax

INSERT INTO table_name(column_name) VALUES (data);

P a g e 28 | 58
 Database Design & Development | Bikash Dhakal

The command insert use in the above Screen shot is use to insert all the data in the Customer
table in their respective columns.

In above picture we inserted data in product table.

P a g e 29 | 58
 Database Design & Development | Bikash Dhakal

Above picture shows data insert in catagory table.

This screen shows data insert in invoice table.

P a g e 30 | 58
 Database Design & Development | Bikash Dhakal

Query: Data insert in sale table.

2 UPDATE
UPDATE is keyword used to update data either its table name column name or data inside the
table.

Syntax to update data in table

UPDATE table_name SET column1 = value1, column2 = value2...., columnN = valueN

WHERE

[condition];

The command Update use in the above Screen shot is use to Update the data in the Customer
table in their respective columns.
P a g e 31 | 58
 Database Design & Development | Bikash Dhakal

Above screen shot shows the updated value of customer table.

In picture shows the update command to update the product table.

Figure shows the updated value of product.

P a g e 32 | 58
 Database Design & Development | Bikash Dhakal

Above command is used to update invoice table.

Updated values of invoice table.

Command use to update sale table.

P a g e 33 | 58
 Database Design & Development | Bikash Dhakal

Updated data of sale.

Above screen shot shows the update command for catagory table.

Above screen shot shows the updated data of category table.

3 SELECT
SELECT is the keyword used to select data from table. It is type of retrieve query.

P a g e 34 | 58
 Database Design & Development | Bikash Dhakal

Syntax:

SELECT*FROM table name;

The statement used in picture is used to retrieve all the data from the customer table.

The statement used in picture is used to retrieve all the data from the category table.

P a g e 35 | 58
 Database Design & Development | Bikash Dhakal

The command used in above screen shot is used to retrieve all the data from the invoice table.

The statement used in picture is used to retrieve all the data from the sale table.

The command used in screen shot is used to retrieve all the data from the sale table.

4 DELETE
DELETE (Back End)

This statement is used to delete the data from the table.

Syntax:

Delete from table name where column name = ‘

P a g e 36 | 58
 Database Design & Development | Bikash Dhakal

The command used in the above Screen shot is used to delete number of desired column from the
Catagory table.

This is the output after performing delete command in Category table. The column name cat_Id
having value2 has been deleted from catagory table.

In above screen shot we have used delete command to delete desired value of invoice table.

P a g e 37 | 58
 Database Design & Development | Bikash Dhakal

Above figure shows successfully deleted the value having inv_ID =2 from invoice table.

Query: command used to delete desire value from sale’

Query: successfully deleted the desire value.

P a g e 38 | 58
 Database Design & Development | Bikash Dhakal

Query: command used to delete the desire data from product table.

Query: The date having pro_ID = 6 is deleted from product table.

Above screen shot shows the delete command to delete desire value from customer table.

P a g e 39 | 58
 Database Design & Development | Bikash Dhakal

Command executed successfully where the data having cus_ID = 6 is deleted from customer
table,

Conclusion:
Without DML no CRUD operation is possible. In every aspect we use DML language whether it
is to create a table or the to insert data in table as well as to update. In same way to create we
create all the tables required in scenario and column along with its data were inserted.

References
DML, W. (2018). What is DDL and DML. [online] Stack Overflow. Available at:
https://stackoverflow.com/questions/2578194/what-is-ddl-and-dml [Accessed 29 Apr. 2018].

P a g e 40 | 58
 Database Design & Development | Bikash Dhakal

Task 8/P4

Test the system against user and system requirements.

Introduction
In this task I am going to testing database which I have prepared as Jaguar database management
system. Database testing is the testing in which user exams or test the existing facts along with
tables, strategies, query, data duplication etc. Testing is executed with the aid user it can be
achieved in both web software or computing device in database software program like SQL or
oracle. Many initiatives call for database nowadays which include banking, schools and colleges,
business and so on. Within the testing technique many stuffs are checked including double data,
if there's duplicate data or not, if there may be key errors or now not.

Following are some significance of database testing.

1. It is able to check capability which can be controlled by way of values in database.

2. Beneath optimized database design leads to fundamental capability failure.

3. It checks data validation and duplication.

4. Incorrect or inefficient or badly written SQL Queries can also lead functionality failure.

5. It guarantees that no data is lost inside the manner.

Following are some method of database testing.

1) Integration Test

In this test one-of-a-kind operation on data is examined to ensure that the data and information
are inserted properly with accurate constraints in order that it gives accurate results. This type of

P a g e 41 | 58
 Database Design & Development | Bikash Dhakal

testing out is particularly relevant to client/server and distributed systems. The modules are
combined in these testing out and are tested as a group. This testing out enables us to do data
access without mistakes. (www.tutorialspoint.com, 2018)

2) Unit Test

In unit test, testing is done in individual basis. Testing of an individual software component or
module is termed as Unit Testing. This type of testing is usually done by programmer.
(SearchSoftwareQuality, 2018)

3) Stress Test

Stress testing is done to identify the system breakpoint. It stresses the application or software
under test with many loads. This type of testing gives a lot load to the system. In other words, it
can be called stress testing also. (Tech, 2018)

P a g e 42 | 58
 Database Design & Development | Bikash Dhakal

Table and query testing.

Date Table Expected/actual result Remarks

Names
It is seen that
Customer the fields are
(cus_ID, same in both
5/13/2018 cus_contact, tables and
cus_Name, form
cus_add,
cus_Email)

Product It is seen that

the fields are
(pro_ID, same in both
5/13/2018 pro_MFG, tables and
pro_Name, form
price,
pro_EXP)

P a g e 43 | 58
 Database Design & Development | Bikash Dhakal

Category Here we can

see that both
in Table as
5/13/2018 well as in
Interface the
Entity are
same

Invoice It is seen that

the fields are
same in both
5/13/2018 tables and
form

Sale Here we can

see that both
5/13/2018 in Table as
well as in
Interface the
Entity are

P a g e 44 | 58
 Database Design & Development | Bikash Dhakal

same.

Testing five tables

1. Product table

Testing Data value Input value Expected output Actual output Remarks
Unit testing Pro_price It should show error message It shows error Test
for not putting value for not putting successful
value

P a g e 45 | 58
 Database Design & Development | Bikash Dhakal

Stress testing Pro_MFG jghhfhj It should show error message for It shows error. Test
putting varchar data instead of successful.
date.

1. Customer table

Testing Data value Input value Expected output Actual output Remarks

P a g e 46 | 58
 Database Design & Development | Bikash Dhakal

Unit Cus_contac 98723627893623 It should show error message It shows error for Test
testing t 45 for putting more than limit putting more value. successful
value

Stress Cus_Name 23234 It should be Varchar It accepts numeric, Int values in Test
testing the column of cus_name. successful.

2. Invoice table

Testing Data value Input value Expected output Actual output Remarks

Unit testing Pro_ID It should show error message for not It shows error Test
P a g e 47 | 58
 Database Design & Development | Bikash Dhakal

putting value for not putting successful

value

Stress Inv_date 766976 It should show error message for putting It shows error. Test
testing 7 integer data instead of date. successful.

3. Category table

Testing Data value Input value Expected output Actual output Remarks
Unit Pro_ID It should show error message It shows error Test
testing for not putting value for not putting successful
value
P a g e 48 | 58
 Database Design & Development | Bikash Dhakal

Stress Pro_ID It should show error message for It shows error. Test
testing putting varchar data instead of successful.
integer.

4. Sale table

Testing Data value Input value Expected output Actual output Remarks

Unit testing agent_ID It should show error message It shows error for Test successful
for not putting value not putting value

P a g e 49 | 58
 Database Design & Development | Bikash Dhakal

Stress quantity jgkhg It should show error message for It shows Test
testing putting varchar data instead of integer. error. successful.

Conclusion
There are many features and processes to test the database. Database is used in many
organization so testing is important. Every data should be tested in order to create a good
database if there is duplicate of data or not if the system has error or not. So, testing is important.
In this task I have done the testing of data.

P a g e 50 | 58
 Database Design & Development | Bikash Dhakal

References
www.tutorialspoint.com. (2018). Integration Testing. [online] Available at:
https://www.tutorialspoint.com/software_testing_dictionary/integration_testing.htm [Accessed
30 Apr. 2018].

SearchSoftwareQuality. (2018). What is unit testing? - Definition from WhatIs.com. [online]

Available at: https://searchsoftwarequality.techtarget.com/definition/unit-testing [Accessed 30
Apr. 2018].

Tech. (2018). How to do database load/stress test. [online] Available at:

https://it.toolbox.com/question/how-to-do-database-load-stress-test-032310 [Accessed 30 Apr.
2018].

Task 11[P5]

Produce a technical and user documentation.

Introduction
The database system is developed to keep records of various things they are taking in a company
which they will offer. For this six table have been created to keep different records of department
store.

P a g e 51 | 58
 Database Design & Development | Bikash Dhakal

In this task I am going to produce a user documentation along with user manual and a technical
documentation. In this documentation, there is the overview of database of Jaguar International
Departmental Store with all risks and assumptions involved in database.

Overview
1. Database Name – Jaguar_assignment
2. NO. of Tables – 6
3. Tables – customer, Product, invoice, sale, catagory, login.
4. Administrator Name – Bikash Dhakal
5. IDE Back-end Application – Microsoft SQL Server Management 2012.
6. IDE Front-end Application – Microsoft Visual Studio 2012,
7. Front-end Form Name – Jaguar International Billing System.

Constraint/Risk
A constraint means a projects limitation. I have applied good effort to make software that begins
with including different relationship diagram, entity relation diagram, data dictionary etc.
Interface were designed using the visual studio for user to interact with system. Then, I have
connected the system to SQL and form a relation among table. Various tests such as integration
test, unit test and stress test were performed to ensure the effectiveness of my system.

After the s completion of these system, there were certain constraints or risks to the database
solution of the system. Some are given below.

 It is not completely protected and the space limit is also limited.

 If some problem occurs in the database, whole database will be lost.
 It is hard to understand for the user who don’t have knowledge about database.
 Need well trained manpower if there is problem.

Assumption
I have designed the database as per the scenario with some assumption, I have designed different
tables which perform different tasks. Assumption of my design are,

For category table I use unique Id, unique name and type.

For product, I have used unique Id, name, price, date (manufacture and expiry).

P a g e 52 | 58
 Database Design & Development | Bikash Dhakal

For customer, I have used unique Id, name, e-mail, and contact of customer.

For sale, I use unique Id, agent name, agent ID and quantity.

For invoice, I have used unique Id of product, customer and invoice, name, invoice date.

User Manual

Step 1st: we open the SQL Management Studio.

Step 2nd: In this step we have to connect SQL server with the desired Server Name.

P a g e 53 | 58
 Database Design & Development | Bikash Dhakal

Step 3rd: This is the step after connecting SQL server with desired Server Name

P a g e 54 | 58
 Database Design & Development | Bikash Dhakal

Step 4th: Now, we can see all the database we have create in SQL server which opens when we
Click on Databases.

Step 5th: In this step we have to choose our database name where we have to perform actions like
insert, update and delete command.

P a g e 55 | 58
 Database Design & Development | Bikash Dhakal

And the command uses to insert, update and delete data should be used by following steps:

1. Insert command

P a g e 56 | 58
 Database Design & Development | Bikash Dhakal

Above screen shots show the insert command.

2. Update

Query: update the table successfully.

P a g e 57 | 58
 Database Design & Development | Bikash Dhakal

3. Delete command

Above screen shots shows the successful execution of delete command.

Conclusion
Documentation helps other user to manipulate the data also. With the information given or told
in documentation other user can modify the data as they like. This above documentation contains
the information of Jaguar International Billing System database.

P a g e 58 | 58