There is another way of looking at this which I think it's really effective. Don't guide your approach by user requirements because customers don't know what are their own requirements. Even we, think we do but many times, we don't. Guide your approach by something concrete based on rapid prototyping.
1) think of the layout (as a prototype). Not so much the details such as colours and font sizes but put into a "wireframe" what is the end result you want to achieve, in a very visual and quick manner. This forces you to implicitly define user requirements, use cases sequences user access roles and, of course, the layout itself. (it's also a good time to make assertions that can be used for tests) 2) Now you also now which type of data needs to be displayed and where but without a database schema, it may be hard to work on the controllers so it's a good time to model your database, if necessary of course. 3) Now you need to do the wiring from 1) and 2) and work on both the controllers and views. 4) Test it! kind regards, Francisco On Friday, 23 January 2015 23:56:05 UTC, 黄祥 wrote: > > i think : > 1. ask more detail about user requirement > 2. analysis and design database to match with user requirement > 3. analysis and design system flow to match with user requirement > 4. design the web layout > 5. testing the system flow, system security and web layout > > best regards, > stifan > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
