0% found this document useful (0 votes)
23 views

Unit 04 Database Design and Development

This document outlines the assignment for Unit 04: Database Design and Development for the HND in Computing program, focusing on creating a database for Quiet Attic Films. It includes details on assessment criteria, internal verification processes, and specific activities required for designing, developing, testing, and documenting a relational database system. The assignment emphasizes the importance of user and system requirements, normalization, and security mechanisms in database development.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
23 views

Unit 04 Database Design and Development

This document outlines the assignment for Unit 04: Database Design and Development for the HND in Computing program, focusing on creating a database for Quiet Attic Films. It includes details on assessment criteria, internal verification processes, and specific activities required for designing, developing, testing, and documenting a relational database system. The assignment emphasizes the importance of user and system requirements, normalization, and security mechanisms in database development.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 91

lOMoARcPSD|50495251

E191807 - Madhubhani Nisansala -


2721-1666807090575-Unit 04 - Database design and
Development
HND In Computing (ESOFT Metro Campus)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university


Downloaded by Hadi Ahmd ([email protected])
lOMoARcPSD|50495251

Pearson Higher
Nationals in
Computing

Unit 04: Database Design &


Development
Assignment 01

S.M.Nisansala Database Design and Development Assignment 01 1

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Higher Nationals

Internal verification of assessment decisions – BTEC (RQF)

INTERNAL VERIFICATION – ASSESSMENT DECISIONS


Programme title BTEC HND in Computing

Assessor Mr. Bhimaja Internal


Verifier
Unit 04: Database Design & Development
Unit(s)
Database Solution for Quiet Attic Films
Assignment title
Sembukuttige Madhubhani Nisansala
Student’s name
List which assessment Pass Merit Distinction
criteria the Assessor
has awarded.
INTERNAL VERIFIER CHECKLIST
Do the assessment criteria
awarded match those shown in
the assignment brief? Y/N
Is the Pass/Merit/Distinction grade
awarded justified by the assessor’s Y/N

comments on the student work?


Has the work been
assessed accurately? Y/N
Is the feedback to the student:
Give details:
• Constructive?

• Linked to relevant Y/N

assessment criteria? Y/N

• Identifying opportunities Y/N

S.M.Nisansala Database Design and Development Assignment 01 2

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

for improved performance? Y/N


• Agreeing actions?
Does the assessment decision
need amending? Y/N

Assessor signature Date

Internal Verifier signature Date


Programme Leader signature (if
required) Date

Confirm action completed


Remedial action
taken
Give details:

Assessor signature Date


Internal
Verifier Date

signature
Programme
Leader signature Date

(if required)

S.M.Nisansala Database Design and Development Assignment 01 3

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Higher Nationals - Summative Assignment Feedback Form

Student Name/ID Sembukuttige Madhubhani Nisansala / E191807

Unit Title Unit 04: Database Design & Development

Assignment Number 1 Assessor Mr. Bhimaja


Date
Submission Date 19/07/2023 Received 1st
submission
Date Received 2nd
Re-submission Date submission
Assessor Feedback:
LO1 Use an appropriate design tool to design a relational database system for a substantial
problem
Pass, Merit & P1 M1 D1
Distinction Descripts

LO2 Develop a fully functional relational database system, based on an existing system
design
Pass, Merit & P2 P3 M2 M3 D2
Distinction Descripts

LO3 Test the system against user and system requirements.


Pass, Merit & P4 M4 D2
Distinction Descripts

LO4 Produce technical and user documentation.


Pass, Merit & P5 M5 D3
Distinction Descripts

Grade: Assessor Signature: Date:


Resubmission Feedback:

Grade: Assessor Signature: Date:

S.M.Nisansala Database Design and Development Assignment 01 4

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Internal Verifier’s Comments:

Signature & Date:

* Please note that grade decisions are provisional. They are only confirmed once internal and
external moderation has taken place and grades decisions have been agreed at the assessment
board.

Assignment Feedback

Formative Feedback: Assessor to Student

Action Plan

Summative feedback

S.M.Nisansala Database Design and Development Assignment 01 5

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Feedback: Student to Assessor

Assessor signature Date

Student signature Date

S.M.Nisansala Database Design and Development Assignment 01 6

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Student Declaration

I hereby, declare that I know what plagiarism entails, namely to use another’s work and to
present it as my own without attributing the sources in the correct form. I further understand
what it means to copy another’s work.

1. I know that plagiarism is a punishable offence because it constitutes theft.


2. I understand the plagiarism and copying policy of Edexcel UK.

S.M.Nisansala Database Design and Development Assignment 01 7

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

3. I know what the consequences will be if I plagiarise or copy another’s work in any of the
assignments for this program.
4. I declare therefore that all work presented by me for every aspect of my program, will be
my own, and where I have made use of another’s work, I will attribute the source in the
correct way.
5. I acknowledge that the attachment of this document signed or not, constitutes a binding
agreement between myself and Pearson, UK.
6. I understand that my assignment will not be considered as submitted if this document is
not attached to the assignment.

Student’s Signature: [email protected] Date: 19/07/2023


(Provide E-mail ID) (Provide Submission Date)

S.M.Nisansala Database Design and Development Assignment 01 8

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Higher National Diploma in Computing

Assignment Brief

Student Name /ID Number Sembukuttige Madhubhani Nisansala / E191807


Unit Number and Title Unit 4: Database Design & Development
Academic Year 2022/23
Unit Tutor Mr Bhimaja
Assignment Title Data base system for Quiet Attic Films
Issue Date 11/04/2023
Submission Date 19/07/2023
IV Name & Date

Unit Learning Outcomes:

LO1 Use an appropriate design tool to design a relational database system for a substantial
problem.

LO2 Develop a fully functional relational database system, based on an existing system design.

LO3 Test the system against user and system requirements.

LO4 Produce technical and user documentation.


Assignment Brief and Guidance:

