Dr. Ergin Huseyin
<b>Department: </b>Computer Science<br><b>Research Area: </b>Model-driven engineering, Software engineering, No-code development
Department: Computer Science
Research Focus: Model-driven engineering, Software engineering, No-code development
Potential Student Project(s):
Most computer science classes start by teaching coding basics like loops, syntax, and algorithms before students get to build anything real. Our project explores a new idea called “Build First, Dissect Later.” Instead of beginning with code, students first use simple no-code tools (such as drag-and-drop or AI-based builders) to build a working app. The analogy is this: students build their own car, drive it around, and later take it apart to see how the engine, tires, and other parts work. In the same way, students will first make a complete app, then gradually dissect it to learn about databases, back-end logic, algorithms, and user interfaces. As a student researcher, you will help test this model by:
- Building small apps (like a mini social media or to-do list) with no-code tools.
- Documenting how app features connect to coding concepts.
- Helping design activities where other students “take apart” their apps. Your work will help us see if this approach makes computer science easier, more engaging, and more welcoming to beginners.
Attributes/skills/background sought in undergraduate:
We seek curious, motivated undergraduates interested in computer science education. No prior coding experience required. Useful skills include creativity, willingness to experiment with no-code tools, clear communication, and attention to detail when documenting and reflecting on learning experiences.
Mentoring Plan:
As a mentor, I will guide the student researcher through a structured, supportive experience that balances independence with close feedback. In the early weeks, I will introduce the student to no-code platforms and modeling tools, providing small, achievable tasks to build confidence. As the project develops, I will encourage the student to take increasing ownership of app-building, documentation, and activity design, while offering feedback on both technical details and broader research goals. Regular check-ins will be used to reflect on progress, troubleshoot challenges, and connect the work to core computer science concepts. I will also support the student in understanding the research process more broadly, including reading related academic papers and discussing potential opportunities for presentations or publications. My goal is to help the student grow as both a learner and a researcher, developing transferable skills in creativity, analysis, and communication.
The student researcher will commit to working 5 hours per week on the project and meet one-on-one weekly for 1 hour either in-person or remotely.
Contact: 765-285-8576, RB 374