Database Design, Implementation, and Testing: BTEC HND, 1st Semester

This document presents a complete database assignment for a BTEC HND Computing student, covering all aspects of relational database design and implementation. The assignment begins with the design of a relational database system using appropriate tools and techniques, including Entity-Relationship Diagrams (ERD), relational diagrams, and data dictionaries. It then moves on to the comprehensive design of a fully functional system, including interface and output design, data validation, and data normalization. The assignment progresses to the development of the database system, with evidence of user interface, output, data validations, and querying across multiple tables using joins. Further tasks include implementing system security and database maintenance, including password policies, stored procedures, triggers, functions, and views. The assignment also covers implementing a query language, assessing data extraction through query tools, and testing the system against user and system requirements, including detailed test logs. Finally, the project concludes with the production of technical and user documentation, including diagrams, flowcharts, and use case diagrams, assessing the effectiveness of the testing and the overall system design and functionality. The project uses SQL Server for the backend and Visual Studio with C# for the frontend and desktop application. This assignment provides a thorough example for database design, implementation, and documentation.

1
Database 2018
Database
Assignment
Submitted by: Sagar Timalsina,
BTEC HND Computing,
1st Semester.
Submitted to: Mr. Umesh Acharya
Tinkune, Kathmandu, Nepal
Contents
Task [1/P 1]............................................................................................................................................7
Sagar Timalsina (HND / First Semester)

2
Database 2018
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. Introduction:.......................7
Choice of tools....................................................................................................................................7
Entity Relational Diagram (ERD)..........................................................................................................7
Relational Diagram................................................................................................................................9
Data Dictionary....................................................................................................................................10
User Requirement.................................................................................................................................12
Conclusion............................................................................................................................................13
Task [2/M 1].........................................................................................................................................13
Produce a comprehensive design for a fully functional system which includes interface and output
design, data validation and data normalization....................................................................................13
Introduction..........................................................................................................................................13
Choice of tools..................................................................................................................................13
Implement fully functional system.......................................................................................................13
Data Normalization..............................................................................................................................15
Types to Normalization....................................................................................................................15
Existing Method – (excel file) vs database normal form.................................................................15
Database Normal form.........................................................................................................................15
Data Validation....................................................................................................................................17
Client-side validation........................................................................................................................17
Server-side and database validation.................................................................................................18
Conclusion............................................................................................................................................18
Task [4/P 2]..........................................................................................................................................18
Develop the database system with evidence of user interface, output and data validations, and
querying across multiple tables............................................................................................................18
Introduction..........................................................................................................................................18
Implement Constraints.........................................................................................................................19
Evidence of user interface and data validation....................................................................................21
Sagar Timalsina (HND / First Semester)

3
Database 2018
Validate data querying multiple tables using joins..............................................................................24
Conclusion............................................................................................................................................26
Task [5/M 2].........................................................................................................................................26
Implement a fully functional database system which includes system security and database
maintenance..........................................................................................................................................26
Introduction..........................................................................................................................................26
System Security....................................................................................................................................26
Password Policy................................................................................................................................26
Store procedure....................................................................................................................................27
Trigger..................................................................................................................................................28
Functions..............................................................................................................................................29
Views....................................................................................................................................................30
Database Maintenance.........................................................................................................................30
Log file and data file management...................................................................................................31
Corruption Detection........................................................................................................................31
Index Fragmentation.........................................................................................................................31
Backup Plan......................................................................................................................................32
Types of Backup...............................................................................................................................32
Step9: Click on next.........................................................................................................................34
Step10: Click On finish....................................................................................................................34
Restore Plan.........................................................................................................................................35
Restore back up file in System.........................................................................................................35
Conclusion............................................................................................................................................36
Task [6/P 3]..........................................................................................................................................36
Implement a query language into the relational database system........................................................36
Introduction:.........................................................................................................................................36
Insert Statement....................................................................................................................................36
Sagar Timalsina (HND / First Semester)

4
Database 2018
Update Statement.................................................................................................................................42
Delete Statement..................................................................................................................................45
Select Statement...................................................................................................................................48
Conclusion............................................................................................................................................51
Task [7/M 3].........................................................................................................................................51
Assess whether meaningful data has been extracted through the use of query tools to produce
appropriate management information..................................................................................................51
Introduction..........................................................................................................................................51
Product wise stock reports...................................................................................................................51
Without Filter Parameter..................................................................................................................51
Using Filter Parameter......................................................................................................................52
Periodical Sales reports........................................................................................................................52
Without Filter Parameter..................................................................................................................52
Using Filter Parameter......................................................................................................................53
Product wise margin reports.................................................................................................................53
Without Filter Parameter..................................................................................................................53
Using Filter Parameter......................................................................................................................54
Supplier wise purchase details.............................................................................................................54
Without Filter Parameter..................................................................................................................54
Using Filter Parameter......................................................................................................................55
Conclusion............................................................................................................................................55
Task [8/P 4]..........................................................................................................................................56
Test the system against user and system requirements........................................................................56
Introduction..........................................................................................................................................56
Testing..................................................................................................................................................56
Types of testing................................................................................................................................56
Unit Test Log.......................................................................................................................................57
Sagar Timalsina (HND / First Semester)

5
Database 2018
Integration Test Log.............................................................................................................................58
Conclusion............................................................................................................................................62
Task [9/M 4].........................................................................................................................................63
Assess the effectiveness of the testing, including an explanation of the choice of test data used.......63
Introduction..........................................................................................................................................63
Testing..................................................................................................................................................63
Importance of testing............................................................................................................................63
Approach of testing..............................................................................................................................63
List of expected result and actual result...............................................................................................64
Login module....................................................................................................................................64
Product module.................................................................................................................................66
Purchase Module..............................................................................................................................68
Sales Module....................................................................................................................................71
Supplier Module...............................................................................................................................74
Customer Module.............................................................................................................................76
Conclusion............................................................................................................................................78
Task [11/P 5]........................................................................................................................................79
Produce technical and user documentation..........................................................................................79
Introduction..........................................................................................................................................79
Important Features of Application.......................................................................................................79
Significance of Application..................................................................................................................79
Limitation of Application.....................................................................................................................79
Choice of tools.....................................................................................................................................80
Technical manual.................................................................................................................................80
User validation module.....................................................................................................................80
Product module.................................................................................................................................81
User manual.........................................................................................................................................82
Sagar Timalsina (HND / First Semester)

6
Database 2018
Step guide to use application............................................................................................................82
Conclusion............................................................................................................................................87
Task [12/M 5].......................................................................................................................................88
Produce a technical and user documentation for a fully functional system, including diagrams
showing movement of data through system and flowcharts describing how the system work...........88
Introduction..........................................................................................................................................88
Important Features of Application.......................................................................................................88
Significance of Application..................................................................................................................88
Limitation of Application.....................................................................................................................89
Choice of tools.....................................................................................................................................89
Layout of Designed Application..........................................................................................................89
Data Dictionary use in Application......................................................................................................90
Flow chart of Application....................................................................................................................91
Use Case Diagram for Application......................................................................................................95
Context or 0-level Diagram for Application........................................................................................95
Project Plan (Gantt chart).....................................................................................................................96
Database Structure...............................................................................................................................96
Product Deployment.............................................................................................................................98
Maintenance technique.........................................................................................................................99
Conclusion............................................................................................................................................99
Bibliography.......................................................................................................................................100
Task [1/P 1]
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.
Introduction:
Sagar Timalsina (HND / First Semester)

7
Database 2018
In RDBMS, the information store in database tables, fields. Each RDBMS table consists of database
table rows and each database table row consists of one or more than one database table fields.
RDBMS structured the information into collection of tables, which might be related each other.
RDBMS also provide relational operators to manipulate the data stored into the database tables. The
standard user and application program interface to a relationship database in the Structure Query
Language (SQL).
Choice of tools
IDE: VisualStudio-2017 community edition
Programming Language – C# using .Net Framework
Relational Database Management System – SQL server -express edition
Platform: Desktop Application
The most common RDBMS are MS SQL Server, Oracle and MySQL. Here I use MS SQL server to
design database program for back end and also use Visual studio-2017 for front end to create desktop
application using C# programming language. In this task, I would like to describe about relational
database management system, entity relationship diagram using appropriate design tools and
techniques containing eight tables. Each row contains a unique instance of data for the categories
defined by the columns and also maintain a defined relationship. Also design relationship diagram
and data dictionary.
Entity Relational Diagram (ERD)
Entity relational diagram is technique of data modeling which graphically representing the logical
relationship between entities while before creating database (Rouse, 2018). In ERD, database
structure is represent in form of diagram.
Sagar Timalsina (HND / First Semester)

8
Database 2018
Figure: Entity Relationship Diagram
Figure: Entity Relationship Diagram
Above figures are the ERD of ‘SMS’ database which have different eight tables name as Product,
Purchase, Sales, Suppliers, Customer, UserInfo, UserRole, and UserRoleAssignment. Product table
have nine different columns, they are ProductID, ProductName, Size, Brand, UOM, Size, SalesPrice,
CreatedOn, CreatedBy. Purchase table have eight different columns, they are PurchaseID,
ProductID, PurchaseOn, PurchaseRate, PurchaseQty, SupplierID, CreatedOn, and CreatedBy. Sales
table have different seven columns name as SalesID, ProductID, SalesDate, SalesQty, CustomerID,
CreatedOn, and CreatedBy. Supplliers table have six different columns name as SupplierID,
SupplierNmae, SupplierAddress, SupplierContact, CreatedOn, and CtreatedBy. Customer table have
six different columns name as CustomeID, CustomerName, CustomerAddress, CustomerConatct,
CreatedOn, and CreatedBy. These are the different tables have different column names in my
database system. In my database system, based on given scenario I implement or maintain one to
many relationship between Product and Purchase, Product and Sales, Sales and Customer, Purchase
and Supplliers tables. Product is parent table for Purchase and Sales tables where ProductID is
common in these tables. Supplliers table is also parent table for purchase where SupplierID is
common in these tables. Customer table is also parent table for Sales table where CustomerID is
common in these two tables. In other three tables name as UserInfo, UserRole and
UserRoleAssignment tables, there are different columns which shown in above ER diagram figure.
Also in these tables, I maintain one to many relation between UserInfo and UserRoleAssignment,
Sagar Timalsina (HND / First Semester)

9
Database 2018
UserRole and UserRoleAssignment. For UserRoleAssignment table both UserInfo and UserRole
tables are parent tables.
Relational Diagram
Relational diagram is diagram which show all various or different factor areas or processes.
Relational diagram define how your system is process, also define uses of different factor in your
database system.
Figure: Relation Diagram of SMS database system.
Above figure shows the relational diagram of my database system ‘SMS’. It shows this system is
new software based user or admin training which increase profitability of this system. It increase
customer services, increase consumption also increase operating cost.
Data Dictionary
Data dictionary is the collection of database table’s information like database data, its relationships,
data type. It define each columns of the table, its name datatype, relationships.
Here, I prepare some data dictionary in form of table to define its column name, data type, and its
relationship based on given scenario. I have different eight tables and different data dictionary which
are as follows:
Table1:Product
TableName CloumnName DAtaType AllowNull isPK isFk
Referenc
e Remarks
Sagar Timalsina (HND / First Semester)

10
Database 2018
Product ProductID Uniqueidentifier N Y N _ _
Product ProductName Varchar Y N N _ _
Product Size Varchar Y N N _ _
Product Brand Varchar Y N N _ _
Product UOM Varchar Y N N _ _
Product MiniStockLevel Varchar Y N N _ _
Product Salesprice Varchar Y N N _ _
Product CreatedOn Datetime Y N N _ _
Product CreatedBy Varchar Y N N _ _
Above table is product table data dictionary. In above table, I define each columns name and its data
type. I also maintain relationship using foreign key and primary key. In ProductID column, I
implement primary key to unique its records and not to accept null value. Its datatype is also
Uniqueidentifier. In other columns also have its own data datatype, it accept null values, there are
no primary and foreign key. This above table define each items or records, relationship of Product
table.
Table2:Purchas
e
TableName CloumnName DAtaType
AllowNul
l isPK isFk
Referenc
e
Remark
s
Purchase PurchaseID
Uniqueidentifie
r N Y N _ _
Purchase ProductID
Uniqueidentifie
r Y N Y Product _
Purchase PurchaseOn Varchar Y N N _ _
Purchase PurchaseDate Varchar Y N N _ _
Purchase PurchaseQty Varchar Y N N _ _
Purchase SupplierID
Uniqueidentifie
r Y N Y Supplliers _
Purchase CreatedOn Datetime Y N N _ _
Purchase CreatedBy Varchar Y N N _ _
This is Purchase table data dictionary. In above table, I define each columns name and its data type. I
also maintain relationship using foreign key and primary key. In PurchaseID column, I implement
primary key to unique its records and not to accept null value. Its datatype is also Uniqueidentifier. In
other columns as ProductID and SupplierID, there are foreign and theirs data types are
Uniqueidentifier but it accept null values. This above table define each items or records,
relationship of Purchase table.
Table3 :Sales
TableName CloumnName DAtaType
AllowNul
l isPK isFk
Referenc
e Remarks
Sagar Timalsina (HND / First Semester)

11
Database 2018
Sales SalesID Uniqueidentifier N Y N _ _
Sales ProductID Uniqueidentifier Y N Y Product _
Sales SalesOn Varchar Y N N _ _
Sales SalesQty Varchar Y N N _ _
Sales CustomerID Uniqueidentifier Y N Y Customer
Sales CreatedOn Datetime Y N N _ _
Sales CreatedBy Varchar Y N N _ _
This is Purchase table data dictionary. In above table, I define each columns name and its data type. I
also maintain relationship using foreign key and primary key. In SalesID column, I implement
primary key to unique its records and not to accept null value. Its datatype is also Uniqueidentifier. In
other columns as ProductID and CustomerID, there are foreign and theirs data types are
Uniqueidentifier but it accept null values. This above table define each items or records,
relationship of sales table.
Table4:Supplliers
TableName CloumnName DAtaType
AllowNul
l isPK isFk Reference
Remark
s
Supplliers SupplierID Uniqueidentifier N Y N _ _
Supplliers SupplierNAme Varchar Y N N _ _
Supplliers SupplierAddress Varchar Y N N _ _
Supplliers SupplierContact Varchar Y N N _ _
Supplliers CreatedOn Datetime Y N N _ _
Supplliers CreatedBy Varchar Y N N _ _
Table5:Customer
TableName CloumnName DAtaType AllowNull
isP
K isFk
Referenc
e Remarks
Customer CustomerID Uniqueidentifier N Y N _ _
Customer CustomerName Varchar Y N N _ _
Customer CustomerAddress Varchar Y N N _ _
Customer CustomerContact Varchar Y N N _ _
Customer CreatedOn Datetime Y N N _ _
Customer CreatedBy varchar Y N N _ _
Above two tables are Suppliers and customer table data dictionary. These above table define each
item or records, relationship of two Suppliers and customer tables.
Table6:UserInf
o
Table Name Cloumn Name Data Type
AllowNul
l isPK isFk
Referenc
e Remarks
UserInfo UserID Uniqueidentifier N Y N _ _
UerInfo FirstName varchar Y N N _ _
Sagar Timalsina (HND / First Semester)

12
Database 2018
UserInfo MiddleName varchar Y N N _ _
UserInfo LastName varchar Y N N _ _
UerInfo Email varchar Y N N _ _
UserInfo UserName varchar Y N N _ _
UserInfo UserPassword Varbinary Y N N _ _
Userinfo isActive Bit Y N N _ _
UerInfo CreatedOn Datetime Y N N _ _
UserInfo CreatedBy varchar Y N N _ _
Above table is userinfo table data dictionary. This above table define each items or records,
relationship of UserInfo table. UserID datatype is uniqueidentifier where I implement primary key.
In UserPassword column, its data type is varbinary which use to encrypt to maintain security.
Table7:UserRole
TableName CloumnName DAtaType
AllowNul
l isPK isFk
Referenc
e Remarks
UserRole RoleID Uniqueidentifier N Y N _ _
UserRole RoleName Varchar Y N N _ _
UserRole isActive Bit Y N N _ _
UserRole CreatedOn Datetime Y N N _ _
UserRole CreatedBy varchar Y N N _ _
Above table is UserRole table data dictionary. This above table define each items or records,
relationship of UserRole table.
Table8:
UserRoleAssignment
TableName
CloumnNam
e DAtaType
AllowNul
l isPK isFk Reference Remarks
UserRoleAssignment UserID Uniqueidentifier N N Y UserInfo _
UserRoleAssignment RoleID Uniqueidentifier N N Y UserRole _
UserRoleAssignment CreatedOn Datetime Y N N _ _
UserRoleAssignment CreatedBy Varchar Y N N _ _
Above table is UserRoleAssignment table data dictionary. This above table define each items or
records, relationship of UserRoleAssignment table.
User Requirement
Considering with given scenario, I designed database name as ‘Stationary Management System’ for
stationary shop. In database, I created different eight table for stationary which helps to unique each
its table as well as column records to overcome spreadsheet records. This database system is
designed on basis of user requirement. User have required database to store data uniquely in regular
basis. Database system automate and centralize their record to stock, customer where every data is
Sagar Timalsina (HND / First Semester)

13
Database 2018
properly organized and provide greater efficiency to user. So the designed database is absolute met
with user requirement.
Conclusion
In order to complete this task, I implement database system with its entity relationship diagram,
relational diagram based on given scenario and user requirement in regular basis to overcome
spreadsheets records. To complete this task, I also define its data type like int, varchar, etc. To
maintain table’s relationships, I also implement primary key as well as foreign key. This designed
based is absolute met user requirement.
Task [2/M 1]
Produce a comprehensive design for a fully functional system which includes interface and
output design, data validation and data normalization.
Introduction
Database is the collection of data. Data validation and normalization are technique to store data in
database system. Data validation is use to prove that somewhat is based on fact and data
normalization is process to well organize data in database. In this task, I am going to implement fully
functional system using appropriate tools. Also discuss about data validation and normalization.
Choice of tools
IDE: VisualStudio-2017 community edition
Programming Language – C# using .Net Framework
Relational Database Management System – SQL server -express edition
Platform: Desktop Application
Implement fully functional system
Fully function system is those system where user give input and get some result or output in the
system. Here I have desktop based application designed using C# programming language with.Net
framework in visual based. This application is user based desktop application which hit back end
system SQL server. Where user can store different product details, purchase details, sales details,
supplier details and customer details. This designed system is very useful for user to store related
details. Here user can give some input and get some output without any standard query language
which store data in the database server system. So to use this application user not need to understand
any query language. Here I have some evidence to show the designed application is fully function for
user requirement. So evidence areas follows;
In login page user have to supply right user name and password as input and get success message as
output which is shown on below.
Sagar Timalsina (HND / First Semester)

14
Database 2018
In product page, where user forget to insert product name in product details as input, it show product
name required message in output.
These are the some example to show designed system in fully functional system on user requirement.
It get some input from user and give some output on the basis of user requirement. Above example
show the designed system or application is fully functional.
Data Normalization
Sagar Timalsina (HND / First Semester)

15
Database 2018
Data normalization is the process to organize data in database system (Rouse, 2016). Data
normalization is very useful to reduce data redundancy and data dependency. There are different
types of data normalization. Among the first normal, second normal, and third normal for data
normalization are more useful in daily activity which are as follow;
Types to Normalization
 First Normal form: It is the sets of essential rules of database. In this form, table records must
be of single value. First normal form eliminate repeating groups in tables and also create a
separate table for each related data.
 Second Normal Form: It is concept of remove duplicate data from database table. To take
second normal form table values must be in first normal form. It is use to remove partial
dependencies. It also helps to create separate table with the functionally dependent records.
 Third Normal Form: It is large normalization among the first and second normal form. Most
of the data in database are in third normal form. To take third normal form table values must
be in second normal form and it is use to remove transitive dependencies.
Existing Method – (excel file) vs database normal form
 Exiting method
Above figure shows the existing method of data which is store in excel file. There some data are
repeated where data is redundant. To overcome the data redundancy and manage data storage data
should normalize in different from which are shown below in data normalization form.
Database Normal form
1. First Normal form
Sagar Timalsina (HND / First Semester)

16
Database 2018
In above figure, there data normalize in first normal form to replace to store data in existing
method. Their each record are must be in single form and helps to maintain data accuracy.
Their also may occurs problem like data redundancy and need large storage. To replace the
first normal form, second normal form is made.
2. Second Normal form
Above figure shows the data in second normal form which is normalization of data in
database. In this figure there are three different table name as Product, Supplier, and
customer. Their repeated data are remove and each record off these table are unique with its
id which helps to reduce data redundancy.
3. Third Normal form
Above figure shows the data in third normal form which is normalization of data in database.
In this figure there are different five tables with their relationship table name as product,
supplier, sales, purchase, and customer. Their all repeated data’s are remove with its
transitive dependencies. Their two table as Purchase and sales are child table for product,
customer, and supplier which helps to maintain relationship between all tables.
 Database Diagram
Database diagram shows the database table information with its column name and also define
their relationship.
Sagar Timalsina (HND / First Semester)

17
Database 2018
Figure: Database Diagram
Data Validation
Data validation is a method of data cleansing. It is use to check accuracy and quality of source data
before importing or using data. Various type of validation can be performed depending on its
objectives.
Client-side validation
Client side validation is a type of validation which is use to take user input. In client side validation,
user input takes place in client side. Client side validation take place with user interface, where user
interact with client side.
In my system, I implement client side validation while making Login page which is user validation
which based on user input. For example, here I have some evidence of client side validation with
user input. If user enter wrong password as well as user name, it display ‘invalid username or
password’ message and if user enter right username with right password, it show ‘success’ message.
1.Wrong username with wrong password 2.Right username with right password
Sagar Timalsina (HND / First Semester)

18
Database 2018
Server-side and database validation
Server side validation take place in server side if user input validation take post back session is
known as server side validation. Server side validation is code level validation. For example, if user
try to insert some values then it show field require value message. In my system it takes in
ProductName filed which shows ‘Product Name is required’ message.
In database, trigger can be used for server side validation which helps to manage three different
event as insert event, update event, and delete event where trigger is take place.
Conclusion
In order to complete this task, I implement fully functional system to overcome spreadsheets records
for stationary. I also produce documentation on how data validation and normalization achieved.
Implemented fully functional system is more useful for user interaction which implement in regular
basis. I also discussed about data normalization type and data validation with client –side as well as
server-side validation.
Task [4/P 2]
Develop the database system with evidence of user interface, output and data validations, and
querying across multiple tables.
Introduction
Database system is a type of software which allows to create and manage databases. It provide an
interface between the database and user or application, which ensure that data is well manage or
organize and remain easily accessible. (Rouse, n.d.) Data validation is the process of database which
provides data consistent. In database key has important role to establish and identify relationships
between tables and also provide uniquely identify row of data inside a table. In this task I am going
to develop database with evidence of user interface, output and data validations, and querying across
multiple tables on given scenario.
Sagar Timalsina (HND / First Semester)

19
Database 2018
Implement Constraints
Primary Key: Primary key is a type of constraint which help to uniquely identify each values in
database table. (Chapple, 2018) Here I have different eight tables name as Product, Purchase,
Sales, Supplliers, Customer, UserInfo, UserRole, and UserRoleAssignment where one of the
column of each table, I have to implement primary key. Here I implement Primary Key on
Product (ProductID), Purchase (PurcahseID), Sales (SalesID), Supplliers (SupplierID),
Customer (CustomerID), UserInfo (UserID), UserRole (RoleID).
In Product (ProductID):
ALTER TABLE Product
ADD PRIMARY KEY (ProductID)
In Purchase (PurcahseID):
ALTER TABLE Purchase
ADD PRIMARY KEY (PurchaseID)
In Sales (SalesID):
ALTER TABLE Sales
ADD PRIMARY KEY (SalesID)
In Supplliers (SupplierID):
ALTER TABLE Supplliers
ADD PRIMARY KEY (SupplierID)
In Customer (CustomerID):
ALTER TABLE Customer
ADD PRIMARY KEY (CustomerID)
In UserInfo (UserID):
ALTER TABLE UserInfo
ADD PRIMARY KEY (UserID)
In UserRole (RoleID):
ALTER TABLE UserRole
ADD PRIMARY KEY (RoleID)
Foreign Key: Foreign key is a type of constraint which used to link multiple table based on parent
table that refers primary key. Here I have different eight table, I have to maintain relation using
foreign key so, I implement foreign key on Purchase(ProductID), Purchase(SupplierID),
Sales(ProductID), Sales(CustomerID), UserRoleAssignment(UserID), UserRoleAssignment(RoleID).
In Purchase (ProductID):
Sagar Timalsina (HND / First Semester)

