Tradeverse Forum is a web application designed to facilitate discussions on financial news, analyses, and related topics. It provides users with a collaborative platform to share insights and engage in interactive discussions about various financial assets, aided by real-time data.

The Tradeverse project is successfully deployed and operational. The following functionalities have been implemented:

• User Registration and Authentication:
  • Users can register and log in securely using JWT-based authentication.
• Interactive Features:
  • Users can create posts, comment, like/dislike, and interact with others' content.
  • Users can annotate posts and comments using the W3C Annotation Standard.
  • Annotations are displayed on the right side of the screen, allowing users to view and interact with them.
  • When a user mentions a stock in their post, an interactive chart showing recent price changes is displayed. This enhances posts with real-time stock data visualization.
• User Profiles and Portfolios:
  • Users can create and manage a personal portfolio.
  • Profiles include customizable user information and user types selected during registration.
  • User types include: Beginner, Day Trader, Investor, Finance Enthusiast, and Finance Analyst.
• Subforums:
  • Subforums enable users to participate in niche discussions, e.g., NASDAQ, Crypto.
  • New subforums can be created dynamically to expand the scope of the forum.

1. The platform is fully deployed and accessible to users.
2. Real-time updates on financial assets are integrated, enhancing the interactivity of discussions.
3. W3C standards for annotations are implemented, elevating the platform's compliance and usability.
4. An extensive and intuitive user interface supports both beginners and seasoned finance professionals.

The project is on track, with all major features implemented and tested. Documentation and deployment processes have been streamlined to ensure ease of maintenance and scalability.

We are excited to announce the final release of the Tradeverse Forum application! This update introduces improved API services with richer data, and expanded functionality with better ui and ux design across web and mobile platforms. This release marks a significant increase in bringin the existing features to a higher level, creating new experiences for our users.

• Users now are able to search for tags in the explore page. Additionally, they can go to the detail screen for the tags and see related posts.

• Post content can now include different references such as users, assets and tags. Users can see the details of this references simply by clicking on them.

• Now having an asset detail screen, users can see the current valuation of the selected asset and choose a date range when viewing the graph to include more insight on the asset.
• Besides the asset graph, a decent description for the asset itself is placed in this screen. Now a user can understand about the assets of which he is not familiar.

• User can see his/her portfolio in a more detailed way with the assets having the real current value fetched dynamically. Also one can see the total value of his portfolio assets.

• Users can now annotate on a desired part of a post which improves the community interaction. A user can all the annotations made on posts to get insights from other people.

• Backend: Spring Boot (Java 17), MySQL, JWT, Docker, Swagger UI
• Frontend: React for web, Expo for mobile
• Development Tools: Docker for containerization, Node.js for mobile development

• Refer to the updated README file for setup instructions, including prerequisites, cloning the repository, configuring environment variables, and running the application using Docker.

This release adds significant new capabilities to the Tradeverse Forum, enhancing its functionality and usability. The improvement on Mobile, Web applications and the expanded API endpoints empower both developers and end-users, enabling better interaction and and more vibrant app community.

Based on previous milestones, our team implemented several changes to improve the development process. One significant improvement was optimizing the backend to make the application faster. This included adding new endpoints and ensuring the backend completed its tasks earlier, giving the frontend team more time to connect with and test API endpoints effectively.

Additionally, we avoided making last-minute changes, which significantly reduced the risk of breaking something critical right before deadlines. This was achieved by thoroughly planning every step in advance and prioritizing robust testing during development.

Another key improvement was enhancing communication within the team. We ensured that everyone stayed aligned on goals and progress, which minimized misunderstandings and improved collaboration. Collectively, these changes led to smoother development cycles, higher-quality deliverables, and an overall more efficient project workflow.

Reflecting on our Final Milestone Demo, we gained valuable insights and lessons from the feedback:

1. User Information Visibility
   Users were unable to identify others beyond profile pictures, resulting in lost information. This highlighted the importance of designing interfaces that make key user details readily visible.

2. Data Structure and Presentation
   While Wikidata was used effectively for assets, subform parts lacked similar support. Additionally, timestamps embedded within text made them less accessible, emphasizing the importance of presenting such information in distinct formats for clarity.

3. Dynamic Features and Historical Data
   The dynamic nature of the news was well-received; however, the absence of historical data for assets pointed to an area where a broader perspective could have enriched the experience.

4. Search Functionality
   The search feature for assets lacked semantic capabilities, it is hardcoded. This limited its usability, and incorporating semantic search, possibly leveraging Wikidata, could have made it far more powerful.

5. Tags and Annotations
   Tags, being derived directly from user-generated text, lacked semantic depth. Annotations, especially on mobile, were unavailable, and requiring users to click to view them diminished usability. Displaying annotations directly could have enhanced the user experience significantly.

This milestone taught us the importance of designing for clarity, accessibility, and semantic richness. While we were unable to address these aspects within the scope of the project, the lessons learned provide a foundation for improving similar projects in the future.

During our project, we had some setbacks including both minor and major ones as a team. Our first -and probably the foremost- issue was the general time management & effort distribution during the project. Most of our contributions were provided just some days ago between our major milestones (Customer Presentation 1,2; and the Final Milestone) and other times our repository was much more stable. Our overall effort can be more equally distributed which would provide a constant ongoing progess to the project, as well as establishing more harmony between our subteams (web, mobile, and backend) and lower our stress accordingly.

Another thing we might have done differently is the communication & progress tracking inside and in-between frontend and backend teams. At some parts of the project, the frontend teams were way ahead of the backend team, which resulted in a rush at the backend team trying to provide necessary endpoints to the frontend teams, while frontend teams were at the same time trying to connect their pages to these endpoints; and when everything was combined with code bugs and lack of time, things did not go very well for us unfortunately. Some other things which can be done differently include more equal task distribution inside our subteams, using GitHub in a more effective manner, etc.

Some signs and their meanings are explained below:

❌: Not started

⚠️: Partially implemented/In Progress

✅: Completed (implemented, tested, documented, deployed)

• 1.1. User Requirements