Assignment brief

Quiet Attic Films is a film production company based in London, England who specialize in
making short information films and advertisements for television. They want you to design and
implement a database that meets the requirements for their data. These requirements are
specified in this scenario and the examples of paper documents kept by the company shown
below.

S.M.Nisansala Database Design and Development Assignment 01 9

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Quiet Attic Films organize their data around the concept of a ‘production’. A production is
specified as being for a particular client; but note that a client might have more than one
production at any time. A production will take place at one or more locations. A production
will also use a number of, what are called, properties, which might be anything from an actual
property like a building, to costumes or small items of any sort. It is important to keep a record
of which properties are required at which location.here should also be a record kept of the
staff types that are assi

S.M.Nisansala Database Design and Development Assignment 01 10

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

gned to productions

S.M.Nisansala Database Design and Development Assignment 01 11

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Activity 1

Identify the user and system requirements to design a database for the above scenario and
design a relational database system using conceptual design (ER Model) by including identifiers
(primary Key) of entities and cardinalities, participations of relationships. Convert the ER
Model into logical database design using relational database model including primary keys
foreign keys and referential Integrities.

It should contain at least five interrelated tables. Check whether the provided logical design is
normalised. If not, normalize the database by removing the anomalies.

(Note:-It is allowed to have your own assumptions and related attributes within the scope of
the case study given)

Design set of simple interfaces to input and output for the above scenario using Wireframe or
any interface-designing tool. Evaluate the effectiveness of the given design (ERD and Logical
design) in terms of the identified user and system requirements.

Activity 2

Develop a relational database system according to the ER diagram you have created (Use SQL
DDL statements). Provide evidence of the use of a suitable IDE to create a simple interface to
insert, update and delete data in the database. Implement proper security mechanisms in the
developed database and evaluate the database solution developed in terms of its effectiveness
with relevance to the user and system requirements identified, system security mechanisms

S.M.Nisansala Database Design and Development Assignment 01 12

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

(EX: -User groups, access permissions) and the maintenance of the database. Suggest
improvements for any identified problems.

Assess the usage of the below SQL statements with the examples from the developed
database to prove that the data extracted through them are meaningful and relevant to the
given scenario.

Select/ Where / Update / Between / In / Group by / Order by / Having

Activity 3

3.1 Provide a suitable test plan to test the system against user and system requirements.
Provide relevant test cases for the database you have implemented. Assess how the selected
test data can be used to improve the effectiveness of testing.

Note: - Learner needs to give expected results in a tabular format and screenshots of the actual
results with the conclusion

3.2 Get independent feedback on your database solution from the non-technical users and
some developers (use surveys, questioners, interviews or any other feedback collecting
method) and make a separate conclusion from the feedbacks.

Activity 4

Produce technical and user documentation for a fully functional system, including data flow
diagrams showing movement of data through the system, and flowcharts describing how the
system works. Evaluate the developed database by suggesting future enhancements to ensure
the effectiveness of the system.

Table of Contents

S.M.Nisansala Database Design and Development Assignment 01 13

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

TABLE OF FIGURES.................................................................16

ACKNOWLEDGEMENT.............................................................19

ACTIVITY 01..........................................................................21
1.1. Introduction........................................................................................................................21

1.2. Requirements.....................................................................................................................21

1.2.1. User Requirements......................................................................................................21


1.2.2. System Requirements..................................................................................................21
1.3. Entities and Attributes........................................................................................................22

1.3.1. Relationships...............................................................................................................22
1.3.2. Cardinalities................................................................................................................23
1.4. Entity – Relationship Diagram...........................................................................................25

1.5. Logical Database................................................................................................................25

Normalization...........................................................................................................................26

1.6. Normalization.....................................................................................................................26

1.7. Interface of Quiet Attic Films.............................................................................................27

1.7.1. Login page...................................................................................................................27


1.7.2. Home page..................................................................................................................27
1.7.3. Client page..................................................................................................................28
1.7.4. Location page..............................................................................................................28
1.7.5. Property page..............................................................................................................29
1.7.6. StaffType page.............................................................................................................29
1.7.7. Production page...........................................................................................................30
1.7.8. Production_Location page...........................................................................................30
1.7.9. Production_StaffType page.........................................................................................31
1.7.10. Production_Property page.........................................................................................31
1.8. Evaluation..........................................................................................................................32

ACTIVITY 02..........................................................................33
2.1. SQL....................................................................................................................................33

2.1.1. Creating a database......................................................................................................33


2.1.2. Creating a table............................................................................................................33

S.M.Nisansala Database Design and Development Assignment 01 14

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.1.3. SQL SELECT syntax...................................................................................................36


2.1.5. Inserting data into tables..............................................................................................37
2.1.5. SQL SELECT statement..............................................................................................40
2.1.6. SQL WHERE clause...................................................................................................41
2.1.7. SQL ORDER BY clause..............................................................................................41
2.1.8. SQL UPDATE statement.............................................................................................42
2.1.9. SQL BETWEEN operator...........................................................................................42
2.1.10. SQL IN operator........................................................................................................43
2.1.11. SQL GROUP BY statement.......................................................................................43
2.1.12. SQL HAVING statement...........................................................................................44
2.1.13. SQL JOIN statements................................................................................................44
2.2. Data Validation...................................................................................................................46

2.2.1. Data type validations...................................................................................................46


2.2.2. Length validation.........................................................................................................47
2.2.3. Not null validation.......................................................................................................47
2.3. IDE (Integrated Development Environment)......................................................................48

2.3.1. System of Quiet Attic Films........................................................................................48


..............................................................................................................................................49
2.3.2. Home page..................................................................................................................49
2.3.3. Inserting Client details.................................................................................................50
2.3.4. Update data in Client table..........................................................................................51
2.3.5. Deleting data in the Client table..................................................................................52
2.4. Security mechanisms using in database developing...........................................................53

