background preloader

Software Design

Facebook Twitter

Introduction to User Stories. 1.

Introduction to User Stories

Introduction to User Stories A good way to think about a user story is that it is a reminder to have a conversation with your customer (in XP, project stakeholders are called customers), which is another way to say it's a reminder to do some just-in-time analysis. In short, user stories are very slim and high-level requirements artifacts. 2. Initial User Stories (Informal) Software architecture document guidelines. Please see the Software Architecture for Developers book for the most up to date version of these guidelines.

Software architecture document guidelines

The purpose of the software architecture document (SAD) is to provide information that is complementary to the code. At a high level, this might include: The code doesn't tell the whole story. We all know that writing good code is important and refactoring forces us to think about making methods smaller, more reusable and self-documenting.

The code doesn't tell the whole story

Some people say that comments are bad and that self-commenting code is what we should strive for. And I don't disagree.