• 1.1.1. Account

  • 1.1.1.1. ✅ Users shall be able to open an account.
    • 1.1.1.1.1. ✅ Users shall enter their unique e-mail, unique username, and password to open an account to become a registered user.
      • 1.1.1.1.1.1. ✅ Registered users shall be able to enter the application using their own username and password.
      • 1.1.1.1.1.2. ✅ Registered users should be able to make the application remember their username and password.
    • 1.1.1.1.2. ✅ Registered users shall be able to put up a profile picture.
      • 1.1.1.1.2.1. ❌ Registered users shall be able to change their profile pictures.
      • 1.1.1.1.2.2. ❌ Registered users shall be able to delete their profile pictures.
    • 1.1.1.1.3. ✅ Registered users shall be able to write their personal information in their personal pages while either creating their account or after registering the application.
      • 1.1.1.1.3.1. ✅ Registered users shall be able to change this information.
  • 1.1.1.2. ✅ Guest users shall be able to use the application.
    • 1.1.1.2.1. ✅ Guest users shall be able to see the content of the forum.
  • 1.1.1.3. ✅ Registered users shall enter their e-mail or username and password to re-enter their account if they are logged out.
  • 1.1.1.4. ❌ Admin user shall be able to block another authenticated user.
  • 1.1.1.5. ❌ Admin users shall be able to unblock another authenticated user.
  • 1.1.1.6. ❌ Registered users shall be able to delete their accounts.
  • 1.1.1.7. ❌ Registered users shall be able to change their password.
  • 1.1.1.8. ✅ Registered users shall be able to follow the subforum topics.
  • 1.1.1.9. ✅ Registered users shall be able to unfollow the subforum topics.
  • 1.1.1.10. ✅ Registered users shall be able to follow the other users.
  • 1.1.1.11. ✅ Registered users shall be able to unfollow the other users.
  • 1.1.1.12. ✅ Registered users shall be able to choose a user tag according to their interests in finance.
    • 1.1.1.12.1. ✅ Registered users shall be able to choose one of the four user tags, which are investors, day traders, Financial Analysts/Researchers, or Financial Enthusiasts.
    • 1.1.1.12.2. ✅ Registered users shall be able to change their user tag to another user tag.

• 1.1.2. Posts

  • 1.1.2.1. ✅ Registered users shall be able to post forum posts.
  • 1.1.2.2. ✅ Registered users shall be able to like posts.
    • 1.1.2.2.1. ✅ Users shall be able to see how many users have liked a post.
  • 1.1.2.3. ✅ Registered users shall be able to unlike a post.
  • 1.1.2.4. ✅ Registered users shall be able to dislike posts.
    • 1.1.2.4.1. ✅ Users shall be able to see how many users have disliked a post.
  • 1.1.2.5. ✅ Registered users shall be able to remove a dislike from a post.
  • 1.1.2.6. ✅ Registered users shall be able to comment on posts.
    • 1.1.2.6.1. ✅ Users shall be able to see the comments.
  • 1.1.2.7. ✅ Registered users shall be able to delete their comment on a post.
  • 1.1.2.8. ✅ Users shall be able to find information about the financial assets in the post.
  • 1.1.2.10. ✅ Guest users shall be able to post charts of financial assets.
  • 1.1.2.11. ✅ Registered users shall be able to delete their posts.

• 1.1.3. Search

  • 1.1.3.1. ✅ Users shall be able to search forums based on their name.
  • 1.1.3.2. ✅ Users should be able to search post and forums by their related tags.

• 1.1.4.1 ✅ Registered users shall be able to create new topics related to financial assets.
• 1.1.4.2 ✅ Registered users shall be able to like, unlike, dislike, and undislike posts.
• 1.1.4.3 ✅ Registered users shall be able to write comments under posts.
• 1.1.4.4 ✅ Registered users shall be able to delete their own posts and comments.
• 1.1.4.5 ❌ Registered users shall be able to edit their own posts and comments.
• 1.1.4.6 ✅ Registered users shall be able to add a title, description, and public tags while creating a post.
• 1.1.4.7 ✅ Registered users shall be able to upload images while creating a post.
• 1.1.4.8 ✅ Registered users shall be able to comment under posts and reply to comments.
• 1.1.4.9 ✅ Registered users shall be able to create posts to share opinions, questions, etc.

• 1.1.5.1 ✅ Admin users shall be able to create subforums (e.g., Bitcoin, Borsa Istanbul).
• 1.1.5.2 ✅ Admin users shall be able to delete subforums.
• 1.1.5.3 ❌ Admin users shall be able to ban users.
• 1.1.5.4 ❌ Admin users shall be able to add only one base tag to the subforums.

• 1.1.6.1 ⚠️ Registered user shall be able to categorize news articles by asset type and relevance.
• 1.1.6.2 ⚠️ Registered user shall be able to filter forum news based on desired financial assets.
• 1.1.6.3 ⚠️ Registered user should be able to set up personalized news feeds for selected assets.

• 1.1.7.1 ❌ Registered user shall be able to create and share their own financial portfolios.
• 1.1.7.2 ❌ Registered user should be able to set privacy levels for their portfolios (public, friends-only, private).
• 1.1.7.3 ✅ Registered user shall be able to view portfolio performance metrics and analytics.
• 1.1.7.4 ✅ The registered user who has portfolios in the application shall not be able to share his/her portfolios on feeds.
• 1.1.7.5 ❌ The registered user who has portfolios in the application shall be able to change the visibility of his/her portfolios on his/her profile page.

• 1.2.1.1 ✅ The system shall be able to provide the current values of financial assets mentioned in the topics.
• 1.2.1.2 ✅ The system shall be able to retrieve financial data from reliable third-party APIs.
• 1.2.1.3 ✅ The system should be able to update financial asset values in real-time or at regular intervals.

• 1.2.2.1 ✅ The system shall be able to provide a search function to find topics, users, and assets.
• 1.2.2.2 ✅ The system should be able to offer advanced search filters (e.g., date range, asset type).

• 2.1.1 ✅ The system shall load pages within 6 seconds under normal network conditions.
• 2.1.2 ✅ The system should handle up to 100 concurrent users without performance degradation.