2.4.1. User authentication......................................................................................................53


2.4.2. User roles and permissions..........................................................................................53
2.4.3. Access logs and monitoring.........................................................................................54
2.4.4. Encryption...................................................................................................................55
2.4.5. Backup and disaster recovery......................................................................................55

ACTIVITY 03..........................................................................57
3.1. Summary of the test planning.............................................................................................57

3.2. Test cases............................................................................................................................57

3.3. SQL codes for test planning...............................................................................................61

3.3.1. Test case 1: Insert a new client....................................................................................61

S.M.Nisansala Database Design and Development Assignment 01 15

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

3.3.2. Test case 2: Update email............................................................................................61


3.3.3. Test case 3: Retrieve production record.......................................................................62
3.3.4. Test case 4: Search productions by period...................................................................62
3.3.5. Test case 5: Associated production with client.............................................................63
3.3.6. Test case 6: Delete a client...........................................................................................63
3.3.7. Test case 7: Assign non-existent property....................................................................64
3.3.8. Test case 8: Login with different roles.........................................................................64
3.3.9. Test case 9: Simulate concurrent operations................................................................65
3.4. Feedback form....................................................................................................................66

69
3.5. Conclusion.........................................................................................................................73

ACTIVITY 04..........................................................................74
4.1 User documentation of interface Quiet Attic Films database...............................................74

4.2. Technical documentation....................................................................................................79

4.3. Instructions for User roles..................................................................................................80

4.3.1. Client user...................................................................................................................80


4.3.2. Staff user.....................................................................................................................81
4.3.3. Admin user..................................................................................................................81
4.3.4. Technical supporter.....................................................................................................81
4.3.5. Database Developer.....................................................................................................82
4.4. Data flow Diagram.............................................................................................................83

4.5. Case diagram......................................................................................................................84

4.6. Future improvements..........................................................................................................85

SUMMARY............................................................................85

REFERENCES......................................................................... 86

Table of figures
S.M.Nisansala Database Design and Development Assignment 01 16

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 1 ER Diagram....................................................................................................................26
Figure 2 Logical Database Diagram..............................................................................................26
Figure 3 Login page......................................................................................................................28
Figure 4 Home page......................................................................................................................28
Figure 5 Client page......................................................................................................................29
Figure 6 Location page..................................................................................................................29
Figure 7 property page..................................................................................................................30
Figure 8 StaffType page................................................................................................................30
Figure 9 Production page..............................................................................................................31
Figure 10 Production_Location page............................................................................................31
Figure 11 Production_StaffType page...........................................................................................32
Figure 12 Production_Property page.............................................................................................32
Figure 13 Creating data base of Quiet Attic Films........................................................................35
Figure 14 Creating Client table.....................................................................................................35
Figure 15 Creating Location table.................................................................................................36
Figure 16 Creating Property table.................................................................................................36
Figure 17 Creating StaffType table................................................................................................36
Figure 18 Creating Production table..............................................................................................37
Figure 19 Creating Producton_Location table...............................................................................37
Figure 20 Creating Production_StaffType table............................................................................37
Figure 21 Creating Production_Property table..............................................................................38
Figure 22 Created tables................................................................................................................38
Figure 23 Inserting data into Client table......................................................................................39
Figure 24 Inserting data into Location table..................................................................................39
Figure 25 Inserting data into Property table..................................................................................40
Figure 26 Inserting data into StaffType table................................................................................40
Figure 27 Inserting data into Production table...............................................................................40
Figure 28 Inserting data into Production_Property table...............................................................41
Figure 29 Inserting data into Production_StaffType table.............................................................41
Figure 30 Inserting data into Production_Location table...............................................................42
Figure 31 Usage of SQL SELECT statement................................................................................42
Figure 32 Usage of WHERE clause..............................................................................................43
Figure 33 Usage of ORDER BY clause.........................................................................................43
Figure 34 Usage of SQL UPDATE statement................................................................................44
Figure 35 Usage of SQL BETWEEN operator..............................................................................44
Figure 36 Usage of SQL IN operator............................................................................................45
Figure 37 Usage of SQL GROUP BY statement...........................................................................45

S.M.Nisansala Database Design and Development Assignment 01 17

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 38 usage of SQL HAVING statement.................................................................................46


Figure 39 usage of SQL INNER JOIN to join FeePerDay and ProTime Period............................47
Figure 40 data type validations.....................................................................................................48
Figure 41 length validation...........................................................................................................49
Figure 42 not null constriction......................................................................................................49
Figure 43 login in to the database..................................................................................................50
Figure 44 code for the Login page................................................................................................51
Figure 45 home page.....................................................................................................................51
Figure 46 inserting data into client table.......................................................................................52
Figure 47 code to insert data into Client table...............................................................................52
Figure 48 updating data in the Client table....................................................................................53
Figure 49 code to update data in the Client table...........................................................................53
Figure 50 deleting data in the Client table.....................................................................................54
Figure 51 code for deleting data from Client table........................................................................54
Figure 52 inserting a new client....................................................................................................63
Figure 53 updating email...............................................................................................................63
Figure 54 Retrieve production record............................................................................................64
Figure 55 Searching productions by period...................................................................................64
Figure 56 Associate production with client...................................................................................65
Figure 57 Deleting a client record.................................................................................................65
Figure 58 Assigning non-existent property....................................................................................66
Figure 59 login with different roles...............................................................................................66
Figure 60 Simulate concurrent operations.....................................................................................67
Figure 61 description of the database interface.............................................................................68
Figure 62 Feedback form page 1...................................................................................................69
Figure 63 feedback form page 2....................................................................................................70
Figure 64 feedback form page 3....................................................................................................71
Figure 65 feedback analysis question 2.........................................................................................72
Figure 66 feedback analysis question 2.........................................................................................72
Figure 67 feedback analysis question 3.........................................................................................73
Figure 68 feedback analysis question 4.........................................................................................73
Figure 69 feedback analysis question 5.........................................................................................74
Figure 70 feedback analysis question 6.........................................................................................74
Figure 71 User documentation cover page....................................................................................76
Figure 72 user manual page 1........................................................................................................77
Figure 73 user manual page 2........................................................................................................78
Figure 74 user manual page 3........................................................................................................79

