Project Plan for First Sprint

• XP for development
• Scrum for Project Management

Hand in delivery cycle documentation, with no code:

The User Stories you chose to consider (pick one or two)

The individual system tasks generated by the user story

The planned tasks for the release (which will be a list of all the system tasks required)

A user acceptance test plan (and it can be simple)

example:

• test1: user will enter one item that does not exist with its description, product id, quantity (list all fields) and hit enter. The system will give a message that it added the item. Then the user will ask to display that item and their entries will show.
• test2: The user will enter one item that exists and be told that the item already exists.
• test3: The user will try to display an item that does not exist and will be told that the item does not exist.

Burn down chart (list all tasks and required effort. In class we will make the calculation.)

Diagrams of the release, only including what will be in the release:

• Class diagram of only the classes needed to complete this first release (and you can use CRC Cards, Use Cases and Scenario descriptions)
• Test cases for each class (but limit to only 4 if more than 4 )
• Use case diagram - It will be simple. Make an actor of every possible type of user. List all the actions you are creating in your release in bubbles and then draw arrows.
• State diagram - Each of you will have a screen of some sort. It will have different states - showing starting code entry, showing all field entry, showing result of entry, listing all available codes of some sort, etc. Put each of these possible screen states in circles and draw an arrow from state to state if one state can move to the other state. If it only moves to that state based upon a condition, list that on the arrow in brackets ex: [ item not found ] .
• Sequence diagram: The roles should be user, screen system and database. These will be very simple with few messages. It will likely show the user initiate the transaction with the screen system, the screen system ask the database for info, that info being passed back to the user, the user making a selection and then the system passing an update transaction to the database.
• Context diagram (boxes of inside and outside the system) - use your existing context diagram but then draw the one piece you are doing inside that context diagram. I recommend you hand this to me by hand.

Plan to code in Eclipse and use GIT change management tool.