Skip to main content

GenAI Productivity: Ideas to project proposal 3

Produced using Google Gemini

In two previous posts I looked at using Generative AI to start producing  project ideas and refining one to be the start of the proposal, Previous blog posts
One of the most significant cognitive hurdles for students is the transition from a high-level area of interest to a rigorously defined project specification. This "blank page" problem often leads to poorly scoped projects or a lack of alignment with current academic literature.

Building on my previous experiments in prompt-mediated productivity, this post examines a structured workflow for using Large Language Models (LLMs)—specifically GPT-4o—to scaffold the development of a BSc Software Engineering project proposal.

The Methodology: Multi-Stage Prompt Scaffolding

Rather than requesting a single output, the workflow utilizes a recursive prompting strategy. This mirrors the iterative refinement process we expect from students, but accelerates the initial drafting phase.

Stage 1: Broad Ideation and Constraint Mapping

The initial objective is to map the "possibility space" within a specific domain, such as Ambient Assisted Living (AAL). By providing the LLM with a specific student persona and technical constraints, we ensure the output is calibrated to the appropriate academic level.

The Instructional Prompt:

"Generate five distinct project ideas suitable for a BSc Software Engineering student specializing in Ambient Assisted Living. The projects must emphasize complex programming logic. For each, provide: a 100-word abstract, a 200-word academic justification, core functional goals, and a bill of materials (physical resources)."

Stage 2: Deepening Rigor and Academic Grounding

Once a candidate project is selected—in this case, a Voice-Controlled Personal Assistant (VCPA) for Dementia Patients—the next phase involves "hardening" the proposal. This requires the LLM to integrate formal citations and expand the technical justification to meet the requirements of a formal module descriptor or proposal document.

The Refinement Prompt:

"Expand Project Idea 4 into a formal 700-word proposal. Integrate Harvard-style citations throughout the justification and description. Focus on the technical implementation (NLP, speech-to-text) and the ethical considerations of assistive technology. Include a comprehensive reference list."

Case Study: The "Cognitive Assistant" Proposal

The resulting output demonstrated a sophisticated understanding of the intersection between software engineering and healthcare informatics. Key highlights included:

  • Technical Stack Identification: Moving beyond generic "AI," the model suggested specific open-source frameworks like Rasa for dialogue management and Vosk/DeepSpeech for privacy-preserving, offline inference—a critical requirement for sensitive healthcare data.

  • Architectural Feasibility: The proposal mapped the solution onto low-cost Edge hardware (Raspberry Pi 4), providing a realistic scope for a self-funded student project.

  • Academic Context: The justification aligned the project with the IEEE's "Ethically Aligned Design" and the WHO's Global Action Plan on Dementia, providing the student with a high-level framework for their literature review.

The Critical Intervention: Human-in-the-Loop (HITL) Verification

In a computing education context, the "Human Bit" is not merely an afterthought; it is the primary learning objective. For supervisors and students, this workflow necessitates a rigorous audit phase:

  1. Citation Forensics: LLMs are prone to "hallucinating" academic sources. Students must be taught to verify every DOI and paper title against reputable databases (ACM Digital Library, IEEE Xplore).

  2. Feasibility Auditing: While the LLM can suggest an architecture, the student must verify whether a Raspberry Pi has sufficient computational capacity for real-time NLP with minimal latency.

  3. Reflective Personalisation: The AI output serves as a "minimum viable product" (MVP). The student’s role is to inject their own unique research questions and technical nuances that distinguish an automated draft from a personal contribution to the field.

Pedagogical Implications

By using GenAI as a "drafting partner," we shift the student’s labour from low-level structural drafting to high-level critical evaluation. This approach doesn't just produce a better proposal; it models the type of AI-augmented engineering workflow that is likely to become standard in  industry.

We should view these tools not as a threat to academic integrity, but as a sophisticated form of scaffolding that allows students to engage with complex project design more rapidly and deeply.


All opinions in this blog are the Author's and should not in any way be seen as reflecting the views of any organisation the Author has any association with. Twitter @scottturneruon

Comments

Popular posts from this blog

Using an LLM to Find Themes using Thematic Analysis in an Academic Career

B rief recap In an earlier post, “Same prompt, four AIs: why answers aren’t always the same” , I looked at what happened when the same prompt was given to four different LLMs. Unsurprisingly, perhaps, the answers were not identical. That raised an interesting follow-on question: what was the prompt actually trying to do? The answer is that it was trying to support a form of thematic analysis. In that case, the object of analysis was an academic profile, including my Google Scholar profile. The version I discuss here is a modified prompt, used with Claude.ai, where I uploaded a CV and asked the system to find other appropriate public resources connected with a named person and institution. The aim was not simply to summarise the CV, but to identify visible and less visible themes across a whole career. Why use thematic analysis? Thematic analysis is widely used by academics, especially in qualitative research. Braun and Clarke’s well-known paper, Using thematic analysis in psy...

Prompt Engineering, Context Engineering and Agentic AI in Higher Education: A Short Briefing

AI in Education Prompt engineering, context engineering and agentic AI are often used interchangeably, but the literature treats them as distinct. Prompt engineering concerns crafting effective single instructions to a model (Glean, 2026). Context engineering is the broader discipline of designing and managing the entire informational environment around a model—memory, retrieval, tool outputs and conversation state—rather than a one-off instruction (Abstracta, 2026); prompt engineering operates within the context window, while context engineering determines what fills it (arXiv:2606.12422, 2026). Agentic AI describes systems that plan and execute multi-step tasks with delegated autonomy, raising organisational questions of accountability rather than purely technical ones (MIT Sloan, 2026; Palo Alto Networks, 2026). There is genuine debate about prompt engineering's durability. IEEE Spectrum (2025) reported research suggesting prompting is increasingly performed by models themse...

AI as a Mirror: Transforming Vague Student Ideas into a More Rigorous Project Agreement

The Problem: The "Generic App" and the "Time Sink" We’ve all been there: a student walks into a 1-to-1 with a vague desire to "do something with AI" or "build a fitness app." You spend 45 minutes trying to find a technical "hook" that justifies a Level 6 or Level 7 grade, only for the student to drift back into "CRUD app" territory by week three. The Philosophy: AI as a Mirror Instead of you doing the heavy lifting, this workflow uses AI as a Mirror . It reflects the student’s own skills and career goals back to them, but with the structural rigour of a virtual supervisory team. It’s not about the AI "giving" the idea; it’s about the AI forcing the student to defend and refine their own concepts until they hold water. The Framework: 3 Months of Rigour This prompt is specifically designed for intensive/conversion MSc or summer capstone projects . It assumes a tight 12-week implementation window. By forcing the AI to w...