pankaj wrote:
> Following are the steps I do before starting to code a Rails project.
>
> 1.) Identify the resources : like user, article, comments etc.
> 2.) Identify the tables and their fields with data types.
> 3.) Identify the models and their relationships.
> 4.) Identify controllers and actions in them, and corresponding views.
> 5.) List of plugins to use.
> 6.) Identify methods in models their inputs and outputs(most of this
> is done at run time.)
Ack!!! Like Robert, you seem to work in reverse from what I attempt...
1. Who are the stakeholders and what are the desired outputs? (what
delivers the value for the system?)
2. What are the perceived entities/models and their relationships?
3. Scaffold a proof of concept with basic functionality.
4. Present the scaffolded app for conceptual review/commentary/usability
comments ('parking lot' UI quibbles in the first round or two for an
'area' of the app). See what a concrete example provokes from the
stakeholders - are the models the right ones, what additional
information is desired, what outputs, are there additional unforseen
stakeholders, etc, etc?
5. Iterate at step 1.
Iterations (generally weekly) are a mix of presenting new scaffolded
items and refining previous items.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
