Modeling Products and Projects

I think many PM tools suffer from the problem of conflating multiple domain models, most likely in the attempt to shoehorm them into the same tool The simple PM tools I talked about (and reviewed previously) suffer from the additional problem oversimplifying, and provide inadequate domain elements to really model the process. I've come up … Continue reading Modeling Products and Projects

Advertisement

Thinking about development and related processes

In my mind, product development is broken down into three stages:  design, development, and deployment.  Project management and quality assurance are supplementary activities.  Project management manages scheduling, budget, resources (people and things) and tasks.  Quality Assurance is  responsible for testing, process, and requirements management.  In general, PM interfaces with "Business", and QA is concerned about … Continue reading Thinking about development and related processes

Model Hierarchies

Hierarchy complexity Hierarchies should be 4-7 levels deep. Three or less is not really a model.  Ten or more is too complex. Two levels is really just a tuple.  Three levels is is just grouping of tuples, which doesn't really require modeling.  Of course there are exceptions. Artificial Hierarchies You often see models (especially in … Continue reading Model Hierarchies

Guidelines for domain modeling

I think two common mistakes are made in modeling data & processes that can lead to unintended complexity.  The first is conflating two models that should be separate, and the second is oversimplifying models.Conflated model: when what should be two separate models are intermingled, resulting in confusing (forced) associations.  If you have two elements in … Continue reading Guidelines for domain modeling

Thinking about PM tools

I've been thinking about Project Management tools a lot lately. One step I took was to try out a bunch of the new breed of lightweight tools:  Basecamp, GoPlan, ActiveCollab, ProjectPier, Wrike, etc.  I wasn't really satisfied with any of them.  While lightweight tools are a breath of fresh air for those coming process heavy … Continue reading Thinking about PM tools

¿Viva Fidel?

I've interrupted my musings to bring you a celebration of Capitalism that is both timely and topical... ¿Viva Fidel? Is he alive? That's the question. And has been for the past 6 months or so. But today, there's evidence he might be, or might not be. Being startled from my reverie of hacking Typo3 to … Continue reading ¿Viva Fidel?

The mass of flames that didn’t come

I was expecting quite a few reponses to my rant the other day, and maybe even a few comments of my framework requirements, but it looks like nobody reads my blog, after all. Boo-hoo. I mean thank goodness. I can once again feel safe in my shell and make stupid sweeping generalizations with impunity. But … Continue reading The mass of flames that didn’t come

Leveraging existing knowledge and techniques — ideal framework requirement #3

Too many framework developers decide they're going to be too clever by half. As a result, writing plugins, extensions, modules, templates, models, views, controllers, classes, procedures, whatever you call them is always a unique experience. My rant about ORM (and templating) tools was one part of this. Writing records to a database is not rocket … Continue reading Leveraging existing knowledge and techniques — ideal framework requirement #3

Being obvious about what it’s doing – requirement #2 of the ideal framework

"What you don't know can't hurt you" -- but it can't help you either. Like many others, I suppose, I fell in love with Rails because it "Gets out of your way" so well.  At least at first. Thanks especially to Ruby's dynamic method modification and anonymous blocks, Rails hides a lot of the details … Continue reading Being obvious about what it’s doing – requirement #2 of the ideal framework

Getting out of the way – requirement #1 of the ideal framework

The framework that manages best, manages least"  or something like that. Even in the original it didn't necessarily mean the least amount of government, but that because of the structure, less intervention was required. This doesn't directly boil down to simplicity,  but simplicity is the easiest way to reduce management overhead.  That's why things like … Continue reading Getting out of the way – requirement #1 of the ideal framework