Requirements

Glossary

• Annotation: A note by way of explanation or comment added to the text and article.
• Article: Documents for users of traders platform about trading that helping users to reach knowledge and share with other users.
• Basic user: Registered user authorized to write comments and articles.
  
• Comment: Basic and traders users' ideas about relevant investment or the stock market.
  
• Common User: The user type which corresponds to both Basic and Trader
  
• Economic Event: Important economic developments such as Fed Interest Rate, GDP of countries, ECB Interest Rate, and more.
  
• Events: News or happenings about stock, economy and trade.
• Follow: An act using for a user can reach others article, investments, comments and share their owns with others.
• Guests: Users who are only authorized to read reviews and view trading equipment.
  
• Investment: Buying and selling trading equipment(indices, stocks, ETFs, commodities, currencies, funds, bonds, and cryptocurrencies) in order to make a profit.
• Log in: When a user logs in to the system with the information they provided signing up.
  
• Password: String of characters used for user authentication to prove identity.
  
• Prediction Success Ratio: A scale that shows what percent of user's predictions were successful.
• Profile Page: The page providing information about predictionpecified trading equipments of users on certain assets and success ratio on these predictions.
• Portfolio: A collection of trading equipments that are owned by the user.
  
• Semantic search: Semantic search seeks to improve search accuracy by understanding the users' intent and the contextual meaning of terms as they appear in the searchable dataspace, whether on the Web or within a closed system, to generate more relevant results.
• Signifigance Level: Marks for how much reiable and important events and news.
• Tag: A categorical designation that attaches to various items.
  
• Trading user: A person who can post, comment, like and invest in any trading equipment
  
• Trading equipment: Bills of exchange, commodities, crypto coins, stock market shares etc.
  
• Username: The name that identifies user account to the system.

1. Functional Requirements

1.1. User Requirements

• 1.1.1. Common User Requirements

  • 1.1.1.1. #

    • 1.1.1.1.1. Users shall # by following below steps.
      • 1.1.1.1.1.1. Users shall # by providing their e-mail address, password, name, surname and location.
        • 1.1.1.1.1.1.1. E-mail addresses shall be unique.
        • 1.1.1.1.1.1.2. User passwords shall be in the specified form.
        • 1.1.1.1.1.1.3. User location shall be specified via Google Maps.
    • 1.1.1.1.2. Users shall # via their Google account.

  • 1.1.1.2. #

    • 1.1.1.2.1. Users shall # by providing their e-mail address and password.
    • 1.1.1.2.2. Users shall # via their Google account.

  • 1.1.1.3. Password Change

    • 1.1.1.3.1. Reset Password
      • 1.1.1.3.1.1. Users shall be able to reset their password by requesting "Reset Password" operation at profile page.
      • 1.1.1.3.1.2. Users should provide old password and new password they desire, when they want to reset their password

  • 1.1.1.4. Profile

    • 1.1.1.4.1. Users shall have a profile either private or public.
      • 1.1.1.4.1.1. Users with a private profile shall be followed in order to see the content of the private user.
    • 1.1.1.4.2. Users shall have at least one portfolio.
      • 1.1.1.4.2.1. Users shall be able to rename their portfolio.
      • 1.1.1.4.2.2. Users shall be able to add any trading equipment to their portfolio.
    • 1.1.1.4.3. Users each prediction success rate should be visible on their profile page.

  • 1.1.1.5. User actions

    • 1.1.1.5.1. Users shall be able to share their portfolio on their profile page.
    • 1.1.1.5.2. Users shall be able to follow shared portfolios.
    • 1.1.1.5.3. Users shall be able to chase economic events and filter those events by considering the significance level and country base.
    • 1.1.1.5.4. Users shall have a "Profit/Loss" section that can show profit/loss amount in terms of currency they choose.
    • 1.1.1.5.5. Users shall be able to share their ideas(predictions) on any trading equipment.
    • 1.1.1.5.6. Users shall be able to follow other users.
    • 1.1.1.5.7. Users shall be able to set alerts for certain trading equipment.
      • 1.1.1.5.7.1. Users shall be able to set alerts for above or below of specific value on the trading equipments.
      • 1.1.1.5.7.2. Users shall be able to set alerts for increase or decrease of specific change on the trading equipment.
    • 1.1.1.5.8. Users shall be able to publish article.
      • 1.1.1.5.8.1. Users shall be able to write a comment to article.
      • 1.1.1.5.8.2. Users shall be able to like and dislike the articles.
    • 1.1.1.5.9. Users shall be able to update their personal information.
    • 1.1.1.5.10. Users shall be able to update their profile picture.

• 1.1.2. Basic Users

  • 1.1.2.1. Basic users shall be able to see their profit/loss amount in terms of the currency they choose by manually entering their investments.

• 1.1.3. Trading Users

  • 1.1.3.1. Trading users should be able to see their profit/loss amount in terms of the currency they choose by both manually entering their investments and using the investments they made.
  • 1.1.3.2. Trading users shall have "My Investment" section where they can invest in any trading equipment, make a buy order for a specified rate, and set stop/loss limits.
  • 1.1.3.3. Trading users shall provide financial services corporation name and regarding IBAN number while signing up.