• 2.2.1 ✅ The system shall encrypt user passwords and sensitive data.
• 2.2.2 ✅ The system should implement measures against common web vulnerabilities (e.g., SQL injection, XSS).
• 2.2.3 ✅ The system shall comply with relevant data protection regulations.

• 2.3.1 ✅ The system shall have an intuitive and user-friendly interface.
• 2.3.2 ✅ The system should be accessible on various devices (desktop, tablet, mobile).
• 2.3.3 ✅ The system should follow UI/UX best practices for navigation and layout.
• 2.3.4 ✅ The system shall allow easy navigation between different sections of the forum.

• 2.4.1 ✅ The system should be designed in a sustainable manner in order to accommodate future growth in user base and functionality.
• 2.4.2 ✅ The system shall use scalable technologies and architectures.

• 2.5.1 ✅ The system shall have an uptime of 99.5% excluding scheduled maintenance.
• 2.5.2 ❌ The system should implement data backup and recovery mechanisms.

• 2.6.1 Annotation Capability

  • 2.6.1.1 ✅ The system shall support W3C Web Annotation standards, enabling users to annotate posts, comments, and financial analysis sections with text, tags, and links.
  • 2.6.1.2 ✅ The system shall support various annotation types, such as highlighting, commenting, and linking within content.

• 2.6.2 Annotation Storage and Retrieval

  • 2.6.2.1 ✅ The system shall securely store annotations, associating them with the relevant content and users.
  • 2.6.2.2 ✅ Users shall be able to retrieve their own and view others' annotations on relevant content.

• 2.6.3 W3C Compliance

  • 2.6.3.1 ✅ The system shall adhere to W3C Web Annotation standards, ensuring compatibility and consistency with external platforms and future technologies.

http://35.246.188.121:8080/swagger-ui/index.html#/

http://35.246.188.121:8080

This API provides a set of endpoints for managing users, subforums, posts, comments, portfolios, and assets in the application. Below is an overview of each API group, explaining their purpose and usage.

Endpoints related to user management:

• Set User Details: Updates user-specific information such as email, bio, and profile photo. (POST /api/user/set-user-details)
• Get Profile: Fetches the profile details of a user by username. (GET /api/user/profile)
• Get User Details: Fethes user-specific information such as email, bio, and profile photo. (GET /api/user/set-user-details/{username})

Endpoints for managing subforums:

• Create Subforum: Allows authorized users to create a new subforum with a name, description, and tag color. (POST /api/subforum/create)
• Delete Subforum: Deletes a subforum by ID. (POST /api/subforum/delete)
• Follow Subforum: Enables users to follow a subforum for updates. (POST /api/subforum/follow)
• Unfollow Subforum: Unfollows a specific subforum. (POST /api/subforum/unfollow)
• Get Subforum by ID: Retrieves detailed information for a specific subforum by ID. (GET /api/subforum/{id})
• Get Followed Subforums: Lists all subforums followed by the user. (GET /api/subforum/followed)
• Get All Subforums: Retrieves a list of all available subforums. (GET /api/subforum/all)

Endpoints for creating and managing posts:

• Create Post: Lets users create a new post with a title, content, and subforum ID. (POST /api/post/create)
• Delete Post: Deletes a specific post by its ID. (POST /api/post/delete)
• Get Post by ID: Retrieves detailed information for a specific post by ID. (GET /api/post/{id})
• Get Recent Posts: Retrieves a list of the most recent posts. (GET /api/post/recent)
• Get Popular Posts: Retrieves a list of the most popular posts. (GET /api/post/popular)
• Get Posts by User: Fetches all posts created by a specific user. (GET /api/post/get-posts-by-user)
• Get Posts by Tag: Retrieves all posts associated with a specific tag. (GET /api/post/get-posts-by-tag)
• Get Posts by Subforum: Fetches all posts within a specific subforum. (GET /api/post/get-posts-by-subforum)
• Get Posts for You: Displays posts recommended for the user based on preferences. (GET /api/post/for-you)
• Get Posts by Followed Topics: Retrieves posts from subforums the user follows. (GET /api/post/followed-topics)
• Get Posts by Followed People: Retrieves posts created by users followed by the current user. (GET /api/post/followed-people)

Endpoints for managing user portfolios:

• Add Asset to Portfolio: Adds an asset to the user’s portfolio with a specified amount. (POST /api/portfolio/add-asset)
• Get Portfolio: Retrieves all portfolio data for a specific user. (GET /api/portfolio/get-portfolio)
• Get Portfolios by Asset: Fetches portfolios associated with a specific asset. (GET /api/portfolio/by-asset)

Endpoints for commenting on posts:

• Create Comment: Adds a new comment to a specific post. (POST /api/comment/create)
• Delete Comment: Deletes a specific comment by ID. (POST /api/comment/delete)
• Get Comments: Retrieves all comments for a specific post by ID. (GET /api/comment/get-comments)

Endpoints for managing assets:

• Add Asset: Allows adding a new asset with details like name, symbol, and image URL. (POST /api/asset/add)
• Get Asset Details: Fetches detailed information about a specific asset. (POST /api/asset/details)
• Get Asset by ID: Retrieves detailed information for an asset by its ID. (GET /api/asset/{id})
• Get Asset Chart: Fetches historical chart data for a specific asset. (GET /api/asset/chart)
• Get All Assets: Retrieves a list of all available assets. (GET /api/asset/all)

Endpoints for user authentication:

• Register: Creates a new user account with a username, email, and password. (POST /api/auth/register)
• Login: Authenticates a user and provides a token. (POST /api/auth/login)
• Validate Token: Checks the validity of the provided authentication token. (GET /api/auth/validate-token)

Endpoints for searching resources:

• Search Users: Retrieves a list of users matching the keyword. (GET /api/search/user)
• Search Tags: Fetches tags associated with the keyword. (GET /api/search/tag)
• Search Subforums: Retrieves subforums related to the keyword. (GET /api/search/subforum)
• Search Posts: Finds posts related to the keyword. (GET /api/search/post)
• Search Assets: Finds assets matching the keyword. (GET /api/search/asset)

Endpoints for managing post likes:

