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

Managing requirements in an Agile way


In waterfall projects, business analysts write comprehensive requirement documents and then hand them over to developers and testers. Developers will create the application according to all of the details specified in the document, and testers use these documents to create test cases. Once the code is complete and integration is done, testers will do quality assurance and developers will fix bugs before the customer performs the acceptance test.

Since the required documents need to include all of the details, it usually takes months for requirement development. And if the schedule is tight, requirements might not be accurate, or worse, not documented. Or later during the implementation, customers might change their mind and some features may have to be discarded even though they have already been built.

There are many other kinds of risks and frustrations associated with a waterfall project because of the way of managing requirements.

Teams that adopt an...