S.M.Nisansala Database Design and Development Assignment 01 18

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 75 user manual page 4........................................................................................................80


Figure 76 Microsoft SQL server....................................................................................................81
Figure 77 SQL server interface.....................................................................................................81
Figure 78 Visual Studio.................................................................................................................82
Figure 79 data flow diagram.........................................................................................................85
Figure 80 case diagram between of client and production team....................................................86

S.M.Nisansala Database Design and Development Assignment 01 19

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Acknowledgement.

First of all I would like to add my gratitude for my lecturer for educating me about
database designing and developing. Then I would like to express my sincere gratitude for
my parents, university mates, academic and non-academic staff of Esoft Metro Campus.

Author,

S. M. Nisansala.

S.M.Nisansala Database Design and Development Assignment 01 20

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Activity 01
1.1. Introduction
In this scenario, database refers to a structured collection of data designed and
implemented to store and manage information related to the operations of Quiet Attic
Films, a film production company.

The purpose of the database is to efficiently organize and manage various aspects of your
business such as productions, clients, locations, properties, staff types, etc.

A database allows Quiet Attic Films to store and retrieve data in a structured and
organized manner.

In this particular scenario, Quiet Attic Films can use the database to track productions,
associated clients, locations, properties and employee types.

1.2. Requirements
There are two types of requirements.

1. User requirements.
2. System requirements.

1.2.1. User Requirements


1. Ability to manage client productions.
2. Ability to track where productions are being held.
3. Ability to keep a record of which property is used when and where.
4. Keeps records of personnel types assigned to productions.

1.2.2. System Requirements


1. Stores information about production, customers, locations, property, and employee
types.
2. Establish relationships between productions, customers, locations, real estate and
talent types.
3. Ensure data integrity and eliminate data anomalies.
4. Provides an interface for data input and output.

S.M.Nisansala Database Design and Development Assignment 01 21

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

1.3. Entities and Attributes

Entity Primary Key Attributes Foreign Keys


Production ProID ProID, ProName, ClientID,
ProTimePeriod, StaffTypeID,
ClientID, StaffTypeID, PropertyID,
PropertyID, LocationID
LocationID
Location LocationID LocationID, LAddress, -

Client ClientID ClientID, CName, -


Email, ContactNo
Property PropertyID PropertyID, -
PropertType
StaffType StaffTypeID StaffTypeID, -
SaffTypeName

1.3.1. Relationships

In the context of the scenario provided by Quiet Attic Films, relationships play a key role
in organizing and connecting different entities in a database. With the help of these
relationships, connections between production, customers, locations, objects and
personnel types can be established.

1. Production – Location
 One production can be filmed in several locations.
 One location can be used in several productions.
 Relationship – Many to Many

2. Production – Client
 One production only can be owned by one client.
S.M.Nisansala Database Design and Development Assignment 01 22

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

 A client can owned several productions.


 Relationship – Many to One

3. Production – Property
 One production can use many properties.
 One property can be used in many productions.
 Relationship – Many to Many

4. Production – StaffType
 One production can have multiple staff types.
 One staff type can involve in several productions.
 Relationship – Many to Many

1.3.2. Cardinalities

In the context of the Quiet Attic Films scenario, cardinality refers to the number of
instances or records that can be related across different tables in the database. This helps
define the nature of the relationship and determine how the entities are related.

1. Production – Location
 There can be productions without locations.
 There can be locations without productions.
 Cardinality (Production)
 Maximum Cardinality : many
 Minimum Cardinality : zero
 Cardinality (Location)
 Maximum Cardinality : many
 Minimum Cardinality : zero

2. Production – Client
 There can be no productions without clients.

S.M.Nisansala Database Design and Development Assignment 01 23

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

 There can be clients without productions.


 Cardinality (Production)
 Maximum Cardinality : many
 Minimum Cardinality : one
 Cardinality (Clients)
 Maximum Cardinality : many
 Minimum Cardinality : zero

3. Production – Property
 There can be no productions without properties.
 There can be properties without productions.
 Cardinality (Production)
 Maximum Cardinality : many
 Minimum Cardinality : one
 Cardinality (Property)
 Maximum Cardinality : many
 Minimum Cardinality : zero

4. Production – StaffType
 There can be no productions without a staff.
 There can be staff without productions.
 Cardinality (Production)
 Maximum Cardinality : many
 Minimum Cardinality : one
 Cardinality (StaffType)
 Maximum Cardinality : many
 Minimum Cardinality : zero

S.M.Nisansala Database Design and Development Assignment 01 24

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

1.4. Entity – Relationship Diagram

Figure 1 ER Diagram

1.5. Logical Database

Figure 2 Logical Database Diagram

S.M.Nisansala Database Design and Development Assignment 01 25

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Normalization
Normalization is the process of database design aimed at eliminating data redundancy,
improving data integrity, and optimizing data storage and retrieval. This includes reducing
data duplication and organizing database tables and their relationships so that each piece
of information is stored in only one place for it. In the Quiet Attic Films scenario,
normalization helps structure the database efficiently.

1.6. Normalization
 Simplifying the many to many relationship between Production and Location.

ProID LocationID

 Simplifying the many to many relationship between Production and StaffType.

ProID StaffTypeID CrewMembers

 Simplifying the many to many relationship between Production and Property

ProID PropertyID Description

1.7. Interface of Quiet Attic Films

S.M.Nisansala Database Design and Development Assignment 01 26

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

1.7.1. Login page

Figure 3 Login page

1.7.2. Home page

Figure 4 Home page

