Skip to content
S

SchoolProject1

Welcome to The Cash Flow Visualization Tool Wiki page.

Figma link to graph ideas: https://www.figma.com/board/49gjnZ5wU8wXuun5QMOKGN/CashFlowToolDiagrams?node-id=0-1&t=jfGIax8l6xbf9OsA-1

Figma link to wireframe ideas: https://www.figma.com/design/L1jCTqMIdP4FdLYd0nPshz/Cash?node-id=0-1&t=FpOyXL0R15yaimTB-1

Font: https://github.com/seb-oss/fonts

Table Of Contents

Project scope

ITERATIONS

Iteration 1. Requirements Engineering (4 people, 3 weeks, 97 hours)

Goal: The goal of this iteration is to gather and refine all necessary functional and non-functional requirements for the Cash Flow Visualization Tool and set up project.

  1. Document at least 24 functional requirements: (about 58 hours)
  • Create initial user stories Issue 8 (24 hours)
  • First meeting with the customer (27 hours 50 minutes) Issue 2, Issue 3, Issue 6
  • Second/Third meeting with the customer (2 hours)
  • Discussing and writing the requirements in team meetings (4 hours)
  1. Document at least 7 measurable non-functional requirements: (3 hours) Issue 10
  2. Create ReadMe (4 hours) Issue 11
  • Write project overview
  • Write dependencies
  • Write documentation how to set up project locally with springboot, angular and postgres.
  1. Document 2 use cases (4 hours) Issue 12
  • Write at least 2 use cases
  • Link them with user stories
  1. Create figma graph to visualize cash flow graphs (11 hours)
  • Create first cash flow graphs in figma (6 hours) Issue 9
  • Create graph to visualize cash flows on account level (2 hours)Issue 103
  • Create tables to figma to visualize top SME or Corporations (3 hours) Issue 112
  1. Set up project repository (about 7 hours)
  • Set up backend (3 hours) Issue 1
  • Set up frontend (2 hours) Issue 4
  • Set up docker compose (50 min ) Issue 5
  • Create initial ngx-graph for visualization how it works (50 min)
  1. Document general information about the project (10 hours)
  • Write product vision (2 hours) Issue 155
  • Write project plan (4 hours) Issue 156
  • Create issues and issue board (4 hours)

Iteration 2: Implementation of Core Features (3 weeks, about 180 hours)

Goal: The primary objectives of this iteration are to implement core functionalities that provide an aggregated overview of cash flows.

Use Cases:

  • UC 1: View aggregated Cash Flows
  • UC 2: View Internal Cash Flows Between Accounts in "My Company"

This use case will need implementation of following tasks.

Tasks

1. Customer Engagement (8 hours) Issue 169

  • Conduct weekly meetings with customers to gather feedback and take detailed notes.

2. Database Setup (8 hours, 30 min)

  • Create migration files using Flyway for version control of the database schema. (2 hour, 30 min) Issue 100, Issue 159, Issue 162
  • Design and implement tables for transactions, accounts, and participants in the database. (4 hours) Issue 99
  • set up testing database (2 hours) Issue 161

3. Main Page Development (8 hours)

  • Develop the main page to display the cash flow overview graph. (8 hours) Issue 136

4. Synthetic Data Generation (17 hours)

  • Write scripts to generate synthetic data for testing purposes. (16 hours) Issue 94
  • Write postgres scripts to populate tables (1 hour) Issue 97

5. User Interface Implementation (10 hours)

  • Create a UI component for selecting SMEs from a list related to "My Company." (10 hours) Issue 27

6. Backend Development (11 hours 30 min)

  • Implement backend endpoints to:
  • Retrieve all SMEs for selection related to "My Company." (1 hour 30 min) Issue 28, Issue 60
  • Fetch aggregated data in terms of source, transaction (including currency), and target. (8 hours) Issue 68
  • Implement country based filtering ( 18 hours) Issue 85, Issue 67

7. Data Visualization Solutions (31 hours 30 min)

  • Design a UI to visualize aggregated data (5 hours 30 min) Issue 42
  • Design UI to visualize outgoing and incoming flows (20 hours) Issue 56, Issue 50
  • Visulize countries as nodes (3 hours 40 min) Issue 31
  • Visualize accounts as nodes (2 hours) Issue 13
  • Visualize account level Cash Flow Graph (3 hours) Issue 105
  • View aggregated incoming and outgoing flows between my company's node and countries nodes (3 hours) Issue 67

8. Testing (6 hours)

  • Conduct thorough testing of:
    • Test aggregated data (2 hours) Issue 158
    • Test getting all companies. (4 hours) Issue 157

9. Use cases related tasks (6 hours)

  • Create testing for use cases (2 hours) Issue 168
  • Create UML graph for diagram (2 hours)Issue 167
  • Create acceptance tests (2 hours) Issue 168

