Chapter 20. Requirements Analysis
I've always found that programmers in the open source world, especially when immersed in PHP, benefit from hands on teaching. While I would love to visit each reader's house, crack open some drinks, and program PHP, that's not really feasible. Instead, I'm going to further the analysis of PHP Design Patterns with a case study.
This particular case study will be broken up into several parts as the book introduction says. First, in this chapter, I'll examine the requirements. I'll try to rule out any assumptions and ask any other questions I can of the stakeholders of this case study. Chapter 21 will be the analysis of the features compared to what Design Patterns that were detailed in the reference chapters. The final chapters (Chapter 22 and 23) will cover the code creation, using the Design Patterns and Unified Modeling Language (UML) diagrams that I developed.
Completing this book with a case study is very important. In addition to providing a sort of "hands-on" training tool, there are three other important things that I hope you gather:
First, it is important to follow along in a requirements analysis. There is a careful balance to maintain between flying by the seat of your pants and analyzing a project to death. I aim to show where the balance should fall with this analysis.
The second thing to observe is the pre-programming analysis. Back in the book's introduction, I mentioned my distaste for those who jump right into programming using ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access