Table 2. Database development process DB... | Emerald Publishing

Table 2.

Database development process

DB lifecycle stage	Description of the lifecycle stage	Methods followed during the development of toolkit
DB analysis	The information needed from the DB is defined	Identified the end-user’s requirement (user’s selection criteria, illustrations and level of details in the toolkit)
DB conceptual design	Entities and their relationships are defined	Main data entities were identified (causes of disputes, dispute avoidance steps, pre-contract stages, parties and themes of causes of disputes of disputes) The relationships and primary keys of each entities were identified Relationship logics among the variables were established using the data modelling options in Microsoft Power BI
DB logical design	The conceptual design advances to design a relational database model
DBMS selection	The nature of the database (distributed / centralised), security was considered to select a database	Opted for a simple Microsoft excel file as the database. The Microsoft Excel database was linked to the power BI report and that report was published to the Web However, the published report only allowed the end-user to retrieve the data; therefore, database security was not compromised
DB implementation	Data was entered and reports were generated	In Microsoft Power BI, two tables for causes of disputes and avoidance steps and a “force-directed graph” that illustrates the relationship between causes and avoidance steps were created
DB management	Database maintenance options (backing up and restoring)	In addition to the primary database, few backups were created and saved securely

DB lifecycle stage	Description of the lifecycle stage	Methods followed during the development of toolkit
DB analysis	The information needed from the DB is defined	Identified the end-user’s requirement (user’s selection criteria, illustrations and level of details in the toolkit)
DB conceptual design	Entities and their relationships are defined	Main data entities were identified (causes of disputes, dispute avoidance steps, pre-contract stages, parties and themes of causes of disputes of disputes) The relationships and primary keys of each entities were identified Relationship logics among the variables were established using the data modelling options in Microsoft Power BI
DB logical design	The conceptual design advances to design a relational database model
DBMS selection	The nature of the database (distributed / centralised), security was considered to select a database	Opted for a simple Microsoft excel file as the database. The Microsoft Excel database was linked to the power BI report and that report was published to the Web However, the published report only allowed the end-user to retrieve the data; therefore, database security was not compromised
DB implementation	Data was entered and reports were generated	In Microsoft Power BI, two tables for causes of disputes and avoidance steps and a “force-directed graph” that illustrates the relationship between causes and avoidance steps were created
DB management	Database maintenance options (backing up and restoring)	In addition to the primary database, few backups were created and saved securely

Source(s): Table created by authors, partly based on information presented in Zygiaris (2018), combined with methods applicable to the current study