20
Database 2018
ALTER TABLE Purchase
ADD FOREIGN KEY(ProductID) REFERENCES Product(ProductID)
In Purchase (SupplierID):
ALTER TABLE Purchase
ADD FOREIGN KEY(SupplierID) REFERENCES Supplliers(SupplierID)
In Sales (ProductID):
ALTER TABLE Sales
ADD FOREIGN KEY(ProductID) REFERENCES Product(ProductID)
In Sales(CustomerID):
ALTER TABLE Sales
ADD FOREIGN KEY(CustomerID) REFERENCES Customer(CustomerID)
In UserRoleAssignment(UserID):
ALTER TABLE UserRoleAssignment
ADD FOREIGN KEY(UserID) REFERENCES UserInfo(ProductID)
In UserRoleAssignment(RoleID):
ALTER TABLE UserRoleAssignment
ADD FOREIGN KEY(RoleID) REFERENCES UserRole(RoleID)
Unique Key
Unique key is same as primary key but it accept only one null value and it no allowed to accept
duplicate values.
Not Null
It is a type of constraints which enforce column to not accept null values. In SQL by default column
hold null values. Not null enforce filed to contain value, when you insert record in database system.
Evidence of user interface and data validation
User interface is the view of database where user have ability to input query in database without use
query language of database. It means user can control a software application or hardware devices.
Data validation is the process which helps to make data accuracy on user input. So that I develop one
desktop application using visual studio, C# programming language to make data consistence on user
Sagar Timalsina (HND / First Semester)

21
Database 2018
input where this application provides consistence data in database. This program is very friendly
with user and make data consistence.
I have some evidence of user interface. For user interface, I have login page where user can log on
and access database records. If user name and password is wrong then its show error message as
‘Invalid User Name or Password! ’.
Figure: Log in error
If user name and password is right then its show ‘success’ with ’login Successfully’ message and
user have to click ‘Ok’ then user able to do some work on database without database query language
using front end program or application.
Figure: Log in success
This is the some evidence of user interface of my desktop base application which is very friendly
application with user.
In case of data validation, I implement filed validation with message, drop down validation in my
program which helps to user input more easier so it also provide consistent data on database. I have
some evidence of data validation which are as follows:
Sagar Timalsina (HND / First Semester)

22
Database 2018
1. Filed validation with message: In my application, I implement field validation in Product
(ProductName), Supplliers (SupplierName), and Customer (CustomerName).
In Product: When user try to insert some record in product without ProductName, then the
program show message ‘Product Name is required’, this is ProductName field validation in
Product table which shown in below figure:
Figure: Product name required.
In Supplliers: When user try to insert some record in Supplliers without SupplierName, then the
program show message ‘Supplier Name is required’, this is SupplierName field validation in
Supplliers table which shown in below figure:
Figure: Supplier name required.
In Customer: When user try to insert some record in Customer without CustomerName, then the
program show message ‘Customer Name is required’, this is CustomertName field validation in
Customer table which shown in below figure
Sagar Timalsina (HND / First Semester)

23
Database 2018
Figure: Customer name required.
2. Drop down validation:
In Purchase: When user try to insert some record in Purcahse, then the program show some
ProductName as well as SupplierName in dropdown, these are ProductName in ProductID as
well as SupplierName in SupplierID dropdown validation in Purchase table which shown in
below figure:
Figure: Purchase dropdown validation.
In Sales: When user try to insert some record in Sales table, then the program show some
ProductName as well as CustomerName in dropdown, these are ProductName in ProductID
as well as CustomerName in CustomerID dropdown validation in Sales table to make
consistent data which shown in below figure:
Sagar Timalsina (HND / First Semester)

24
Database 2018
Figure: Sales dropdown validation.
Validate data querying multiple tables using joins
Join is the feature of database which is use to attach multiple table which helps to see multiple table
records. It establish connection between different tables. There are different types of join which are
as follows;
Join types
 Inner join: It is most common and useful join which is used to create seeing similar values
or record from multiple table where join conditions is met.
 Left-outer join: In this type of join returns all rows from the left-hand table specified in the
on condition and only those rows from the other table where the joined fields are equal.
 Right-Outer join: In this type of join return all rows from the left-hand table specified in the
on condition and only those rows from the other table where the joined fields are equal.
 Full join: In this type of join return all rows from left-hand, right-hand table with nulls in
place where the join condition is not met.
 Cross join: Cross join is use to produce a set of result which is number of rows in first table
multiple by numbers of rows in second table. It is also to for Cartesian product.
These are the some types of join which use to see data from multiple. Here I have some join query
that use to see data in my database system which are as follows;
Query to see balance quantity using multiple join:
Sagar Timalsina (HND / First Semester)

25
Database 2018
Output:
Query to see product, purchase, supplier detail using join:
Output:
Conclusion
Sagar Timalsina (HND / First Semester)

26
Database 2018
In order to complete this task, I implement primary key, foreign key, and unique key, not null in my
database system. The different key helps to maintain relationship in database. To complete this task,
I also make some evidence of user interface as well as data validation. Data validation and user
interface helps to work in front end program without using query language. I also discuss about
different data validation query using join to seen data in database system.
Task [5/M 2]
Implement a fully functional database system which includes system security and database
maintenance.
Introduction
Database security is the process of keeping data secure from unauthorized access or corruption in
database system. Database system is a software which helps to create or manage database. In this
task, I am going to implement fully functional database system with security and also implement
database maintenance based on given scenario.
System Security
In SQL Server and Windows mode Authentication, you need to create SQL Server Logins and you
have to supply User name and password while you run SQL server. It provides more security in
database system more than windows authentication. In Windows mode authentication user are
already logon to system without requiring any user name or password. So, in my database system I
use SQL Server and Windows Authentication mode in server authentication for database security. It
is mixed mode to authenticate server.
Figure: Authentication Mode
Password Policy
SQL server provides password policy for login which helps to secure your records in database. In my
database system, I enable password policy also to secure data or records from unauthorized access.
Sagar Timalsina (HND / First Semester)

27
Database 2018
Figure: Password Policy
In order to secure my database system I have require to implement different SQL programmability
features like store procedure, trigger, functions, views, etc.
Store procedure
Store procedure is structure query language statement with given name store in database system
which can be reused and share by multiple program (Rouse, 2014). Store producer in SQL server
take multiple input parameters and return multiple values of parameter in the form of output. It
allows modular programming, faster execution, and also use to reduce network traffic. It is use to
access data from database.
In my database system, I implement store procedure to access data from data base with its input
parameter as ‘@productid’ which is using in following query:
Query for Store procedure
This is the query to create store procedure. After creating procedure, if we use following query
passing with its input parameter as ‘@productid’, it show following output which are as below;
Sagar Timalsina (HND / First Semester)

28
Database 2018
 Query
EXEC USP_StockReport '542BBADD-B394-417B-9518-0B5B75EC5274'
 Output
Trigger
Trigger is special type of procedure which is automatically executes when event occurs in database.
DML trigger execute when user try to modify through DML (data manipulation language). DML
trigger has three different event as insert, update, delete.
Here I have some example of trigger which are implemented in my database system. To implement
trigger in database system need to make new table for Product same as this table.
 Query:
Query trigger from Product Table
 Query
This is the query to create trigger in database system
Functions
Sagar Timalsina (HND / First Semester)

29
Database 2018
Function is an activity to perform something on of its operation. There are different types of function
in database system as table value function, scalar value function, aggregate function, system
function.
Types of function:
 Table-value Function: Table value function is known as user define function that return table
data type which is powerful alternative to views. The value of table variable should be
derived from a single SELECT statement.
 Scalar-valued Function: Scalar value function is also known as user define function which
returns single value as a result of actions perform by function. It return any datatype value
from this function.
 Aggregate Function: An aggregate function use to perform a calculation on a set of values to
return a single scalar value. Aggregate functions can perform in select lists and in ORDER
BY and HAVING clauses
 System Function: In SQL Server system, system functions perform processes on and return
information about values or record, objects, and settings in SQL Server.
These are the some type of function which are in database system. For Example, here I have some
table value function in system which are as follows;
Query for table-valued function:
 Query
select * from udf_GetSupplierNameByAddress('Baneshwor')
 Output
Views
Sagar Timalsina (HND / First Semester)

30
Database 2018
Views is accessible object which is characterized by structure query language in database. It is also
known as virtual for table when view is created on this table in database system. It provides security
as well as query simplicity and also enhance programming productivity.
For Example, I have implement view in my system to see details of records which is shown in
below;
Query for creating View name as Details:
After that, the view is created which make query simplicity. After creating view, we do not write
complex query more than one type which is increase querying performance. Then we can see
complex query in single select form.
 Query
SELECT * FROM Details
 Output
Database Maintenance
Database Maintenance is define as a set of tasks that are all run with the intent to improve database
system which means to find corruption, to increase system performance etc. It is use to control
redundancy control in data storage restricting unauthorized data which also provide backup and
recovery plan.
Sagar Timalsina (HND / First Semester)

31
Database 2018
Log file and data file management
Log file is aggregate procedures and rules which is used to administer and facilitate the generation,
transmission, analysis, storage, archiving and ultimate discarding of the large volumes of log data
produced within an information system. Operational log management is important to both security
and agreement. Log management software automates several of the processes involved. Data file
management is the effective system uses to establish and keep track of files. A file management
system is a type of software which manage data files in a computer system. It also known as file
manager. Data file management manage all files and data types in database management system.
Corruption Detection
Corruption detection is also the part of database maintenance. Database corruption is defined as a
problem related with the unsuitable storage of the real zeroes and ones required to store database data
in external storage. To detect the corruption problem is known as corruption detection.
In database to find out corruption, we use DBBC command which shown in below with its query as
well as output of my database system.
 Run DBCC command
 Query
DBCC CHECKDB (SMS)
 Output
Index Fragmentation
In SQL index fragmentation is occurs when data is stored in a non- contiguous way. When data is
modify in database, the indexes of it’s become fragmented. When indexes fragmented, retrieval data
become less efficient and reduce performance. Index fragmentation also helps to maintenance of
database. Here I have some query to see index fragmentation, query with its output as below;
Sagar Timalsina (HND / First Semester)

32
Database 2018
 Query
 Output
Backup Plan
Normally backup means copy of something like data, file etc. in case the original is lost. In SQL
backup is created to store or copy database data. Copies data from SQL server can be used to restore
and recover the data after a failure. A backup in SQL is created at the level of database not table
level. Backing up data from SQL server database is essential for protecting data.
There are different types of backup in SQL server database as full backup, differential backup, and
log backup. A more use backup that is self-determining of the regular sequence of SQL Server
backups.
Types of Backup
 Full back up: Full backup is the starting phases for all other backups and contains all data in
folders and files which are select to be backed up. The full backup stores all files and folders
all data, frequent full backups result in faster and simpler restore operations
 Differential backup: A differential backup is based on the most recent, previous full
data backup. It captures only the data that has changed since that full backup.
 Log backup: It is a serial record log of all transactions which is performed against database
since the transaction log was last backed up. It is the base of both differential backup and
transaction log backup.
Sagar Timalsina (HND / First Semester)

33
Database 2018
Step to Implement Full Back up in System
Step1: Click on management then click
maintenance and click maintenance plan wizard.
Step2: Then click on next.
Step3: Then give name for backup. Step4: Then click on schedule and set schedule
for back up then click ok and click on next.
Step5: Choose the Backup plan, here I choose
full backup then click on next.
Step6: Click on next.
Sagar Timalsina (HND / First Semester)

34
Database 2018
Step7: Click on backup component then choose
database for backup plan, click on ok and Click
next.
Step8: Define a path for back up and click on
next.
Step9: Click on next. Step10: Click On finish.
Sagar Timalsina (HND / First Semester)
Step11: After some time backup plan is finish
then click on close.