• Like Post: Adds a like to a specific post. (POST /api/like/like-post)
• Unlike Post: Removes a like from a specific post. (POST /api/like/unlike-post)
• Get Liked Posts: Retrieves all posts liked by the user. (GET /api/like/get-liked-posts)

Endpoints for managing user follow relationships:

• Follow User: Adds a user to the current user’s follow list. (POST /api/follow/follow-user)
• Unfollow User: Removes a user from the current user’s follow list. (POST /api/follow/unfollow-user)
• Get Followings: Retrieves a list of users followed by the current user. (GET /api/follow/get-followings)
• Get Followers: Retrieves a list of users following the current user. (GET /api/follow/get-followers)

Endpoints for managing post dislikes:

• Dislike Post: Adds a dislike to a specific post. (POST /api/dislike/dislike-post)
• Undislike Post: Removes a dislike from a specific post. (POST /api/dislike/undislike-post)

Endpoints for managing images:

• Get Image by Filename: Retrieves an image file by its filename. (GET /api/images/{filename})

Endpoint: GET /api/portfolio/get-portfolio

• username (string): The username of the account.

GET http://35.246.188.121:8080/api/portfolio/get-portfolio?username=johndoe

 {
  "isSuccessful": true,
  "message": "Portfolios retrieved successfully",
  "username": null,
  "portfolios": [
    {
      "id": 1,
      "asset": {
        "id": 3,
        "name": "Amazon.com, Inc.",
        "yahooFinanceSymbol": "AMZN",
        "tradingViewSymbol": "NASDAQ:AMZN",
        "imageUrl": "https://static2.finnhub.io/file/publicdatany/finnhubimage/stock_logo/AMZN.png"
      },
      "amount": 1.0,
      "totalCurrentPrice": 223.2899932861328
    },
    {
      "id": 18,
      "asset": {
        "id": 1,
        "name": "Apple Inc.",
        "yahooFinanceSymbol": "AAPL",
        "tradingViewSymbol": "NASDAQ:AAPL",
        "imageUrl": "https://static2.finnhub.io/file/publicdatany/finnhubimage/stock_logo/AAPL.png"
      },
      "amount": 4.0,
      "totalCurrentPrice": 999.1599731445312
    }
  ],
  "totalValue": 1222.449966430664
}

Endpoint: POST /api/post/create

• Authorization (string): Bearer token for authentication (Bearer {token}).

{
  "title": "BIST 100 Post performance 📈",
  "content": [
    {
      "type": "text",
      "value": "Did you know the BIST 100 reflects the performance of Turkey's top 100 companies?\nWhich sectors do you think perform best in this index? 🧐"
    },
    {
      "type": "chart",
      "value": "BIST:XU100"
    }
  ],
  "subforumID": 2
}

{
  "isSuccessful": true,
  "message": "Post created successfully",
  "id": 73
}

Endpoint: GET /api/comment/get-comments

• postId (int): The ID of the post to retrieve comments for.

GET http://35.246.188.121:8080/api/comment/get-comments?postId=24

[
  {
    "id": 6,
    "content": [
      {
        "type": "text",
        "value": "Why are manufacturing and exports important?"
      }
    ],
    "createdBy": "ege_yalin",
    "postID": 24,
    "parentCommentID": null,
    "creationDate": "2024-12-17T09:14:44.500795",
    "replies": [
      {
        "id": 8,
        "content": [
          {
            "type": "text",
            "value": "Turkey’s manufacturing industry produces goods like cars, textiles, and electronics, which are sold to other countries (exports). This brings money into the economy and helps companies grow."
          }
        ],
        "createdBy": "warrenthebuff",
        "postID": 24,
        "parentCommentID": 6,
        "creationDate": "2024-12-17T09:17:33.065789",
        "replies": [
          {
            "id": 9,
            "content": [
              {
                "type": "text",
                "value": "Thanks!"
              }
            ],
            "createdBy": "ege_yalin",
            "postID": 24,
            "parentCommentID": 8,
            "creationDate": "2024-12-17T09:20:02.817937",
            "replies": []
          }
        ]
      }
    ]
  },
  {
    "id": 7,
    "content": [
      {
        "type": "text",
        "value": "What is value over hype?"
      }
    ],
    "createdBy": "ege_yalin",
    "postID": 24,
    "parentCommentID": null,
    "creationDate": "2024-12-17T09:16:03.306361",
    "replies": []
  },
  {
    "id": 14,
    "content": [
      {
        "type": "text",
        "value": "Interesting take! For beginners like me, what’s the best way to start analyzing these 'rising star' companies on the BIST? Any tools or resources you recommend? 📈"
      }
    ],
    "createdBy": "karatashsyn",
    "postID": 24,
    "parentCommentID": null,
    "creationDate": "2024-12-17T11:25:28.104471",
    "replies": []
  }
]

Related ScreenShots will be given in same order.

• Profile Settings
• Profile
• Add Asset
• Asset Detail
• Create
• Create Post
• Create Subforum
• Explore
• Search Results
• Followed Topics
• Follower Users
• Following Users
• Home
• Portfolio
• Post Detail
• User Profile
• Subforum Detail
• Tag Detail
• Welcoming Screen

• Annotation
• Comment
• Feed
• Post
• Post Header
• Home Page
• Subforum Navbar

• Standard Adoption:
  We adopted the W3C Web Annotation Data Model to structure annotations, ensuring compliance with international web standards.

• Annotation Features:

  • Users can annotate text within posts and comments.
  • Annotations are displayed contextually on the right-hand side of the screen for easy accessibility.
  • Both posts and comments can have multiple annotations, allowing users to highlight and discuss specific parts.

• Backend Implementation:

  • The backend was designed to handle storing and retrieving annotations as JSON-LD (Linked Data).
  • Annotations are linked to specific posts or comments using unique identifiers.
  • RESTful endpoints for annotation CRUD (Create, Read, Update, Delete) operations were developed.

• Frontend Integration:

  • A user-friendly annotation tool was integrated into the post/comment view. Users can select text and create an annotation with a simple interface.
  • Annotations are displayed in a sidebar, showing details such as the selected text, user who created the annotation, and any associated comments.