1.7.3. Client page

S.M.Nisansala Database Design and Development Assignment 01 27

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 5 Client page

1.7.4. Location page

Figure 6 Location page

1.7.5. Property page

S.M.Nisansala Database Design and Development Assignment 01 28

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 7 property page

1.7.6. StaffType page

Figure 8 StaffType page

S.M.Nisansala Database Design and Development Assignment 01 29

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

1.7.7. Production page

Figure 9 Production page

1.7.8. Production_Location page

Figure 10 Production_Location page

S.M.Nisansala Database Design and Development Assignment 01 30

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

1.7.9. Production_StaffType page

Figure 11 Production_StaffType page

1.7.10. Production_Property page

Figure 12 Production_Property page

S.M.Nisansala Database Design and Development Assignment 01 31

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

1.8. Evaluation

The interface design for the Quiet Attic Films Database has been evaluated based on
several factors:

1) User-Friendliness: The interface is intuitive and easy to navigate, making it user-


friendly for both clients and production teams. The layout and organization of
information are well-structured, allowing users to find the desired features
quickly.
2) Visual Appeal: The interface has a modern and visually appealing design with
appropriate colour schemes and fonts, creating a pleasant user experience.
3) Functionality: All essential functionalities, such as adding production details,
managing staff assignments, and accessing property information, are well-
implemented and easily accessible.
4) Responsiveness: The interface is responsive, adapting well to different
Screen sizes and devices, ensuring a consistent experience across desktops,
tablets, and smartphones.
5) Data Validations: The interface includes data validation checks, preventing users
from entering incorrect or invalid data, ensuring data integrity and accuracy.

Activity 02
2.1. SQL
2.1.1. Creating a database
CREATE DATABASE db_name;
S.M.Nisansala Database Design and Development Assignment 01 32

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 13 Creating data base of Quiet Attic Films

2.1.2. Creating a table

CREATE TABLE table_name (column1 data_type, column2 data_type);

Figure 14 Creating Client table

S.M.Nisansala Database Design and Development Assignment 01 33

Figure 15 Creating Location table


Downloaded by Hadi Ahmd ([email protected])
lOMoARcPSD|50495251

Figure 16 Creating Property table

Figure 17 Creating StaffType table

S.M.Nisansala Database Design and Development Assignment 01 34

Figure 18 Creating Production Downloaded


table by Hadi Ahmd ([email protected])
lOMoARcPSD|50495251

Figure 19 Creating Producton_Location table

Figure 20 Creating Production_StaffType table

S.M.Nisansala Database Design and Development Assignment 01 35

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 21 Creating Production_Property table

2.1.3. SQL SELECT syntax

SELECT * FROM table_name;

Figure 22 Created tables

2.1.5. Inserting data into tables.

INSERT INTO table_name (colomn1, colomn2, colomn3…) VALUES (value1,


value2, value3);

S.M.Nisansala Database Design and Development Assignment 01 36

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 23 Inserting data into Client table

Figure 24 Inserting data into Location table

S.M.Nisansala Database Design and Development Assignment 01 37

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 25 Inserting data into Property table

Figure 26 Inserting data into StaffType table

Figure 27 Inserting data into Production table

S.M.Nisansala Database Design and Development Assignment 01 38

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 28 Inserting data into Production_Property table

Figure 29 Inserting data into Production_StaffType table

S.M.Nisansala Database Design and Development Assignment 01 39

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 30 Inserting data into Production_Location table

2.1.5. SQL SELECT statement

SELECT * FROM table_name;

Figure 31 Usage of SQL SELECT statement

S.M.Nisansala Database Design and Development Assignment 01 40

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.1.6. SQL WHERE clause

SELECT column1, column2 FROM table_name WHERE condition;

Figure 32 Usage of WHERE clause

2.1.7. SQL ORDER BY clause

SELECT column1, colmun2 FROM table_name ORDER BY colomun1 ASC/DESC;

Figure 33 Usage of ORDER BY clause

S.M.Nisansala Database Design and Development Assignment 01 41

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.1.8. SQL UPDATE statement

UPDATE table_name SET column1 = value1 WHERE condition;

Figure 34 Usage of SQL UPDATE statement

2.1.9. SQL BETWEEN operator


SELECT * FROM table_name WHERE column_name BETWEEN value1 AND

value2;

Figure 35 Usage of SQL BETWEEN operator

S.M.Nisansala Database Design and Development Assignment 01 42

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.1.10. SQL IN operator


SELECT * FROM table_name WHERE column_name IN (value1, value2..);

Figure 36 Usage of SQL IN operator

2.1.11. SQL GROUP BY statement

SELECT COUNT (primary key), column_name FROM table_name WHERE


column_name < value GROUP BY column_name;

Figure 37 Usage of SQL GROUP BY statement

S.M.Nisansala Database Design and Development Assignment 01 43

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.1.12. SQL HAVING statement

SELECT column_name, COUNT (*) AS column_name FROM table_name


GROUP BY column_name HAVING COUNT (*) < value1

Figure 38 usage of SQL HAVING statement

2.1.13. SQL JOIN statements

Inner join

SELECT column_name FROM table1 INNER JOIN table2 ON

table1.column_name = table2.column_name;

Left join

SELECT column_name FROM table1 LEFT JOIN table2 ON

table1.column_name = table2.column_name;

S.M.Nisansala Database Design and Development Assignment 01 44

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Right join

SELECT column_name FROM table1 RIGHT JOIN table2 ON

table1.column_name = table2.column_name;

Figure 39 usage of SQL INNER JOIN to join FeePerDay and ProTime Period

S.M.Nisansala Database Design and Development Assignment 01 45

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.2. Data Validation

Data validations are essential checks implemented in a database system to ensure the
accuracy, integrity, and reliability of the data being stored. These validations enforce rules
and constraints on the input data, preventing the entry of invalid or inconsistent
information.

