⚠️ Student applications and proposals are reviewed and processed on Tuesdays and Thursdays.
Have a software development project that could benefit from skilled computer science students? CSC400 connects real clients with senior-level students for semester-long projects.
Cost-Effective: No development fees (API costs may apply) — students gain real-world experience while solving your business needs.
Skilled Teams: Senior CS students with 6+ advanced courses, working in 3-person teams (6-10 hours/week per student).
Professional Process: Modern practices (Git, CI/CD, testing), regular presentations, instructor oversight, and structured milestones.
Complete Deliverables: Working software, source code, documentation, training materials, and final presentation.
Ideal Scope: 15-week semester, 300-500 development hours, clear, achievable goals, non-mission-critical.
✅ Internal tools & automation
✅ Data dashboards
✅ Proof-of-concepts
✅ Web/mobile apps
✅ AI/ML prototypes
✅ System integrations
❌ Mission-critical systems
❌ Hard May deadlines
❌ Extensive domain expertise
❌ Expensive APIs
❌ Sensitive data
❌ Legacy maintenance
Pre-Semester: Submit proposal → Interview teams → Team matching
Weeks 1-2: Kickoff meeting, refine requirements
Weeks 3-5: Initial development, 1st presentation
Weeks 6-11: Core development, 2nd presentation
Weeks 12-15: Final features, testing, 3rd presentation
Finals Week: Final demo, handoff, deliverables transfer
20-30 hours total over the semester: Initial planning (2-4 hrs), weekly/bi-weekly check-ins (30-60 min), final handoff (2-4 hrs).
What you provide: Clear requirements, weekly availability, timely feedback, domain knowledge, sample data/access (if applicable).
Technical skills: Web/mobile development (React, Vue, Flutter, iOS/Android), AI/ML (chatbots, NLP, classification), databases, APIs, data visualization, testing, deployment.
What students are learning: complex system architecture, client communication, project management, professional development practices, requirement gathering and iteration
Working Software
- Functional application meeting agreed-upon requirements
- Source code repository with version history
- Deployed application (if applicable)
- Testing suite
Documentation
- Technical documentation (architecture, setup, deployment)
- User documentation and guides
- Code documentation and comments
- Maintenance guide
Professional Communication
- Regular progress updates
- Clear status reports
- Professional presentations
- Timely responses to feedback
Training and Handoff
- Training session for end users (if needed)
- Administrative training
- Handoff meeting
- Transition support
Proposal should include: Organization background, problem description, desired outcomes, key features, available resources, timeline constraints.
Submit to: cainn3@southernct.edu
Subject: CSC400 Client Project Proposal - [Organization Name]
Deadline: Mid-November 2025 for Spring 2026
Process: Proposal review → Feasibility discussion → Student team matching → Informational interviews → Team selection → Project kickoff
Q: Do I need to pay the students?
A: No. Students receive course credit.
Q: Can I use the software commercially?
A: Yes. Clients typically retain all IP rights (discussed at project start).
Q: Do I need technical expertise?
A: No. You provide business knowledge; students handle technical implementation with instructor guidance.
Q: Can the project involve sensitive data?
A: No. Use anonymized or synthetic data only.
Q: What happens after completion?
A: You receive all deliverables and are responsible for ongoing maintenance.
Q: What if my needs change?
A: Minor changes are expected. Major scope changes require instructor approval.
Prof. Nisreen Cain | Computer Science, Southern Connecticut State University
Email: cainn3@southernct.edu
Questions? Email cainn3@southernct.edu to discuss your project idea.