Member Avatar for gaam

please guide me i'm confused i have to make a banking project using .Net and i don't from where to start my mind is really not working :sad: :?:

  • 2 Contributors
  • 1 Reply
  • 307 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by cpopham

Dani AI

Generated

A short, practical roadmap for a .NET banking project that turns confusion into clear first steps. For , scope the project down to a minimal, testable set of features (account and customer records, secure login/roles, deposits/withdrawals, internal transfers, transaction history and a simple statement/report). Keep non‑functional requirements explicit from the start: data integrity, atomic money moves, auditability, and basic security.

Architecture: use a layered approach — presentation (web or desktop), business logic that enforces rules, and a data layer that owns persistence. As hinted, choosing a backend is pivotal: pick a relational DB with ACID guarantees and design the schema first. Suggested core tables: Customers, Accounts, Transactions (ledger-style), Users/Roles, and AuditLog. Represent money with a fixed‑point type (or integer cents) — never floating point. Implement transfers as atomic DB transactions that create paired ledger entries (debit + credit) rather than trying to reconcile balances by ad hoc updates.

Implementation checklist and good practices: start by drawing an ER diagram and sample workflows, then implement the data layer and migration scripts, then the business rules and tests. Add unit tests for logic and integration tests that exercise full transaction flows. Use parameterized queries or an ORM to reduce injection risk; keep schema migrations under source control; seed test data for repeatable tests.

Security and delivery cautions: never store plaintext passwords (use salted hashing), protect transport with TLS, encrypt sensitive fields at rest when appropriate, avoid storing full cardholder data (consider PCI rules), and log only what’s necessary. Milestones that work well: DB + ERD → data layer + migrations → business rules + tests → UI → basic audit/logging and final documentation.

Member Avatar for cpopham

What will it involve? Will you be using a Database as the backend? If you do have a database as a backend will it be access or something else? If you are not using a db as a backend, will you be storing your information in a file? If it is a file, will it be a text file, random access file, or binary file? There are many ways to approach this. If you do have to use a db as a backend, you should design the db first and go from there.

Chester

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.