• 1.1.4. Guests

  • 1.1.4.1 Guests shall be able to view the price of trading equipment and read user comments about trading equipment.
  • 1.1.4.2. Guests shall be able to search, which includes semantic searching, for users and trading equipment.

• 1.1.5. Administrators

  • 1.1.5.1. Admins shall be able to ban users for inconvenient behaviors.
  • 1.1.5.2. Admins shall be able to delete inconvenient comments and articles.

1.2. System Requirements

• 1.2.1. Transaction

  • 1.2.1.1. The system shall support transaction from users' banking account to its account balance.

• 1.2.2. Notification

  • 1.2.2.1. The system shall be able to send notification to the user if there is a private message from other users.
  • 1.2.2.2. The system shall be able to send notification to the user about following trading equipment.
  • 1.2.2.3. The system shall be able to recommend articles and trading equipment to users based on their search history.

• 1.2.3. Interface

  • 1.2.3.1. The system shall support Turkish characters.
  • 1.2.3.2. System interface language shall be English.

• 1.2.4. Database

  • 1.2.4.1. The system shall store and update data for each user in the database:
    • 1.2.4.1.1. Users' search history
    • 1.2.4.1.2. Articles published by users and its comments
    • 1.2.4.1.3. Alerts set by users
    • 1.2.4.1.4. Investments made by Traders
    • 1.2.4.1.5. Portfolios
    • 1.2.4.1.6. Trading equipments and its comments
    • 1.2.4.1.7. Events
    • 1.2.4.1.8. Users' personal informations

• 1.2.5. Trading equipment

  • 1.2.5.1. The system shall support trading equipment as follow.

    • 1.2.5.1.1. Trade Indices

      • 1.2.5.1.1.1. DJI
      • 1.2.5.1.1.2. IXIC
      • 1.2.5.1.1.3. INX

    • 1.2.5.1.2. Stocks

      • 1.2.5.1.2.1. General Motors (GM)
      • 1.2.5.1.2.2. Google (GOOG)
      • 1.2.5.1.2.3. Apple (AAPL)

    • 1.2.5.1.3. ETFs

      • 1.2.5.1.3.1. SPDR S&P 500 (SPY)
      • 1.2.5.1.3.2. iShares Core S&P 500 (IVV)
      • 1.2.5.1.3.3. Vanguard Total (VTI)

    • 1.2.5.1.4. Commodities

      • 1.2.5.1.4.1. Gold
      • 1.2.5.1.4.2. Silver

    • 1.2.5.1.5. Parities

      • 1.2.5.1.5.1. System shall support most traded currencies.
      • 1.2.5.1.5.2. System shall have exchange rates for existing currencies.
      • 1.2.5.1.5.3. Examples :
        • 1.2.5.1.5.3.1. Pound
        • 1.2.5.1.5.3.2. Euro
        • 1.2.5.1.5.3.3. Turkish Lira

    • 1.2.5.1.6. Cryptocurrencies

      • 1.2.5.1.6.1. Bitcoin
      • 1.2.5.1.6.2. Litecoin
      • 1.2.5.1.6.3. Etherium

  • 1.2.5.2. Each trading equipment should include many functionalities as follow.

    • 1.2.5.2.1. The previous close
    • 1.2.5.2.2. Percentage change with the previous close
    • 1.2.5.2.3. Amount change with the previous close
    • 1.2.5.2.4. Day’s range
    • 1.2.5.2.5. Moving averages

• 1.2.6. Search Mechanism

  • 1.2.6.1. The system shall support search with keywords.
    • 1.2.6.1.1. The system shall support searching for users, trading equipments, and economic events.
    • 1.2.6.1.2. The system shall support some semantic search mechanism to find semantically similar users and trading equipment based on the context information provided in the semantic tags.
    • 1.2.6.1.3. The system shall enable the users to search for the other users in a specific location.

2. Non-functional Requirements

2.1. Availability and Accessibility

• 2.1.1. The application shall have a native web and native mobile (Android) client.
• 2.1.2. The application shall be deployable on a remote and manually configurable server.
• 2.1.3. The application shall be available in English.
• 2.1.4. The system should be able to continue operating properly in the event of the failure.
• 2.1.5. The number of system failures shall happen at most once in a year.
• 2.1.6. The application shall support Chromo, Safari, Firefox, Internet Explorer browsers.

2.2. Annotations

• 2.2.1. Annotations shall be congruent with the specifications of The W3C Web Annotation Data Model.
• 2.2.2. The platform shall follow W3C Web Annotation Protocol so that the contents (e.g., graph, figure, comment) can be annotated by users.

2.3. Performance

• 2.3.1. The system shall respond to requests in 3 seconds.
• 2.3.2. The system should be able to respond up to 1000 requests per second.
• 2.3.3. The system shall be able to support up to 100000 users.

2.4. Privacy

• 2.4.1. Personal data of users cannot be used explicit consent.
• 2.4.2. Processing personal data like location shall be asked for permission.
• 2.4.3. GDPR and KVKK regulations will be ensured.

2.5. Security

• 2.5.1. Users shall be forced to change their passwords with a different one from last three passwords 6 months after registration or the latest password change.
• 2.5.2. Users shall be prevented to construct his/her password containing at least 4 sequential characters of well-known public pieces of information which are his user-name and his email.