god-object

I have been writing a PHP class that is exactly 450 lines long and it contains 14 static methods and 4 static properties as well as 6 constants (and private __construct() and __clone() ). I am wondering here is that am I doing something wrong, is my class evil? When you use the class, you always call a single method like: MyClass::coolMethod(); and then you leave it alone altogether so it feels that it would be stupid to make it constructable? There's really not much point in constructing objects out of it, because it is more like a tool that contains a few methods that you can just call

Does anyone know the best way to refactor a God-object? Its not as simple as breaking it into a number of smaller classes, because there is a high method coupling. If I pull out one method, i usually end up pulling every other method out. It's like Jenga. You will need patience and a steady hand, otherwise you have to recreate everything from scratch. Which is not bad, per se - sometimes one needs to throw away code. Other advice: Think before pulling out methods: on what data does this method operate? What responsibility does it have? Try to maintain the interface of the god class at first

I've been reading a lot of blogs which advocate the fat models and skinny controllers approach, esp. the Rails camp. As a result the routers is basically just figuring out what method to call on what controller and all the controller method does is call the corresponding method on the model and then bring up the view. So I've two concerns here which I don't understand: The controller and router are really not doing much different tasks other than just calling a method on the God-like model based on the route. Models are doing too much. Sending emails, creating relationships, deleting and