20.1.5. Tools Used

• JIRA (User Stories)
• Figma (Wireframes)
• Confluence (BRD/FRD)
• SQL (Verify cart behavior in DB)

In the E-commerce case study, four specific tools are used to facilitate various activities. JIRA is employed to manage user stories, which capture the requirements and expectations of users. Figma is used for creating wireframes that provide a visual representation of the shopping cart's user interface. Confluence serves as a platform for documentation, specifically for the Business Requirements Document (BRD) and Functional Requirements Document (FRD). Finally, SQL is utilized to verify the behavior of the shopping cart in the database, ensuring that the system operates correctly.

Think of these tools like a recipe for baking a cake. JIRA is like the list of ingredients that you need to make the cake, helping you track what you have and what's missing. Figma is akin to a visual guide that shows you how your finished cake should look, while Confluence is like your cookbook, documenting all the steps and methods. SQL, on the other hand, is like the oven that ensures your cake rises correctly by checking the temperature and ensuring everything is baking properly.

• Lucidchart (Process flows)
• Excel (Traceability Matrix)
• JIRA (Sprint planning and bug tracking)
• SQL (Validate appointment data and time slots)

For the healthcare system, several tools were selected to streamline the project processes. Lucidchart is employed to create process flows, visualizing how patients interact with the system to book appointments. Excel is utilized as a traceability matrix, which helps ensure that all requirements are met and can be tracked throughout the project. JIRA is again utilized for sprint planning and to track any bugs that arise during development. Finally, SQL is used to validate appointment data and time slots, ensuring that the availability and functionality align with user expectations.

Imagine planning a family reunion. Lucidchart is like your diagram that shows how everyone will arrive and where they will sit, making it clear and organized. Excel is your checklist that tracks who has confirmed their attendance and who hasn't. JIRA acts as a daily planner, where you note the tasks that need to be completed each day leading up to the reunion. SQL is like the confirmation process that helps you verify that everyone arrives at the correct place and at the right time.

• Draw.io (Data Flow Diagrams)
• Confluence (BRD, API documentation)
• JIRA (Requirements and test logging)
• MS Excel (Eligibility criteria modeling)

In the banking loan application case study, multiple tools are used to assist various functionalities. Draw.io is used to create data flow diagrams that illustrate how data moves within the loan application process. Confluence again comes into play to document the Business Requirements Document (BRD) as well as API documentation needed for integration with other systems. JIRA is utilized for logging requirements and tracking testing phases effectively. Finally, MS Excel is employed to model the eligibility criteria for loan applications, allowing the team to calculate potential applicants' qualifications systematically.

Consider a team preparing for a big sports event. Draw.io represents the game plan, showing how different players move and interact during the game. Confluence is your team's handbook, containing all strategies and plays for every situation. JIRA serves as your daily practice schedule that outlines what needs to be achieved each day, while Excel calculates and tracks player statistics, determining who plays based on their performance and eligibility.

--