Why, oh why?

I saw a post at LifeHacker that strucked me: "Hey, that's exactly why we use goal models", rather than use cases or anything else.

The post in question was about ToDo lists: "If You Want to Actually Finish the Tasks on Your To-Do List, Include Why You Should Do Them". When we know the goal, we can prioritize the tasks, think through alternatives, select what is more valuable to us, etc. Quite reasonable, right? That's pretty much why goal modeling is a good option for requirements modeling.

There are two more known goal modeling notations¹: i* (reads iStar) and KAOS. Both have been the target of invaluable research, even though they are not widely used in industry (yet?). More on then later.

¹ they are more than just notations, actually.