Feedback
The Enterprise PHP book contains my recommendations for a PHP development life-cycle. But my view is certainly not the only view. If you have opposing views, recommendations, additions, please let me know by posting a comment to this post.
Also, any general comments and criticism on the book are very welcome. Feel free to post your comments below.
If you rather send me private feedback, please send an email to ivo at jansch dot nl.
Entries (RSS)
April 4th, 2009 at 2:30 pm
Hello,
I am a student currently studying applied informatics and after reading your book am i left with a question: In chapter 4 you are talking about requirements gathering where you first define the business goals and afterwards sum up the possible functional requirements and non-functional requirements.
After googling functional requirements did i found a few articles talking about business requirements, functional requirements and system requirements. This is probably the same thing.
Well for my question how is this methodology called? I have read books about analysis & design but requirements gathering only starts after you have already a feature list, use case diagrams and already broke the problem up into modules where each module has its own requirements.
Your approach is much more simpler and easier to manage therefore am i really interested in the name of this methodology to perform some more research on the topic.
P.S. any tips are greatly appreciated
Best regards,
ignace