Software Engineering Syllabus

Note:

This is a modified syllabus (9-19-02) resulting from conversations between Suzanne Buchele and Michael Higgs. It is still preliminary. The major modification is more of an emphasis on Extreme Programming (XP) principles: in particular, there is no longer an SDS document or Verification and Validation plan or document. Design will follow an overall architecture conceived by the faculty for each project and will evolve during "stand-up meetings" with the students. Students will present to each other and to other teams regularly. Testing will be done as part of development - unit testing, and "use case" testing. This course will encourage "pairwise programming", both in design and implementation, by mixing up pairs within the teams (probably 4 people per team) on a daily basis, and mixing up what part(s) of the project pairs are working on (so one person doesn't become the database expert and know little about the rest of the project, for example).

Saturday, June 7: Students arrive at Southwestern University in Georgetown, TX.

Week One: June 9-13

Faculty: Paula Gabbert (Furman) & Donald Schwartz (Millsaps)

Mornings
Teamwork (readings and discussion, importance of, team building exercises), Project Planning and Management Issues (Gannt Charts, PERT chanrts, etc.), Requirements Anaylsis (teach what is necessary for them to get started on their projects).
Afternoons:
Various workshops on topics of interest:
Suggested topics: Weeklong case study using CASE tools, carrying over into week 2, CVS (introduce a particular tool), Databases and mySQL, Unix shell commands, PERL, PHP, UML, Technical writing and presentation issues, Web Page Development and Design, Others? These workshops would introduce the major ideas, and point them to resources where they might learn more/teach themselves what they need.

Week Two: June 16-20

Faculty: Michael Higgs (Austin College)

Mornings:
Projects and teams assigned. Software Life Cycle and Development Models, including XP and agile methodologies
Afternoons:
Case study continues. Begin working in teams on testing framework and on Requirements Analysis and development of SRS (Software Requirements Specification). 1st draft of SRS by end of week 2. Introduce conceptual framework for architecture of project..

Week Three: June 23-27

Faculty: Shellene Kelley (Austin College); (Suzanne Buchele and Kevin Treu will be around)

Mornings:
Requirements Reviews, more Teamwork, begin daily stand-up meetings for design evolution.
Afternoons:
Work in teams, finish SRS by mid-week, begin implementation of testing framework for use cases. Faculty meet with teams for feedback for on 1st draft of SRS on Monday, and for Formal Requirements Review when final draft of SRS is complete. Faculty work with students on design evolution

Week Four: June 30-July 3 (Friday, July 4 is a holiday)

Faculty: Donald Schwartz may be available; (Suzanne Buchele will be around); virtual mentoring via the CDS

Mornings:
Daily stand-up meetings continue, more Teamwork, Project Planning and Management Issues
Afternoons:
Work in teams, in pairs within teams. Mix up pairs and sub-project they are working on daily.

Weeks 5-8: July7-11; 14-18; 21-25; July 28-August 1
Teams work independently, communicating with faculty via email/phone as needed. Beta testing of projects begins in Week 8 (ACSTC staff can help facilitate, find testers, etc)

Week 9: August 4-8
Project presentations, wrap-up, evaluation of process and teams, evaluation of internship program.

Saturday, August 9: Students depart.