Pharmville specs

• This is based on the Volere Requirements Specification Template.

Also, remembering the five points to a SMART goal: Specific, Measurable, Attainable, Realistic, Timely / Timed.

1. The Purpose of the Project

-- Service Goal

• Allow customers to gain experience, prestige, and credits inside Zynga games in an automated manner. This goal is actually a set of goals to be attained, and can later be transformed into a set of goals to make the service faster or more reliable over a set period of time.

-- Revenue Goal

• Starting small, we expect revenue to be in the 10s of dollars by the end of the semester. Further goals will not be stated here.

-- Legal Goal

• Have the product and company comply with all state and federal laws, avoiding torts and copyright infringements.

-- Security Goal

• The product shall employ online verification mechanisms to avoid being hacked and distributed without permission.

-- Learning Goal

• Production team shall learn how to employ agile techniques in the product development cycle, how to advertise on Facebook, how to program in Python, and how to use some of the Facebook APIs for python.

2. The Stakeholders

-- the client: Joe Kniss

-- the customer: millions of Facebook users

-- other stakeholders: team members who will be graded on our performance

-- hands-on users of the product: same as the customer

3. Mandated Constraints

-- Solution constraints

• Follow the direction of the teacher
• Be legal
• Use python, php, SQL, and developer APIs

-- Anticipated workplace environment

• We expect school, as well as team members' houses. Maybe even the institute.

-- Schedule constraints

• Other classes
• 10 weeks

-- Budget constraints

• No money

4. Naming Conventions and Definitions

-- Not currently applicable

5. Relevant Facts and Assumptions

-- Not currently applicable

6. The Scope of the Work

-- The Current Situation

• Not started yet

-- The Context of the Work

• Not currently important

-- Work Partitioning

• TBD

7. Business Data Model and Data Dictionary

-- Not sure

8. Scope of the Product

-- Product Boundary

• Users are to play with the product, but not reverse engineer or otherwise misuse it

-- Product Use Case Table

• TBD

9. Functional and Data Requirements

-- Functional Requirements

• Should be broken down into atomic parts, and kept track of by the product owner
• The product shall maintain a history of what it's done for the user
• The product shall check in with a server every 15 minutes for verification
• The product shall allow user to set different behavior modes

-- Data Requirements

• There shall be a user database, that includes payment receipts and history

10. Look and Feel Requirements

-- The product shall be user tested for quality

11. Usability and Humanity Requirements

-- Ease of use

• The product shall be user tested by a wide demographic

-- Personalization and Internationalization Requirements

• We'll cross that bridge when we come to it

-- Learning Requirements

• The product shall be easy to use

-- Understandability and Politeness Requirements

• The product shall be tested for sensitivity to audience's sense of appropriateness

12. Performance Requirements

-- Product shall be fast on an ordinary computer

-- Product shall be safe to use and void of dangerous bugs

-- Product shall be robust and updated to reflect changes in Zynga games

... and the list continues. See http://www.volere.co.uk/template.htm