Rails source code architecture

[Matthieu Foucault]

Hello, I am a software engineering PhD student. I am currently performing and empirical study in which I am studing software metrics on the Rails project. I am analyzing the code of Rails 2.3 for this study.

I need your help because for this study I need to split the source code in several modules, considering that a module is a file, a set of files, a directory or a set of directories containing a standalone piece of code that provides specific and tightly coupled functionalities.

Given this definition and the architecture of Rails 2.3, what would be the modules for you?

The source code tree of Rails 2.3 is described here: https://gist.github.com/matthieu-foucault/0bf58ab46e2011a10841

[fitrah firdaus]

Why You Use Version 2.3 not 4.1, 2.3 is obsolete, 4.1 is newer.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/af2c5b13-b445-432c-b0f6-7bb7feae8eb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matt Jones]

You may want to do some research on the 2.3 -> 3.0 transition and the merge with Merb; the explicit motivation for that process was to split the code into better-separated modules. 2.3 was *not* straightforward to divvy up in that fashion.

--Matt Jones