Member Avatar for GianFire

Hi, I apologized if I am not asking the right question here or I am posting in the wrong question. But, I hope I can get some direction on where to go to accomplish this.
I trying to create a secured site. Users will be log in with their own user name and password. After log in, the user will have access to a series of subjects where he/she can choice to take and test of the desirable subject. He/she have the option of the number of question. After taking the test, the person should be able to see their results by percentage, chart how they did on the test. Also, I would like to be able to create a report of the results for the user to see.
the question is, what is the appropriate software to develop and web application that can be accessed from anywhere in the world as long as you have an internet connection. I check a few companies out there but, they where not as flexible on what I wanted to do or more discouraging when I talk to them.
Thank you for taking the time to help with this.

Gian

  • 4 Contributors
  • 3 Replies
  • 196 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by peter_budo

Dani AI

Generated

As laid out, the project is a secured, web-accessible test engine with user accounts, selectable subjects, configurable question counts, per-test scoring and charts, plus printable/exportable reports. Treat it as five cooperating pieces: authentication, a question bank/test-builder, the test runner, a persistent attempt store, and a reporting/analytics layer.

A practical minimum data model (conceptual) that keeps results auditable:

  • Users: id, email, password_hash, role, created_at
  • Subjects/Categories: id, name
  • Tests (or TestVersions): id, subject_id, title, time_limit, version, randomize_flag
  • Questions: id, bank_id, type, body, metadata
  • Choices/Answers: id, question_id, text, correct_flag, weight
  • Attempts: id, user_id, test_version_id, started_at, finished_at, score_percent, raw_responses (JSON)
  • AttemptItems: attempt_id, question_id, response, score_awarded

Store the exact test_version and raw_responses for every attempt so old results remain valid even after the bank changes. Index dates and user_id for fast queries. Keep question types flexible (MCQ, multi-select, essay, numeric) and store per-item scoring to allow partial credit.

Security, integrity and operational notes: require TLS for all access; hash passwords with a modern algorithm (bcrypt/Argon2) and never log plaintext credentials; protect sessions (secure, httpOnly cookies, reasonable timeouts), use CSRF tokens and server-side authorization checks, validate/sanitize all input to prevent XSS/SQL injection, log auditable events (who, when, IP), and implement rate-limits/account lockout for brute-force protection. Keep regular backups, a retention policy for personal data, and consider encryption for sensitive exports.

UX/reporting and rollout: show per-test percent plus question-level correctness and trend charts; allow CSV/PDF export and async snapshot reports for heavy analytics. Support question pools, option randomization, timed tests, and resume where sensible. Build an MVP first (accounts, bank, runner, scoring, a simple results page), then add charting, PDF reports and analytics. was right to call out persistent storage, correctly prioritized secure logins, and ’s hosting/cost point is worth factoring into your deployment plan.

Recommended Answers

All 3 Replies

Member Avatar for syljms

You can do this in any scripting language you are familiar with, PHP, asp or asp.net etc.

Besides you need to host your app on a web server to make your app available to users all the time.

If you would like users to be able to see their past test results, then you need to store each test result in a database. Try php/mySQL combination. It should work fine for you.

Member Avatar for textbox

Developing this site in asp.net would be a good choice because it has the built-in functionality to allow for secure logins, role-based content viewing, profile management, etc.

Member Avatar for peter_budo

Developing this site in asp.net would be a good choice because it has the built-in functionality to allow for secure logins, role-based content viewing, profile management, etc.

same can be achieved with JSP or PHP and there can be endless discussion on which is better. One for sure, there is lesser number IIS servers on the market then Apache and as far I'm concerned ASP wouldn't run on anything else, plus IIS hosting is more expensive then Apache

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.