35
Database 2018
Finally, I implement full backup plan in my database system.
These are the some steps to implement full back in database system. For differential and log backup
we have to implement differential as well as log back up plan by selecting differential and log
backup in maintenance wizard page.
Restore Plan
Simply restore is bring back something which was backed up. In SQL term restore is define as to
store file or some information of database system which may backed up before failure. Restore plan
is actually done after the backed up plan got success.
Here I have some step how to restore database in SQL server which are as follows;
Restore back up file in System
Step1: Right click on Database then choose New
database.
Step2: After choosing new database, you have
to give path where back up file located.
Step3: Then click on option and choose overwrite
the existing database.
Step4: After some time restore is finish then
click on.
Sagar Timalsina (HND / First Semester)

36
Database 2018
Conclusion
In order to complete this task, how your system is fully functional. Here I discuss system security
which make database data secure applying database password policy that is already discuss in above.
I also discuss about how to create store procedure, trigger, function and views, how actually they
dose. Here I also discussed about how database maintenance from corruption fragmentation and also
discuss about back up as well as restore plan with their implementing steps.
Task [6/P 3]
Implement a query language into the relational database system.
Introduction:
Query language is the set of command use to retrieve data form database. So in this task, I am going
to write some basic SQL queries for insert, update, delete and select statements which is use in back
end as well as in the front end while doing queries. The back end queries will do in some server like
database and front end query is use to get data from database where user try to see data using certain
IDE like here I use visual studio. Here, I have to implement a query language use in back end as well
as in the front end based on give scenario which are as follows:
Insert Statement
Insert statement is used to insert one or more records in table. In insert statement, I implement insert
query based on scenario. Here I have eight tables name as Product, Purchase, Sales, Supplliers, and
Customer where I have to implement insert statement.
In Product: In Product table, there are different nine columns name as ProductID, ProductName,
Size, Brand, UOM, MiniStockLevel, SalesPrice, CreatedOn, and CreatedBy.
Sagar Timalsina (HND / First Semester)

37
Database 2018
Back end Insert Query:
insert into Product
values (NewID(),'Stapler PIN', 'Small', 'Kangaro', 'PKT', '30', '28',
GetDate(), SYSTEM_USER),
(NewID(),'INK', 'Large', 'Pilot', 'Bottle', '18', '300', GetDate(),
SYSTEM_USER),
(NewID(),'Pencil', 'Normal', 'Nataraj', 'PKT', '25', '35', GetDate(),
SYSTEM_USER),
(NewID(),'A4 Paper', 'Normal', 'Jastin', 'RIM', '20', '250', GetDate(),
SYSTEM_USER),
(NewID(),'NoteCopy', 'Medium', 'Surya', 'PCS', '15', '220', GetDate(),
SYSTEM_USER),
(NewID(),'NoteCopy', 'Large', 'surya', 'PCS', '28', '45', GetDate(),
SYSTEM_USER),
(NewID(),'Pen', 'Normal', 'Schneider', 'PKT', '30', '30', GetDate(),
SYSTEM_USER),
(NewID(),'INK', 'Medium', 'Aurora', 'Bottle', '17', '200', GetDate(),
SYSTEM_USER),
(NewID(),'Pencil', 'Normal', 'Tombow', 'PKT', '14', '15', GetDate(),
SYSTEM_USER)
Front end Insert Query:
private void btnSave_Click(object sender, EventArgs e)
{
if (txtProductName.Text == "")
{
MessageBox.Show("Product Name is required.");
return;
}
conn.Open();
String query = "INSERT INTO
Product(ProductID,ProductName,Size,Brand,UOM,MiniStocklevel,SalesPrice,CreatedOn,Crea
tedBy)
Values(NewID(),'"+txtProductName.Text+"','"+txtSize.Text+"','"+txtBrand.Text+"','"+Tx
tUOM.Text+"','"+txtMinStockLevel.Text+"','"+txtSalesPrice.Text+"',GETDATE(),USER_NAME
())";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Product Inserted Successfully");
refresh_data();
conn.Close();
dataLoad();
}
In Purchase: In Purchase table, there are different eight columns name as PurchaseID, ProductID,
PurchaseOn, PurchaseRate, PurchaseQty, SupplierID, CreatedOn, CreatedBy.
Sagar Timalsina (HND / First Semester)