For example, data validations can include checks for data types, lengths, formats, and
ranges. They can verify that required fields are not left empty, and that dates are entered
in the correct format. Additionally, data validations can enforce referential integrity by
verifying the existence of related records in other tables through foreign key constraints.

By implementing data validations, the database system can prevent the storage of
incorrect or irrelevant data, leading to a more reliable and consistent database. These
validations help maintain data quality and improve the overall effectiveness of the system
by ensuring that only valid and meaningful data is stored and processed.

2.2.1. Data type validations

Figure 40 data type validations

S.M.Nisansala Database Design and Development Assignment 01 46

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.2.2. Length validation

Figure 41 length validation

2.2.3. Not null validation

Figure 42 not null constriction

S.M.Nisansala Database Design and Development Assignment 01 47

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.3. IDE (Integrated Development Environment)

An Integrated Development Environment (IDE) is a software application that provides


developers with a comprehensive set of tools for writing, debugging, and testing code. It
offers a user-friendly interface, code editing features, and debugging capabilities,
streamlining the software development process and enhancing productivity.

2.3.1. System of Quiet Attic Films

User can log into the system.

Figure 43 login in to the database

S.M.Nisansala Database Design and Development Assignment 01 48

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 44 code for the Login page

2.3.2. Home page

User can select the table

Figure 45 home page

S.M.Nisansala Database Design and Development Assignment 01 49

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.3.3. Inserting Client details

Figure 46 inserting data into client table

Figure 47 code to insert data into Client table

S.M.Nisansala Database Design and Development Assignment 01 50

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.3.4. Update data in Client table

Figure 48 updating data in the Client table

Figure 49 code to update data in the Client table

S.M.Nisansala Database Design and Development Assignment 01 51

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.3.5. Deleting data in the Client table

Figure 50 deleting data in the Client table

Figure 51 code for deleting data from Client table

S.M.Nisansala Database Design and Development Assignment 01 52

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.4. Security mechanisms using in database developing

Database security is a critical aspect of protecting sensitive information and ensuring the
integrity of a database system. It involves implementing various measures to prevent
unauthorized access, safeguard data from breaches, and maintain data confidentiality.

2.4.1. User authentication

Implementing robust user authentication mechanisms, such as username and password


verification or multi-factor authentication, to ensure that only authorized users can access
the database.

2.4.2. User roles and permissions

Assign specific rights and permissions to users based on their roles and responsibilities.
This restricts access to sensitive data and database functions and ensures that users can
only perform authorized actions.

1. Administer / Super user :


 Has complete control and privileges all over the database.
 Can perform all tasks such as creating and managing user accounts,
defining roles.
 Has permissions to modify all database in the database.

2. Owner of the database


 Should bare the responsible for managing the database of Quiet Attic
Films.
 Has permissions create, modify, delete and view tables and other
objectives in their owned database.
 Can access and manage data within their owned databases.

S.M.Nisansala Database Design and Development Assignment 01 53

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

3. Data entry operators


 Responsible for adding and updating data in the database.
 Have permission to insert, update and delete records in only data entry
forms.
 Works under limited or read only access to other data and database objects.

4. Data analysts
 Tasked with analysing data and generating reports based on user
requirements.
 Have permissions to run queries, retrieve data and generate reports from
relevant tables.
 Works under limited or read only access to other data and database objects.

5. Read only user


 Has read only access to specific tables and can view data but cannot
modify them.

6. System Administrator
 Manage the overall system infrastructure and database server.
 Have permission to perform tasks like installing updates, configuring
backups and monitoring system performance.

2.4.3. Access logs and monitoring

Enable logging of user activities and system events to track and monitor user access.
Access logs can provide an audit trail for detecting unauthorized access attempts,
identifying suspicious behaviour, and investigating security incidents.

S.M.Nisansala Database Design and Development Assignment 01 54

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2.4.4. Encryption

In the given scenario, encryption plays a crucial role in safeguarding sensitive


information stored in the database of Quiet Attic Films. Encryption is a security technique
used to convert plain text data, such as client details or financial records, into an
unreadable format called cipher text. This ensures that even if unauthorized individuals
gain access to the database, they cannot interpret or access the sensitive data without the
decryption key.

Quiet Attic Films can employ encryption mechanisms to protect data both at rest and
during transmission. Encryption at rest involves encrypting the data stored in the
database, ensuring that it remains secure even if the physical storage is compromised.
This prevents unauthorized access to sensitive information, such as client contact details
or production-related data.

2.4.5. Backup and disaster recovery

In the given scenario of Quiet Attic Films, implementing backup and disaster recovery
measures is crucial to ensure data integrity and availability, as well as to minimize the
impact of system failures or data loss.

By regularly performing backups, Quiet Attic Films can protect against data loss caused
by hardware failures, software errors, or human mistakes.

In the event of data corruption or accidental deletion, the organization can restore the
database from a recent backup, ensuring that critical information is not permanently lost.

This includes considerations such as alternative backup locations, backup restoration


procedures, and testing the recovery plan to ensure its effectiveness.

By implementing backup and disaster recovery measures, Quiet Attic Films can minimize
downtime, prevent data loss, and ensure business continuity.

S.M.Nisansala Database Design and Development Assignment 01 55

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

In the event of a system failure or data


breach, they can recover the database quickly and efficiently,
reducing the impact on their operations and minimizing potential financial and
reputational damage.

Regular testing and validation of backup and disaster recovery procedures are essential to
ensure their effectiveness.

S.M.Nisansala Database Design and Development Assignment 01 56

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Activity 03

3.1. Summary of the test planning

Test planning is a crucial step in validating the functionality and effectiveness of a


database system. It involves identifying test objectives, defining test scenarios, and
creating relevant test cases. By selecting appropriate test data and expected results,
potential issues and areas for improvement can be identified. Feedback from non-
technical users and developers can provide valuable insights into the usability,
functionality, and performance of the database solution. Summarizing the test results and
feedback helps evaluate the effectiveness of the testing process and determine the
strengths and weaknesses of the database solution. This aids in making informed
decisions for further improvements and enhancements.

