Tentative Fall 2012 Schedule with Dr. Judy Veranas
Note that reports are due by 8:00 am on the Monday before class.
Week 1: August 27, 2012:
Initiation Phase: Orientation to the Software Development Lifecycle and Project Concept Development
In class:- Discussion on class structure, syllabus, and schedule to be finalized by end of class time
- Discussion on roles: students as project leaders, peers as clients, instructor as supervisor, project director and mentor
- Read Project Proposal Information and Suggestions and discuss ideas
- In class work developing project ideas
- Read on Reports in order to discuss the purpose and expectations for the reports
Week 2: September 3, 2012:
Planning Phase: Project Concept Development
Due before class time:- R1 : Weekly Report, including the Project Concept Proposal and using on Reports
- Mini presentations on proposed projects and small group discussion
- Overview of a Vision and Scope Document and Software Requirements Specifications
- Class discussion
- Individual meetings with Project Director
Week 3: September 10, 2012
Planning Phase: Vision and Scope and Preliminary Software Requirements Specifications
Due before class time:- R2: Weekly Report, including the Vision and Scope Document and Preliminary Software Requirements Specifications and using on Reports
- Mini presentations on vision and scope followed by discussion.
- Individual meetings with Project Director
Week 4: September 17, 2012
Planning Phase: Planning and Software Requirements Specifications
Due before class time:- R3: Weekly Report and refinement of the Software Requirements Specifications (SRS) and using on Reports
- Discussion on designing a software architecture
- In class work on application development
- Individual meetings with Project Director
Week 5: September 24, 2012
Planning and Design Phase: Software Design--the Preliminary Architectural Model
Due before class time:- R4: Weekly Report, including the preliminary design of the software architecture and using on Reports
- Discussion.
- In class work on application development.
- Individual meetings with Project Director
Week 6: October 1, 2012
Implementation Phase: Development of a Prototype Project Component
Due before class time:- R5: Weekly Report, including beginning the implementation of the design of the software architecture
- Discussion.
- In class work on implementation
- Individual meetings with Project Director
Week 7: October 8, 2012
Fall Reading Period - no class meeting and nothing due
Week 8: October 15, 2012
Implementation Phase: Expanding the Prototype
Due before class time:- R6-7: Report on Weeks 6 and 7, including report on implementation progress and prototype
- Prototype of project component
- Mini presentations on prototype componentry followed by discussion
- In class work on application development
- Individual meetings with Project Director
Week 9: October 22, 2012
Implementation: Expanding the Prototype to Alpha or Beta Status
Due before class time:- R8: Weekly Report on the work of week 8 including the addition of a known bugs section
- Prototype expanded to alpha or beta status
- Resume updates due
- Mini presentations on prototype followed by discussion.
- In class work on application development
- Individual meetings with Project Director
Week 10: October 29, 2012
Testing Phase: Initiating the Test Plan
Due before class time:- R9: Weekly Report and report on the Test Plan
- Discussion of resumes
- Presentation and meeting with James Atkinson, Berea College Career Development and Co-Director of Berea College Center for Transformative Learning
- In class work on application development
- Individual meetings with Project Director
Week 11: November 5, 2012
Testing Phase: Unit Testing
Due before class time:- R10: Weekly Report and report on unit testing
- Mini presentations on projects followed by discussion
- Discussion of video demos and public poster session
- In class work on testing and application refinement
- Individual meetings with Project Director
Week 12: November 12, 2012
Testing Phase: Integration Testing
Due before class time:- R11: Weekly Report and report on integration testing
- Mini presentations on projects followed by discussion
- Discussion of video demos and public poster session
- In class work on testing and application refinement
- Individual meetings with Project Director
Week 13: November 19, 2012 - The Day BEFORE Thanksgiving Vacation begins
Continuing Systems Testing and Presentation Phase Begins: Practice Video Demos
Due before class time:- R12: Weekly Report creating the practice video demos
- Of course system testing is likely still going on, so don't worry if everything is not yet perfect.
- Practice demo(s) (no more than 7 minutes in total length) MUST be uploaded into youtube before class. Note that they may be "unlisted" so search engines cannot find them, but they must be uploaded and the URL submitted in the report.
Week 14: November 29, 2012
Continuing Systems Testing and Presentation Phase:
Due before class time:- Have watched and commented in writing on all practice demos using faculty.berea.edu/pearcej/csc493/CSC493-demoeval.doc
- R13: Weekly Report on polishing, testing, demo development, and demo evaluation
- (Possibly revised) practice demo(s) (no more than 7 minutes in total length) must be uploaded into youtube before class.
- Discussions of practice demos in small groups
- Discussion of upcoming Poster Session
Week 15: December 3, 2012
Culmination: Presentation Phase Culminates with Video Demos and Public Poster Session
Due before class time:- RF: Final Report due
- Final codebase with documentation and final executable due
- Final demo(s) (no more than 7 minutes in total length) due to be uploaded into youtube before class
- Final poster for poster session due
- 3:00-4:00 pm Preparation for Public Poster Session
- 4:00-4:50 pm Public Poster Session
Week 16: December 10, 2012
Evaluation Phase: Finals Week Due by December 10, 2012 at 8:00 am
No class meeting- Complete the Post-Production Memo
- Complete the Demo Evaluations using faculty.berea.edu/pearcej/csc493/CSC493-demoeval.doc
- And, please don't forget to submit your course IEQs. Your thoughts matter.