Member Avatar for stusfella@yahoo

Hi guys,
I am starting my project and thought You pple could give a hand.I want to develop a stand-alone real property management systemin Java (netbeans platform)...I have some problems in design and content of the system.I would greatly appreciate any assistance on the same ..no of databases(mysql),forms and such..(design) and some advice on content(i believe its universal).

thanks and regards
Festus

  • 3 Contributors
  • 2 Replies
  • 101 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by new_programmer

Dani AI

Generated

A compact, practical plan to move from idea to working app. is right that you should pick a basic framework up front; asked for specifics — the list below gives concrete pieces to design before you write code so can scope the project and defend it as a final-year submission.

Core functional areas and typical data entities to model:

  • Properties, Units (for multi-unit buildings), Owners, Tenants, Leases, Payments, MaintenanceRequests, Users/Roles, Documents, Inspections.
  • Screens/forms to implement: property list/detail, unit management, owner/tenant CRUD, lease creation/renewal, payment/receipt entry, maintenance ticket workflow, search/filter, reporting dashboard, administration screens.

Design and DB guidance (practical rules):

  • Use a single MySQL database per deployment unless you need strict tenant isolation. Normalize to avoid duplicate data; denormalize only for reports.
  • Use integer surrogate PKs, foreign keys for integrity, and indexes on search columns (address, tenant name, lease id).
  • Store money in DECIMAL, timestamps in ISO format; keep file blobs out of the DB where possible (store files on disk or object store and save metadata).
  • Use transactions for payment and lease operations, prepared statements or JPA/Hibernate to avoid SQL injection, and strong password hashing (bcrypt/Argon2). Add an audit trail for changes.

Project workflow and deliverables:

  • Start with requirements, an ER diagram and UI mockups. Build the DB and simple CRUD first, then implement business flows (leases, payments, maintenance), add reporting and tests, and finish with deployment notes and user manual. Watch for scope creep, poor validation, and mixing UI and business logic.

Recommended Answers

All 2 Replies

Member Avatar for Member #814414

Stuff like number of forms and the design should generally be decided by the coder. Other people can help you along the way, but your project will turn out better if you think up the basic framework.

Member Avatar for new_programmer

Hi Festus,
Mention your ideas and your design and make your question more specific. Everyone one will assist you.
All the best.

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.