Member Avatar for GeoDude^^

a thesis proposal that can solve current community issues..

  • 5 Contributors
  • 5 Replies
  • 183 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by georgieo

Dani AI

Generated

A compact, practical plan for after repeated proposal rejections. Rejections often trace to an unclear problem statement, scope that is too large, or no concrete evaluation. This synthesizes the thread’s suggestions (from , , and ) into an actionable workflow and a short proposal skeleton that examiners can accept.

Recommended workflow:

  1. Discover: harvest short problem statements from the community — recent unanswered threads, moderator queues, feature requests, support emails or tag analytics. Capture 20–30 one-line problems.
  2. Prioritize: score each by frequency, user impact and estimated effort. Favor high-impact, low-effort items.
  3. Narrow: turn one problem into a single measurable research question (example: “reduce median time-to-first-answer for tag X from 8h to 2h”). Keep scope to a single metric.
  4. Prototype & evaluate: build the smallest possible prototype that demonstrates the idea (script, plugin, dashboard). Use before/after logs, simple A/B testing, task-completion times or small user studies (n≈10–30) as evaluation. Anonymize data and get moderator permission.
  5. Align with the advisor: present a two-page pitch (problem, method, metric, timeline, risks) and a fallback plan based on analysis of historical data if the prototype can’t be finished.

Proposal skeleton (one paragraph each): Title; Problem statement (1–2 sentences); Motivation/impact; Objectives (3 measurable goals); Scope (in/out); Methodology (prototype + dataset + evaluation); Deliverables; Timeline with milestones; Risks & fallback; Ethics/permissions.

Quick practical tips: keep the technical surface small by reusing APIs or libraries; prefer demonstrable metrics over feature lists; document reproducible steps and test data; if coding confidence is low, select an analysis/automation or UX-focused project or collaborate with a developer. Early advisor sign-off and a clear, measurable success criterion are the fastest routes from a rejected draft to an accepted proposal.

Recommended Answers

All 5 Replies

Member Avatar for Ketsuekiame

make a list of community issues and think about how you can create a piece of software that can help combat those issues. It doesn't have to be direct intervention. Think about things like the administration and office work that goes on behind the scenes.

Member Avatar for Momerath

Don't you have an advisor for this? It's part of their job to help you pick a thesis topic.

Member Avatar for GeoDude^^

My advisor helps me and he always suggest find issues to the developers community and i cannot find any since im not familiar with all the tools used and im not that pro when it comes to developing apps :(

Member Avatar for Seten

I got one, but I don't knwo if it is still up-to-date :D Make an application:
WindowsMobile <-> ActiveSync <-> Contact manager or calendar manager
WindowsMobile <-> Bluetooth <-> Contact manager or calendar manager

All would be locally. :D

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.