Convention on model names in ruby on rails

I was doing my ER diagram for a rails application I’m about to begin with and there I have an entity called Class News so I’d have a model ClassNew but I don’t know if I will have problems in the future with the New part or what would be the right way to do this o how should I call the model? since the right thing would be ClassNews and the table should be class_news…

Are factors such as Intellisense support and strong typing enough to justify the use of an ‘Anaemic Domain Model’?

It’s easy to accept that objects should be used in all layers except a layer nominated as a data layer. However, it’s just as easy to end-up with an ‘anaemic domain model’ that is just an object representation of data with no real functionality ( http://martinfowler.com/bliki/AnemicDomainModel.html ).

MVC two models required?

I’ve been doing software for a long time, but almost all of it has been back-end centric.

Achieving decoupling in Model classes

I am trying to test-drive (or at least write unit tests) my Model classes but I noticed that my classes end up being too coupled. Since I can’t break this coupling, writing unit tests is becoming harder and harder.

How should I architect my Model and Data Access layer objects in my website?

I’ve been tasked with designing Data layer for a website at work, and I am very interested in architecture of code for the best flexibility, maintainability and readability.

How to create view models – Constructor, Factory Method, …?

I’m trying to lead a charge for re factoring our rather bloated controllers.
We currently have a BaseModel from which all our other models inherit. The BaseModel contains things common to all pages, such as the page title, css files needed, current user.

Is it ‘safe’ to expect myClasses to agree not to only call package Scope methods from other Package scope methods?

The questions says it all, but a quick overview of the situation. I’m creating a Model which contains classes (all inherriting myObject) which have a large amount of interconnection. I want the controller to be able to create any of these objects any time, without modifying the Model. Only an explicit cal to the model to “AddToModel” would ‘install’ the object into the model (including updating all the connected objects). myObjects will use a factory pattern, if a user tries to create something already represented in the Model the already-instanced object in the model will be returned instead of constructing a new one.

Is there an industry standard for systems registered user permissions in terms of database model?

I developed many applications with registered user access for my enterprise clients. In many years I have changed my way of doing it, specially because I used many programming languages and database types along time.

Getting related foreign keys from parent entities

I’m thinking about a design issue which affects my project’s data base. Supposing there are three diferent tables:

Breaking Up A Model Class – MVC

I am not sure whether there is a ‘right’ or ‘wrong’ answer to this one, but I was curious about the general consensus.