Option 2: SQL Code AnalysisDashboard

Background

Organisations rely on the data they collect and store for the success of their business. A database can quickly become a bottleneck in a software system. Good SQL practises take years to develop. The repercussions from misaligned incremental changes can be severe and painful to turn around.

An SQL code analysis tool can be very useful at preventing many of the different problems encountered across relational databases. It can also be useful to speed up the regular development process.

Summary

Research and design an SQL code analysis dashboard that can be leveraged against existing schemas and consider the volume expected in production data. Analyse the different facets the tool can be applied to.

You must determine clear requirements for this system and write them up together with any decisions and assumptions youre making. Some Q&A sessions will be arranged with Redgate to allow you to research the requirements.

You must also design the system in pseudo code and use trace tables to test your design.

Objective

This task should encourage critical thinking, attention to detail and question asking. Its ok to make assumptions but highlighting the risk with each one. Wed like the students to understand that there is more to software development than coding.

Deliverables

A product artifact, which could be a prototype application or wireframes. The artefact must demonstrate the user interactions with the system and highlight the unique features of your idea.

There is no expectation or merit to be gained by implementing your own code analyser. There is also no expectation to integrate with commodity static code analysers. The prototype should use fake data or hardcoded responses; however, you may wish to consider how your code could be adapted to use a third-party API.

Your artifact must demonstrate:

• Youve identified a solution to the underlying
• Youve considered the balance of functionality, deliverability, and
• Youve thought about potential issues the brief didnt

Requirements

• The prototype must provide an overview of the health of the SQL code across the database
• The prototype must present a list of code analysis issues to the
• The prototype must show how issues details of issues are
• The prototype must show how issues could be fixed
• The prototype should include screens to show how changes are applied to the database
• You may wish to consider how this could plug into a CI/CD

Based on the project chosen for element 010 which is provided by RedGate and the report submitted by your team you are required to produce a Java-based application following OOP principles to implement your design. You are not expected to produce a GUI application for this assignment and all interaction should be accomplished through the console.

Your Java project should meet the following minimum requirements.

• Contain a header comment at the top of the application class including your SID number and which team you were in for element 010 of the assignment.
• Contain at least two classes that are implemented in the project in addition to the application class.
• Contain a range of class attributes within all implemented classes (for example int, list, String, Boolean etc).
• Contain at least four implemented methods across all classes.
• Include a range of code statements within the main() method of the application class to illustrate the use of all implemented classes as well as their methods and attributes.
• Names of classes, methods and attributes should be taken from the work produced for element 010 of the assignment and must follow the best-coding practices Links to an external site..
• If you find it necessary to deviate from the plan set out in your submission for element 010 then you should briefly explain the reasons for any changes made in the comments of your code.

The quality of your code matters and has a significant impact on your final mark. You should use best coding practices (information will be provided in lectures and tutorials) and you should include sufficient comments in your code to establish the relationship to your initial planning document (element 010) as well as your understanding of the code.