20.1.4. BA Activities

• Gather user stories (e.g., “As a shopper, I want to remove an item from my cart”)

Gathering user stories involves collecting requirements directly from users about what they want from the system. Each story typically follows a format that describes who the user is, what they want, and why it’s important. For example, in an e-commerce setting, a user story might express a shopper's desire to easily manage their shopping cart.

Imagine you're planning a party and asking your friends what snacks they would like. Each request represents a 'user story' that helps you understand how to create a menu that everyone will enjoy.

• Create wireframes for cart UI

Creating wireframes is the process of designing a visual guide that represents the skeletal structure of a webpage or application. These wireframes indicate how users will interact with different elements of the cart's user interface, including buttons, product displays, and checkout options.

Think of wireframes like blueprints for a house. They show where everything should go, including rooms, doors, and windows, before construction starts, allowing for modifications and plans before the actual building takes place.

• Define business rules (e.g., max quantity per product, cart expiration)

Defining business rules means establishing the guidelines that govern how the business operates within the system. For instance, setting a maximum allowed quantity for each product ensures that inventory management is efficient, and defining cart expiration helps manage customer expectations and inventory turnover.

Consider business rules like the rules in a board game. They are essential for ensuring fairness and proper gameplay. If everyone knows the rules, the game runs smoothly without confusion.

• Document functional & non-functional requirements

Documenting requirements involves detailing what the system must accomplish (functional requirements) and how it should perform (non-functional requirements). Functional requirements might include allowing users to add items to the cart, while non-functional requirements could specify that the system should load the cart in under 2 seconds.

Creating a restaurant menu can be compared to documenting requirements. The menu outlines what dishes are available (functional) and their price points or dietary options (non-functional) to cater to customers.

• Conduct UAT for checkout and promo logic

User Acceptance Testing (UAT) involves verifying that the functionalities work as intended from the user’s perspective. During UAT, users test the checkout process and apply promo codes to ensure everything operates smoothly and as expected before the system goes live.

Think of UAT like a dress rehearsal for a play. Actors practice in front of an audience to ensure everything runs flawlessly before the big opening night.

--