Scribd
Upload
25 views10 pages

Lab 1

Uploaded by

Sporkion Suz-beero
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
25 views10 pages

Lab 1

Uploaded by

Sporkion Suz-beero
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/ 10

Lab 1

Review of Use-Cases, User Stories and Business Canvas


REMEMBER Process Sale Use-case

Preconditions: Cashier is identified and authenticated.


Success Guarantee (Postconditions): Sale is saved. Tax is correctly calculated.
Accounting and Inventory are updated. Commissions recorded. Receipt is generated.
Payment authorization approvals are recorded.

Main Success Scenario (or Basic Flow):

1. Customer arrives at POS checkout with goods and/or services to purchase.


2. Cashier starts a new sale.
3. Cashier enters item identifier.
4. System records sale line item and presents item description, price, and running total.
Price calculated from a set of price rules.
Cashier repeats steps 3-4 until indicates done.
5. System presents total with taxes calculated.
6. Cashier tells Customer the total, and asks for payment.
7. Customer pays and System handles payment.
8. System logs completed sale and sends sale and payment information to the external
Accounting system (for accounting and commissions) and Inventory system (to
update inventory).
9. System presents receipt.
10.Customer leaves with receipt and goods (if any).
Remember the use-story format

A user story typically follows a simple format:

As a [type of user], I want [a specific goal] so that [benefit or reason].

Can you name a user story of "Process Sale" process


As a Cashier, I want to be able to add item(s) to the sale, so I can record the
sale with all items purchased by the customer

What is the acceptance criteria for this


Acceptance Criteria:

1. Add Single Item to Sale:


1. The cashier can scan or enter a product code to add a single item to the current sale.
2. The item details (e.g., name, price, quantity) will be displayed on the screen once
added.
3. The sale total is updated to reflect the addition of the item.

2. Add Multiple Items to Sale:


1. The cashier can scan or enter multiple items consecutively to add them to the sale.
2. Each item will be displayed with its details on the sales screen.
3. The sale total is updated accordingly as items are added.

3. Modify Item Quantity:

1. The cashier can modify the quantity of an item if the customer is purchasing more than
one of the same item.
2. The sale total and item subtotal will update automatically based on the new quantity.

...What Else
Test Scenario: Add Multiple Items to Sale
Objective: Verify that the cashier can add multiple items to a sale, and the system correctly updates the sales
screen and the sale total.
Preconditions:
•The cashier is logged into the point-of-sale (POS) system.
•The POS system is ready for a new sale.
Steps:
1. Action: The cashier scans or enters the product code for the first item (e.g., "12345").
1. Expected Result: The system adds the first item to the sales screen, showing the item name, price, and
quantity of 1. The sale total is updated to reflect the price of the first item.
2. Action: The cashier scans or enters the product code for the second item (e.g., "67890").
1. Expected Result: The system adds the second item to the sales screen, showing the item name, price, and
quantity of 1. The sale total is updated to include the prices of both the first and second items.
3. Action: The cashier scans or enters the product code for a third item (e.g., "11223").
1. Expected Result: The system adds the third item to the sales screen, displaying the item name, price, and
quantity of 1. The sale total updates to reflect the combined price of all three items.
4. Action: The cashier scans or enters the product code for an existing item (e.g., "12345" for the first item again).
1. Expected Result: The system increases the quantity of the first item to 2 and updates the subtotal for that item
accordingly. The sale total updates to reflect the increased quantity.
5. Verification:
1. The sales screen accurately displays all items added, including the item names, prices, and quantities.
2. The sale total correctly reflects the combined cost of all items and any quantity updates.
Postconditions:
•The cashier can proceed to modify the sale, add more items, or finalize the sale as needed.
You need different type tests to verify this acceptence criteria

- Acceptence Test
Purpose: To determine if the software meets the business
requirements and is ready for deployment. Usually conducted by
end-users or testers.

Test Scenario: Add Multiple Items to Sale is executed by browser-


based test automation tool (Selenium)

- Integration Testing
Purpose: To test the interaction between different modules or
components of an application.

Test the correct product retrieved from db and added to the sale

- Unit Testing
Purpose: To verify that individual components or units of code
(e.g., functions, methods, or classes) work as expected.

Test the method of the Sale adds the products to the Sale
Managing a university registration system

A small university would like to create a registration system for its students. The students will use
this system to obtain information about courses, when and where the classes meet, register for
classes, print transcripts, drop classes, etc. The faculty will be using this system to find out what
classes they are assigned to teach, when and where these classes meet, get a list of students
registered for each class, and assign grades to students in their classes. The university administrative
staff will be using this database to add new faculty and students, remove faculty and students who
have left, put in and update information about each course the university ofers, enter the schedules
for classes that are being offered in each term, and any other housekeeping tasks that need to be
performed.

Your task is to analyse this system, extract and list the details of the various business processes,
develop the use cases, and find the conceptual classes and their relationships.
In finding the classes for this system, one of the issues that comes up is that of distinguishing a
course from an offering of the course. For instance ‘CS 430: Principles of Object-Oriented Software
Construction’ is a course listed in the university’s course bulletin. The course is offered once during
the fall term and once during the spring term. Each offering may be taught at a different time and
place, and in all likelihood will have a different set of students. Therefore, all offerings have some
information in common and some information that is unique to that offering. How will you choose a
set of classes that models all these interactions?
Think an innovation for this System

And define your Value Proposition

Value Propositions:
• This describes the unique value a company offers to its customers—
what problem is being solved or what need is being fulfilled. It’s the
reason customers choose one company over another.

• Example: A faster, cheaper, more reliable, or innovative product or


service.

Then define the Business Canvas

You might also like