38
Database 2018
Back end Insert Query:
NSERT INTO Purchase
VALUES(NEWID(),'015C9A06-95C3-4159-8E86-0DE4D69E2A3D', '2017-02-04', '20',
'100','C2D26F70-F5DB-4C99-94D3-568F06E60E7C', GETDATE(), SYSTEM_USER),
(NEWID(),'C195AB76-8C07-43CF-BCC5-11A9DBF37127', '2017-01-01', '20', '200',
'07D10F99-DACF-4AB3-B4C3-8C3DEDE09A39', GETDATE(), SYSTEM_USER),
(NEWID(), 'B5C6E6E1-4560-4BC0-803B-19D4B2ED3B6D', '2017-01-02', '30', '50',
'885680EA-02D0-4B8B-9125-64A587AF6AD4', GETDATE(), SYSTEM_USER),
(NEWID(), '962BA293-4494-419F-9BA1-D81CE9E26C12', '2017-07-09', '200', '100',
'A0CD8276-C1A7-4CE2-84D0-B92CB522BA47', GETDATE(), SYSTEM_USER),
(NEWID(), '698F0D19-8965-438B-8DCF-83A1903958CE', '2017-06-06', '200', '100',
'885680EA-02D0-4B8B-9125-64A587AF6AD4', GETDATE(), SYSTEM_USER),
(NEWID(), '172E6F3D-D979-4FDD-9A84-9053E52DC5FE', '2017-02-03', '40', '50',
'A0CD8276-C1A7-4CE2-84D0-B92CB522BA47', GETDATE(), SYSTEM_USER),
(NEWID(), '203E010D-832D-4F8B-B3D6-9BBD9361906F', '2017-10-10', '150', '200',
'C2D26F70-F5DB-4C99-94D3-568F06E60E7C', GETDATE(), SYSTEM_USER),
(NEWID(), 'F1D90089-1BD7-4081-9A69-ABFCA08B3AE2', '2017-03-05', '150', '200',
'885680EA-02D0-4B8B-9125-64A587AF6AD4', GETDATE(), SYSTEM_USER),
(NEWID(), '962BA293-4494-419F-9BA1-D81CE9E26C12', '2017-07-08', '10', '100',
'C2D26F70-F5DB-4C99-94D3-568F06E60E7C', GETDATE(), SYSTEM_USER),
(NEWID(), 'B5BFBC46-0B15-495B-8B84-F35F2E190945', '2017-06-07', '20', '200',
'505599AE-F71A-43C7-B42A-9AAEFED94287', GETDATE(), SYSTEM_USER)
Front end Insert Query:
private void btnSave_Click(object sender, EventArgs e)
{
if (txtPurchaseID.Text == " ")
{
MessageBox.Show("PurchaseID is Required.");
return;
}
conn.Open();
String query = "Insert into Purchase
(PurchaseID,ProductID,PurchaseOn,PurchaseQty,SupplierID)values ( NewID(),'" +
txtProductID.SelectedValue.ToString() + "','" + txtPurchaseOn.Text + "','" +
txtPurchaseQty.Text + "','" + txtSupplierID.SelectedValue.ToString()+ "',GETDATE(),
SYSTEM_USER)";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Purchase Inserted Sucessfully.");
refresh();
conn.Close();
dataLoad();
}
In Sales: In Sales table, there are different seven columns name as SalesID, ProductID, SalesDate,
SalesQty, CreatedOn, CreatedBy.
Back end Insert Query:
VALUES (NEWID(), '015C9A06-95C3-4159-8E86-0DE4D69E2A3D', '2017-01-02', '15',
'37AF8958-8E31-4DEC-B399-0E0DA9AC39CA', GETDATE(), SYSTEM_USER),
(NEWID(),'C195AB76-8C07-43CF-BCC5-11A9DBF37127', '2017-06-07', '5', 'A0E8479B-764C-
451C-BD37-20B500C68F83',GETDATE(), SYSTEM_USER),
Sagar Timalsina (HND / First Semester)

39
Database 2018
(NEWID(), 'F1D90089-1BD7-4081-9A69-ABFCA08B3AE2', '2017-10-21', '10',
'6D0124AB-C0AA-4D5F-8320-0F7E50F9ED4C', GETDATE(), SYSTEM_USER),
(NEWID(), '015C9A06-95C3-4159-8E86-0DE4D69E2A3D', '2017-07-09', '20',
'7FD3B89A-3716-4D33-A930-9716B0B98B48',GETDATE(), SYSTEM_USER),
(NEWID(), '698F0D19-8965-438B-8DCF-83A1903958CE', '1900-01-01', '0', '37AF8958-
8E31-4DEC-B399-0E0DA9AC39CA', GETDATE(), SYSTEM_USER),
(NEWID(), '203E010D-832D-4F8B-B3D6-9BBD9361906F', '2017-01-02', '10',
'67E9E940-5639-4567-B153-DAAA4EA4AC28', GETDATE(), SYSTEM_USER),
(NEWID(), 'F1D90089-1BD7-4081-9A69-ABFCA08B3AE2', '2017-07-10', '5', '09953099-
B0A4-4E23-97E7-9FB1A87BC907',GETDATE(), SYSTEM_USER),
(NEWID(), 'B5BFBC46-0B15-495B-8B84-F35F2E190945', '2017-03-05','2', '6D0124AB-C0AA-
4D5F-8320-0F7E50F9ED4C', GETDATE(), SYSTEM_USER)
Front end Insert Query:
private void btnSave_Click(object sender, EventArgs e)
{
if (txtProductList.Text==" ")
{
MessageBox.Show("ProductID is Required.");
return;
}
conn.Open();
String query = "Insert into
Sales(SalesID,ProductID,SalesDate,SalesQty,CustomerID)values ( NewID(),'" +
txtProductList.SelectedValue.ToString() + "'," + txtSalesDate.Text + "','" +
txtSalesQty.Text + "', '" + CustomerList.SelectedValue.ToString() + "'',
GetDate(),SYSTEM_USER)";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show ("Sales Inserted Sucessfully.");
refresh();
conn.Close();
dataLoad();
}
In Supplliers: In Supplliers table, there are different seven columns name as SupplierID,
SupplierName, SupplierAddress, SupplierContact, CreatedOn, and CreatedBy.
Back end Insert Query:
insert into Supplliers
values (NewID(), 'Argrawal Enterprises', 'KhichaPokhari', '442398', SYSTEM_USER
SYSTEM_USER)
(NewID(), 'Raj Treders', 'NewRoad', '4423189', GetDate(),SYSTEM_USER),
(NewID(), 'KK Supliers', 'Baneshwor', '443228', GetDate(), SYSTEM_USER),
(NewID(), 'Nepal Distributor', 'Koteshwor', '4423133', GetDate(),SYSTEM_USER),
(NewID(), 'KK Supliers','Baneshwor', '421768', GetDate(), SYSTEM_USER)
Front end Insert Query:
private void btnSave_Click(object sender, EventArgs e)
{
if (txtSupplierName.Text == "")
{
Sagar Timalsina (HND / First Semester)

40
Database 2018
MessageBox.Show("SupplierName is required.");
return;
}
conn.Open();
String query ="INSERT INTO
Supplliers(SupplierID,SupplierName,SupplierAddress,SupplierContact)
values(NewID(),'"+txtSupplierName.Text+"','"+txtSupplierAddress.Text+"','"+txtSupplie
rContact.Text+"', GetDate(), SYSTEM_USER)";
SqlDataAdapter sda = new SqlDataAdapter(query,conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Suppliers Insert Sucessfully.");
refresh();
conn.Close();
dataLoad();
}
In Customer: In Customer table, there are six different columns name as CustomerID,
CustomerName, CustomerAddress, CustomerContact, CreatedOn, and CreatedBy.
Back end Insert Query:
insert into Customer
values (NewID(),'Hari Bahadur', 'Balaju', '987740', GetDate(), SYSTEM_USER),
(NewID(),'Sunita Shrestha', 'Thankot', '98013', GetDate(), SYSTEM_USER),
(NewID(),'Sabita Chalise', 'Biratnagar', '9867737', GetDate(),
SYSTEM_USER),
(NewID(),'Mina Kumari Ojha', 'Basundhara', '987668', GetDate(),
SYSTEM_USER),
(NewID(),'Gopal Kharel', 'Naikap', '9851023', GetDate(), SYSTEM_USER),
(NewID(),'Mina Rewat', 'Bhadrapur' ,'98766', GetDate(), SYSTEM_USER)
Front end Insert Query:
private void btnSave_Click(object sender, EventArgs e)
{
if (txtCustomerName.Text == "")
{
MessageBox.Show("Customer Name is required.");
return;
}
conn.Open();
string query = "Insert Into
Customer(CustomerID,CustomerName,CustomerAddress,CustomerContact) Values(NewID(),'" +
Sagar Timalsina (HND / First Semester)

41
Database 2018
txtCustomerName.Text + "','" + txtCustomerAddress.Text + "','" +
txtCustomerContact.Text + "', GetDate(), SYSTEM_USER)";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Customer Insterted Sucessfully");
refresh();
conn.Close();
dataLoad();
}
In UserInfo: In UserInfo table, there are ten different columns name as UserID, FirstName,
MiddleName, LastName, Email, UserName, UserPassword, isActive, CreatedOn, and CreatedBy.
Back end Insert Query:
Insert Into UserInfo
values(NEWID(),'Shyam','','
Sharma','[e-mail]','shyam1','shyam123'),1,getdate(),SYSTEM_USER),
(NEWID(),'Ram','Prasad','
Karki','[e-mail]','pram','pram123'),1,getdate(),SYSTEM_USER),
(NEWID(),'Hari','','
Thapa','[e-mail]','hari','skiran123'),1,getdate(),SYSTEM_USER)
In UserRole: In UserRole table, there are five different columns as RoleID, RoleName, isActive,
CreatedOn, and CreatedBy.
Back end Insert Query:
insert into UserRole
values(NEWID(),'Shya',1,GETDATE(),SYSTEM_USER),
(NEWID(),'Ram',1,GETDATE(),SYSTEM_USER),
(NEWID(),'Hari',1,GETDATE(),SYSTEM_USER)
In UserRoleAssignment: In UserRoleAssignment table, there are two columns name as UserID and
RoleID.
Back end Insert Query:
insert into UserRoleAssignment
values( '77F34460-7FA7-4FD3-98BF-226D70E3A257', 'A8CF10E5-614C-450F-A228-
FAC129DDD08E', GETDATE(),SYSTEM_USER),
( 'AF34589F-8B65-4FAB-89CB-36D6C17C83F4', '411BD5CF-705E-4AD5-8CCE-
8A8A6D3250E6', GETDATE(),SYSTEM_USER),
('0E24F6EE-8A14-4F08-8863-E059EBC4562E', 'B3889753-7EE8-4D73-963E-
78F4E8A1FE99', GETDATE(),SYSTEM_USER)
Update Statement
Sagar Timalsina (HND / First Semester)

42
Database 2018
Update statement a statement which is used to change or modify existing record from database in the
form of structure query language. (Chen, 2018)
In Product:
Back end Update Query:
UPDATE Product SET MiniStockLevel = 40
,SalesPrice = 30
,CreatedOn = getdate()
,CreatedBy = USER_NAME()
WHERE ProductID= 'D66450C0-E5AF-4B52-A428-70FAFFCCC115'
Front end Update Query:
private void btnInsert_Click(object sender, EventArgs e)
{
conn.Open();
String query = "update Product set ProductName= '" +
txtProductName.Text + "',Size='" + txtSize.Text + "',Brand='" + txtBrand.Text +
"',UOM='" + TxtUOM.Text + "',MiniStockLevel='" + txtMinStockLevel.Text +
"',SalesPrice='" + txtSalesPrice.Text + "' where ProductID='"+txtProductID.Text+"'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Product Update Successfully");
conn.Close();
dataLoad();
}
In Purchase:
Back end Update Query:
UPDATE Purchase SET PurchaseOn = '2017-01-03'
,PurchaseRate = 40
,CreatedOn = getdate()
,CreatedBy = SYSTEM_USER()
WHERE ProductID= '698F0D19-8965-438B-8DCF-83A1903958CE'
Front end Update Query:
private void btnUpdate_Click(object sender, EventArgs e)
{
conn.Open();
String query = "update Purchase set ProductID= '" +
txtProductID.SelectedValue.ToString() + "',PurchaseOn='" + txtPurchaseOn.Text +
"',PurchaseRate='" + txtPurchaseRate.Text + "',PurchaseQty='" + txtPurchaseQty.Text +
"',SupplierID='" + txtSupplierID.SelectedValue.ToString() + "'where PurchaseID='" +
txtPurchaseID.Text + "'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
Sagar Timalsina (HND / First Semester)

43
Database 2018
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Purchase Update Successfully");
conn.Close();
dataLoad();
}
In Sales:
Back end Update Query:
UPDATE Sales SET SalesDate = '2017-01-02'
,SalesQty = 30
,CreatedOn = getdate()
,CreatedBy = SYSTEM_USER
WHERE SalesID= 'B2D07ACA-E54D-4D47-B6FE-350683EC2A0E'
Front end Update Query:
private void btnUpdate_Click(object sender, EventArgs e)
{
conn.Open();
String query = "update Sales set ProductID= '" +
txtProductList.SelectedValue.ToString() + "',SalesDate='" + txtSalesDate.Text +
"',SalesQty='" + txtSalesQty.Text + "',CustomerID='" +
txtCustomerList.SelectedValue.ToString() + "'where SalesID='" + txtSalesID.Text +
"'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Sales Update Successfully");
conn.Close();
dataLoad();
}
In Supplliers:
Back end Update Query:
UPDATE Supplliers SET SupplierAddress = 'Jamal'
,SupplierContact= '9988122'
,CreatedOn = getdate()
,CreatedBy = SYSTEM_USER
WHERE SupplierID= '1FA21BE0-8EB5-4079-B352-816CA6703F0D'
Front end Update Query:
private void btnUpdate_Click(object sender, EventArgs e)
{
conn.Open();
string query = "update Supplliers set SupplierName='" +
txtSupplierName.Text + "',SupplierAddress='" + txtSupplierAddress.Text +
"',SupplierContact='" + txtSupplierContact.Text + "'where
SupplierID='"+txtSupplierID+"'";
Sagar Timalsina (HND / First Semester)

44
Database 2018
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Suppliers Update Sucessfully.");
conn.Close();
dataLoad();
}
In Customer:
Back end Update Query:
UPDATE Supplliers SET SupplierAddress = 'Jamal'
,SupplierContact= '9988122'
,CreatedOn = getdate()
,CreatedBy = SYSTEM_USER
WHERE SupplierID= '1FA21BE0-8EB5-4079-B352-816CA6703F0D'
Front end Update Query:
private void btnUpdate_Click(object sender, EventArgs e)
{
conn.Open();
String query = "update Customer set CustomerName='" +
txtCustomerName.Text + "',CustomerAddress='" + txtCustomerAddress.Text +
"',CustomerContact='" + txtCustomerContact.Text + "' where CustomerID='" +
txtCustomerID.Text + "'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Customer Update Successfully");
conn.Close();
dataLoad();
}
In UserInfo:
Back end Update Query:
UPDATE UserInfo SET Email = '[e-mail]'
,CreatedOn = getdate()
,CreatedBy = SYSTEM_USER
WHERE UserID= '77F34460-7FA7-4FD3-98BF-226D70E3A257'
In UserRole:
Back end Update Query:
Sagar Timalsina (HND / First Semester)

45
Database 2018
select * from UserRole
UPDATE UserRole SET RoleName = 'Ram1'
,CreatedOn = getdate()
,CreatedBy = SYSTEM_USER
WHERE RoleID= 'B3889753-7EE8-4D73-963E-78F4E8A1FE99'
In UserRoleAssignment:
Back end Update Query: In UserRoleAssignment table which update based on UserRole and
UserInfo.In this table I just maintain relationship between two parent table name as UserInfo and
UserRole.
Delete Statement
Delete statement is a statement which is used to remove or clear records from database.
In Product:
Back end Delete Query:
DELETE FROM Product
Front end Delete Query:
private void btnDelete_Click(object sender, EventArgs e)
{
DialogResult result = MessageBox.Show("Do you Want Delete Selected Row",
"Important",
MessageBoxButtons.YesNo,
MessageBoxIcon.Question);
if (result == DialogResult.Yes)
{
conn.Open();
String query = "Delete from Product where ProductID='" +
txtProductID.Text + "'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Product Deleted Successfully");
refresh_data();
conn.Close();
dataLoad();
}
}
In Purchase:
Back end Delete Query:
DELETE FROM Purchase
Sagar Timalsina (HND / First Semester)

46
Database 2018
Front end Delete Query:
private void btnDelete_Click(object sender, EventArgs e)
{
DialogResult result = MessageBox.Show("Do you Want Delete Selected Row",
"Important",
MessageBoxButtons.YesNo,
MessageBoxIcon.Question);
if (result == DialogResult.Yes)
{
conn.Open();
String query = "Delete from Purcahse where PurchaseID='" +
txtPurchaseID.Text + "'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Purchase Deleted Successfully");
refresh();
conn.Close();
dataLoad();
}
}
In Sales:
Back end Delete Query:
DELETE FROM Sales
Front end Delete Query:
private void btnDelete_Click(object sender, EventArgs e)
{
DialogResult result = MessageBox.Show("Do you Want Delete Selected Row",
"Important",
MessageBoxButtons.YesNo,
MessageBoxIcon.Question);
if (result == DialogResult.Yes)
{
conn.Open();
String query = "Delete from Sales where SalesID='" + txtSalesID.Text
+ "'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Sales Deleted Successfully");
refresh();
conn.Close();
dataLoad();
}
}
In Supplliers:
Back end Delete Query:
Sagar Timalsina (HND / First Semester)

47
Database 2018
DELETE FROM Supplliers
Front end Delete Query:
private void btnDelete_Click(object sender, EventArgs e)
{
DialogResult result = MessageBox.Show("Do you Want Delete Selected Row",
"Important",
MessageBoxButtons.YesNo,
MessageBoxIcon.Question);
if (result == DialogResult.Yes)
{
conn.Open();
String query = "Delete from Supplliers where SupplierID='" +
txtSupplierID.Text + "'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Supplier Deleted Successfully");
refresh();
conn.Close();
dataLoad();
}
}
In Customer:
Back end Delete Query:
DELETE FROM Customer
Front end Delete Query:
private void btnDelete_Click(object sender, EventArgs e)
{
DialogResult result = MessageBox.Show("Do you Want Delete Selected Row",
"Important",
MessageBoxButtons.YesNo,
MessageBoxIcon.Question);
if (result == DialogResult.Yes)
{
conn.Open();
Sagar Timalsina (HND / First Semester)

48
Database 2018
String query = "Delete from Customer where CustomerID='" +
txtCustomerID.Text + "'";
MessageBox.Show(query);
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
sda.SelectCommand.ExecuteNonQuery();
MessageBox.Show("Product Deleted Successfully");
refresh();
conn.Close();
dataLoad();
}
}
In UserInfo:
Back end Delete Query:
DELETE FROM UserInfo
In UserRole:
Back end Delete Query:
DELETE FROM UserRole
In UserRoleAssignment:
Back end Delete Query:
DELETE FROM UserRoleAssignment
Select Statement
Select Statement is a statement which is used to view all records in database system. (Chen, 2018)
In Product:
Back end Select Query:
SELECT * FROM Product
Front end Select Query:
public void dataLoad()
{
conn.Open();
string query = "select *from Product";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
DataTable dt = new DataTable();
sda.Fill(dt);
dataGridView2.DataSource = dt;
conn.Close();
Sagar Timalsina (HND / First Semester)

49
Database 2018
}
In Purchase:
Back end Select Query:
SELECT * FROM Purchase
Front end Select Query:
public void dataLoad()
{
conn.Open();
String query = "select * from Purchase";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
DataTable dt = new DataTable();
sda.Fill(dt);
dataGridView1.DataSource = dt;
conn.Close();
}
In Sales:
Back end Select Query:
SELECT * FROM Sales
Front end Select Query:
public void dataLoad()
{
conn.Open();
String query = "select * from Sales";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
DataTable dt = new DataTable();
sda.Fill(dt);
dataGridView1.DataSource = dt;
conn.Close();
}
In Supplliers:
Back end Select Query:
SELECT * FROM Supplliers
Front end Select Query:
public void dataLoad()
{
conn.Open();
Sagar Timalsina (HND / First Semester)

50
Database 2018
String query = "select*from Supplliers ";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
DataTable dt = new DataTable();
sda.Fill(dt);
dataGridView1.DataSource = dt;
conn.Close();
}
In Customer:
Back end Select Statement:
SELECT * FROM Customer
Front end Select Statement:
public void dataLoad()
{
conn.Open();
String query = "Select*from Customer";
SqlDataAdapter sda = new SqlDataAdapter(query, conn);
DataTable dt = new DataTable();
sda.Fill(dt);
dataGridView1.DataSource = dt;
conn.Close();
}
In UserInfo:
Back end Select Query:
SELECT * FROM UserInfo
In UserRole:
Back end Select Query:
SELECT * FROM UserRole
In UserRoleAssignment:
Back end Select Query:
SELECT * FROM UserRoleAssignment
Conclusion
Sagar Timalsina (HND / First Semester)

51
Database 2018
In this task, I implement all query language like select, update, insert, and delete statement based on
given scenario. In order to complete this task, I implement different eight tables in one database. In
these tables, each records are unique in different column.
Task [7/M 3]
Assess whether meaningful data has been extracted through the use of query tools to produce
appropriate management information.
Introduction
Query is specially expressing hesitation or requesting for information. Query language in database
must be in structure language (SQL) structure query language. In database we usually querying to
seen database data, information also use to calculate or find out different report using query. In this
task I am going to discuss about how we can get product wise stock report, periodical sales report,
and supplier wise purchase report and margin report use query with its filter parameter as well as
without their filter parameter based on given scenario.
Product wise stock reports
The product wise stock reports provides all of the data of product would normally require
summarized onto one page. Here I produce query to see product wise stock report in my database.
Without Filter Parameter
 Query
 Output
Sagar Timalsina (HND / First Semester)

52
Database 2018
Using Filter Parameter
 Query
 Output
Periodical Sales reports
Normally periodical reports known as progress report. In periodical sales reports also to helps to get
some progress in sales stages. Here I have query for periodical sales report from stationary
management system with filter parameter as well as without filter parameter.
Without Filter Parameter
 Query
 Output
Sagar Timalsina (HND / First Semester)

53
Database 2018
Using Filter Parameter
 Query
 Output
Product wise margin reports
Simply margin reports use to
find out profit. Product wise
margin reports helps to find out product wise profit report. Here I have query to find out product
wise margin reports for stationary management system.
Without Filter Parameter
 Query
 Output
Sagar Timalsina (HND / First Semester)

54
Database 2018
Using Filter Parameter
 Query
 Output
Supplier wise purchase details
Supplier wise purchase details helps to find out which supplier purchase for which product. It helps
to maintain purchase details in stationary. Here I have query to find out supplier wise purchase
details which is shown in below with its output.
Without Filter Parameter
 Query
Sagar Timalsina (HND / First Semester)

55
Database 2018
 Output
Using Filter Parameter
 Query
 Output
Conclusion
In order to complete this task, I discuss about query language which is use to see data, information or
records in SQL database system. In database the query the in SQL form which is standard query
language. In this task I discuss about how we use different query language to seen data, information
as product wise stock report, periodical sales report etc.
Sagar Timalsina (HND / First Semester)

56
Database 2018
Task [8/P 4]
Test the system against user and system requirements.
Introduction
Testing is finding out how well something works. Generally, testing is use to check all process of
system to determine whether objects are being met. In this task, I am going to discuss about testing. I
also produce some test log against user and system based on given scenario. I also discuss about unit
testing as well as integration testing of system.
Testing
Testing is check all information or process of system, software. So database testing is checking all
information or data which stored in database. Testing can be performed in web or desktop
application, SQL server database. Depending on the nature of system we can use different approach
of testing. Testing should be done different on the basis of its Types. There are two types of testing
which are as follows;
Types of testing
 Black box testing: Black box texting is method of software testing where each internal
structure of system being tested which not know to the tester. Black box testing is applicable
to higher level of testing where programming and implementation knowledge not required.
 White Box texting: White box texting is method of software testing where each internal
structure of system being tested which know to the tester. Black box testing is applicable to
higher level of testing where programming and implementation knowledge not required.
Testing is mainly deals with finding errors in the system so as to eliminate them. This will improve
the quality of the system. So, here I tested desktop application to know the error of system. I tested
application on the basis of unit and integration testing, both testing methods is low level testing
where programming and implementation knowledge required.
Unit testing: Unit testing is testing where individual part or piece of application are tested. Unit
testing is low level testing. Unit testing is starts with the module specification. Unit testing
performed any time. Unit test does not verify code works with external dependencies correctly.
Integration testing: Unit testing is testing where individual module of application are tested.
Integration testing is low level testing. Integration testing is starts with the interface specification.
Integration testing carried out after the unit testing. Integration test verify code works with external
dependencies correctly.
Sagar Timalsina (HND / First Semester)

57
Database 2018
Unit Test Log
In unit testing, I use single module which is shown below with expected as well as actual result.
Simply unit testing is single module testing shown in below test log.
Test Ticket
ID
Test Ticket
Description
Test
Case ID
Test
Case
Description Expected Result
Actual
Result
TKT_M_00
1
Verify Login
Page
C_M_00
2
Wrong user
and wrong
password.
Login Error with
message 'Invalid username
and password'
Log In
error with
message
C_M_00
3
Wrong user
and right
password.
Login Error with
message 'Invalid username
and password'
Log In
error with
message
C_M_04
Right user
and wrong
password.
Login Error with
message 'Invalid username
and password'
Log In
error with
message
C_M_00
5
Right user
and right
password.
Login Success with
message 'success'
Log In
success
with
message
Snapshot:
1. Wrong user and wrong password. 2. Right user and right password.
In unit testing, I use Login module to verify log in page which working properly or not. So I chose
data like wrong user name and wrong password as well as right user name and right password.
Sagar Timalsina (HND / First Semester)

58
Database 2018
Integration Test Log
In integration testing, I use different module which are shown below with expected as well as actual
result. Simply integration testing is group of unit testing so in below test log.
Test Ticket
ID
Test Ticket
Description
Test
Case ID
Test
Case
Description Expected Result
Actual Result
TKT_M_002 Main page C_M_006
Click on
Product
Product module should
be displayed
Product Click
menu works
C_M_007
Click on
Purchase
Purchase module
should be displayed
Purchase Click
menu works
C_M_008
Click on
Sales
Sales module should be
displayed
Sales Click
menu works
C_M_009
Click on
Customer
Customer module
should be displayed
Customer Click
menu works
C_M_010
Click on
Supplier
Supplier module should
be displayed
Supplier Click
menu works
Snapshot:
1. Click on Product 2. Click on Customer
TKT_M_003 Product Page C_M_011
Click On
Home
Main page should be
displayed
Back to main
page.
C_M_012
Click On
save
Save message should
be Displayed
Messaged
Appeared
Sagar Timalsina (HND / First Semester)

59
Database 2018
C_M_013
Click on
Update
Update message
should be Displayed
Messaged
Appeared
C_M_014
Click on
delete
Delete message should
be Displayed
Messaged
Appeared
Snapshot:
1. Click on home 2. Click On save
3. Click on update 4. Click on delete
TKT_M_004 Sales C_M_015
Click On
Home
Main page should be
displayed
Back to main
page.
C_M_016
Click On
save
Save message should
be Displayed
Messaged
Appeared
C_M_017
Click on
Update
Update message
should be Displayed
Messaged
Appeared
Sagar Timalsina (HND / First Semester)

60
Database 2018
C_M_018
Click on
delete
Delete message should
be Displayed
Messaged
Appeared
Snapshot:
1.Click on home 2.Click On save
3.Click on update 4.Click on delete
TKT_M_005 Supplier page C_M_019
Click On
Home
Main page should be
displayed
Back to main
page.
C_M_020
Click On
save
Save message should
be Displayed
Messaged
Appeared
C_M_021
Click on
Update
Update message
should be Displayed
Messaged
Appeared
Sagar Timalsina (HND / First Semester)

61
Database 2018
C_M_022
Click on
delete
Delete message should
be Displayed
Messaged
Appeared
Snapshot:
1.Click on home 2.Click On save
3.Click on update 4.Click on delete
TKT_M_006
Customer
page C_M_023
Click On
Home
Main page should be
displayed
Back to main
page.
C_M_024
Click On
save
Save message should
be Displayed
Messaged
Appeared
C_M_025
Click on
Update
Update message
should be Displayed
Messaged
Appeared
Sagar Timalsina (HND / First Semester)

62
Database 2018
C_M_026
Click on
delete
Delete message should
be Displayed
Messaged
Appeared
Snapshot:
1.Click on home 2.Click On save
3.Click on update 4.Click on delete
These are the integration testing of system. Here are I chose test description with different case id to
check verifying page or module work properly or not against system and user. So to know about
these information, I produce these test log. Integration testing is group of unit testing so here I
produce combination of unit testing of each module in integration testing. Here I use different
module like product, supplier, sales, and customer to produce integration testing against user or
system which define each module work properly or not.
Conclusion
In order to complete this task, I produced tested Log against system and user. I discussed about
testing, unit testing as well as integration testing. In this task I prepare tested log on the basis of these
two testing name as unit and integration testing.
Task [9/M 4]
Assess the effectiveness of the testing, including an explanation of the choice of test data used.
Sagar Timalsina (HND / First Semester)

63
Database 2018
Introduction
Testing is finding out how well something works. Generally, testing is use to check all process of
system to determine whether objects are being met. In this I am going to discuss about testing and its
types, important of testing, approach of testing. I also require to produce test log based given
scenario, and their modules with its expected result, actual and comment also.
Testing
Testing is check all information or process of system, software. So database testing is checking all
information or data which stored in database. Testing can be performed in web or desktop
application, SQL server database. There are different type of testing as black box testing and white
box testing. Black box texting is method of software testing where each internal structure of system
being tested which not know to the tester. White box testing is also the method of testing each
internal structure of system being tested which know to the tester. Unit and integration testing is also
the part of white box testing.
Importance of testing
Testing is required in any phase, where we all make some mistake to produce specially software and
others. So, testing is very important which helps to improve the system. Testing is required to find
the some issues and error that were made during development phase which helps to correct that
errors. So testing is very important for an effective performance of software or system or application.
It also very important to ensure that the application should not result into any failures. In testing,
good testing can be controlled to improve understanding and testability. Testing also helps to
understand the system so it is very important. Testing is mainly deals with finding errors in the
system so as to eliminate them. This will improve the quality of the system. These are the some
important of testing because everyone earn mistake at developing phase.
Approach of testing
The plan implementation of a project is define approach of testing which define how testing would
be carried out. Test approach has different two techniques as proactive and reactive. Proactive testing
approach define the test design process is initiated as early as possible in order to find and fix the
defects before the build is created and reactive approach of testing define the testing is not started
until after design and coding are completed. There are different testing approach based on project
like consultative, dynamic or heuristic approach. Methodical approach, which is based on failures.
List of expected result and actual result
Sagar Timalsina (HND / First Semester)

64
Database 2018
Login module
Project Name Stationary Management System
Module Name Login Module
Created By Sagar
Created On 5/2/2018
Reviewed By Supervisor
Reviewed On
What was tested: Login module Date:5/2/2018
Choice of data Expected Output Actual Output Comment
1. Wrong
user
name,
wrong
password.
Login Error with message
'Invalid username and
password'
Log In error with message Login error message is
better to show in
message box no in label.
Snapshot:
2. Right user
name,
wrong
password.
Login Error with message
'Invalid username and
password'
Log In error with message
Snapshot:
Sagar Timalsina (HND / First Semester)

65
Database 2018
3. Right user
name,
Right
password.
Login Success with
message 'success'
Log In success with
message.
Snapshot:
In log in module, I use different data to test Log in module working properly or not. First of all, I
used wrong user name with wrong password, its shows invalid username or password which is
actually meet with its actual and expected result. In others like Right user name and wrong password
also produce same result. So finally right user name and right password give different result like
login successfully which is shown in above test log. These are the some data which is used to check
login module.
Sagar Timalsina (HND / First Semester)

66
Database 2018
Product module
Project Name Stationary Management System
Module Name Product Module
Created By Sagar
Created On 5/2/2018
Reviewed By Supervisor
Reviewed On
What was tested: Product module Date:5/2/2018
Choice of data Expected Output Actual Output Comment
1. Delete
Action
Delete successfully
message should be
Displayed
Messaged Appeared Control require on
Delete Confirmation
message with Yes/ No
option
Snapshot:
2. Insert
action
Insert successfully
message should be
Displayed
Messaged Appeared
Snapshot:
Sagar Timalsina (HND / First Semester)

67
Database 2018
3. Update
Action
Update successfully
message should be
Displayed
Messaged Appeared Update confirmation
message require
Snapshot:
5.Drop
down action
’Size’
Should not Allow manual
input
Not accepting external
values
Control required on
manual input
Snapshot:
Sagar Timalsina (HND / First Semester)

68
Database 2018
In product module, I used different data to verify product page working or not on the basis of system
and user requirement. I chose different data like delete action to show delete button working or not,
insert action to show save button working properly or not, update action to show working properly or
not. And also tested dropdown of size that working properly or not against user and system
requirement.
Purchase Module
Project Name Stationary Management System
Module Name Purchase Module
Created By Sagar
Created On 5/2/2018
Reviewed By Supervisor
Reviewed On
What was tested: Purchase module Date:5/2/2018
Choice of data Expected Output Actual Output Comment
1. Delete
Action
Delete Confirmation
message should be
Displayed
Messaged Appeared with
Yes/ No option
Snapshot:
Sagar Timalsina (HND / First Semester)

69
Database 2018
2. Insert
Action
Insert successfully
message should be
Displayed
Message Appeared
Snapshot:
3. Update
Action
Update successfully
message should be
Displayed
Message Appeared Updating message
require with details.
Snapshot:
Sagar Timalsina (HND / First Semester)

70
Database 2018
4.Drop down
action
’Product ID’
Should not Allow manual
input
Not accepting external
values
Control required on
manual input
Snapshot:
5.Drop
down action
’Supplier ID’
Should not Allow manual
input
Not accepting external
values
Control required on
manual input
Snapshot:
Sagar Timalsina (HND / First Semester)

71
Database 2018
In purchase module, I used different data to verify purchase page working or not on the basis of
system and user requirement. Here, I chose different data like delete action to show delete button
working or not, insert action to show save button working properly or not, update action to show
working properly or not. And also tested dropdown of product ID with Product Name as well as
Supplier ID with Supplier Name that working properly or not against user and system requirement.
Sales Module
Project Name Stationary Management System
Module Name Sales Module
Created By Sagar
Created On 5/2/2018
Reviewed By Supervisor
Reviewed On
What was tested: Sales Date: 5/2/2018
Choice of data Expected Output Actual Output Comment
1. Delete
Action
Delete successfully
message should be
Displayed
Messaged Appeared
Snapshot:
Sagar Timalsina (HND / First Semester)

72
Database 2018
2. Insert
Action
Insert successfully message
should be Displayed
Messaged Appeared
Snapshot:
3. Update
Action
Update successfully
message should be
Displayed
Snapshot:
Sagar Timalsina (HND / First Semester)

73
Database 2018
4.Dropdown
action ’Product
ID’
Should not Allow manual
input
Not accepting external
values
Control require on
manual input.
Snapshot:
5.Dropdown
action
’Customer ID’
Should not Allow manual
input
Not accepting external
values
Control required on
manual input
Snapshot:
Sagar Timalsina (HND / First Semester)

74
Database 2018
In module, I used different data to verify sales page working or not on the basis of system and user
requirement. Here, I chose different data like delete action to show delete button working or not,
insert action to show save button working properly or not, update action to show working properly or
not. And also tested dropdown of product ID with Product Name as well as Customer ID with
Customer Name that working properly or not against user and system requirement.
Supplier Module
Project Name Stationary Management System
Module Name Supplier Module
Created By Sagar
Created On 5/2/2018
Reviewed By Supervisor
Reviewed On
What was tested: Supplier Module Date: 5/2/2018
Choice of data Expected Output Actual Output Comment
1. Delete
Action
Delete successfully
message should be
Displayed
Messaged Appeared
Snapshot:
Sagar Timalsina (HND / First Semester)

75
Database 2018
2. Insert
Action.
Insert successfully
message should be
Displayed
Messaged Appeared
Snapshot:
3. Update
Action
Update successfully
message should be
Displayed
Snapshot:
Sagar Timalsina (HND / First Semester)

76
Database 2018
In supplier module, I used different data to verify supplier details page working or not on the basis of
system and user requirement. I chose different data like delete action to show delete button working
or not, insert action to show save button working properly or not, update action to show working
properly or not against user and system requirement.
Customer Module
Project Name Stationary Management System
Module Name Customer Module
Created By Sagar
Created On 5/2/2018
Reviewed By Supervisor
Reviewed On
What was tested: Customer Module Date: 5/2/2018
Choice of data Expected Output Actual Output Comment
1. Delete
Action
Delete successfully
message should be
Displayed
Messaged Appeared
Snapshot:
Sagar Timalsina (HND / First Semester)

77
Database 2018
2. Update
Action
Update successfully
message should be
Displayed
Snapshot:
3. Insert
Action.
Insert successfully
message should be
Displayed
Messaged Appeared
Snapshot:
Sagar Timalsina (HND / First Semester)

78
Database 2018
In customer module, I used different data to verify customer detail page working or not on the basis
of system and user requirement. I chose different data like delete action to show delete button
working or not, insert action to show save button working properly or not, update action to show
working properly or not against user and system requirement.
Conclusion
In order to complete this task, I discussed about testing, testing types, importance of testing, different
approach of testing. Here I also produced test log based on given scenario with expected result,
actual result and comment also.
Sagar Timalsina (HND / First Semester)

79
Database 2018
Task [11/P 5]
Produce technical and user documentation.
Introduction
Documentation is the information that describes the product to its users. Document should be
technical or user manual. Here, I am going to discuss of technical as well as user manual of designed
application. I also discuss about important features of application, significance and limitation of
desktop based designed application.
Important Features of Application
The designed application is desktop application using C#.Net visual base programming languages.
This application is the creation of user-defined functions and the automation of specific computer
processes and calculations. It important features is user do not need to understand query language of
SQL to operate this application. It provides security on data which stored because the user need to
access data through log on process so unauthorized user cannot access data, only validate user access
data. This is important feature for this application. These are the some feature of these application
like user validation, drop down validation, text box validation.
Significance of Application
The designed application is desktop application using C#.Net visual base programming languages,
these languages are more powerful and object based concept which deal with object rather than
methods. Here I designed application for user to interact with database without query language. So
its main purpose is user do not need any query language of database. This application is friendlier
with user. User can update, delete view database records through single log on process. Its
significance is user know all data, information, which provide access through database administrator
on user single validate process. These are the some significance of designed desktop.
Limitation of Application
The designed application is based on desktop application so it has lots of limitation. This designed
application is installed separately on each user computer. This application is standalone in nature so
it do not face any hindrances resulting from internet connectivity. In case of desktop application
upgrade, user need to upgrade first their hardware system then only upgrade application. User do not
start directly installation, first user know about all hardware requirement so user faces lots of
problem, it also called more complexity. To overcome these problem we can use web base
application. These are the some limitation of designed desktop base application.
Choice of tools
Sagar Timalsina (HND / First Semester)

80
Database 2018
IDE: VisualStudio-2017 community edition
Programming Language – C# using .Net Framework
Relational Database Management System – SQL server -express edition
Platform: Desktop Application
Technical manual
User validation module
Validating user input is the first and one of the most important steps to securing site where lots of
information are stored. Here I validating user input for login with supplying parameter as username
as well as password which in below with query and output of snapshots.
 Front end query
This query is use to validate user that hit back end system database which provide or validate
user name and password for login in front end application. This is technical field where if
user name and password are wrong or not validate, it shows error message else success. The
front end application is validate with supply parameter that are username and password which
Sagar Timalsina (HND / First Semester)

81
Database 2018
store their information in database. The output of this user log in validation is shown in
below;
 Output
Wrong user name, password Right user name, password.
Product module
Product module is also validating with product name so it helps to maintain product details accuracy
at the inserting time of product details. When user forget to inserting product name, then product
name is required message displayed which related with technical term of field validation. The query
and its output shown in below;
 Front end Query
 Output
Sagar Timalsina (HND / First Semester)

82
Database 2018
These are some example of technical manual which make data accuracy in system with well security.
These code level validation is very important to accessing data from system. These technical manual
also need to know before using this application.
User manual
User manual is very useful information for user which provides guideline for how to use system or
software application. Here, I have some guide of designed desktop based application of each module
which is shown in below;
Step guide to use application
 Login module
In Login module user have to supply right input parameter as user name as well as password
in text field to get success otherwise error would be displayed. When user supplied
parameters are wrong the Login not success else success which are shown in below;
1. Wrong user name, password 2. Right user name password
User have to input right username and password then click on login button that show success
message, after click on ok, main page would be displayed.
 Main page module
In main page module, it was designed on the basis of user requirement where are different
menu like product to displayed product page, purchase to displayed purchase page, sales to
Sagar Timalsina (HND / First Semester)

83
Database 2018
display sales page, supplier to display supplier page and customer to display customer page
on single clicking process of each. Each pages of this menu items shown in below;
1.Product 2.Purchase
3.Sales 4.Customer
5.Supplier
After login process, user would be click on different item when it required.
 Product Module
Product module is design to view all detail about product, insert new record, update current
record, and delete unwanted record based on user requirement. There are different bottom to
perform these different event.
1. Home 2. Save
Sagar Timalsina (HND / First Semester)

84
Database 2018
3. Update 4. Delete
After login process, if user click on product then product page displayed where user can
insert new record, view all record, delete unnecessary record, and update record on required
or needed condition. To go back user have to click on home menu to go main page where
user can select others item also.
 Purchase module
Purchase module is design to view all detail about purchase, insert new record, update current
record, and delete unwanted record based on user requirement. There are different bottom to
perform these different event.
1.Home 2.Save
3.Update 4.Delete
Sagar Timalsina (HND / First Semester)

85
Database 2018
After login process, if user click on purchase then purchase page displayed where user can
insert new record, view all record, delete unnecessary record, and update record on required
or needed condition. To go back user have to click on home menu to go main page where
user can select others item also.
 Sales module
Sales module is design to view all detail about sales, insert new record, update current record,
and delete unwanted record based on user requirement. There are different bottom to perform
these different event.
1.Home 2.Save
5. Update 3.Delete
After login process, if user click on sales then sales page displayed where user can insert new
record, view all record, delete unnecessary record, and update record on required or needed
Sagar Timalsina (HND / First Semester)

86
Database 2018
condition. To go back user have to click on home menu to go main page where user can
select others item also.
 Supplier module
Supplier module is design to view all detail about supplier, insert new record, update current
record, and delete unwanted record based on user requirement. There are different bottom to
perform these different event.
1.Home 2.Save
3.Update 4.Delete
After login process, if user click on supplier then supplier page displayed where user can
insert new record, view all record, delete unnecessary record, and update record on required
or needed condition. To go back user have to click on home menu to go main page where
user can select others item also.
 Customer module
Customer module is design to view all detail about customer, insert new record, update
current record, and delete unwanted record based on user requirement. There are different
bottom to perform these different event.
1.Home 2.Save
Sagar Timalsina (HND / First Semester)

87
Database 2018
3.Update 4.Delete
After login process, if user click on customer then customer page displayed where user can
insert new record, view all record, delete unnecessary record, and update record on required
or needed condition. To go back user have to click on home menu to go main page where
user can select others item also.
Conclusion
In order to complete this task, I discussed about important features, significance with limitation of
designed application. I also prepare some step guide for how to use application which helps user to
use this application.
Sagar Timalsina (HND / First Semester)

88
Database 2018
Task [12/M 5]
Produce a technical and user documentation for a fully functional system, including diagrams
showing movement of data through system and flowcharts describing how the system work.
Introduction
Database is collection of information which helps to well manage or organize data that is easily
accessible, manageable in different ways. SQL server provides fully function system for database
which more easy for user to interact with system. In this task, I am going to discuss about important
features of application, its important as well as its significance with its limitation. In this task, I also
discuss about layout of designed application, its data dictionary, its flow chart, its use case diagram,
0-level diagram and also produce a project plan and the product deployment based on given scenario.
Important Features of Application
The designed application is desktop application using C#.Net visual base programming languages,
these languages are more powerful and object based concept which deal with object rather than
methods. This application is the creation of user-defined functions and the automation of specific
computer processes and calculations. It important features is user do not need to understand query
language of SQL to operate this application. It provides security on data which stored because the
user need to access data through log on process so unauthorized user cannot access data, only
validate user access data. This is important feature for this application. It list out its items when user
try to insert data on application. These are the some feature of these application like user validation,
drop down validation, text box validation.
Significance of Application
The designed application is desktop application using C#.Net visual base programming languages,
these languages are more powerful and object based concept which deal with object rather than
methods. Here I designed application for user to interact with database without query language. So
its main purpose is user do not need any query language of database. Each inserted, updated, deleted
record hit database system through this designed application so its features it work on the basis of
structural query language. This application is friendlier with user. User can update, delete view
database records through single log on process. Its significance is user know all data, information,
which provide access through database administrator on user single validate process. It also helps to
manage database system through this application. These are the some significance of designed
desktop.
Limitation of Application
Sagar Timalsina (HND / First Semester)

89
Database 2018
The designed application is based on desktop application so it has lots of limitation. This designed
application is installed separately on each user computer. This application is standalone in nature so
it do not face any hindrances resulting from internet connectivity. Most of the desktop applications
have traditionally been limited by the hardware so it also face these challenge or limitation. In case
of desktop application upgrade, user need to upgrade first their hardware system then only upgrade
application. User do not start directly installation, first user know about all hardware requirement so
user faces lots of problem, it also called more complexity. To overcome these problem we can use
web base application. These are the some limitation of designed desktop base application.
Choice of tools
IDE: VisualStudio-2017 community edition
Programming Language – C# using .Net Framework
Relational Database Management System – SQL server -express edition
Platform: Desktop Application
Layout of Designed Application
1. Login page Layout 2. Main Page Layout
3. Product Page Layout 4. Purchase Page Layout
5. Sales Page Layout 6. Supplliers Page Layout
Sagar Timalsina (HND / First Semester)

90
Database 2018
7. Customer Page layout
These are the application layout which is design in order to making application which helps to
application is much friendlier with user. These layout design in visual studio with its C#.Net
framework. To design these layout need different tools which provide by visual. To design these
layout I use label, textbox, data grid view, combo box, button, menu strip etc. These different tools
have their own function base on its own working principle.
Data Dictionary use in Application
In database, data dictionary is use to define each column name of table, its datatype, references, as
well as their relationship. Here I have five different data dictionary that use is application which are
as follows;
Sagar Timalsina (HND / First Semester)

91
Database 2018
Table1:Product
TableName CloumnName DAtaType AllowNull isPK isFk
Referenc
e Remarks
Product ProductID Uniqueidentifier N Y N _ _
Product ProductName Varchar Y N N _ _
Product Size Varchar Y N N _ _
Product Brand Varchar Y N N _ _
Product UOM Varchar Y N N _ _
Product MiniStockLevel Varchar Y N N _ _
Product SalesPrice Varchar Y N N _ _
Table2:Purchase
TableName CloumnName DAtaType AllowNull isPK isFk
Referenc
e Remarks
Purchase PurchaseID Uniqueidentifier N Y N _ _
Purchase ProductID Uniqueidentifier Y N Y Product _
Purchase PurchaseOn Varchar Y N N _ _
Purchase PurchaseDate Varchar Y N N _ _
Purchase PurchaseQty Varchar Y N N _ _
Purchase SupplierID Uniqueidentifier Y N Y Supplliers _
Table3 :Sales
TableName CloumnName DAtaType AllowNull isPK isFk
Referenc
e Remarks
Sales SalesID Uniqueidentifier N Y N _ _
Sales ProductID Uniqueidentifier Y N Y Product _
Sales SalesOn Varchar Y N N _ _
Sales SalesQty Varchar Y N N _ _
Sales CustomerID Uniqueidentifier Y N Y Customer
Table4:Supplliers
TableName CloumnName DAtaType
AllowNul
l isPK isFk Reference
Remark
s
Supplliers SupplierID Uniqueidentifier N Y N _ _
Supplliers SupplierNAme Varchar Y N N _ _
Supplliers SupplierAddress Varchar Y N N _ _
Supplliers SupplierContact Varchar Y N N _ _
Table5:Custome
r
TableName CloumnName DAtaType AllowNull
isP
K isFk
Referenc
e Remarks
Customer CustomerID Uniqueidentifier N Y N _ _
Customer CustomerName Varchar Y N N _ _
Customer CustomerAddress Varchar Y N N _ _
Customer CustomerContact Varchar Y N N _ _
sCustomer CreatedOn Datetime Y N N _ _
Sagar Timalsina (HND / First Semester)

92
Database 2018
Customer CreatedBy varchar Y N N _ _
Flow chart of Application
Usually flow chart is known as diagram re presentation of work flow of the system which define
actually how system is work. Here I have some flow chart of designed application which show work
flow of application where application started and where application ended. Each step in the
arrangement is distinguished within a diagram shape. Steps are connected by connecting lines and
directional arrows. In flow chart, each part of designed application is a picture of the separate steps
of a process in serial order.
 Starting phase of flow chart of designed application:
This flow chart define how application start and follow sequential steps. This diagram
show first run application then login is displayed if authenticate is true then main page
display with their items.
 For Product:
Sagar Timalsina (HND / First Semester)

93
Database 2018
After the starting phase of application, if click on product, there are add/ view option
where product should be added, viewed, updated, deleted. These all step flow are shown
in above flow chart diagram which is related with fig: product.
 For Purchase:
After starting phase, if click on purchase, it also show some step flow which are shown in
above diagram. In purchase, there are add/ view option, if click on view its shows update
delete option. If click on add., it shows product available or not, then their product is
available its show supplier option if supplier is also available, then purchase is added
otherwise return back on fig: product related with product as well as fig: supplier related
with supplier.
 For sales:
Sagar Timalsina (HND / First Semester)

94
Database 2018
After starting phase, if click on sales, it also show some step flow which are shown in
above diagram. In sales, there are add/ view option, if click on view its shows update
delete option. If click on add., it shows product available or not, then their product is
available its show customer option if customer is also available, then sales is added
otherwise return back on fig: product related with product as well as fig: customer related
with customer.
 For Supplier:
After the starting phase of application, if click on supplier, there are add/ view option
where supplier detail should be added, viewed, updated, deleted. These all step flow are
shown in above flow chart diagram which is related with fig: product.
 For Customer:
Sagar Timalsina (HND / First Semester)

95
Database 2018
After the starting phase of application, if click on customer, there are add/ view option
where customer detail should be added, viewed, updated, deleted. These all step flow are
shown in above flow chart diagram which is related with fig: customer.
Use Case Diagram for Application
Use case diagram is simple representation of diagram which show how system communicate with
user. It also show user and system relationship. Here, l have use case diagram of my system which
shown below with user and system relationship.
Figure: Use case Diagram
Context or 0-level Diagram for Application
Context diagram is data flow diagram which is also known as 0-level diagram. It shows a data
system as a whole and emphasizes the way it interacts with external entities. Below diagram shows
0-level diagram of my system.
Sagar Timalsina (HND / First Semester)

96
Database 2018
Figure: 0-level Diagram
Project Plan (Gantt chart)
Gantt chart is graphical representing chart which activities or task performed against time. Gantt
chart is specially to make plan of project which visually represent graph chart in contradiction of
time. Here I implement my project plan to build or produce application which is based on given
scenario. Gantt chart of the stationary management system is shown is below;
Sagar Timalsina (HND / First Semester)

97
Database 2018
Database Structure
Simply database structure define database each table and their columns datatype with their
relationship in database. In database system, table column use different data type, relationship,
different keys, its function, store procedure, all these thing define in database structure. In my
system I have been implemented different database function, trigger, different keys, trigger etc.
Database structure also define system table and other tables. Database also monitors different session
which display current information of database. We use different query to see database structure
which are as follows;
Query to see a list of user-created tables with output
Query:
FROM SYSOBJECTS WHERE xtype = 'U';
Output:
Here this query is use to find user created table in database system ‘SMS’ with its output in above.
The SYSOBJECTS hold all information about which things are added to server. Xtpye use to
specifies object types and U is stand for user table.
Query to view all table in System
Query:
SELECT * FROM INFORMATION_SCHEMA.TABLES
Output
Sagar Timalsina (HND / First Semester)

98
Database 2018
These are the some query to see database structure in SQL server. Sysdiagrams also define database
structure with table structure and their relationship. Sys diagram is system diagram or database
diagram of database.
This the system diagram or database diagram of SMS.
Product Deployment
Here, I have topic about product deployment. Here I define different requirement to deployed SQL
server, visual studio as well as designed application.
SQL server requirement:
Component Requirement
Memory * Minimum:
Express Editions: 512 MB
All other editions: 1 GB
Sagar Timalsina (HND / First Semester)

99
Database 2018
Component Requirement
Recommended: Express Editions: 1 GB
All other editions: At least 4 GB and should be increased as database size
increases to ensure optimal performance.
Processor
Speed
Minimum: x64 Processor: 1.4 GHz
Recommended: 2.0 GHz or faster
Processor
Type
x64 Processor: AMD Opteron, AMD Athlon 64, Intel Xeon
with Intel EM64T support, Intel Pentium IV with EM64T
support
Visual requirement:
 1.6 GHz or faster processor.
 1 GB of RAM (1.5 GB if running on a virtual machine)
 4 GB of available hard disk space.
 5400 RPM hard disk drive.
 DirectX 9-capable video card that runs at 1024 x 768 or higher display resolution.
Designed Application requirement:
The application is basically designed using visual base C# programming with .Net Framework. So at
least, the requirement also need to meet with visual requirement as well as SQL requirement which is
best for using or deployed application. This application also deploy in normal with normal processer,
ram, storage, etc. but the best is use new system which provides advance features.
Maintenance technique
Simply maintenance means keeping something in proper, good condition. So maintenance technique
means use technical ideas to keep something in well condition. Maintenance technique are different
types like corrective maintenance, periodic maintenance, preventive maintenance, etc. depending on
nature of object where needed we can apply these different technique. In case of my system, we can
use corrective maintenance, preventive maintenance, periodic maintenance and others technique.
Corrective maintenance means we use to correct the defects to be found in the system or using
equipment. Preventive maintenance means use to know and report the status and operational capacity
Sagar Timalsina (HND / First Semester)

100
Database 2018
of the installations of system or software which helps to find out operational ability. Periodic
maintenance means time based maintenance which is completely based on total productive
maintenance. These are some maintenance technique, we can use these technique at the time of
system maintenance.
Conclusion
In order to complete this task, I discuss about application important features, significance of
application, and choice of different tools to design application. These may help to produce a simple
desktop application. I also discuss about flow chart, how application work, use case diagram to know
about how system interact with user, its context diagram, database structure. I also define different
maintenance technique.
Sagar Timalsina (HND / First Semester)

101
Database 2018
Bibliography
Chapple, M., 2018. lifewire. [Online]
Available at: https://www.lifewire.com/primary-key-definition-1019179
[Accessed 04 2018].
Chen, J., 2018. dofactory. [Online]
Available at: http://www.dofactory.com/sql/delete
[Accessed 1 5 2018].
Rouse, M., 2014. techtarget. [Online]
Available at: https://searchoracle.techtarget.com/definition/stored-procedure
[Accessed 8 5 2018].
Rouse, M., 2016. techtarget. [Online]
Available at: https://searchsqlserver.techtarget.com/definition/normalization
[Accessed 1 5 2018].
Rouse, M., 2018. techtarget. [Online]
Available at: https://searchdatamanagement.techtarget.com/definition/entity-relationship-diagram-
ERD
[Accessed 2 5 2018].
Rouse, M., n.d. searchsqlserver. [Online]
Available at: https://searchsqlserver.techtarget.com/definition/database
[Accessed 2018].
Sagar Timalsina (HND / First Semester)