• Real-Time Updates:

  • Annotations are synced in real time using WebSockets. Users viewing a post can see new annotations without refreshing the page.

• Permissions and Visibility:

  • Annotations are user-specific, with options to make them public or private.
  • Public annotations are visible to all users, fostering collaborative discussions.
  • Private annotations are restricted to the user who created them.

• Use Cases:

  • Highlighting key points in financial analyses.
  • Adding clarifications or insights to specific phrases in posts.
  • Enhancing discussions with targeted feedback or questions.

Ege Yalın is a student at Dokuz Eylül University studying Economics. He is a freshman. He wants to explore finance. Also, he needs money so he wants to get an insight how to make money from stock exchange. When they are in a microeconomic class, their professor suggest Tradeverse application. After class, Ege wants to give a chance to Tradeverse. At first sight, he enters as a guest. After he spends time in the application, he likes the Tradeverse. He decides to sign up, and put a tag as "beginner". He follows his professor, Warren Buffet and Doran Acemoğlu since he trusts their advices. After that, he sees the post of his professor. He wants to put some questions as annotation about what the professor writes in his post. Since he has some assets in stock exchange, he wants to share his portfolio with other users. Then, he searches the assets to add and add his assets. Then he goes to search page to see recent posts. He faces that Aygaz assets prices increases, so he wants to get an information about Aygaz. He clicked the asset name and faces the information page about Aygaz. He decides to buy some Aygaz assets, since he thinks that the price of Aygaz is going to increase. He goes back to his portfolio and add Aygaz assets. He finally goes to for you page and looks for the posts of followed topics and followed users.

1-) Guest User, Login & Register Properties: "At first sight, he enters as a guest. After he spends time in the application, he likes the Tradeverse. He decides to sign up..."

2-) User Tags: "... and put a tag as "beginner""

3-) Following Other Users: "He follows his professor, Warren Buffet and Doran Acemoğlu since he trusts their advices."

4-) Annotation Standard: "He wants to put some questions as annotation about what the professor writes in his post."

5-) Search Functionality, seeing recent posts: "Then, he searches the assets to add and add his assets. Then he goes to search page to see recent posts."

6-) Asset Details: "He clicked the asset name and faces the information page about Aygaz."

7-) Adding Assets to Portfolio: "He goes back to his portfolio and add Aygaz assets."

8-) "For You", "Followed Topics/Subforums", "Followed Users' Posts" Pages: "He finally goes to for you page and looks for the posts of followed topics and followed users."

• Leading and improving the mobile application for the milestone 3.
• Establishing connection to backend for newly added endpoints.
• Refactoring on mobile application logic relating to other endpoints both on programming and user experience level.
• Fixing network problem on the APK.

• Connected new backend endpoints to the mobile application.
• Determined backend response types and logics for some endpoints.
• Refactored mobile app according to new/modified endpoints.
• Documented mobile related parts of the Customer Milestone 3 Report
• Refactored mobile app's ui by creating skeleton loaders.
• Fixed major Network Problem occuring on APK.
• Added new feature named tag detail page which returns posts including the tag.
• Added new feature to post cards which allows user to add references to post for users, assets and tags. User can go to related entity detail page by pressing on them.
• Created Release Notes for the final customer milestone here.

• Throughout Milestone 3, significant improvements were made to the mobile application's architecture to ensure better maintainability, scalability, and user experience.
• Collaboration with the backend team was key in defining and integrating new endpoint logic, ensuring seamless communication between frontend and backend.
• On the APK, I was constantly ecountering with the error that blocks our http requests to backend API. I researched and found that this is a new security measure for the new Android versions. So it was blocking http and forcing https for each network requests. Solution was to modify the application config so that android will allow our app to use http on the requests.
• Introducing skeleton loaders in the UI enhanced the perceived performance and user experience by providing immediate visual feedback during loading times.
• The addition of rich post content features, such as tag detail pages and post references, improved the app's functionality, making it more dynamic and user-centric. The refactored navigation structure not only simplified user journeys but also gave a user consistency across different parts of the application.
• One Mistake I made: On the refactor branch, I, unintentionally, pushed some improvements that should have been opened as a seperate PR. Even the improvements were not huge, it would be more convenient to have them in seperate PRs.

• Mobile aplication page design, writing/editing required functions and establishing connections between pages and backend endpoints
• Writing some reports (Most of Customer Presentation 2 Report, some parts of the Final Milestone Report, as well as some of the Lab reports)
• Giving support to team members in related tasks, especially during Lab hours

• Connecting (Mobile) Profile Update page with its related endpoint #525
• Fixing Asset Details Screen
• Helped Hüseyin Karataş for Fixing Portfolio Screen #526
• Added Tag Detail Screen with required endpoint connections with help of Hüseyin Karataş #530
• Added some unit tests #528
• Helped the team for adding realistic data to our application
• Writing some parts of the Final Milestone Report
• Helped Nazlıcan Aka and Gülşen Sabak for writing the Final Milestone Presentation Scenario

• User Service Unit Tests

• As some important tasks in the mobile team were done at the last minute, I could not open related issues for these tasks inside such a hurry; so unfortunately ignored an important software convention. I am sorry about that inconvenience.
• Apart from the tasks explained above, I also helped Hüseyin Karataş while trying to solve the APK Network Problem. He was the one managing to solve the problem, so I did not write this above but here instead.

• Led the development of frontend pages, including critical components and user interaction features.

• Contributed to API development by adding and enhancing endpoints.

• Collaborated with team members to resolve critical issues and improve system performance.

• Solved errors and issues encountered by team members to ensure smooth progress.

• Documented API endpoints with clear examples for efficient onboarding and maintenance.

• Designed and implemented key API endpoints, including the "Get Asset by ID" and "Search Subforums" functionalities.

• Enhanced frontend components and pages, such as the Asset Info Page, Subforum Page, Tag Page, Create Subforum Page, and Search Page, to improve user experience and functionality.

• Created and integrated reusable components, including NewsWidget and ProfileWidget, to streamline UI development.

• Spearheaded API integration efforts, ensuring compatibility and robust interaction between frontend and backend systems.

• Contributed to UI enhancements and styling improvements, aligning with the project’s design standards.

