CPI Spring 1996 Syllabus






Catalog description of CS411.
Board Presentation

In this course students develop an implementation plan for the project specified in CS410. The implementation plan includes estimates of project size and costs, a development schedule, a resource allocation schedule, a validation plan, and a test plan. The major deliverable of this semester is a fully developed proposal ready for submission to an external funding agency (e.g. NIH, NSF, SBIR, industry see deliverables)

The semester begins with a review and evaluation of the CS410 specifications for the purpose of improving the specifications and determining which areas of the project appear to present the greatest risks in the course of the project's development. Action will be taken to gain knowledge to reduce these risks. In addition to the activities involved in implementation plan as described above, such actions might include prototyping, market research, hardware availability research, simulations, algorithm analysis, and the development of detailed specifications. This pattern of risk estimation and resolution will be repeated several times during the semester. Each project will develop a business plan with costing estimates.

Since the particular activities undertaken depend upon the project chosen and the students' analysis thereof, no set schedule can be written in stone. However the following may serve as an example:

Week 1: Project management structure decided, objectives identified
Week 2: Preliminary schedule outlined, list of deliverables. Charge CS250/CS300
Week 3: HTML and CGI programming
Week 4: CGI/PERL/C
Week 5: Cocomo Costing Model.
Week 6: Project Management
Week 7: CIG maps Week 4-7: Business Plan analysis, Costing models Domain Analysis (Round 1)
Week 8: Mid-Term Peer Review. Risk resolution information received. Appropriate decisions taken. Revised Schedule/Deliverables.
Week 9-12: Second round of planning identifies new risks, for example, high unit cost to consumer. Alternatives to solve problem are assigned to teams for investigation.
Week 10-12: Concurrently, class develops plans for project: development schedule, resource schedule, test plan and validation plan. Possibly include user manual and guide.
Week 13: Finally, plans revised in light of decisions about second round of risk resolution.
Week 14:
Presentation of results. Proposal ready for submission.

Email the cs411 class <cs411@cs.odu.edu>
Email Chief Project Engineer <wild@cs.odu.edu> for changes, questions...
Last updated by: <Chris Wild>
CPI HOME PAGE