Understanding Problem Domain


There is a blog post that is corollary to Rule 10 of my 12-Rule App Manifesto:

  • You can’t ship what you don’t understand
  • Before you come up with a solution, figure out your problem
  • The solution should match your problem’s size.
  • Break it all down
  • Review often

I can’t say enough how important understanding the problem domain first. The solution space is a design endeavor. The problem domain is the domain of analysis.

Coming up with a solution with bare understanding of the problem is like putting a cart before the horse.


Subjectivity aside, leave a reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s