• Actively resolved errors and provided technical support for issues faced by team members.

• Throughout the development process, I demonstrated a high level of effort and responsibility. I consistently responded to issues as soon as possible, ensuring the team’s progress was not hindered. Despite my efforts to foster collaboration and maintain project timelines, some team members were less responsible in their roles. Their lack of accountability often limited our potential to make the forum even better. Additionally, our backend team showed a lack of responsibility at times, requiring frontend members to step in and contribute to the implementation of services. Nevertheless, I took initiative to address these gaps and ensured that the project met its essential goals.

Link for unit tests that I implemented:

1-) Follow service Unit Test

• Led the design and implementation of the personal profile page and user page.
• Developed front-end components and integration with the backend through API connections.
• Managed the routing and navigation to ensure users could easily access their own profiles and view others’ profiles.
• Debugged and resolved issues across various pages to ensure consistent functionality and user experience.

• Created the layout and functionality of the personal profile and user pages, enhancing user interaction with their accounts.
• Integrated API calls to retrieve user data and posts, ensuring real-time updates.
• Implemented routing logic to switch between pages dynamically, improving the overall site navigation.
• Worked collaboratively with other team members to address design and technical challenges.

• For my project, I was in charge of the front-end development, focusing primarily on designing both the personal profile page and the user page. This involved crafting intuitive and visually appealing interfaces, ensuring seamless API connections, efficient routing, and a smooth user experience. I worked through various bugs and errors, optimizing functionality where needed. I made sure that users profiles and other user details are displayed accurately and responsively across the site.

• Present the customer milestone 3.
• Improving the mobile application for the milestone 3.
• Connecting backend endpoints to the mobile application.
• Document integration tests and user tests

• Present the customer milestone 3.
• Connected assigned backend endpoints to mobile application.
• Created screens for mobile application.
• Created integration tests and user tests.

• Link for unit tests that I implemented: Portfolio Service Unit test

• Led the backend development.
• Designed the current backend architecture and distributed tasks among the team.
• Communicated with other teams for feature requests.

• Refactored the entire codebase to reduce technical debt.
• Implemented asset endpoints and created the portfolio logic.
• Scraped Yahoo Finance to retrieve YahooFinance links for assets.
• Redesigned the request/response structure of all subforum, post, and comment endpoints.
• Designed and implemented the "For You" and "Explore" algorithms.
• Reviewed PRs from other backend members and some from other teams.
• Carried Base64 encoded photos to permanent storage to accelerate page-loading.

• Actively collaborated with team members to ensure smooth implementation of features and architectural decisions.
• Supported inter-team efforts by reviewing PRs and providing feedback on changes affecting the backend.

• Written most of the unit tests.
• Changed endpoint responces by requests from frontend.
• Fixed small mistakes in the backend code.
• Implemented search controller.
• Found photos for the assets.

• Collaborate mainly with backend team, and get feedbacks from frontend team.
• Test endpoints.
• Documentation of Milestone-3 report.
• Create project plan.

• Fixed some endpoints according to feedback from the frontend team.
• Return “view counts” for posts.
• Return the date for posts and comments.
• Added unit tests for assets and portfolio endpoints.
• Increased forum activity with posts, comments, and interactions.
• Created the project plan using Project Libre according to progress in the team.
• Uploaded the project plan as a code for public accessibility.
• Separated the subsections of Milestone-3 report among teammates.
• Documented scenario for the milestone-3 presentation for comprehensive coverage of all important features of Tradeverse.
• Took notes during milestone-3 presentation, document reflections from milestone-3 presentation.
• Document process improvements from previous milestones.
• Document API endpoints with 3 important features.
• Documented detailed and well-structured user manual for the system.

Because team wanted to prepare all requirements to final as soon as possible, experienced people worked on code related parts more. I have tried to get some parts but frontend wanted endpoints completely accurate with no error, they did not want to spend time on error corrections. As a result of this, there was an injustice separating tasks in backend. I have done my best in code part in this situation, and worked on documentation.

• Discussed and designed some crucial web pages and components to enhance the user experience.

• Searched about the W3 annotation standard and examined the related documentations.

• Implemented the annotation service and its database.

• Implemented the frontend of the annotation standard to the web page. Added annotation create flow.

• Dockerized the annotation service and its database.

• Tested and reviewed team members' contributions and gave valuable feedback.

• Responded rapidly to errors and bugs and fixed them like the image rendering bug.

• Deployed the services and monitored for the possible issues.

• Added unit test for web page.

• Designed and implemented the annotation service which complies with the proposed annotation data models.

• Added the annotation creation and highlighting to the frontend.

• Added the related docker files and updated the docker compose file for the ease of deployment.

• Solved the image rendering issue for various components like postHeader, post, user etc.

• Helped team members to solve the problems faced during the implementation.

• Added dynamic refetch for comment posts and annotations for a better user experience.

• Added jest to create unit tests for the web page.

Link for unit tests that I implemented:

1-) Singin Unit Test

Instructions for Using the Stock Forum System

The Stock Forum, branded as "Tradeverse," is an interactive platform designed for financial enthusiasts, investors, and analysts to discuss financial assets, view real-time asset values, filter news, and share personal financial portfolios. This manual provides step-by-step instructions for utilizing the platform's features efficiently.

1. Getting Started

   • Creating an Account
   • Logging In
   • Selecting User Type
   • Navigating the Interface

2. Features and Functionality

   • Subforums and Discussions
   • Posting and Commenting
   • News Filtering
   • Portfolio Management

3. Search and Advanced Filters

4. Admin Tools

   • Managing Subforums
   • Content Moderation

5. Security and Best Practices

6. Troubleshooting and Support

To access all features as a registered user:

1. Click the Register button on the homepage.
2. Provide your name, username, email, and password in the form that appears.
3. Click Next to proceed.
4. On the next screen, select your user type from the following options:
   • Beginner
   • Day Trader
   • Investor
   • Finance Enthusiast
   • Financial Analyst
5. Click Submit to complete your registration.

Note: Guest users can view posts and comments without registering.

1. Enter your username/email and password on the login page.
2. Click Log In.

If you encounter login issues, use the Forgot Password option or contact support.

• During registration, select your user type to customize your experience.
• Options include Beginner, Day Trader, Investor, Finance Enthusiast, or Financial Analyst.

• The homepage displays subforums such as BIST, NASDAQ, Crypto Insights, ETF Discussions, and Stock Picks.
• Use the sidebar on the left to navigate between your account, search, and followed topics.
• Access the personalized news feed and portfolio sections via the top navigation bar.

• Explore subforums dedicated to specific topics, such as "NASDAQ" or "Crypto Insights."
• Join subforums by clicking the Follow button.
• View detailed discussions and posts related to the subforum’s topic.

• To create a post:
  1. Select a subforum from the dropdown menu.
  2. Add a title and write your post in the text area.
  3. Optionally, attach an image or select a financial asset tag.
  4. Click Post 🚀 to publish.
• Comment on posts by typing in the comment box and clicking Comment.

• Access the News Feed section to view articles related to your selected financial assets.
• Filter news by asset type or subforum topics for a personalized experience.

• Create and share financial portfolios in the Portfolio section.
• Add assets to your portfolio by clicking Add Asset.
• View your portfolio’s total value, breakdown by assets, and individual performance metrics.

Use the search bar to:

• Find subforums by name.
• Locate posts or topics using tags.
• Search for assets, posts, or users directly.

Advanced filters allow sorting by asset type, tags, or users.

• Admin users can create or delete subforums.
• Add or remove base tags to categorize subforums.

• Admins can flag or remove inappropriate content and ban disruptive users.

• Always use a strong, unique password.
• Avoid sharing sensitive personal or financial information.
• Log out after using public devices.

• Cannot log in: Ensure your credentials are correct or use the password reset feature.
• Missing features: Check if you are logged in as a registered user.

Tradeverse is a comprehensive platform for financial discussions, networking, and portfolio sharing. Follow this manual to make the most of its features and enhance your experience.

• Operating System: Any OS with Docker support (Linux, macOS, Windows)
• Software:
  • Docker (version 20.10 or later)
  • Docker Compose
• Hardware:
  • Minimum 4 GB RAM
  • 10 GB of free disk space

• Operating System: Any OS with Node.js and Expo support
• Software:
  • Node.js (version 16 or later)
  • Expo CLI
  • Android Studio (optional, for emulation)
• Hardware:
  • Minimum 4 GB RAM
  • 5 GB of free disk space

1. Install Prerequisites: Ensure Docker and Docker Compose are installed on your system.

2. Clone the Repository:

   git clone https://github.com/bounswe/bounswe2024group10.git
   cd bounswe2024group10

3. Configure Environment Variables:

   • Open the docker-compose.yaml file.
   • Modify the database credentials if necessary:

     MYSQL_ROOT_PASSWORD=rootpassword
     MYSQL_DATABASE=tradeverse
     MYSQL_USER=tradeuser
     MYSQL_PASSWORD=tradepassword

4. Build and Run the Application:

   docker-compose up --build

5. Access the Application:

   • Frontend: http://localhost:3000/
   • Backend API: http://localhost:8080/api/
   • Database: http://localhost:3306/

1. Install Prerequisites: Ensure Node.js and Expo CLI are installed:

   npm install -g expo-cli

2. Clone the Mobile Repository:

   git clone <your-mobile-repo-url> cd tradeverse/mobile

3. Install Dependencies: Navigate to the mobile directory and install the required dependencies:

   npm install

4. Start the Development Server: Start the Expo development server by running:

   npm start

   This will open a new tab in your browser with the Expo developer tools.

5. Run the Application:

   • Using Android Emulator:
     • Ensure Android Studio is installed and an emulator is set up.
     • In the Expo developer tools, click "Run on Android device/emulator."
   • Using a Physical Device:
     • Install the Expo Go app from the Google Play Store.
     • Scan the QR code displayed in the Expo developer tools to run the app on your device.

6. Build the APK: To create a standalone APK for the mobile app:

   npm install -g eas-cli eas build -p android --profile preview

   • Follow the Prompts: The EAS build process will guide you through configuration options.
   • Download the APK: Once the build is complete, you will receive a link to download the APK file. You can then install this APK on any Android device.

The purpose of Tradeverse Forum is to create a collaborative platform for financial enthusiasts, traders, and analysts. It enables users to discuss financial topics, share analyses, and access real-time data about financial assets.

Tradeverse Forum includes the following functionalities:

• User registration and authentication.
• Post creation with tagging for financial assets.
• Annotation support for posts and comments.
• Interactive stock charts displayed when stock symbols are mentioned in posts.
• Subforums for niche financial discussions.
• User profiles with a "user type" classification.

The application integrates with APIs for real-time financial data and adheres to the W3C Web Annotation Data Model.

Tradeverse Forum is a standalone web and mobile application built using Spring Boot (backend) and React (frontend). It integrates with third-party APIs for financial data and uses Docker for deployment.

• Authentication: Secure login/logout using JWT.
• Posting: Create, like/dislike, and comment on posts.
• Annotations: Highlight and annotate text in posts and comments.
• Interactive Charts: Display stock price charts for mentioned symbols.
• Subforums: Group discussions by financial topics (e.g., NASDAQ, crypto).
• User Profiles: Display user information and posts.

• Beginners
• Day Traders
• Investors
• Finance Analysts
• Finance Enthusiasts

User classes help in connecting users with similar knowledge with each other, through our feed algorithm.

• REQ-1: System must support user registration with username and password

  • Priority: High
  • Status: Implemented
  • Notes: No specific password requirements needed

• REQ-2: System must implement three distinct user roles

  • Priority: High
  • Status: Implemented
  • Notes: Roles include guest user, registered user, and admin

• REQ-3: System must generate and manage JWT tokens for authenticated sessions

  • Priority: High
  • Status: Implemented
  • Notes: Tokens used for maintaining user sessions and API access

• REQ-4: System must allow users to create posts with title and text content

  • Priority: High
  • Status: Implemented
  • Notes: No length restrictions on either field

• REQ-5: System must automatically detect and tag financial assets mentioned in posts

  • Priority: High
  • Status: Implemented
  • Notes: Tags are used for search functionality

