Friday, December 14, 2012

Organized Notes

To say in the lamest terms, the Project manager would like tot have a better way of managing and organizing meeting notes from post-its into an organizable database. Post its may be useful at setting ideas in motion, but once the madness is on the floor, technology can help you sort through it.



So I have started writing user stories for the Project Manager by listing his needs. Here is what I got so far:


1. Feature: Having User friendly meeting notes taking database
As a Project Manager
So I can report summarized extensive data
I want a reportable copy of separate notes during meetings
Scenario: have a user friendly meeting notes taking database
Given I am in the database system home form
When I go to print page (form)
And I enter the meeting number
And I press enter
And I press print
Then I should get a printed version of the meeting notes summary
Complexity: Currently Complex - hoping to move to Average
2. Feature: Having User friendly meeting notes taking database
As a Project Manager
So I can organize my thoughts
I want to be able to print categorized notes from meetings
Scenario: have a user friendly meeting notes taking database
Given I am in the database system home form
When I go to category view (from)
And I enter the meeting number
And I press enter
And I select "GoneWell", "LooseEnds" or "NotWell"
Then I should get an organized list of category selected
Complexity: Currently Complex - hoping to move to at least Average
3. Feature: Having User friendly meeting notes taking database
As a Project Manager
So i can keep track of who is attending meetings
I want to keep accountability on who was present during meetings
Scenario: have a user friendly meeting notes taking database
Given I am in the database system home form
When I go to Meeting view (from)
And I enter the meeting number
And I press enter
Then I should get an organized list of Meeting Name, date, place, and attendees
Complexity: Currently Average - hoping to move to simple
view raw gistfile1.txt hosted with ❤ by GitHub
Posted by at

2 comments:

  1. Sam JosephDecember 14, 2012 at 10:59 PM

    Great to see these written out. The main challenge with the way you've written the scenarios are that the final "Then ..." lines are not in a form that is explicitly testable.

    The idea with the cucumber scenarios is that they can be run as integration tests that checks whether your system actually provides the desired functionality. This was the essence of HW3 from the first EdX course.

    So rather than "Then I should get a printed version of the meeting notes summary" you should have something like "Then I see ''Meeting Number 6 Summary (print version)", which would correspond not to actually printing the document, but the view on the screen prior to printing.

    Similarly for "Then I should get an organized list of category selected" should be something that actually check for the presence of particular notes under particular categories. As you have hopefully seen in some other cucumber examples, the scenario background can include setup of the database so that you have for example, two notes in each category, and then you can check explicitly that those appear under the correct category headings.

    ReplyDelete
  2. UnknownDecember 16, 2012 at 6:36 PM

    Okay, I see what you mean, I'll update accordingly. :)

    ReplyDelete

Subscribe to: Post Comments (Atom)