Member Avatar for nemo

hello,
my final year project is to make a web application for a discussion forum for a university environment. i am about to submit my requirement specification document.
i guess the context diagram for this system will have three actors,
1- Students.....who post questions
2- Moderators/ Instructors...... who reply to posts
3- Administrators.......takes overall care

can someone please tell me the difference in privileges of a moderator and an administrator in such an environment, how do i show these two actors in my context diagram. my project supervisor is not satisfied with my system diagram as yet, need to improve.

regards,
nemo

  • 4 Contributors
  • 4 Replies
  • 182 Views
  • 9 Months Discussion Span
  • Latest Post Latest Post by rick22

Dani AI

Generated

Good start, . 's super‑moderator suggestion is a helpful refinement — for the context diagram focus on scope and interactions rather than surface-level task lists.

Keep the context diagram high level: draw the forum application as a single system box and place external actors outside it. Represent Administrators and Moderators as separate actors and label the lines with the high‑level interactions they initiate (for example: authenticate, create/post content, submit report, manage users, configure system). Capture scope explicitly: annotate Moderator as "per‑forum" (or show multiplicity like Moderator [per forum]) and Super‑Moderator as "global moderator" so the supervisor can see the difference at a glance.

Deliverables that clarify the diagram for a supervisor:

  • a short use‑case list that breaks each labeled interaction into atomic actions (e.g., ManageUsers -> create/disable/assign roles/audit);
  • a concise role×permission matrix (roles as rows, fine‑grained permissions as columns) so every privilege is unambiguous;
  • a Level‑1 DFD or sequence diagram for at least one common flow (post → report → moderation) to show internal handling without cluttering the context diagram.

If "scheduling" refers to background jobs (digest emails, notifications, spam cleanup), keep it simple for the project: cron or a time‑based job queue plus a small worker process is sufficient. For moderate scalability, use a durable FIFO job queue and add a priority queue only where reports/alerts need faster handling. Design jobs to be idempotent, include retry/backoff, and log actions for auditability.

Recommended Answers

All 4 Replies

Member Avatar for John A

Here's how the forum hierarchy is organized on DaniWeb (some things have been purposely left out):

Admin -> Has complete control over the forum. They tend to handle things such as technical details of running it, as well as high-level issues and other stuff.

Super-Mod -> Kind of like the duties of a regular moderator, except that they have control over all forums. Their main goal is for the general well-being of the forum. Think of them as supervisors over other moderators.

Moderator -> Take care of low-level issues that come in the specific forums where they have expertise in. They do things such as snipping profanity, deleting spam, infracting/banning people. They also do a lot of helping for other people with their problems.

Regular Member -> Asks questions, helps other members out. Has the potential to become a moderator if they prove themselves knowledgeable enough.

So in terms of your diagram, I'd say you need to specify that moderators take care of the more low-level tasks. Another key thing to remember is that moderators don't have power over every forum, only the ones that they have expertise in.

Member Avatar for nemo

Thanks, i hadn't thought about the super moderator, this is a nice feature and i am keeping it too. still will keep things simple so that i am sure i can make it in the end.

any idea what algorithm to use for scheduling? though i havn't reached the design stage but would welcome comment on it.

Member Avatar for flower88

hey thanx for the information
its is very helpful for the assignments

Member Avatar for rick22

i think both admin nd moderator can help u a lott

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.