March 2009
Beginner
160 pages
3h 15m
English
Content preview from Telling Stories: A Short Path to Writing Better Software RequirementsBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 6. Creating the Body of the Document
With your document well planned, and having conducted initial meetings with the product team and subject matter experts, you're now ready to assemble summaries, diagrams, and process descriptions into a compelling story. You will most likely create two compelling stories: the current state and the future state. I will also explore the importance of a few types of nonnarrative content like a gap analysis, data specification, and requirements summary.
The current and future states both have very similar, if not identical, structures. Both include an arrangement of elements, most of which I have already covered, similar to the following:
A short introduction to the main processes of the current state
A list of nonfunctional requirements and business rules
A high-level diagram that shows the entire work of the system and how it interacts with other systems (a context diagram)
One or more data flow diagrams (including summaries)
Process descriptions and requirements for all processes
Is Documenting the Current State Really Necessary?
Use a current state analysis when a manual business process is being automated for the first time, or when an existing system is being substantially changed. A thorough current state analysis captures what is being done, so that the future system will meet the same requirements. If you are working on a completely new process that is now not functioning at all, you may be able skip the current state and go straight to ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.