1st SIT EXAMINATION QUESTION PAPER: Year Long 2020

Module Code: CC6001NT

Module Title: Advance Database System Development

Module Leader: Mr. Rohit Panday

Date: 23 May 2021

Day / Evening: Day
Time: 09:00 AM – 09:00 PM
Duration: 12 Hours

Exam Type: Examination

Materials supplied: NA
Materials permitted: NA
Warning: Candidates are warned that plagiarism is a serious
assessment offence.

Instructions to Please Note: Inclusive of this cover page, this examination

candidates: paper consists of 5 pages.
This examination accounts for 40% of your total module
grades.
You are to submit the ANSWER with QUESTIONS to the RTE
Classroom within 12 Hours of Distribution.

DO NOT TURN PAGE OVER UNTIL INSTRUCTED

© London Metropolitan University

1
The seen examination components consist of a scenario where you are required to use
your own analysis and reasoning to find solution and answer.
Student is required to play roles of database designer and administrator to understand
the scenario and answer the questions that follow.
This document contains, two sections. First section gives students scenario description
to understand a case. Second section has questions which need to be answered based
on the case study.

SECTION ONE - SCENARIO

SchemaName: IssuesTracking
Problem Description:
You are required to design and implement database for Issues Tracking Software.
Software issue tracking is an integral part of any enterprise software development lifecycle. The
issue tracking toolkit is responsible to create, store, trace, and manage issues (e.g., software
bugs or requests for new features). Each issue is represented by a ticket that must capture the
following information
• the actual issue
• the components or projects effected by the issue
• developer/customers who first identified the issue
• the developers/managers who are responsible to address the issue
• the state of the issue
• other related issues (tickets)

Detailed Requirements:
Here we outline minimum requirements for an enterprise change management toolkit. You are
encouraged to modify, add, and (if clearly justifiable) remove requirements as you deem to be
necessary.
Ticket - possible attributes: owner, title, description, state (e.g., open, assessing, working,
testing, deferred, rejected, closed, etc.), priority (e.g., low, mid, high, urgent), planned
completion date, one or more related projects, one or more related tickets, category (task,
feature, question, defect, milestone), milestone status, submitter, submission date, escalation
person, blog entry (a ticket discussion forum), related resources, and related artifacts (e.g.,
diagrams and documents to help resolve the problems), work log (number of hours worked on
each day which could be different for each day and for each user)

2
Project - Possible attributes: title, description, planned completion date, actual completion date,
project manager, creator, creation date, work log (number of hours worked on each day which
could be different for each day and for each user)
User - Possible attributes: name, title (e.g., developer, manager, sysadmin), security (username
and password)
Artifact - Possible attributes: title, description, category, version, size, data
Comment - possible attributes: ticket, submitter, submitter date, text
-
Your role as a Student
The goal of this exercise is to provide a practical experience, as a database designer and
administrator. Prepare a script and document it. You may actually use tools like SQL Developer
in order to implement the database design. Use examples where ever appropriate.

SECTION TWO – QUESTIONS

All questions are compulsory. Answer all questions serially. Make sure, you indicate each
question and follow with answers. Use syntax and examples wherever necessary.
You are to derive your answers based on the scenario. The numbers at the end of questions
indicate full marks.
Questions:
1. Create User Schema (IssueTracking) and grant permission to all Objects. [5]
2. Create possible DB table in Oracle that should be represent the given scenarios. [10]
3. Define and explain the relationship among the tables [10]
4. Define the proper table structures (e.g., date column can be date field, Amount data filed
should be Numeric data field) [10]
5. Explain the DBs Object Security and System Security. Create DBReader and DBWriter
users, DBWriter user should get access on DDL and DML command execution,
DBReader user can access only read permission on all tables [4+4+2+6+4]
6. What is locking mechanism? Why is it necessary? Demonstrate the Shared Lock and
Exclusive lock situation in any one table [2+4+7+7]
7. What is the Deadlock and how do you manage deadlock in DB system? Create a
deadlock situation in ‘Ticket’ table. [5+10]
8. ABC Inc. business losses last week’s data due to system failure, the business Owner
doesn’t want to lose the anything for business. Normally, DBA takes daily backup on
End of Day. You are the DBA of ABC Inc.; How do you manage data of that week and
what would be the best way forward? [10]

END OF EXAMINATION.