Scribd
Upload
101 views

2024 SPRING SWR302 Assignment - 01

This document outlines two assignments for a software requirements engineering course. The first assignment involves modeling a bookstore website system using context diagrams, feature trees, use case diagrams, use case descriptions, and user stories. The second assignment involves a similar modeling exercise for a library management system. Both assignments require drawing models, writing use case scenarios, and specifying user stories and acceptance criteria. References for how to write acceptance criteria are also provided.

Uploaded by

Le Hai Dang (K16HL)
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
101 views

2024 SPRING SWR302 Assignment - 01

This document outlines two assignments for a software requirements engineering course. The first assignment involves modeling a bookstore website system using context diagrams, feature trees, use case diagrams, use case descriptions, and user stories. The second assignment involves a similar modeling exercise for a library management system. Both assignments require drawing models, writing use case scenarios, and specifying user stories and acceptance criteria. References for how to write acceptance criteria are also provided.

Uploaded by

Le Hai Dang (K16HL)
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

FPT UNIVERSITY

SWR302 – SPRING SEMESTER


quetd2@fe.edu.vn, tdque@yahoo.com
=========================== ========
Assignment 1
Due date: WEDNESDAY 17/01/2024
PT1: MONDAY 22/01/2024

Exercise 1: A Book Store Online permits customers and Staff/Manager to perform the following
functionalities:
Customer
• Register
• Login/Log out
• Search
• Create/view/update/cancel Cart
• Check out
• Select shipment
• Select payment
• Create/view/update/cancel order
• ….
Staff/Manager
• Login/Log out
• Search
• Store items
• Put items on selling Web
• Process (view, update, cancel…) order
• View statistics of item selling (Manager)
Your tasks are:
1. Construct a context diagram for the system (page 93 and page 585)
2. Construct a feature tree for the system (page 95 and page 578)
3. Using VP Tool to draw a use case diagram (page 145, 149)
4. Write scenarios for 10 use cases (page 150, 581)
5. Write user stories & acceptance criteria w.r.t your 10 use cases (page 145). Using the
template from the link
https://rubygarage.org/blog/clear-acceptance-criteria-and-why-its-important
https://www.altexsoft.com/blog/business/acceptance-criteria-purposes-formats-and-
best-practices/
Exercise 2: A Library Management system permits actors to perform the following
functionalities.
Actors

• Librarian: Mainly responsible for adding and modifying books, book items, and users.
The Librarian can also issue, reserve, and return book items.

1
• Member: All members can search the catalog, as well as check-out, reserve, renew, and
return a book.
• AutoSystem: Mainly responsible for sending notifications for overdue books, canceled
reservations, etc.

Functionalities

• Add/Remove/Edit book: To add, remove or modify a book or book item.


• Search catalog: To search books by title, author, subject or publication date.
• Register new account/cancel membership: To add a new member or cancel the
membership of an existing member.
• Check-out book: To borrow a book from the library at desk room or via Internet
• Reserve book: To reserve a book which is not currently available.
• Renew a book: To re-borrow an already checked-out book.
• Return a book: To return a book to the library which was issued to a member.
Your tasks are to:
1. Construct a context diagram for the system (page 93 and page 585)
2. Construct a feature tree for the system (page 95 and page 578)
3. Using VP tool to draw a use case diagram (page 145, 149)
4. Write scenarios for 10 use cases (page 150, 581)
5. Write user stories & acceptance criteria w.r.t your 10 use cases (page 145). Using the
template from the above links in Exercise 1

References
[1] https://rubygarage.org/blog/clear-acceptance-criteria-and-why-its-important
[2] https://www.altexsoft.com/blog/business/acceptance-criteria-purposes-formats-and-best-
practices/
[3] https://www.mobindustry.net/blog/how-to-write-acceptance-criteria-examples-and-best-
practices/
[4] https://www.softwaretestinghelp.com/user-story-acceptance-criteria/#
[5] https://viblo.asia/p/tim-hieu-ve-user-story-va-acceptance-criteria-qua-examples-
4P8560XBZY3

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy