Development Process
- Started
- Last post
- 18 Responses
- kuttnhaste
Does any here have a good link to detailed steps involved in preperation and documentation needed before actually creating a website.
I'm talking needs analysis, requirements doc, specification etc...
Or does anyone know the general documents normally required?
- kuttnhaste0
awww:(
- ********0
I'm working on one myself just now....
Dunno if he's still around these parts or not but jpolk sent me a very good example of his a few months ago... see if you can find him...
- stem0
Go and talk to the client - ask them what they are trying to achieve?
The client is usually a good starting point!!!
- kuttnhaste0
The site is for me, and I'm using myself as a test case.
I Thought there would have been a standard process for creating sites... probably similar to software development. However I don't know the official steps one should take.
I know the overall picture but was hoping there was some formalised way.
- kuttnhaste0
Hey MX_OnD, could you send me what jpolk sent you?
- stem0
Not sure if there is a standard, I guess you've just got to go with your heart... and your pocket!!!
- kuttnhaste0
Ha. This is sad. No offence intended. But seriously you don't just meet the client, ask what they want and just do it adhoc.
You must have processes in place for gathering the needs, assessing requirements, gathering media, mapping the information architecture, developing interfaces, implementing interfaces, testing the system... etc.
If not then you're crazy!
- ********0
I think what the man is after is more a step by step of what to discuss with the client at which stage, no?
- kelpie0
I'm sure I saw somethiing like that on a big developer/designer forum somewhere - I'll have a look...
Sitepoint I think, something like that...
- ********0
You must have processes in place for gathering the needs, assessing requirements, gathering media, mapping the information architecture, developing interfaces, implementing interfaces, testing the system... etc.
If not then you're crazy!
kuttnhaste
(May 17 05, 05:44)Then call me crazy.
We show a few visuals - showing how the nav would work, and then once one is approved - we make it.
- kelpie0
not far from what we do either Moth - no time for lengthy processes...
http://www.sitepoint.com/
has some good stuff I think, check that out for help...
- stem0
Are these the same processes that NASA used when they designed Challenger!
More often than not a simple approach can get good results.
Problem with this approach is people sometimes find it hard to justify their effort.
If it's easy, see it as a blessing.
- kuttnhaste0
That's fair enough. Everyone has there own methods I guess.
It probably also depends on the scale of the project.
kelpie: I will check sitepoint.. they're a great resource.
MX_OnD: you're right, but i'm also looking at what documents you should be writing up after various meetings with the clients at different stages.
- blaw0
1) audience: who are you trying to reach? are there secondary audiences?
2) goals: what are you trying to do? what will happen that one year from now you look back and say, "this was a success (or failure)"?
everything that you do after that (design, content type, content delivery, limiting factors, etc.) should revolve around the answers to those first two questions.
- stem0
If I wanted a website I'd ask moth & kelpie - no bullshit
- kuttnhaste0
Yep sitepoint have exactly what I was after.
http://www.sitepoint.com/article…
And probably more useful information.
cheers kelpie.
adhoc is good when you don't want a site to last long. It's quick and efficient.
- kelpie0
If I wanted a website I'd ask moth & kelpie - no bullshit
stem
(May 17 05, 05:55)£80 per hour.
send me an e-mail ;)
- stem0
"adhoc is good when you don't want a site to last long. It's quick and efficient"
This is what the web is, isn't it. Keep changing and evolving?
Who's to say what's the thing tommorow?
kelpie - I said "If"