Legacy Document Guidelines
As you proceed through the development of your chosen software product,
you should begin the final document required for this course--the legacy
document. You may consider the legacy document your team's diary of project
activity. My expectations of the legacy document are somewhat different
from those usually found in practice. The rationale for this document is
to give you a place to collect various information about the project over
time and to react to certain activities during the semester. It is an
opportunity for each of you to consider the experiences of the semester.
The format of the legacy document is --
- Section 1: Project Description
- Provide an overview of the project your group worked on. This should be
some combination of the problem statement and solution strategy from the system
definition.
- Section 2: Current Status of Project
- Describe the nature of the process through which the group has gone.
Try to present a sense of where the group is on the project versus where
I think they should be, and why there is a discrepancy between these views.
- Section 3: Initial Expectations
- Each has team member prepared a statement.
- Section 4: Technical Lessons Learned
- Each team member should write a short narrative regarding what
technical lessons were learned during the project. Be sure that each
team member is named within the portion they write.
- Section 5: Managerial Lessons Learned
- Each team member should write a short narrative regarding what
management lessons were learned during the project. Be sure that each
team member is named within the portion they write.
- Section 6: Recommendations for Future Projects
- Section 7: Final Comments
- A narrative from each team member that summarizes the experience(s) of
the semester. Look back at you initial expectations and react to them.
Give serious attention to what you have done/learned/not learned during
the semester.
- APPENDIX I: Progress Reports (those you submit, and I comment on)
- APPENDIX II: Minutes from all Meetings (group and/or subgroup)
- APPENDIX III: Reviews or correspondence related to the project
This document should be wordprocessed and submitted in a three-ring binder.