Individual Deliverable: Use Case, Persona, Functional, Non-functional requirement

• Fully-dressed Use Case
  • Select a use case from your team project.
  • Develop it into a fully-dressed use case.
  • Use complete sentences where appropriate, with good grammar and spelling. Avoid ambiguous terms.
  • Coordinate so you do not choose the same use case as a teammate.
  • Do the work by yourself. If you refine the use case with your team in the normal course of iteration 2, do not include these collaborative refinements in what you turn in for this individual assignment.
  • Follow the example on p. 142 in the text and use the SRS template in PolyLearn.
  • The fully-dressed use case should fit on one page of paper (front and back if necessary).
  • This artifact will be evaluated based on following the above specifications, the quality of the analysis (e.g. did you make good choices?, are the steps atomic and unambiguous?, did you think of appropriate alternative courses?), and the quality of the textual presentation.
• Persona
  • Develop a persona for a user of our proposed system.
  • Follow the example on p. 101 in the text.
  • Use complete sentences with good grammar and spelling.
  • The persona should fit on one page of paper (front only).
  • This artifact will be evaluated based on following the above specifications, the quality of the analysis (e.g. did you select an appropriate example?, are user needs clear?, is it obvious how this user might be different from others?), and the quality of the textual presentation.
• Functional Requirement
  • Based on your use-case (above), identify one functional requirement for your system.
  • Document the functional requirement.
  • Follow the example on pp. 186-189 in the text.
  • Use complete sentences with good grammar and spelling.
  • Do the work by yourself. If you refine the functional requirement with your team in the normal course of iteration 2, do not include these collaborative refinements in what you turn in for this individual assignment.
  • The functional requirement should fit on one page of paper (likely less than half a page).
  • This artifact will be evaluated based on following the above specifications, the quality of the analysis (e.g. unambiguous, correct, feasible, verifiable), and the quality of the textual presentation.
• Non-functional Requirement
  • Identify one non-functional requirement (i.e. quality attribute) for your system. Ideally choose one related to your use-case (above).
  • Document the non-functional requirement.
  • Follow the example on pp. 219-228 in the text.
  • Use complete sentences with good grammar and spelling.
  • Do the work by yourself. If you refine the non-functional requirement with your team in the normal course of iteration 2, do not include these collaborative refinements in what you turn in for this individual assignment.
  • The non-functional requirement should fit on one page of paper (likely less than half a page).
  • This artifact will be evaluated based on following the above specifications, the quality of the analysis (e.g. unambiguous, correct, feasible, verifiable), and the quality of the textual presentation.