Business brief
- A student has one or many classes and a class has one or many students.
- According to the case study music divided into two parts. First one is live music and second one is teach music. So that here music is superclass and live music and teaches music is subclass.
- According to the case study the classes divided into two parts. First one is children class and second one id adult class. So that here a class is super class and children class and adult class are subclasses.
- A class has one or many teacher but a teacher is related to one and only one class.
- A class has one or many teach music and each teaches music is related to one and only one class.
- A teacher has one or many bookings and a booking is related to one or many booking.
- A booking has one or many teach music and each tech music is related to one and only one booking.
- A musician work as one and only one teacher and each teacher is related to one and only one musician.
- A venue has one or many live music and each live music is related to one and only one venue.
- A venue is related to one or many musician and each musician related to one or many venue. So that here a venue booking has one to many venue and each venue is related to one and only one venue booking. A venue booking has one or many musician and each musician is related to one and only one venue booking.
- A venue booking has one or many bands and each band is related to one and only one venue booking.
Create tables: –
1. STUDENT TABLE
CREATE TABLE STUDENT
(
STUDENT_ID INTEGER NOT NULL,
FIRSTNAME VARCHAR (50) NOT NULL,
LASTNAME VARCHAR (50) NOT NULL,
DOB DATE NOT NULL,
ADDRESS VARCHAR (150) NOT NULL,
EMAIL VARCHAR (50) NOT NULL,
PRIMARY KEY (STUDENT_ID)
)
;
2. MUSIC TABLE-
CREATE TABLE MUSIC
(
MUSIC_NO INTEGER NOT NULL,
MUSIC_STYLE VARCHAR (50) NOT NULL,
MUSIC_NAME VARCHAR (100) NOT NULL,
DESCRIPTION VARCHAR (200),
PRIMARY KEY (MUSIC_NO)
)
;
3. LIVE_MUSIC TABLE-
CREATE TABLE LIVE_MUSIC
(
LIVE_MUSIC_NO INTEGER NOT NULL,
PRIMARY KEY (LIVE_MUSIC_NO),
FOREIGN KEY (LIVE_MUSIC_NO) REFERENCES MUSIC (MUSIC_NO)
)
;
4. TEACH_MUSIC TABLE-
CREATE TABLE TEACH_MUSIC
(
TEACH_MUSIC_NO INTEGER NOT NULL,
PRIMARY KEY (TEACH_MUSIC_NO),
FOREIGN KEY (TEACH_MUSIC_NO) REFERENCES MUSIC (MUSIC_NO)
)
;
5. MUSICIAN_INFO TABLE
CREATE TABLE MUSICIAN_INFO
(
MUSICIAN_ID INTEGER NOT NULL,
FIRSTNAME VARCHAR (50) NOT NULL,
LASTNAME VARCHAR (50) NOT NULL,
DOB DATE NOT NULL,
GENDER VARCHAR (2) NOT NULL check (GENDER in (‘M’, ‘F’)),
ADDRESS VARCHAR (200) NOT NULL,
EMAIL VARCHAR (50) NOT NULL,
PHONE_NUMBER VARCHAR (15) NOT NULL,
PRIMARY KEY (MUSICIAN_ID)
)
;
6. TEACHER TABLE-
CREATE TABLE TEACHER
(
TEACHER_ID INTEGER NOT NULL,
QUALIFICATION VARCHAR (200) NOT NULL,
MUSIC_TYPE VARCHAR (100) NOT NULL,
START_DATE DATE NOT NULL,
EXPIRY_DATE DATE NOT NULL,
PRIMARY KEY (TEACHER_ID),
FOREIGN KEY (TEACHER_ID) REFERENCES MUSICIAN_INFO (MUSICIAN_ID)
)
;
7. BOOKING TABLE-
CREATE TABLE BOOKING
(
BOOKING_NO INTEGER NOT NULL,
TEACH_MUSIC_NO INTEGER NOT NULL,
BOOKING_DATE DATE NOT NULL,
JOIN_DATE DATE NOT NULL,
PRIMARY KEY (BOOKING_NO),
FOREIGN KEY (TEACH_MUSIC_NO) REFERENCES TEACH_MUSIC (TEACH_MUSIC_NO)
)
;
8. STUDENT_BOOKING TABLE
CREATE TABLE STUDENT_BOOKING
(
BOOKING_NO INTEGER NOT NULL,
STUDENT_ID INTEGER NOT NULL,
PRIMARY KEY (BOOKING_NO),
FOREIGN KEY (BOOKING_NO) REFERENCES BOOKING (BOOKING_NO),
FOREIGN KEY (STUDENT_ID) REFERENCES STUDENT (STUDENT_ID)
)
;
9. TEACHER_BOOKING TABLE-
CREATE TABLE TEACHER_BOOKING
(
BOOKING_NO INTEGER NOT NULL,
TEACHER_ID INTEGER NOT NULL,
PRIMARY KEY (BOOKING_NO),
FOREIGN KEY (BOOKING_NO) REFERENCES BOOKING (BOOKING_NO),
FOREIGN KEY (TEACHER_ID) REFERENCES TEACHER (TEACHER_ID)
)
;
10. CLASSES TABLE
CREATE TABLE CLASSES
(
CLASS_NO INTEGER NOT NULL,
ROOM_NO VARCHAR (10) NOT NULL,
TEACHER_ID INTEGER NOT NULL,
TEACH_MUSIC_NO INTEGER NOT NULL,
NO_OF_STUDENT INTEGER NOT NULL,
START_DATETIME TIMESTAMP NOT NULL,
END_DATETIME TIMESTAMP NOT NULL,
PRIMARY KEY (CLASS_NO),
FOREIGN KEY (TEACHER_ID) REFERENCES TEACHER (TEACHER_ID),
FOREIGN KEY (TEACH_MUSIC_NO) REFERENCES TEACH_MUSIC (TEACH_MUSIC_NO)
)
;
11. CHILDREN_CLASS TABLE-
CREATE TABLE CHILDREN_CLASS
(
CLASS_NO INTEGER NOT NULL,
PRIMARY KEY (CLASS_NO),
FOREIGN KEY (CLASS_NO) REFERENCES CLASSES (CLASS_NO)
)
;
12. ADULT_CLASS TABLE-
CREATE TABLE ADULT_CLASS
(
CLASS_NO INTEGER NOT NULL,
PRIMARY KEY (CLASS_NO),
Operations
FOREIGN KEY (CLASS_NO) REFERENCES CLASSES (CLASS_NO)
)
;
13. STUDENT_CLASS TABLE-
CREATE TABLE STUDENT_CLASS
(
S_NO INTEGER NOT NULL,
STUDENT_ID INTEGER NOT NULL,
CLASS_NO INTEGER NOT NULL,
JOIN_DATE DATE NOT NULL,
PRIMARY KEY (S_NO),
FOREIGN KEY (STUDENT_ID) REFERENCES STUDENT (STUDENT_ID),
FOREIGN KEY (CLASS_NO) REFERENCES CLASSES (CLASS_NO)
)
;
14. BAND TABLE-
CREATE TABLE BAND
(
BAND_NO INTEGER NOT NULL,
BAND_NAME VARCHAR (200) NOT NULL,
MEMBERS INTEGER NOT NULL,
PRIMARY KEY (BAND_NO)
)
;
15. VENUE TABLE
CREATE TABLE VENUE
(
VENUE_NO INTEGER NOT NULL,
VENUE_NAME VARCHAR (200) NOT NULL,
START_DATETIME TIMESTAMP NOT NULL,
END_DATETIME TIMESTAMP NOT NULL,
LOCATION VARCHAR (200) NOT NULL,
PRIMARY KEY (VENUE_NO)
)
;
16. VEMUE_LIVE_MUSIC TABLE-
CREATE TABLE VENUE_LIVE_MUSIC
(
VENUE_NO INTEGER NOT NULL,
LIVE_MUSIC_NO INTEGER NOT NULL,
PRIMARY KEY (VENUE_NO, LIVE_MUSIC_NO),
FOREIGN KEY (VENUE_NO) REFERENCES VENUE (VENUE_NO),
FOREIGN KEY (LIVE_MUSIC_NO) REFERENCES LIVE_MUSIC (LIVE_MUSIC_NO)
)
;
-17. VENUE_BOOKING TABLE-
CREATE TABLE VENUE_BOOKING
(
VENUE_BOOKING_NO INTEGER NOT NULL,
VENUE_NO INTEGER NOT NULL,
MUSICIAN_ID INTEGER NOT NULL,
BAND_NO INTEGER,
PRIMARY KEY (VENUE_BOOKING_NO),
FOREIGN KEY (VENUE_NO) REFERENCES VENUE (VENUE_NO),
FOREIGN KEY (MUSICIAN_ID) REFERENCES MUSICIAN_INFO (MUSICIAN_ID)
)
;
1. STUDENT TABLE
INSERT INTO STUDENT VALUES(1, ‘RAMIYA’, ‘CABIN’, ’29-JUN-1996′, ‘US’,’[email protected]‘);
INSERT INTO STUDENT VALUES(2, ‘JANIYA’, ‘CABIN’, ’25-JUN-1996′, ‘US’,’[email protected]‘);
INSERT INTO STUDENT VALUES(3, ‘TINA’, ‘CABIN’, ’21-JUN-1996′, ‘US’,’[email protected]‘);
INSERT INTO STUDENT VALUES(4, ‘VIVAN’, ‘CABIN’, ’19-JUN-1996′, ‘US’,’[email protected]‘);
INSERT INTO STUDENT VALUES(5, ‘FREEK’, ‘CABIN’, ’09-JUN-1996′, ‘US’,’[email protected]‘);
-2. MUSIC TABLE-
INSERT INTO MUSIC VALUES (1, ‘POP’,’JACK’,”);
INSERT INTO MUSIC VALUES (2, ‘ROCK’,’VINNNA’,”);
INSERT INTO MUSIC VALUES (3, ‘JAZZ’,’MARIYA’,”);
INSERT INTO MUSIC VALUES (4, ‘CLASSIC’,’VIVA’,”);
INSERT INTO MUSIC VALUES (5,’HIP HOP’,’YOYO’,”);
3. LIVE_MUSIC TABLE-
INSERT INTO LIVE_MUSIC VALUES (1);
INSERT INTO LIVE_MUSIC VALUES (2);
INSERT INTO LIVE_MUSIC VALUES (3);
4. TEACH_MUSIC TABLE
INSERT INTO TEACH_MUSIC VALUES (4);
INSERT INTO TEACH_MUSIC VALUES (5);
INSERT INTO TEACH_MUSIC VALUES (3);
INSERT INTO TEACH_MUSIC VALUES (1);
5. MUSICIAN_INFO TABLE-
INSERT INTO MUSICIAN_INFO VALUES (1, ‘VIVNA’,’RANIKA’,’19-FEB-1985′,’M’,’US’,’[email protected]‘, ‘0987678767’);
INSERT INTO MUSICIAN_INFO VALUES (2, ‘BINA’,’RANIKA’,’19-FEB-1985′,’M’,’US’,’[email protected]‘, ‘0985678767’);
INSERT INTO MUSICIAN_INFO VALUES (3, ‘CINA’,’RANIKA’,’21-FEB-1985′,’F’,’US’,’[email protected]‘,’3574678767’);
INSERT INTO MUSICIAN_INFO VALUES (4, ‘EINA’,’RANIKA’,’09-FEB-1985′,’F’,’US’,’[email protected]‘,’0987677876’);
INSERT INTO MUSICIAN_INFO VALUES (5, ‘DINA’,’RANIKA’,’14-FEB-1985′,’M’,’US’,’[email protected]‘,’0567678767’);
INSERT INTO MUSICIAN_INFO VALUES (6, ‘DINA’,’RANIKA’,’14-FEB-1994′,’M’,’US’,’[email protected]‘,’0567678767’);
6. TEACHER TABLE-
INSERT INTO TEACHER VALUES (1, ‘YA’,’POP’,’19-JAN-2012′,’19-DEC-2019′);
INSERT INTO TEACHER VALUES (2, ‘YU’,’ROCK’,’14-JAN-2012′,’29-DEC-2019′);
INSERT INTO TEACHER VALUES (3, ‘YR’,’CLASSIC’,’17-JAN-2012′,’09-DEC-2019′);
INSERT INTO TEACHER VALUES (4, ‘TR’,’POP’,’18-JAN-2012′,’29-DEC-2019′);
INSERT INTO TEACHER VALUES (5, ‘WA’,’JAZZ’,’29-JAN-2012′,’19-DEC-2019′);
INSERT INTO TEACHER VALUES (6, ‘WA’,’JAZZ’,’29-JAN-2012′,’19-DEC-2017′);
7. BOOKING TABLE-
INSERT INTO BOOKING VALUES (1, 1,’01-JAN-2018′,’01-JULY-2018′);
INSERT INTO BOOKING VALUES (2, 3,’02-JAN-2018′,’02-JULY-2018′);
INSERT INTO BOOKING VALUES (3, 4,’03-JAN-2018′,’03-JULY-2018′);
INSERT INTO BOOKING VALUES (4, 5,’04-JAN-2018′,’04-JULY-2018′);
Task
INSERT INTO BOOKING VALUES (5, 1,’05-JAN-2018′,’05-JULY-2018′);
8. STUDENT_BOOKING TABLE-
INSERT INTO STUDENT_BOOKING VALUES (1, 1);
INSERT INTO STUDENT_BOOKING VALUES (2, 2);
INSERT INTO STUDENT_BOOKING VALUES (3, 3);
9. TEACHER_BOOKING TABLE-
INSERT INTO TEACHER_BOOKING VALUES (4, 1);
INSERT INTO TEACHER_BOOKING VALUES (5, 2);
10. CLASSES TABLE-
INSERT INTO CLASSES VALUES (1, 20, 1, 1, 23,’02-Sep-2018 09:50:16.78′,’02-Sep-2018 11:50:16.78′);
INSERT INTO CLASSES VALUES (2, 23, 3, 3, 23,’02-Sep-2018 11:50:16.78′,’02-Sep-2018 01:50:16.78′);
INSERT INTO CLASSES VALUES (3, 24, 4, 4, 23,’03-Sep-2018 09:50:16.78′,’03-Sep-2018 11:50:16.78′);
INSERT INTO CLASSES VALUES (4, 22, 5, 5, 23,’03-Sep-2018 11:50:16.78′,’03-Sep-2018 01:50:16.78′);
INSERT INTO CLASSES VALUES (5, 27, 1, 1, 23,’04-Sep-2018 09:50:16.78′,’04-Sep-2018 11:50:16.78′);
INSERT INTO CLASSES VALUES (6, 25, 3, 3, 23,’04-Sep-2018 11:50:16.78′,’04-Sep-2018 01:50:16.78′);
INSERT INTO CLASSES VALUES (7, 23, 4, 4, 23,’05-Sep-2018 09:50:16.78′,’05-Sep-2018 11:50:16.78′);
INSERT INTO CLASSES VALUES (8, 25, 5, 5, 23,’05-Sep-2018 11:50:16.78′,’05-Sep-2018 01:50:16.78′);
INSERT INTO CLASSES VALUES (9, 22, 1, 1, 23,’06-Sep-2018 09:50:16.78′,’06-Sep-2018 11:50:16.78′);
INSERT INTO CLASSES VALUES (10, 20, 3, 3, 23,’06-Sep-2018 11:50:16.78′,’06-Sep-2018 01:50:16.78′);
11. CHILDREN_CLASS TABLE
INSERT INTO CHILDREN_CLASS VALUES (1);
INSERT INTO CHILDREN_CLASS VALUES (2);
INSERT INTO CHILDREN_CLASS VALUES (3);
INSERT INTO CHILDREN_CLASS VALUES (4);
INSERT INTO CHILDREN_CLASS VALUES (5);
12. ADULT_CLASS TABLE-
INSERT INTO ADULT_CLASS VALUES (6);
INSERT INTO ADULT_CLASS VALUES (7);
INSERT INTO ADULT_CLASS VALUES (8);
INSERT INTO ADULT_CLASS VALUES (9);
INSERT INTO ADULT_CLASS VALUES (10);
13. STUDENT_CLASS TABLE-
INSERT INTO STUDENT_CLASS VALUES (1, 1, 1,’01-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (2, 2, 2,’02-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (3, 3, 3,’03-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (4, 4, 4,’04-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (5, 5, 5,’05-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (6, 1, 6,’01-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (7, 2, 7,’02-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (8, 3, 8,’03-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (9, 4, 9,’04-JULY-2018′);
INSERT INTO STUDENT_CLASS VALUES (10, 5, 10,’05-JULY-2018′);
14. BAND TABLE-
INSERT INTO BAND VALUES (1, ‘JH’, 10);
INSERT INTO BAND VALUES (2, ‘QH’, 10);
INSERT INTO BAND VALUES (3, ‘JHE’, 10);
INSERT INTO BAND VALUES (4, ‘SH’, 10);
INSERT INTO BAND VALUES (5, ‘GH’, 10);
15. VENUE TABLE-
INSERT INTO VENUE VALUES (1, ‘GHJ BUHJ’,’01-SEP-108′,’02-SEP-2018′,’Australian’);
INSERT INTO VENUE VALUES (2, ‘DSHJG JJH’,’02-SEP-108′,’03-SEP-2018′,’Australian’);
INSERT INTO VENUE VALUES (3, ‘GFUKH BVK’,’03-SEP-108′,’04-SEP-2018′,’Australian’);
INSERT INTO VENUE VALUES (4, ‘CHT BKJH’,’04-SEP-108′,’05-SEP-2018′,’Australian’);
INSERT INTO VENUE VALUES (5, ‘CHGF VK’,’05-SEP-108′,’06-SEP-2018′,’Australian’);
16. VEMUE_LIVE_MUSIC TABLE-
INSERT INTO VENUE_LIVE_MUSIC VALUES (1, 1);
INSERT INTO VENUE_LIVE_MUSIC VALUES (2, 2);
INSERT INTO VENUE_LIVE_MUSIC VALUES (3, 3);
INSERT INTO VENUE_LIVE_MUSIC VALUES (4, 1);
INSERT INTO VENUE_LIVE_MUSIC VALUES (5, 2);
17. VENUE_BOOKING TABLE——————
INSERT INTO VENUE_BOOKING VALUES (1, 1, 1, 1);
Enhanced Entity-Relationship (EERD)
INSERT INTO VENUE_BOOKING VALUES (2, 2, 2, 2);
INSERT INTO VENUE_BOOKING VALUES (3, 3, 3, 3);
INSERT INTO VENUE_BOOKING VALUES (4, 4, 4, 4);
INSERT INTO VENUE_BOOKING VALUES (5, 5, 5, 5);
- Count of all new students who have joined Kevin’s music after the 1st of July 2018.
SELECT COUNT (STUDENT.STUDENT_ID) AS “TOTAL NUMBER OF STUDENTS”
FROM STUDENT, STUDENT_CLASS
WHERE STUDENT.STUDENT_ID=STUDENT_CLASS.STUDENT_ID
AND STUDENT_CLASS.JOIN_DATE>’1-JULY-2018′;
- List of all underage male musicians and their age sorted by the first name.
SELECT MUSICIAN_ID, CONCAT (FIRSTNAME, LASTNAME)AS “NAME”,
TRUNC (months_between (sysdate, DOB) / 12) AS “Age”
FROM MUSICIAN_INFO
WHERE TRUNC (months_between (sysdate, DOB) / 12)<25
AND GENDER=’M’
ORDER BY FIRSTNAME;
iii. List of all teachers who have an expired working with Children Check (WWCC), with names, expiry date and their age, sorted by date.
SELECT CONCAT (MUSICIAN_INFO. FIRSTNAME, MUSICIAN_INFO.LASTNAME) AS “TEACHER NAME”,
TEACHER.EXPIRY_DATE, TRUNC (months_between(sysdate, MUSICIAN_INFO.DOB) / 12) AS “Age”
FROM MUSICIAN_INFO, TEACHER
WHERE MUSICIAN_INFO.MUSICIAN_ID=TEACHER.TEACHER_ID
AND TEACHER.EXPIRY_DATE<SYSDATE
ORDER BY TEACHER.EXPIRY_DATE;
- List of all current lesson bookings sorted by the style of music and the booking date (Most recent first). Hint: You may have to join various tables in SQL to achieve the desired output, lookup join command.
SELECT MUSIC.MUSIC_NAME AS “LESSON”, MUSIC.MUSIC_STYLE AS “STYLE OF MUSIC”,
BOOKING.BOOKING_DATE FROM BOOKING, MUSIC, STUDENT_BOOKING, TEACH_MUSIC
WHERE BOOKING.BOOKING_NO=STUDENT_BOOKING.BOOKING_NO
AND BOOKING.TEACH_MUSIC_NO=TEACH_MUSIC.TEACH_MUSIC_NO
AND MUSIC.MUSIC_NO=TEACH_MUSIC.TEACH_MUSIC_NO
ORDER BY BOOKING.BOOKING_DATE DESC;
- (Research required) a report on the students enrolled the style of music and the teacher for the current calendar month. Current calendar month refers to the month in which this SQL query is run.
SELECT STUDENT.STUDENT_ID, CONCAT (STUDENT.FIRSTNAME, STUDENT.LASTNAME) AS “STUDENT NAME” ,
MUSIC.MUSIC_STYLE AS “STYLE OF MUSIC”,
CONCAT (MUSICIAN_INFO.FIRSTNAME, MUSICIAN_INFO.LASTNAME) AS “TEACHER NAME”, CLASSES.START_DATETIME
FROM STUDENT, CLASSES, STUDENT_CLASS, TEACHER, MUSICIAN_INFO, MUSIC, TEACH_MUSIC
WHERE STUDENT.STUDENT_ID=STUDENT_CLASS.STUDENT_ID
AND TEACH_MUSIC.TEACH_MUSIC_NO=MUSIC.MUSIC_NO
AND CLASSES.TEACH_MUSIC_NO=TEACH_MUSIC.TEACH_MUSIC_NO
AND CLASSES.TEACHER_ID=TEACHER.TEACHER_ID
AND CLASSES.CLASS_NO=STUDENT_CLASS.CLASS_NO
AND MUSICIAN_INFO.MUSICIAN_ID=TEACHER.TEACHER_ID
AND EXTRACT (Month from CLASSES.START_DATETIME)=EXTRACT(month from sysdate);
After being alarmed by the recent security incidents reported in the media, Kevin decides to employ a part-time System Administrator to manage system security.
- a) Identify 6 security threats to the proposed system (Choose a mix of internal/external, deliberate/unintentional threats).
- Unmanaged sensitive data: –
All the data is warehoused organized without to some extent encryption. This penetrating data is stored in the same table without any encryption. It can be hacked or escaped to incorrect hands
- Weak audit: –
This database has no examining abilities aided. So any user can make any variations and no one will variation that what variation was prepared by whom?
- Denial of service : –
Denial of facility attack can be made on this database. Anyone can make a Denial of facility spasm on this database.
- Exposure of Backup Data :
All table data backups must be translated. As all the backups also have very sensitive material which can be changed, if it is conceded to any incorrect hands.
- Weak authentication:
Confirmation of the system commitment is strong. Today, the world is full of hackers. So, authenticity of the database is a major issue.
- SQL Injection:
SQL injection is a main criminal of most of the data harm that happens. Our database must be able to handle SQL injection. Anyone running a script that can cause SQL Injection must be obstructed.
- b) Classify each threat on a probability-impact matrix and explain your reasoning for the classification.
Thread |
Impact Out of 10 |
Probability Out of 10 |
Reason |
Unmanaged sensitive data |
5 |
5 |
Data stored without encryption |
Weak audit |
6 |
7 |
No audit in CRUD operations |
Denial of service |
2 |
4 |
Overloading for failing DB |
Exposure of Backup Data |
7 |
8 |
Backup not encrypted |
Weak authentication |
8 |
8 |
Authentication is poor and anyone can log in |
SQL Injection |
3 |
7 |
Sql injection to steal data |
- c) For each threat which of the risk controls would you recommend? Justify your choice. If you have opted for avoidance or mitigation of risk, clearly explain the policies, measures or strategies that need to be put in place to achieve the desired outcome.
- Unmanaged sensitive data: –
All the data is stored together without any encryption. The data must be correctly coded before storing it. Data which is very private to purchaser should not be kept together and should be stored unconnectedly in encrypted form.
- Weak audit: –
Assumption
Audit functionality must be added to the database. Whenever a creature make any alterations to the database like Insertion, Modernizing , Deletion etc. , proper checking must be done by using Activates etc. Proper data logs essential be there for all the alterations made to the database.
- Denial of service : –
Denial of service attack can be complete on this database. Proper guidelines must be made at the database admin end that blocks user forever/temporarily when any user tries to make DOS attack on the database.
- Exposure of Backup Data: –
All table data backups must be encrypted. Database backups are usually stored in many or separate locations to handle unusual circumstances like loss because of Natural or human calamities. These reserves also contain all the crucial data and can be used in evil ways if distorted.
- Weak authentication: –
Authentication of the system must be strong. Proper rules and rules must be made to certify that only an authentic user is using the structure and no other user can enter or corrupt the System.
- SQL Injection:
SQL injection is a major lawbreaker of most of the data loss that happens. Various dealings can be taken at mutually the system and application end to ensure that the database is not prone to SQL Injection. This can also be reached by the proper use of Procedures, triggers, views etc.
Alhir, S. (2003) Learning UML. Sebastopol, Calif.: O’Reilly.
Ambler, S. (2003) The elements of UML style. Cambridge: Cambridge U.P.
Ambler, S. (2005) The elements of UML 2.0 style. Cambridge [U.K.]: Cambridge University Press.
Awad, E. and Gotterer, M. (1992) Database management. Danvers, Mass.: Boyd & Fraser Pub. Co.
Belloc, H. (1967) On. Freeport, N.Y.: Books for Libraries Press.
Dennis, A., Wixom, B. and Tegarden, D. (2015) Systems Analysis and Design. New York: Wiley.
Fowler, M. (n.d.) UML distilled.
Harmon, P. and Sawyer (1999) UML for Visual Basic 6.0 Developers. San Francisco, Cal.: Morgan Kaufmann.
Holt, J. (2007) UML for systems engineering. London: The Institution of Electrical Engineers.
Kimmel, P. (2011) UML demystified. New York: McGraw Hill Professional.
Li, D. (1987) A PROLOG database system. Letchworth Herts.: Research Studies Press.
Mason, D. and Willcocks, L. (1994) Systems analysis, systems design. Henley-on-Thames: A. Waller.
Naiburg, E. and Maksimchuck, R. (2002) UML for database design. Boston: Addison-Wesley.
Obermair, W. (1995) Extending the object-oriented database management system VODAK with active capabilities. Sankt Augustin: GMD.
PATHAK, N. (2011) DATABASE MANAGEMENT SYSTEM. [S.l.]: HIMALAYA PUBLISHING HOUSE.
Ramarkrishnan, R. (1997) Database management system. London: McGraw-Hill Pub. Co. (ISE Editions).
Satzinger, J., Jackson, R. and Burd, S. (2016) Systems analysis and design in a changing world. Boston: Cengage Learning.
Siau, K. and Halpin, T. (2001) Unified modeling language. Hershey, Pa.: Idea Group Pub.
Silberschatz, A., Korth, H. and Sudarshan, S. (2009) Database system concepts. Boston: McGraw-Hill.
Weilkiens, T. and Oestereich, B. (n.d.) UML 2 Certification Guide.