EST 573 Term Project

Overview

Students are expected to produce an educational software program development plan, similar to a research proposal. In fact, the development plan could be prepared in response to an actual RFP (see www.grants.gov). Collaborative proposals (no more than 3 students) are acceptable, but all participants will receive the same grade. (Be aware that funding agencies, like NSF, encourage interdisciplinary proposals).

Students will submit their development and implementation plan as a PDF document/Powerpoint presentation/web site, on CD-R. It is due on the last day of class, and students will present their work on that day to the class.

1) Educational software development plan:

The plan should include a profile of target audience(s), description of learning environment(s), task analysis, software flow diagram, storyboard and/or sample screens, sample content, script, lesson plan(s), proposed milestones, review of technology to be used (and rationale), software prototype assessment plan, and a bibliography. While a proposed development budget is not required, students should be aware of the potential costs of developing and distributing their software and factor it into their plan.

Where possible the development plan should demonstrate that it supports the objectives and meets the criteria for relevant NY State learning standards.

Documentation should be structured with an abstract, introduction, literature review, and the software development proposal and plan. The documentation should contain illustrations, such as photographs and diagrams, and can have appendices as well. Approximate length is 10 - 15 pages.

2) Presentation:

Students are expected to present their term project in class, as well as submit documentation. The presentation should include a slide show or web site, and can include a poster.

Submitting your work

Students should maintain backups of their work. They can use their lab accounts on the file server, but will need to burn a final CD-R that will contain their documentation and presentation, along with all necessary supporting resource files (such as photographs, digital video, etc). The CD-R should be labeled with the student's name(s).

Instructions for logging into your account on the file server >>

Grading

Term projects will be evaluated on thoroughness. Attention should be paid to a good literature review and independent research. A concise and compelling abstract is very important. Although the documentation should be richly illustrated, illustrations should not be gratuitous or merely decorative. The design, function, and content of the proposed software should flow from a solid analysis of:

1. the learner(s), learning task(s), and objective(s)
2. pedagogy for the subject(s) chosen for instruction
3. the learning environment(s) and community
4. the technology to be used, what it offers that is relevant, its limitations, and the benefits expected in using it
5. interface and instructional design guidelines

Project documentation and the presentation should be clean and professional in design. They don't need to be "slick", but they should be high-quality.

Class participation, both in-person and on-line, will be considered in student evaluations.

A grade of "I" (incomplete) for the course is very rarely granted!