• REQ-6: System must integrate TradingView charts for tagged financial assets

  • Priority: High
  • Status: Implemented
  • Notes: Charts should be displayed inline with posts

• REQ-7: System must implement W3C Web Annotation Data Model

  • Priority: High
  • Status: Implemented
  • Notes: Applicable to all text content

• REQ-8: System must highlight annotated text when corresponding annotation is selected

  • Priority: High
  • Status: Implemented
  • Notes: Visual feedback for annotation navigation

• REQ-9: System must allow any user to create and view annotations

  • Priority: High
  • Status: Implemented
  • Notes: No permission restrictions on annotations

• REQ-10: System must integrate with TradingView API

  • Priority: High
  • Status: Implemented
  • Notes: For real-time financial data and charts

• REQ-11: System must provide interactive candlestick charts

  • Priority: High
  • Status: Implemented
  • Notes: Charts must support zoom, pan, and scale operations

• REQ-12: System must maintain user profiles with:

  • Profile photo
  • Follower count
  • Post history
  • Priority: High
  • Status: Implemented

• REQ-13: System must support portfolio management

  • Priority: High
  • Status: Implemented
  • Notes: Users can add assets with quantities

• REQ-14: System must generate pie charts for portfolio visualization

  • Priority: High
  • Status: Implemented
  • Notes: Based on asset quantities in user portfolio

• Actor: Unregistered User
• Description: User creates an account and logs in
• Preconditions: User is not logged in
• Basic Flow:
  1. User enters username and password
  2. System validates credentials
  3. System generates JWT token
  4. User gains registered user privileges
• Postconditions: User is authenticated and token is assigned

• Actor: Registered User
• Description: User creates a post with financial analysis
• Preconditions: User is authenticated
• Basic Flow:
  1. User enters post title and content
  2. System identifies financial assets in text
  3. System adds appropriate tags
  4. System embeds relevant TradingView charts
  5. Post is published
• Postconditions: Post is visible to all users

• Actor: Registered User
• Description: User manages their investment portfolio
• Preconditions: User is authenticated
• Basic Flow:
  1. User adds asset to portfolio
  2. User specifies asset quantity
  3. System updates portfolio composition
  4. System generates updated pie chart
• Postconditions: Portfolio reflects new asset allocation

• REQ-15: System must support 100 concurrent users

  • Priority: High
  • Status: Implemented

• REQ-16: System must operate within 100GB storage limit

  • Priority: High
  • Status: Implemented
  • Notes: Includes all user data, posts, and annotations

• REQ-17: System must store all post content and metadata

  • Priority: High
  • Status: Implemented
  • Notes: Includes titles, content, tags, and timestamps

• REQ-18: System must maintain user authentication data

  • Priority: High
  • Status: Implemented
  • Notes: Includes usernames and passwords

• REQ-19: System must store annotation data following W3C standard

  • Priority: High
  • Status: Implemented
  • Notes: Includes selected text and annotation content

• The system must support both mobile and desktop interfaces
• The application must maintain a responsive design that adapts to different screen sizes
• The application must use a bright purple color scheme throughout

All pages must include:

• Navigation bar at the top of the page
• Sidebar for navigation options
• Dropdown menu in the top right corner (for authenticated users only)

• Mobile layout must automatically adjust from desktop version
• Content must be readable and accessible on both mobile and desktop devices
• UI elements must maintain consistent styling across all pages
• Navigation elements must remain accessible regardless of device type

• The system must be platform-independent
• No specific hardware requirements beyond basic internet-capable device
• Must function on any operating system with a modern web browser

• The system must integrate with TradingView's charting API
• Requirements for chart display:
  • Must display candlestick patterns
  • Must show price movements over time
  • Must update with market data
  • Must be interactive (zoom/pan capabilities)

• Must support storage and retrieval of:
  • User data
  • Post content
  • Annotations
  • Portfolio information
  • Authentication tokens

• Frontend-Backend communication must be implemented through RESTful API calls
• API endpoints must support:
  • User authentication
  • Post management
  • Portfolio updates
  • Annotation management
  • User profile operations

• All API requests and responses must use JSON format
• API responses must include appropriate status codes
• Error responses must include descriptive messages

• All API communications must transmit sensitive data securely
• Authentication tokens must be included in API request headers

• Class Diagram
• Sequence Diagrams
• Use Case Diagram

Below are our user group scenarios, user scenarios and mockups; in addition to the ones given at here (mobile) and here (web):

• User Group Scenario 1
• User Group Scenario 2
• User Scenario 1
• User Scenario 2
• User Scenario 3
• User Scenario 6
• User Scenario 7
• User Scenario 8
• Mockups

Project plan is created using Project Libre, link

Below are links for our prepared unit tests:

1-) Post Service Unit Tests

2-) Subforum Service Unit Tests

3-) User Service Unit Tests

1. Ensure Docker and Docker Compose are installed on your machine.

2. Clone the repository:

   git clone https://github.com/bounswe/bounswe2024group10.git
   cd bounswe2024group10
   

1. Edit docker-compose.yaml to update the database credentials if needed:

   MYSQL_ROOT_PASSWORD=rootpassword
   MYSQL_DATABASE=tradeverse
   MYSQL_USER=tradeuser
   MYSQL_PASSWORD=tradepassword
   

1. Build and run the application:

   docker-compose up --build
   

   This command will:

   • Build the backend and frontend applications.

   • Start the MySQL database.

2. Once running:

   • Access the main application at http://localhost:3000/.

   • Access the backend API at http://localhost:8080/api/.

   • Access the database at http://localhost:3306/.

1. Clone the mobile project repository:

   git clone https://github.com/bounswe/bounswe2024group10.git
   cd mobile/tradeverse
   

2. Install dependencies:

   npm install
   

3. Start the development server:

   npm start
   

4. Run the mobile application on an emulator or physical device:

   • For Android: Use Android Studio or scan the QR code with the Expo Go app.

1. Install the EAS CLI:

   npm install -g eas-cli
   

2. Build the APK:

   eas build --platform android --profile preview
   

3. Download and install the APK on your Android device.