Client Sponsored Projects in Software Engineering (Preparation and Planning) Ken Surendran Southeast Missouri State University cst.semo.edu/surendran/capstone/index.htm

Preparation and Planning Based on experience with three different approaches: UNITEC, NZ (one semester two-course credit, one or two students per project) Rose-Hulman, IN (two quarter, one-course credit per quarter, five students per project) SEMO, MO (one semester, project is part of SE course, five students per project)

Planning Issues Course Sequencing Identifying sponsors and projects Project Allocation Team size Evaluation Supervisor Workload

Sequencing and Timing Ideal to have a SE concept course just before the capstone (Junior Year) Get the projects presented during the previous semester (SE course) Give team based projects with phased deliveries in the concept course Discuss project management issues Have Seniors share project experience

Identifying project sponsors Identification –By students (reviewed by committee) –By faculty members –By Advisory committee and or Alums –Mix of External clients and internal clients –Must be known (directly / indirectly) Scoping the project with client –Analysis and design elements –Avoid time critical ones; Proof of concept –Ensure resources for development

Project Allocation Presentation by clients –Contacts –Special requirements / constraints Team formation –Known before to each other –Team coordinator (PM) Teams choose their projects from list –Guidance during selection; avoid forcing –Match interest with application domain

Team Size Could vary by project and curriculum intent Two per team Usually four per team Factors –Number of students –Number of credits –Size and type of the project Ensure balance

Evaluation Comprehensive; several inputs Presentation to advisory committee and other faculty members Organize a show and tell day for demo Clients provide feedback throughout Other teams to evaluate Decided by the Supervisor but guided by other faculty and advisory board and client

Supervisor Workload Usually high Liaison with client Visit client with team Weekly review meetings (observer and project director) Three teams equivalent to one course