Member Avatar for nhlagumbi

hi
i'm doing my final year project in computer science and its an online share trading system, well the topic was gaven to me bcos i would have not chosen it. its giving me a lot of problems,firstly i dont know anything about trading of shares. plz anyone can u give a few ideas.

  • 5 Contributors
  • 4 Replies
  • 111 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by jasimp

Dani AI

Generated

A practical way to handle a final-year "online share trading system" project is to treat it as a simulated exchange with a narrow, well-tested scope rather than trying to reproduce a full broker or connect to live markets. As stated, background knowledge of trading is useful but not required; concentrate on core domain concepts (orders, matching, account ledger) and clear, testable rules. As implied, produce original code; requests like asking for full project code are inappropriate for academic submission—sharing short, well-documented examples or algorithms for learning is acceptable but the submitted work should be the student’s own.

Critical components to plan and implement:

  • Account and ledger: maintain balances in the smallest currency unit (integers for cents) or use language Decimal/BigDecimal. Ledger updates must be atomic and auditable.
  • Order entry and types: at minimum support market and limit orders, plus cancel. Validate funds/shares before accepting orders.
  • Matching engine and order book: implement a price-time priority matcher (continuous double auction is standard). Keep the live order book in memory and persist trades immediately.
  • Market data and UI: simulate a feed (CSV/historical) and use WebSockets or polling for real-time updates to the front end.
  • Persistence, logging, audit trail: every state change must be logged for reproducibility and grading.

Practical engineering tips and common pitfalls:

  • Avoid floating-point math for money; use integer cents or fixed decimals.
  • Use transactions (ACID) for ledger writes. Decouple matching via a queue (RabbitMQ/Kafka/Redis) to reduce contention.
  • Concurrency: test race conditions aggressively with deterministic replay of order sequences.
  • Security and legality: keep the project in a sandbox with simulated money; do not deploy real-money trading without legal/compliance approval.

A minimal, demonstrable deliverable looks like: user auth and virtual wallet, order placement, live order book view, matching engine producing trades, portfolio and trade history, plus a test-suite and a short design document explaining decisions.

Recommended Answers

All 4 Replies

Member Avatar for dhanasekar1986

hai friend .. i have seen ur msg.... can u share ur coding on online share trading system.....

commented: Pathetic. -2
commented: Make that 2x -4
commented: pathetic homework kiddo -4
commented: Hai! +0
Member Avatar for Ezzaral

hai friend .. i have seen ur msg.... can u share ur coding on online share trading system.....

No, "u" must do "ur" own coding. If you turn in someone else's code for your project you deserve to fail.

Member Avatar for jwenting

Must be a new record. -14 reputation points from a single post :)

Member Avatar for jasimp

Nah I think it is this one. The only member to have two negative reputation blocks. He only posted seven times, two of them received negative rep, resulting in -153 rep points.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.