W8W Event System - User Stories

Evite and even Google Calendar has been an imperfect fit for our weekly dinner event planning. We've been looking for something that can help automated the venue selection and event notification process and so far it's been trying like trying to fit a size 12 foot into a size 6 stilleto. Decision has been finally made to home brew an event system. I'll be following the best practice approach to designing a software system as I know it. Input is welcome as always. The following steps will be taken:

*Gather User Stories
*Identify Actors and Entities
*Create a System Requirements Doc
*Create a System Design Doc
*Create a Mid-level Plan for Development (project management)
*Execute (code, etc)

Input throughout the process is very welcome.

First the User Stories. Think about it like Netflix, where the next restaurant (venue) is chosen from a venue queue. Unlike Netflix though a venue is recycled into the back of the queue after it was used.

W8W User Story Documentation
W8W Event System
06/14/2006
Yong Woo

User Stories

1) User logs into W8W system and is given proper user credentials.

2) User signs up to join W8W and become a Member.

3) W8W system automatically creates a new open event on the midnight after the current event is closed; venue from current event is returned to the end of the venue queue; venue with the highest recommendation points in the venue queue is chosen for the new event; if there is a tie in points venue for the new event, the one closer to the head of the venue queue is chosen.

4) Member reviews the details of the current event.

5) Member reviews the list of past events.

6) Member reviews the list of venues.

7) Member reviews the venue queue.

8) Member adds a new venue to end of the venue queue.

9) Admin moves a venue up, down, out of, or into the event queue.

10) Member votes for a venue point value ranging +1 or -1; multiple votes are allowed, but one for each venue.

11) Member sends a non-member an invitation to join W8W.

12) Non-member accepts or rejects an invitation to join W8W.

13) W8W system automatically notifies members the details of next event and allows the members to update their attendance status the Monday before and on the same day of the event.

14) Member sets the status of the member’s attendance to an event as a yes, no, or maybe.

15) Member posts a comment for the current event.

16) Admin changes the details of the current event and notifies the members.

17) Member broadcasts a message to all members.

18) Admin assigns a member as a default point person.

19) Admin assigns a member as a point person for the current event.

20) Admin assigns a user as an admin.

Entities Identified

Actors

1) W8W System

2) User

a. Admin

b. Member

c. Non-member

Entities

1) User

2) Event

3) Venue

4) Venue Queue

5) Vote

6) Invitation to Join

7) Attendance Status

8) Comment

Coming up next: Requirements documentation from the User Stories.