Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Software Architecture with Java

You're reading from   Hands-On Software Architecture with Java Learn key architectural techniques and strategies to design efficient and elegant Java applications

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781800207301
Length 510 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Giuseppe Bonocore Giuseppe Bonocore
Author Profile Icon Giuseppe Bonocore
Giuseppe Bonocore
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Section 1: Fundamentals of Software Architectures
2. Chapter 1: Designing Software Architectures in Java – Methods and Styles FREE CHAPTER 3. Chapter 2: Software Requirements – Collecting, Documenting, Managing 4. Chapter 3: Common Architecture Design Techniques 5. Chapter 4: Best Practices for Design and Development 6. Chapter 5: Exploring the Most Common Development Models 7. Section 2: Software Architecture Patterns
8. Chapter 6: Exploring Essential Java Architectural Patterns 9. Chapter 7: Exploring Middleware and Frameworks 10. Chapter 8: Designing Application Integration and Business Automation 11. Chapter 9: Designing Cloud-Native Architectures 12. Chapter 10: Implementing User Interaction 13. Chapter 11: Dealing with Data 14. Section 3: Architectural Context
15. Chapter 12: Cross-Cutting Concerns 16. Chapter 13: Exploring the Software Life Cycle 17. Chapter 14: Monitoring and Tracing Techniques 18. Chapter 15: What's New in Java? 19. Other Books You May Enjoy

Chapter 2: Software Requirements – Collecting, Documenting, Managing

Collecting requirements is arguably one of the most frustrating activities in software production for several reasons. Difficulties often arise because it is never completely clear who the owner is, as well as because architects cannot do a good design without certain requisites, and developers, of course, can't do a proper job without the designs.

However, it is fairly common practice for a development team to start doing something without a complete requirements collection job because there is no time. Indeed, what often happens, especially in regards to large and complex projects, is that the milestones are put in place before the project scope is completely defined. In this industry, since software is an intangible product (not like a building or a bridge), budget approval is usually a more fluid process. Therefore, it's not unusual to have a project approved before all the details (including...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime