Writing Requirement Documents

  • 2,023 views
Uploaded on

Writing the requirement documents that get you what you want…

Writing the requirement documents that get you what you want…

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • You are welcome to address me with further questions:

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

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

Views

Total Views
2,023
On Slideshare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
37
Comments
1
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

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