StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<ul> <li>You start with a mission statement: what purpose does your application serve?</li> <li>Then you create the business analys: what tasks must a user be able to perform? What does he want to achieve?</li> <li>Then you create the functional design: what does the user want to do with your application? What functions does your application offer? How does the user perform his tasks? What steps does he go through.</li> <li>Only then you start thinking technical: what technologies do we use? What application stack (UI, data, ...)</li> </ul> <p>Now, <strong>don't view this as a waterfall model</strong>, where each step is only done once and never revisited. Your process should be <strong>highly iterative</strong>: when you discover in fase 3 that something in fase 2 is missing, go back to fase 2 and add it. Then either edit or restart fase 3.</p> <p>So now you have all specifications, and you're ready to start implementing. You might want to consider going over the specifications with the client (maybe using a prototype?) before starting, because changing the specs is cheaper than changing the application afterwards. Anyway, when you decide you are ready with the implementing, it doesn't matter so much where you start.</p> <p>Your technical specification will have listed the API's of the supporting classes, and the classes that use these supporters. You can start designing the API's, or, if you prefer Test-Driven-Development, you start writing tests first and make sure your supporting objects pass all tests.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload