20.2.5. Tools Used

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

In the e-commerce case study, various tools were employed to facilitate the development process. JIRA was used to manage user stories, allowing the team to track requirements and work progress efficiently. Figma was utilized for designing wireframes, which are visual representations of the shopping cart interface, to help stakeholders visualize the end product. Confluence served as a collaborative space for documentation, including the Business Requirements Document (BRD) and Functional Requirements Document (FRD), ensuring everyone was on the same page. Lastly, SQL was used to verify that the shopping cart's behavior met the requirements by checking the database functionalities.

Think of this like building a house. Just like you would use blueprints (Figma for wireframes) to plan the layout, checklists (JIRA for user stories) to track tasks, a shared workspace (Confluence for documents) to ensure everyone has access to necessary information, and tools (SQL for database verification) to test the strength of the structure — these tools help in managing complex projects effectively.

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

In the healthcare appointment system project, several tools were essential for ensuring a smooth build and implementation process. Lucidchart was used to create flowcharts that visualize the appointment processes, which helps in understanding how patients interact with the system. Excel was utilized to maintain a traceability matrix, ensuring that all requirements were tracked throughout the project. JIRA assisted in organizing sprints and tracking bugs effectively. Lastly, SQL was employed to validate appointment data, confirming that the system correctly handled booking and scheduling.

Imagine planning an event, like a wedding. You’d use a flowchart (Lucidchart for process flows) to see the timeline from invites to ceremony, a spreadsheet (Excel for traceability matrix) to keep track of guest RSVPs, a project management tool (JIRA for sprint planning) to organize tasks among helpers, and a checklist (SQL for data validation) to ensure every detail, like reservation times, is confirmed. Each tool has its role in making sure the event is a success.

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

For the banking loan application project, various tools were utilized to streamline the development and ensure functions were built correctly. Draw.io was used to create data flow diagrams, helping visualize how data moves through the systems. Confluence was critical for documenting the Business Requirements Document (BRD) and API documentation, ensuring that everyone involved has the necessary information. JIRA was essential for managing requirements and logging tests, allowing for efficient tracking. Finally, MS Excel was employed for modeling eligibility criteria, which determines who qualifies for loans based on various factors.

Picture assembling a complex puzzle. You’d use diagrams (Draw.io for data flow diagrams) to strategize how pieces fit together, a binder (Confluence for documentation) to keep important information in one place, a task manager (JIRA for requirements and test logging) to ensure each piece is tested, and a chart (MS Excel for modeling eligibility) to decide which pieces actually belong in a specific spot, ensuring the finished puzzle looks just right.

--