Refactoring Databases P2.5: Scoping the Cheats

One of the side-effects of the little cheat posted here is that, if we are going to design early we have to decide what we will design early… and this question has two complications. First, we have to ask ourselves how detailed do we design before the result becomes un-agile? Next, we have to ask ourselves if we should design up the stack a little? My opinions will be doggedly blogged in this post.

I will offer two ends of a spectrum to suggest a way to manage the scope of your advance design cheat. Let me remind you that the cheat suggests that you look at the user stories that will be sprinted on next and devise the schema required from those stories… and maybe refactor the existing schema a little (more in the next post) no more than that.

On one side we may develop a complete design with every detail specified: subject areas, tables, columns, data types, and domains. The advantage here is that the code developers have a spec to code to and these could increase velocity. But the down side is that developers will be working with users to adjust the code in real-time. If the schema does not fit the adjustments then you may be refactoring the new stuff and velocity may decrease.

The other side of the spectrum would have database designers just build a skeleton; a conceptual schema with subject areas, tables and primary keys for each table. This provides a framework that corrals the developers without fencing them in so tight that they cannot express agility.

Remember that the object here is to reduce refactoring without reducing agility…

IMO the conceptual model approach is best. Let’s raise free range software engineers who can eat bugs in the wild rather than be penned in. The conceptual model delimits the range… a detailed schema defines a pen.

There is one more closely related topic for the next post… how do we manage transient objects in a restful application?

One thought on “Refactoring Databases P2.5: Scoping the Cheats

  1. Looks like the snow and the day off from the government is giving you a chance to catch up on blog writing :-). Hope you made it through the blizzard ok.

    All the best!

    Manav.

    From: Database Fog Blog <comment-reply@wordpress.com>
    Reply-To: Database Fog Blog <comment+e60qlbsgju7y0p4czfxvwe1@comment.wordpress.com>
    Date: Monday, January 25, 2016 at 8:47 AM
    To: Manav Misra <manavendra.misra@cognilytics.com>
    Subject: [New post] Refactoring Databases P2.5: Scoping the Cheats

    Rob Klopp posted: “One of the side-effects of the little cheat posted here is that, if we are going to design early we have to decide what we will design early… and this question has two complications. First, we have to ask ourselves how detailed do we design before the r”

    Like

Comments are closed.