10. Other (52 hours)

  • Create Continuous Integration (CI) (16 hours) Issue 164
  • Create Mocks (20 hours ) Issue 70
  • Create release notes (2 hours) Issue 171
  • Write scope (8 hours) Issue 172
  • Refactoring code according to requirements (8 hours)

Overview

  • Functional main page displaying cash flow graphs.
  • Database schema with tables for transactions, accounts, and participants.
  • Working backend endpoints for data retrieval and visualization.
  • UI components for SME selection and aggregated cash flow visualization.
  • Testing reports for aggregated nodes and flows.

Iteration 3: Implementation of Additional Features and Enhancements (3 weeks, 226 hours spent)

Use cases:

  • UC 3: Filter Cash Flows by Specific Parameters
  • UC 4: Analyze Cash Flows to and from Customers
  • UC 5: Select and Analyze Specific Transactions with Key Companies

Goal:

The goal of this iteration is to implement core features for filtering and analyzing cash flows, including building the logic to handle specific transactions with key companies. Additionally, the iteration focuses on refining graph visualizations and enhancing the UI to support better data interaction and filtering.

Tasks:

1. Customer Engagement (8 hours)

  • Gather customer feedback on the implemented features.
  • Record and track any new requirements or changes as per customer feedback.
  • Register any customer-reported bugs in the issue tracker.

