Book Image

Building Applications with Spring 5 and Vue.js 2

By : James J. Ye
Book Image

Building Applications with Spring 5 and Vue.js 2

By: James J. Ye

Overview of this book

Building Applications with Spring 5 and Vue.js 2, with its practical approach, helps you become a full-stack web developer. As well as knowing how to write frontend and backend code, a developer has to tackle all problems encountered in the application development life cycle – starting from the simple idea of an application, to the UI and technical designs, and all the way to implementation, testing, production deployment, and monitoring. With the help of this book, you'll get to grips with Spring 5 and Vue.js 2 as you learn how to develop a web application. From the initial structuring to full deployment, you’ll be guided at every step of developing a web application from scratch with Vue.js 2 and Spring 5. You’ll learn how to create different components of your application as you progress through each chapter, followed by exploring different tools in these frameworks to expedite your development cycle. By the end of this book, you’ll have gained a complete understanding of the key design patterns and best practices that underpin professional full-stack web development.
Table of Contents (23 chapters)
Title Page
Copyright and Credits
Dedication
About Packt
Contributors
Preface
Index

Logical data modeling


Now, let's create the logical data models of TaskAgile. In this stage, we will add attributes to each type of entity in the conceptual data model by going through user stories by theme and implementing the relationships between entities, as well as the subtypes we used.

Based on Users theme and Teams theme, we create the following logical data models:

Figure 5.20: Logical data model of User and Team entities

As you can see in Figure 5.20, for User entities, we use surrogate key ID as its primary key because even though Email Address and Username can be used to identify a user, they can be changed. The system-generated ID will always stay the same. It is the same for Team entities. And the User ID attribute in the Team Creator entities is a foreign key. In the diagram, PK is short for Primary Key, and FK is short for Foreign Key. And, in Team Creator entities, the Team ID and User ID attributes form a composite key that can be used to uniquely identify a Team Creator.

Based...