Wiley Telling Stories: A Short Path to Writing Better Software Requirements 978-0-470-43700-1 ユーザーズマニュアル

Telling Stories 

Having discussed these general ideas about requirements and stories, I’ll 

thoroughly describe specific skills and tools, beginning with three skills that 
may be new to you:

Write clear and precise words, sentences, and paragraphs that specify 

•

testable requirements.
Create data flow diagrams simple enough for anyone to follow, but suf‑

•

ficiently rigorous and precise to be useful to engineers. 
Explain processes systematically to capture all the vital information 

•

and requirements. 
Associate requirements with processes. Write requirements using precise 

•

terms and with a measurable outcome. 
Create a system inventory that includes every element of the system: 

•

every known process, actor, output, report, category of data, and any‑
thing that the team thinks is important about the system.
Break down the system into a series of events or processes so that they 

•

form a linear story of what happens at every step. 
Structure this information in a logical sequence, including an executive 

•

summary, the current state, future state, data descriptions, and various 
summary sections and optional appendixes for handling specialized 
material specific to certain projects.
Maintain and reuse requirements content when writing test plans, user 

•

documentation, functional specifications, and other materials. 

The rest of this book covers this advice in considerably more detail. The 

next chapter starts where the story begins, with clear and precise words, 
sentences, and paragraphs.

37001c01.indd   19

1/29/09   10:50:42 PM