Beyond requirements

427 views

Published on

I wrote this conference paper and created the associated presentation for a technical writing class. The paper explains my experienced observation that requirements analysts often must do more analysis of existing business processes and data models than actual requirements documentation.

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
427
On SlideShare
0
From Embeds
0
Number of Embeds
17
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Beyond requirements

  1. 1. When documenting software requirements is not enoughBEYOND REQUIREMENTS
  2. 2. As an analyst, have you ever Been treated as just a note-taker? Been ignored? Felt vaguely guilty? (Author unknown, n.d.)
  3. 3. Tale of two projectsProject A Project B4 months of analysis 4 months of analysis329 requirements 4 requirements
  4. 4. Types of projects vs. analyst tasks Project A Project B100% 90% 80% 70% 60% 50% 40% Understand "as is" 30% Identify "to be" 20% 10% 0% All New Automate Modify Replace Existing Legacy Systems Process System
  5. 5. Why identifying requirementsis not enough System or process? Unanticipated impact Change strategy
  6. 6. Why it’s hard to understandthe “as is” Missing experts Busy experts Myopic experts Resistant experts
  7. 7. But… I’m not asked Ask permission to do this I’m not given Explain why it time to do this matters. Do at least a little This is someone Learn from else’s responsibility their analysis
  8. 8. You can help
  9. 9. ReferencesAuthor unknown. (n.d.). Tree swing cartoon. Retrieved July 3, 2011 from http://www.businessballs.com/treeswing.htm

×