3.2. Test cases

Test case Test plan Test steps Expected Status


results

1 Insert an 1) Enter client New record PASS


unused client details to the added
record. table. successfully
2) Verify if the
record added

2 Update email. 1) Find an Successfully PASS


existing client update the
in the table. email

S.M.Nisansala Database Design and Development Assignment 01 57

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

2) Update
the email
3) verify if
the email
has been
updated

3 Retrieve 1) Search Production PASS


production for a record is
Record specific found and
production details
record in match with
the the
database expected
2) Verify records
the
accuracy of
the retrieve
production

4 Search 1) Specify Production PASS


production a time s within
s by period period for the
the search. specified
2) Verify if period are
the correct displayed
production
s are
displayed.

5 Associate 1) Create a New PASS

S.M.Nisansala Database Design and Development Assignment 01 58

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

new production
production record is
production
record. successfull
with client
2) y created
Associate and
the production
production is
with an associated
existing with the
client. client
3) Verify if
the
association
is reflected
in the
database.

6 Delete a 1) Select a Client PASS


client client to record is
delete. successfull
2) Verify if y deleted
associated and
production associated
s are also production
removed. s are no
longer in
the
database.

7 Assign 1) Select a Appropriat PASS


non- production e error
existent and specify message is

S.M.Nisansala Database Design and Development Assignment 01 59

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

a non- displayed
existent
property
property.
2) Verify if
the error
handling is
appropriate
.

8 Login with 1) Attempt Successful PASS


different login with login with
roles an administrat
administrat or
or role. privileges
2) Verify if and access
the to all
appropriate system
access functionalit
rights are ies is
granted. proved.

9 Simulate 1) Perform System PASS


concurrent a large responses
operations. number of time
simultaneo remains
us database within
operations. acceptable
limits.

10 Increased 1) Add a System PASS


data significant performanc

S.M.Nisansala Database Design and Development Assignment 01 60

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

amount of e remains
data to the unaffected.
volume.
database.

3.3. SQL codes for test planning

3.3.1. Test case 1: Insert a new client

Figure 52 inserting a new client

3.3.2. Test case 2: Update email

S.M.Nisansala Database Design and Development Assignment 01 61

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 53 updating email

3.3.3. Test case 3: Retrieve production record

Figure 54 Retrieve production record

3.3.4. Test case 4: Search productions by period

S.M.Nisansala Database Design and Development Assignment 01 62

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 55 Searching productions by period

3.3.5. Test case 5: Associated production with client

Figure 56 Associate production with client

3.3.6. Test case 6: Delete a client

S.M.Nisansala Database Design and Development Assignment 01 63

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 57 deleting a client record

3.3.7. Test case 7: Assign non-existent property

Figure 58 Assigning non-existent property

3.3.8. Test case 8: Login with different roles

S.M.Nisansala Database Design and Development Assignment 01 64

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 59 login with different roles

3.3.9. Test case 9: Simulate concurrent operations

Figure 60 Simulate concurrent operations

S.M.Nisansala Database Design and Development Assignment 01 65

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

3.4. Feedback form

S.M.Nisansala Database Design and Development Assignment 01 66

Downloaded by Hadi Ahmd ([email protected])


Figure 61 description of the database interface
lOMoARcPSD|50495251

S.M.Nisansala Database Design and Development Assignment 01 67

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 62 Feedback form page 1

S.M.Nisansala Database Design and Development Assignment 01 68

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 63 feedback form page 2

S.M.Nisansala Database Design and Development Assignment 01 69

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 64 feedback form page 3

S.M.Nisansala Database Design and Development Assignment 01 70

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 65 feedback analysis question 2

Figure 66 feedback analysis question 2

S.M.Nisansala Database Design and Development Assignment 01 71

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 67 feedback analysis question 3

Figure 68 feedback analysis question 4

S.M.Nisansala Database Design and Development Assignment 01 72

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 69 feedback analysis question 5

Figure 70 feedback analysis question 6

S.M.Nisansala Database Design and Development Assignment 01 73

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

3.5. Conclusion

In summary, feedback plays an important role in organizational growth and improvement.


Feedback received from users or customers provides valuable insights that enable
companies to better understand user experiences and expectations.

Feedback allows us to rate the positive aspects of our products, services, or experiences
that you may find valuable. This allows us to recognize and celebrate our strengths and
reinforces our commitment to delivering superior quality.

In addition, feedback helps us identify areas that need improvement and address concerns
and issues raised by users. Careful research and analysis of feedback allows us to glean
constructive criticism and valuable suggestions that pave the way for improvement and
innovation.

We value user and customer feedback and ensure that their opinions are important to our
decision-making process. We use your feedback to drive positive change and strive to
provide an even better experience in the future.

We encourage ongoing engagement and welcome ongoing feedback from our users and
customers. Together we are committed to continuous improvement, ensuring that their
voices are heard and taken into account in shaping our products, services and the overall
customer experience.

S.M.Nisansala Database Design and Development Assignment 01 74

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Activity 04

4.1 User documentation of interface Quiet Attic Films database

Figure 71 User documentation cover page

S.M.Nisansala Database Design and Development Assignment 01 75

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 72 user manual page 1

S.M.Nisansala Database Design and Development Assignment 01 76

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 73 user manual page 2

S.M.Nisansala Database Design and Development Assignment 01 77

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 74 user manual page 3

S.M.Nisansala Database Design and Development Assignment 01 78

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Figure 75 user manual page 4

S.M.Nisansala Database Design and Development Assignment 01 79

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

4.2. Technical documentation

System Introduction
Software requirements
 Windows 7 or higher version (32-bit or 64-bit)
 Microsoft SQL Server 2018

