By the way you are describing this project of yours, it seems to be a "one time thing" and your advisor is suggesting an iterative and incremental approach by using Scrum, but didn't explain what Scrum is. I also have the feeling that they don't themselves know how Scrum works. I suggest you read the Scrum Guide to figure out what Scrum is all about.
The idea is to have a functional piece of software at the end of each sprint. Be it completely implemented or just partially implemented but enough to learn, gather feedback and figure out what is needed next. It seems you already planed out how you will do your work and now you are just trying to fit it in two sprints. Your approach is incorrect. Not to mention that the structures of your sprints are wrong (each sprint has a sprint goal, a sprint planning, a review, and a retrospective; you can't spread these activities like you did in your example, over multiple sprints).
You should think about what's the minimum functional thing you can get working into the first sprint (or even first few days of the sprint), then think what else to add to that, and then repeat until you have implemented the full feature or something you are satisfied with, or anything that can be reviewed at the end of the sprint.
Each Sprint end is an opportunity to inspect and adapt. And you do so by looking at working software, not class diagrams, use case diagrams, building an API in one sprint and the UI in another.
One other thing (which goes back to your advisor possibly not understanding Scrum) is that this seems to be a solo project. Scrum is not the best choice for a one man team. You can still use the incremental and iterative approaches by applying the principles themselves, but without the overhead of the Scrum framework.
