20.3.4. BA Activities

● Gather user stories (e.g., “As a shopper, I want to remove an item from my cart”) ● Create wireframes for cart UI ● Define business rules (e.g., max quantity per product, cart expiration) ● Document functional & non-functional requirements ● Conduct UAT for checkout and promo logic

This chunk describes the business analyst (BA) activities specific to the e-commerce cart system project. BAs start by gathering user stories, which are short descriptions of how users will interact with the system, emphasizing their needs (like removing an item from the cart). Next, they create wireframes, which are visual layouts of the cart user interface, helping teams visualize how the application will look and function. Then, they define business rules that dictate how the system should behave under certain conditions, for instance, limiting how many of a single product can be added to the cart or how long the cart will keep items saved. Documenting both functional (what the system should do) and non-functional requirements (how the system should perform) is crucial for development. Lastly, BAs conduct user acceptance testing (UAT) to ensure that the checkout process and promotional code application function correctly, validating that the system meets user expectations.

Consider planning a party. Gathering user stories is like asking friends what games they want to play or food they want to eat. Creating wireframes is like sketching out how the party area will be set up. Defining business rules is akin to setting limits on the number of people who can attend or how long the party will last. Documenting requirements is similar to making a checklist of what needs to happen for the party to go well, while UAT is like doing a final walkthrough to ensure everything is ready before guests arrive.

● Elicit functional and non-functional requirements ● Create activity diagrams for patient-doctor workflows ● Define data privacy requirements (e.g., storing patient data securely) ● Collaborate with QA on test cases for booking, notifications ● Assist in UAT with hospital staff

In this section, we look at the BA activities associated with the healthcare appointment system project. BAs work to elicit both functional and non-functional requirements, which specify what the system must achieve and how it should function in terms of reliability and performance. They create activity diagrams that visually map out workflows between patients and doctors, illustrating how interactions will occur. Data privacy is a significant concern in healthcare, so BAs must define stringent requirements for securely storing patient information. Collaborating with quality assurance (QA) teams to develop test cases ensures that the system works as intended for booking and notifications. Finally, BAs assist with user acceptance testing (UAT), working closely with hospital staff to validate that the system meets all necessary criteria and functions seamlessly in a real-world environment.

Imagine developing a new health app. Eliciting requirements is like interviewing users to find out which features they value most, like appointment reminders. Creating activity diagrams is like making a flowchart of how users will navigate through the app to book an appointment. Defining data privacy requirements is akin to ensuring the app locks sensitive information, much like a vault keeps valuables safe. Working with QA is like rehearsing before a performance to ensure everything goes smoothly. Assisting in UAT would be similar to having users try the app to verify that it meets their needs before launching.

● Gather BRD and map user personas (Salaried vs Self-Employed) ● Write user stories and define system integrations (APIs with credit bureaus) ● Coordinate test scenarios for fraud checks and KYC compliance ● Prepare data mapping for reports and dashboards ● Assist in training call center on system usage

This chunk focuses on the BA activities for the banking loan application project. The first step is to gather the Business Requirements Document (BRD) and identify user personas, like individuals who are salaried versus those who are self-employed, so the system can cater to their different needs. Writing user stories helps clarify how each persona will interact with the loan application. BAs also define system integrations to connect the loan application with external services, like credit bureaus, facilitating data checks. They coordinate test scenarios to ensure the system adheres to anti-fraud measures and Know Your Customer (KYC) regulations, ensuring legal compliance. Data mapping is critical for creating meaningful reports and dashboards that help stakeholders visualize data. Lastly, BAs play a role in training call center staff on how to use the new system effectively, ensuring operational smoothness.

Think of launching a new online loan application service. Gathering the BRD is like collecting all the rules for a game before you play. Mapping user personas is akin to understanding the different types of players in a game and how they might play. Writing user stories equals defining character actions in a video game. Coordinating test scenarios mirrors playtesting the game for bugs and ensuring the rules are followed. Data mapping is similar to creating strategy guides to help players understand how to win, while training the call center is like coaching players on how to master the game mechanics.

--