Assignment Overview

Using what you have learned from the lesson notes, readings, and videos shared in this module, reflect on how to pull objects from use cases and user stories, and how to think of those cases from a user$/$testing perspective.

You will be assessed on your achievement of the following course learning outcomes:

Use documents to generate classes

Identify entity classes from use cases and user stories

Identify attributes

Identify actions

Think of use cases and stories from a user$/$test perspective

Explain the difference between a use case and a test case

Explain who should meet to determine scenarios and why?

Explain the $3$ parts of a Gherkin Scenario

Explain why this meeting on testing the feature should occur before development has started

Estimated completion time: $2$ hour

How to Proceed

Using the Attached Detailed Use Cases and User Stories for a library system:

Use noun$/$verb analyses to find the classes involved in each use case. Use the template provided for listing nouns$/$verbs$.$

Using the detailed use cases and the TestScriptTemplate provided, provide detailed test scripts for the $2$ use case details.

To the detailed use stories provided add BDD scenario's

Remember the point is to measure your understanding of how to design software in the language of the business.

Upload all files created to Learn.

Format

Complete assignment in Word, Visio, or Paint etc. Your answers should be well$-$structured, written in full sentences, and focused on clarity and understanding.

Submission

Submit your assignment in Word, Visio, PDF$,$ or Image to your instructor through the LEARN Dropbox. Include in your file name the course code, assignment name, and your name $($e$.$g$.$ WEBD $2011\_$Assignment $1\_$JDoe.rtf$).$

Due date

Your assignment must be completed and submitted to Dropbox before beginning the next module.

Evaluation

Your instructor will use the attached grading rubric to evaluate your assignment. Review this marking rubric carefully before beginning this assignment.

Grading

This assignment is worth $20$ marks or $6\%$ of your final grade.

Attachments

Library Use Case Diagram.pdf

$(192\mathrm{.}39$ KB$)$

Detailed Use Cases.docx

$(20\mathrm{.}75$ KB$)$

Detailed User Stories.docx

$(13\mathrm{.}35$ KB$)$

TestScriptTemplate.docx

$(14\mathrm{.}3$ KB$)$

NounVerbAnalysis.docx

$(14\mathrm{.}04$ KB$)$TEST CASE

Author:$\_\_\_\_\_\_\_\_\_\_\_$ Date:$\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_$

USE CASE NAME:

ACTOR$($S$)$:

DESCRIPTION:

REFERENCES

TYPICAL COURSE OF EVENTS: Actor Action System Response

Step $1$

Step $2$

PRE$-$CONDITION:

POST$-$CONDITION:

ASSUMPTIONS: User Story : Add Title

As a Librarian I want to add new titles with their information so that they can be found for borrowers and loaned out

Acceptance Criteria

Title must be new or save is cancelled

User must confirm save before it is permanent

Scenarios

User Story : Add Item

As a Librarian I want to add new items with their information to titles I$$ve entered so that they can be found for borrowers and loaned out

Acceptance Criteria

Title must exist for items to be added

Items can be books, audio tapes, videos, etc.

Scenarios

User Story : Add Borrower

As a checkout clerk I want to add new borrowers with their information so I can loan items to them

Acceptance Criteria

The borrower must be new or save is cancelled

User must confirm save before it is permanent

Scenarios

User Story : Remove Reservation

As a checkout clerk I want the reservation for an item removed so that the item is available to be loaned to someone else later

Acceptance Criteria

The reservation must exist

User must confirm save before it is permanent

Scenarios

User Story : Return Item

As a checkout clerk I want to receive returned items so that the item is available to be loaned to someone else

Acceptance Criteria

User should be able to return many items at once

Items are not necessarily for the same borrower

Scenarios