This preview shows page 1. Sign up to view the full content.
Unformatted text preview: consistent document, that does not look like the contribution of many individuals, but of a solid team. • Title Page • (accurate) Table of Contents • Introductory Problem Statement • History / Research / Current Solutions / Deficiencies of current solutions (if applicable) • Functional Requirements - detail everything that the system has to do. e.g. Interface between user & system, and more • Proposed Solution (optional) - from the domain perspective • Objectives / Goals – Relevance & Quality of Life • User Profile / Deployment Environment / Who will use the system? The system may be used by both a client, and therapist, or family members. There may be many users. • Constraints – budget, schedule, technical (note: not a budget or schedule, but constraints ) • Project Deliverables • Future Plans and Expandability Post your Phase 2 documentation on your web site....
View Full Document
This note was uploaded on 12/11/2011 for the course CSE 442 taught by Professor Buckley during the Fall '06 term at SUNY Buffalo.
- Fall '06
- Software engineering