PROJECT JOURNAL

Team Members

APIs created on Spring Boot Framework.
- Programming Language: Java
- Input and Output: Json
- Added Validation and error handling
Database used: MySQL
For transactions part, transfer between accounts, recurring transfer, recurring bill payment, manual refunds by the admin, adding credit would need either to deposit or withdraw money from saving or checking account to complete transaction
An interface called "AddTransactionCustomInterface" was created so that all the functionalities that perform transactions would be performing transactions using this interface.
Two more additional interfaces- "SavingAccountCustomInterface" and "CheckingAccountCustomInterface" were created to perform deposit and withdraw functions for transacting through the accounts.

Meeting Date	What tasks did I work on / complete?	What am I planning to work on next?	What tasks are blocked?
October 26	Understand Requirements	Create Meeting Minute Documents	None
November 2	Create Meeting Minute Documents	Set Up a MySQL database on an EC2	None
November 9	Setting Up Database	Learn Spring Boot	None
November 20	Learn Spring Boot	Add, get, and delete user	None
November 23	Add, get, and delete user	Check due balances, Check balance, close existing account. Finish meeting minutes docs. Create wireframes. Do extra credit.	All APIs I am planning on work on next are blocked. 'Creating accounts' needs to be finished first. I can't work on the extra credit until the APIs are done.
December 4	Check due balances, Check balance, close existing account.	Few days to work on the wireframes and extra credit	Extra credit can't get started until everything else that is required is finished.

Meeting Date	What tasks did I work on / complete?	What am I planning to work on next?	What tasks are blocked?
October 26	Understand Requirements	Explore frameworks for APIs creation & Decide technology stack	None
November 2	Explored different frameworks and Finalized Spring Boot	Create product backlog and design database schema and tables creation	None
November 9	Designed Datbase Schema & Product Backlog	Learn Spring Boot	None
November 20	Learn Spring Boot and populated tables with dummy data	Create Checking and Savings Account	None
November 23	Created Checking and Savings Account APIs	Modify account APIs and implement internal transfers and view/search transactions	Transactions API
December 4	Transfer between accounts & View/Search transactions	Validations, UI Wireframes	None

Meeting Date	What tasks did I work on / complete?	What am I planning to work on next?	What tasks are blocked?
October 26	Understand Requirements	Decide the technology stack	None
November 2	Decided the technology stack as Spring Boot, MySQL database, IDE- STS/IntelliJ	Design database schema	Product backlog
November 9	Designed database schema, product backlog	Learn Spring Boot- use of tables with Spring Boot, knowledge of REST APIs	None
November 20	Learnt Spring boot, REST APIs, connecting MySQL to application	Update user	Add user functionality
November 23	Updated user/customer's phone number, email, mailing address	Adding manual transactions, credit	Transactions table, account creation
December 4	Added manual transactions, credit, approve/deny transactions, implemented deposit and withdraw functions that form basis for all transactions, recurring transfer	Adding validations, component diagram

Meeting Date	What tasks did I work on / complete?	What am I planning to work on next?	What tasks are blocked?
October 26	Understand Requirements	Design Datbase Schema/Product Backlog	None
November 2	Design Database schema	Learn Spring boot	None
November 9	Learnt Spring boot	ADD Payee/Remove Payee	None
November 20	Add Payee/Remove Payee	Approve Payee	None
November 23	Approve Payee	One time/Recurring bill payment	Transactions API
December 4	One time bills/recurring bills	Validations,UI Wireframes/Burndown	None

Meeting Date	XP Core Value	Explanation
October 26	Communication	First time we met and everyone encouraged communication by discussing what the project was about and what we needed to do next.
November 2	Communication	We discussed various programming languages and frameworks to use in this project. Everyone was participating and giving their own opinion.
November 9	Communication	During this meeting we worked on the backlog and agreed on how many hours each task would take. Everyone participated.
November 20	Feedback	We met today to check how everything was going with the project. We all gave our feedback about each others contributions so far and made changes according to it.
November 23	Simplicity	We kept this meeting simple. We met online for a short time and divided tasks before the long break.
December 4	Communication	The team got together and discussed solutions for some problems in the code. We helped each other a lot by communicationg since we all came up with solutions.

Meeting Date	XP Core Value	Explanation
October 26	Communication	We met and discussed the problem statement and understood the requirements
November 2	Communication	We communicated face to face and expressed ourselves clearly regarding our opinions and explorations of which technology stack would be better to opt
November 9	Communication	Coordinated and finalized the product backlog and no. of hours required for completion of each task
November 20	Simplicity	We shortlisted what was required for the project and divided it such that it would create least dependency and complications
November 23	Feedback	We communicated what tasks were blocked and everyone took apt steps to resolve the blockage based on the feedback each one shared and received
December 4	Communication	Shared the implementation to reduce workload of team members and helped overcome code redundancy/duplication and inconsistency conflicts

Meeting Date	XP Core Value	Explanation
October 26	Communication	As a champion of communication value, I encouraged communication in the team by arranging standup meetings every week
November 2	Communication	Asked my team members to share their take on various available frameworks
November 9	Communication	Engaged my team members in conversation about the database schema, product backlog
November 20	Communication	Encouraged everyone to ask doubts to each other, asking how a functionality is implemented
November 23	Communication	Engaged my team members in conversation about their current work, what they're planning to work on next
December 4	Communication	Sharing the implementation helped in reducing workload of individual team member

Meeting Date	XP Core Value	Explanation
October 26	Communication	We communicated face to face regularly.
November 2	Communication	We Created Backlog effectively by discussing various aspects of the project
November 9	Simplicity	We designed what was required for the project and no more
November 20	Feedback	We Demonstrated and listend carefully and made any changes needed. We talked about the project and adapt our process to it, not the other way around.
November 23	Communication	We worked together on everything from requirements to code. We created the best solution to our problem that we can together.
December 4	Communication	We sat together and implemented the pending backlogs by bringing them to none