2. User Interface Implementation (20 hours)

  • Create filter UI for the application (Issue #190)(8 hours)
  • Move graphs to one page (Issue #197) (2 hours)
  • Move company seleciton to filter (Issue #192)(2 hours)
  • Create table UI (Issue #190)(8 hours)

3. Table to and from tasks (15 hours total)

  • List companies in the SME or Corporate category sorted by total cash flows to my company (Issue #113)
  • List SMEs or corporations based on cash flows to them (Issue #178)
  • Create net flow table data (Issue #218)

4. Graph-related tasks (72 hours total)

  • Adjust current graph according to mocks in Figma (8 hours)
  • Visualize average transactions in the graph (Issue #98)
  • Visualize by frequency in the graph (Issue #90)
  • Visualize cash payments in different currencies (Issue #70)
  • Visualize cash flow in a specific currency (Issue #76)
  • Visualize net flow in the graph (Issue #66)
  • Visualize internal cash flows (Issue marielle.lepson/cash-flow-visualization-tool#61**)** ( 5 hours)
  • Bug fix of edges stuck together (Issue #180)
  • Visualize private persons as aggregated node (Issue #211) (1,5 hours)
  • Visualize SEB customer's accounts as currency nodes (Issue #209) (4 hours)
  • Create group node to group customer's accounts (Issue #208) (2 hours)
  • Visualize cash fow edge thickness based on flow size (Issue #206) (45 min)

5. Applying filters frontend (20 hours total)

  • Add country filter UI (Issue #86)
  • Add currency filter UI (Issue #79)
  • Add UI for selecting a timeframe (Issue #222)
  • Add UI to select average transactions amount (Issue #95)
  • Add UI to select transactions by frequency (Issue #89)
  • Create UI component for time ranges (Issue #108)

6. Other frontend tasks (10 hours total)

  • Create custom time ranges (Issue #106) ( 5 hours)
  • Create input to send top n number of counterparties (Issue #214), (Issue #215) (5 hours)

7. Backend endpoint related tasks (17 hours total)

  • Create net flow calculation logic (Issue #62) ( 2 hours)
  • Extend backend to calculate average transactions (Issue #93)
  • Extend backend to calculate frequency (Issue #88)
  • Add statistics to transaction edges (Issue #93)
  • Calculate transaction amount in different types (Issue #216)
  • Amend external-transfers endpoint to select top n counterparties (Issue #203) ( 1hour 30 min)
  • Add private person node under transactions (Issue #202) (1 hour 30 min)
  • Create endpoint for incoming and outgoing transactions for my group (Issue #184) ( 3 hours)
  • Database corrections and table altering (Issue #201), (Issue #182) (3 hours)

8. Automated Testing (16 hours total)

  • Create automated tests for two core use cases, including system tests for cash flow filtering and transaction analysis.

9. Continuous Integration (CI) and Release Notes (4 hours)

  • Modify CI and run tests, add pipeline to MR. (Issue #235) ( 4 hours)
  • Provide detailed release notes for the iteration, highlighting new features, modified functionality, and known bugs.(Issue #234) ( 3 hours)

10. Requirements Documentation (30 hours)

  • Document all finalized requirements in individual wiki pages.
  • Track and document any changes or updates based on customer feedback.

11. Collaboration and Issue Tracking (16 hours)

  • Regularly commit code linked to tasks in the issue tracker.
  • Keep the issue tracker up to date, tracking bugs and completed tasks.
  • Record meeting minutes with customers and update requirements accordingly.

Deliverables:

  • Core functionality for filtering and analyzing cash flows.
  • UI for filtering transactions and visualizations based on customer requirements.
  • Visual representations (graphs) for transaction amounts, frequency, and net flow.
  • Automated tests covering major use cases.
  • Continuous Integration pipeline with automated builds and tests.
  • Updated requirements documentation in the Wiki.
  • Detailed release notes for this iteration.

Iteration 4: Final Features and System Optimization (3 Weeks, 221 Hours Total)

Goals

The goal of this iteration is to finalize the system by optimizing key features for comprehensive cash flow analysis. This includes prioritizing partnerships, enabling detailed transaction analysis, and optimizing usability and performance, especially for visualizing and sorting cash flow data.

Use Cases

  • UC 6: Comprehensive Cash Flow Analysis by Amount and Frequency
  • UC 7: Prioritizing Key Partnerships Based on Cash Flow Data
  • UC 8: Analyze Outgoing Transactions to Key Partners by Amount and Frequency

Tasks

1. Data Related Tasks (8 hours)

  • Set up scripts to create a large amount of data (Issue #97): 8 hours

2. Graph Visualization (66 hours 45 minutes)

  • Display payment amounts in different representations (Issue #215, #217): 2 hours
  • Visualize counterparties by bank country (Issue #83): 8 hours
  • View average frequency of transactions (Issue #87): 8 hours
  • Visualize accounts as nodes for selected counterparties (Issue #227): 32 hours
  • Create front-end counterparty selection component (Issue #229): 16 hours
  • Edges of the graph show the total amount of transactions (Issue #230): 45 minutes

3. Backend (28 hours)

  • Implement country-based filtering (Issue #85): 4 hours
  • Filter by payment channel type (Issue #226): 8 hours
  • Endpoint that returns counterparties based on names (Issue #228): 16 hours

4. Filtering (12 hours)

  • Create selection component for top companies within countries (Issue #86): 4 hours
  • Filtering by postal codes (Issue #225): 8 hours

5. Table (20 hours)

  • List external transactions of a single SEB customer company (Issue #118): 3 hours
  • List internal transactions of a single SEB customer company (Issue #131): 3 hours
  • Make table columns sortable (Issue #219): 2 hours
  • Add option to sort by frequency (Issue #116): 2 hours
  • Sort the table by the count of transactions (Issue #117): 2 hours
  • List companies in the SME or Corporate category sorted by transaction frequency to my company (Issue #113): 3 hours
  • List companies in the SME or Corporate category sorted by transaction count from my company (Issue #19): 3 hours
  • A table displaying the net cash flows between SEB customers and counterparties, (Issue #205 ): 2 hours

6. Customer Feedback (6 hours)

  • Gather customer feedback on delivered features: 3 hours
  • Register customer-reported bugs or issues for tracking: 3 hours

7. Application Functionality Testing (16 hours)

  • Ensure all defined requirements are covered by the application's functionality: 8 hours
  • Perform manual verification to compare requirements with the implemented features: 8 hours

8. Automated Tests (14 hours)

  • Write automated tests covering all core use cases: 10 hours
  • Create reproducible tests that run without human intervention: 4 hours

9. Continuous Integration (CI) (8 hours)

  • Ensure the CI pipeline handles all dependencies, builds, deploys, and tests the application: 6 hours
  • Monitor CI runs to detect and fix any build or test failures: 2 hours

10. Internal Acceptance Testing (16 hours)

  • Conduct manual verification for obvious bugs: 10 hours
  • Document the internal acceptance tests in the Wiki: 6 hours

11. Non-Functional Requirements Verification (30 hours)

  • Perform stress tests to verify performance requirements using tools like JMeter: 24 hours
  • Monitor at least five end users to verify usability requirements and document results: 6 hours

12. Release Notes (3 hours)

  • Write detailed release notes covering added/modified functionality, fixed bugs, and known issues (Issue #239): 3 hours

13. Response to Peer-Review (8 hours)

  • Analyze peer-review feedback: 4 hours
  • Post a response to the peer-review in the Wiki: 4 hours

14. Bugs and Issues (4 hours 50 minutes)

  • Application page refresh does not work (Issue #179): 20 minutes
  • Mouse click + drag on table displays a duplicate table on screen (Issue #236): 30 minutes
  • Scrolling table makes numbers/text appear slightly blurred (Issue #237): 1 hour
  • Each click on "Visualize" button opens a new table on top of the existing table (Issue #238): 2 hours

Deliverables

  • Finalized system covering comprehensive cash flow analysis.
  • Full implementation of features related to filtering, sorting, and transaction analysis.
  • Documentation of internal acceptance tests and non-functional requirements testing.
  • Stress tests for performance and user monitoring for usability verification.
  • Response to peer-review and final release notes.
  • Stable, tested system with deployment via CI pipeline.