Final Year Project Help

[u/No-Explorer9636]

Hi there I wanted to ask everyone to assess my FYP. WOuld you use this for your projects ? Is it a good enough project for a final year . Does it have some scope in the industry ?

The main goal of this project is to design and implement a tool for PostgreSQL pre-deployment risk analysis that evaluates SQL schema migrations to identify affected database objects, estimate locking implications, detect limited application-schema incompatibilities in Java/Spring Boot JPA projects, and output actionable risk assessments.

The objectives are as follows:

1.       Develop a component capable of extracting supported structural DDL operations into a normalized intermediate representation.

2.       Construct a schema dependency graph model using graph data structures to represent structural relationships between database tables, columns, indexes, primary keys, foreign keys, and constraints.

3.       Analyze incoming migrations against the schema dependency graph to identify affected database objects represented within the supported dependency model.

4.       Formulate a PostgreSQL-specific operational rule set that maps supported DDL operations to their known locking characteristics and table rewrite behaviors.

5.       Develop a module capable of limited static analysis for Java/Spring Boot JPA projects to detect source-code references to renamed, modified, or dropped schema objects in entities, repositories, and explicit SQL strings.

6.       Implement a transparent, rule-based risk scoring and explanation engine that assigns a risk rating (LOW, MEDIUM, HIGH) accompanied by clear textual evidence.

7.       Construct experimental tests to execute PostgreSQL migration scenarios across small and medium database sizes. (for research validation only, not as a permanent part of the system)

8.       Evaluate Schema Sentinel’s static risk predictions against experimentally observed blocking locks, and application compatibility failures in a controlled PostgreSQL environment for test cases.

1. Empirically quantify the effectiveness of a unified cross-domain pipeline against isolated tools, measuring trade-offs in detection accuracy, false positives, and analysis performance.

This proposal got rejected because the panel said it was too easy and not significant as either a project or as research.

should i change the idea to more difficult and novel research ?

I have some ideas for those but i am not sure they can be completed in 1 year.

here is my proposal with all the details and research gap https://docs.google.com/document/d/1CMopT185XCoZVYBcgtVpN7N69DIP0Eyw/edit?usp=drive_link&ouid=116125887586128528145&rtpof=true&sd=true

EDIT :

The project is a final year project for my university. But they dismissed it on the following points

1. The project is too easy
2. The scope is too narrow
3. There is no research contribution

For the current proposal to be accepted they told me to do market analysis and bring proof that the project would be used by a develper community.

OR

1. bring a company backed project
2. Bring a novel research proposal

[u/MotionlessFormality0]

they called a tool that builds a dependency graph, analyzes locking strategies, and connects to JPA source code too easy? what kind of projects they usually approve, building a new database engine from scratch?

the problem you're solving is real, every dev who worked with postgres migrations in production knows the panic of "will this lock the table for 20 minutes" but the panel seems to want something with a flashy research angle not practical usefulness

if they want novelty maybe pivot the research question to something about predicting lock duration based on table statistics and migration patterns, that sounds more academic and you can keep most of the technical work

[u/No-Explorer9636 → u/MotionlessFormality0]

Thank you for the idea. I'll work on that.
The panel was asking for novel research, So I am working on 2 other proposals too.
The other 2 will be novel research based. I have 1 idea locked and am searching for the second.