Writing Requirement Documents

2,494 views

Published on

Writing the requirement documents that get you what you want…

Published in: Technology, Education
1 Comment
0 Likes
Statistics
Notes
  • You are welcome to address me with further questions:

    http://www.linkedin.com/in/asazaidman

    zaidman[at]gmail[dot]com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
2,494
On SlideShare
0
From Embeds
0
Number of Embeds
275
Actions
Shares
0
Downloads
46
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Writing Requirement Documents

  1. 1. Getting YOUR requirements DEVELOPED Writing the requirement documents that get you what you want… Asa Zaidman & Mike Darnell
  2. 2. What does it take to write a GOOD* requirements document? <ul><li>*Good = You ask for what you want, & get what you asked for… </li></ul>
  3. 3. What does it take to write a GOOD requirements document? <ul><li>Good planning </li></ul><ul><li>Clarity </li></ul><ul><li>Good formatting </li></ul><ul><li>Good communication and supervision. </li></ul>
  4. 4. Good Planning <ul><li>Know your users </li></ul><ul><li>Know what you need & want: </li></ul><ul><ul><li>What processes must users complete? </li></ul></ul><ul><ul><li>What’s the general look & feel? </li></ul></ul><ul><li>Test your assumptions Conduct user tests. </li></ul><ul><li>Familiarize yourself with your team: developer, designers, etc. </li></ul>
  5. 5. Maintain Clarity I <ul><li>Write from a user’s point of view: “ The user will be able register his/her email and register for a newsletter ” </li></ul><ul><li>Nothing is obvious </li></ul><ul><ul><li>Set ground rules </li></ul></ul><ul><ul><li>Another behavior/scenario? Detail! </li></ul></ul>
  6. 6. Maintain Clarity II <ul><li>Detail! Scan your web pages from top to bottom How will every section behave? </li></ul><ul><li>Technology? </li></ul><ul><ul><li>“ I don’t care. If it meets my requirements, it can run on steam” </li></ul></ul><ul><ul><li>K.I.S.S = Keep it simple stupid </li></ul></ul><ul><li>References: A great method for communicating your wishes by providing examples </li></ul>
  7. 7. Good Formatting <ul><li>“ Poetry: The BEST WORDS in the BEST ORDER ” Samuel Taylor Coleridge </li></ul><ul><li>Ordering your document : </li></ul><ul><ul><li>Important = First </li></ul></ul><ul><ul><li>Numbering </li></ul></ul><ul><li>Suggested ordering* </li></ul><ul><ul><li>Introduction </li></ul></ul><ul><ul><li>Need </li></ul></ul><ul><ul><li>Concept </li></ul></ul><ul><ul><li>Goal </li></ul></ul><ul><ul><li>Background: Challenges, Environment, Compatibility </li></ul></ul><ul><ul><li>Features & Functional Requirements </li></ul></ul><ul><ul><li>Statistics </li></ul></ul><ul><ul><li>Open Issues </li></ul></ul><ul><ul><li>Supporting data & assumptions </li></ul></ul><ul><li>*Use only sections that apply </li></ul>
  8. 8. Good Formatting <ul><li>English </li></ul><ul><ul><li>Allows the flexibility of working with developers ANYWHERE </li></ul></ul><ul><li>Screenshots </li></ul><ul><ul><li>Make them CLEAR , don’t worry about beautiful… Check out these tools: Inkspace , Mockflow , Mockingbird *, Iplotz *, Axure *, Balsamiq *, Powerpoint, Paint, pen & paper, … </li></ul></ul><ul><li>Track changes </li></ul><ul><ul><li>Use Google Docs </li></ul></ul>
  9. 9. A Few More Tips… <ul><li>List not only what you want, but also what happens when things go wrong… </li></ul><ul><li>Consider SEO & page meta data </li></ul><ul><li>Statistics*: </li></ul><ul><ul><li>What do you want to know? </li></ul></ul><ul><ul><li>How are you going to act? </li></ul></ul><ul><ul><li>Who is going to read and analyze? </li></ul></ul><ul><li>List open issues </li></ul><ul><li>Review Review Review </li></ul><ul><ul><li>Have someone else review your document </li></ul></ul><ul><li>* - Google Analytics </li></ul>
  10. 10. Working with developers <ul><li>It’s your responsibility to have timely answers for your developers’ questions </li></ul><ul><li>Evaluating developers’ ideas: </li></ul><ul><ul><li>Does it met your requirements? </li></ul></ul><ul><ul><li>What is the risk? </li></ul></ul><ul><ul><li>What is the cost? (time, money) </li></ul></ul>
  11. 11. THANK YOU <ul><li>Asa Zaidman [email_address] </li></ul><ul><li>Mike Darnell [email_address] </li></ul><ul><li>Image Credits </li></ul><ul><li>“ Goal, almost…” - ◄M► </li></ul><ul><li>“ Dallas Early Subway plan” -   austrini </li></ul><ul><li>“ Order” - timsamoff </li></ul><ul><li>“ Autumnal clear sky” - *msk </li></ul><ul><li>“ South Clear Creek Falls” – OakleyOriginals </li></ul>

×