Figure 76 Microsoft SQL server

Figure 77 SQL server interface

S.M.Nisansala Database Design and Development Assignment 01 80

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

 Dot Net Framework 6

Figure 78 Visual Studio

4.3. Instructions for User roles

4.3.1. Client user

Access: limited access only to view the information with regard to their own productions.

Task:

 Can view details of their ongoing productions.


 Check assigned staff types, access location details and associated properties.
 Provide feedbacks or request changes according to their perceptions.

S.M.Nisansala Database Design and Development Assignment 01 81

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

4.3.2. Staff user

Access: Do not have access to view or update their production related records.

Task:

 Can view their assigned productions, location details, and properties they need.
 Should update their availability and confirm participation in productions.
 Can request additional information with regarding to the productions they have
assigned.

4.3.3. Admin user

Access: Have full access in all aspects.

Task:

 Add and manage client information.


 Assign staff member, locations and properties to each productions.
 Manage production details.
 Track and modify location information.
 Generate reports on effectiveness of productions and their status.

4.3.4. Technical supporter

Access: Have access to troubleshoot and provide assistance to other users.

Task:

 Address technical errors and issues encountered by users.


 Resolve all the issues other users facing.

S.M.Nisansala Database Design and Development Assignment 01 82

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

4.3.5. Database Developer

Access: Has full access to the database structure and design.

Task:

 Monitor and do optimization of the database.


 Implement necessary changes to improve the efficiency of the database.
 Ensure data security and regularly update the database.

S.M.Nisansala Database Design and Development Assignment 01 83

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

4.4. Data flow Diagram

Figure 79 data flow diagram

S.M.Nisansala Database Design and Development Assignment 01 84

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

4.5. Case diagram

Figure 80 case diagram between of client and production team

S.M.Nisansala Database Design and Development Assignment 01 85

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

4.6. Future improvements

Future improvements aim to enhance user experience, increase efficiency, and provide
better insights for decision – making.

1) Modern user interface: upgrade a modern user interface with intuitive design to
improve usability and accessibility.
2) Mobile application: developing a mobile application for production team and
clients will effectively engage the staff and system in the incident.
3) Automated notifications: using automated notifications for updates, security
checking, and important events.

Summary

The database design for Quiet Attic Films is organized around the concept of a
"production" and is designed to meet the requirements of the film production company.
The database includes interrelated tables for clients, locations, properties, staff types, and
productions. Each production is associated with a client, one or more locations, and
utilizes various properties and staff types. The design includes proper primary keys,
foreign keys, and referential integrity constraints to maintain data integrity and
relationships. The database is normalized to remove anomalies and improve data
efficiency. The system also incorporates security mechanisms, user roles, and permissions
to protect data and control access. Additionally, interfaces and data validations have been
implemented to ensure smooth interactions and accurate data entry. Continuous
improvements and feedback will help maintain the effectiveness of the database system
over time.

S.M.Nisansala Database Design and Development Assignment 01 86

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

References

Entity relationship diagram (ERD) (no date) Entity Relationship Diagram


(ERD) - What is an ER Diagram? Available at:
https://www.smartdraw.com/entity-relationship-diagram/ (Accessed: 15 July
2023).

Create a database and add tables - visual studio (windows), Create a


database and add tables - Visual Studio (Windows) | Microsoft Learn.
Available at: https://learn.microsoft.com/en-us/visualstudio/data-tools/create-
a-sql-database-by-using-a-designer?view=vs-2022 (Accessed: 16 July
2023).

Connect to a database or open an MDF file - visual studio (windows), or


open an MDF file - Visual Studio (Windows) | Microsoft Learn. Available at:
https://learn.microsoft.com/en-us/visualstudio/data-tools/add-new-
connections?view=vs-2022 (Accessed: 16 July 2023).

SQL tutorial. Available at: https://www.w3schools.com/sql/ (Accessed: 18


July 2023).

Different types of database security in DBMS, Cyber Threat & Security


Portal. Available at: https://cyberthreatportal.com/types-of-database-
security/ (Accessed: 18 July 2023).

S.M.Nisansala Database Design and Development Assignment 01 87

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

Grading Criteria Achieved Feedback

LO1 Use an appropriate design


tool to design a relational
database system for a substantial
problem.
P1 Design a relational database
system using appropriate design
tools and techniques, containing at
least four interrelated tables, with
clear statements of user and
system requirements.
M1 Produce a comprehensive
design for a fully-functional
system, which includes interface
and output designs, data
validations and data normalization.
D1 Evaluate the effectiveness of
the design in relation to user and
system requirements.

LO2 Develop a fully-functional


relational database system, based
on an existing system design
P2 Develop the database system
with evidence of user interface,
output and data validations, and
querying across multiple tables.

S.M.Nisansala Database Design and Development Assignment 01 88

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

P3 Implement a query
language into the
relational database system
.
M2 Implement a fully
functional database
system, which includes
system security and
database maintenance.

M3 Assess whether
meaningful data has been
extracted through the use
of query tools to produce
appropriate management
information
LO3 Test the systems
against user and system
requirements
P4 Test the system against
user and system
requirements.
M4 Assess the
effectiveness of the
testing, including an
explanation of the choice
of test data used.
D2 Evaluate the
effectiveness of the
database solution in
relation to user and
system requirements and

S.M.Nisansala Database Design and Development Assignment 01 89

Downloaded by Hadi Ahmd ([email protected])


lOMoARcPSD|50495251

suggest improvements.
LO4 Produce technical and
user documentation
P5 Produce technical and
user documentation.
M5 Produce technical and
user documentation for a
fully-functional system,
including data flow
diagrams and flowcharts,
describing how the

system works.
D3 Evaluate the database
in terms of improvements
needed to ensure the
continued effectiveness of
the system.

S.M.Nisansala Database Design and Development Assignment 01 90

Downloaded by Hadi Ahmd ([email protected])

You might also like