These are my rapid development strategies.
Works well for simple sites where the page layout is very important.
- Build the HTML/CSS framework of the screen
- Create navigation and page stubs
- Set up help, about, terms/privacy stubs
- Create a login screen (if necessary), that does nothing, and a logout. This helps to establish the logic flow.
- Build a home page
- Build pages out in a logical order (it will vary), again, front2back - start with the way it looks on the screen, then build the server side logic.
Works well when the complexity and risk are related to server-side logic and interfaces, or when there is a designer and developer on the project.
- Get the documentation, find the resources for the difficult parts
- Choose the simplest task, for example, submitting access credentials, and get it working.
- Define an object-oriented architecture and one class to support the requirements.
- Get the OO code interface working
- Break the OO code into two layers (if necessary), one a general interface, the other specific to the class.
- Clone the OO code for the remaining data types
- Create the view for one class, then use the same approach as before to define the display architecture. Strive to use only very basic HTML, so the design can be managed efficiently with CSS.
- Refine the interfaces to make integration easy.