Menu
Community /Pin to ProfileBookmark
@NogDogJul 07.2010 — #Well, I'm not going to provide you with a "thorough" answer, as that's what systems analysts get paid for. ?
The only general rule I pretty much stick to is getting a good start on the database design before I start writing any application code. However, sometimes I also start the front end work early on, as getting the screens in the customer's hands -- even though they don't [i]do[/i] anything yet -- can often help both to find missing requirements and to clarify existing requirements ("That's not what I meant!").
Anyway, if you really want to dig into the process, there are plenty of good books out there. One interesting one is [i]Head First Object-Oriented Analysis and Design [/i] (not suitable though if you are not reasonably proficient with OOP in PHP).
First frontend or backend implementation?
Hi,
For most of you web developing guru’s my question will sound stupid, but as newbie I would like to ask if it is ok that I will have a frontend developed and only after Backend?
Also, if I will need database should I have the design of it first?
I also would like to know about the analysis part of the project. A friend in short informed me that to start the project requirements analysis (internal, technical and design) is a must. Let’s say if I want to build a social e-commerce site with ability for users to register. Can you determine a numbered list what would you do to prepare the analysis for such project (etc. 1. Database design a) prepare data models…)
I would be very happy if somebody could provide with a thorough answer.
Thank you.
Regards,
Donny
Sign in
to post a comment2 Comments(s) ↴
0
@NogDogJul 07.2010 — #Well, I'm not going to provide you with a "thorough" answer, as that's what systems analysts get paid for. ?The only general rule I pretty much stick to is getting a good start on the database design before I start writing any application code. However, sometimes I also start the front end work early on, as getting the screens in the customer's hands -- even though they don't [i]do[/i] anything yet -- can often help both to find missing requirements and to clarify existing requirements ("That's not what I meant!").
Anyway, if you really want to dig into the process, there are plenty of good books out there. One interesting one is [i]