52 lines
5.7 KiB
Markdown
52 lines
5.7 KiB
Markdown
### Mission and Scope
|
|
*TODO: Answer these questions in your own words by filling in each*
|
|
|
|
#### What problem does this project address?
|
|
::2-4 SENTENCE PROBLEM
|
|
|
|
#### What is the goal of this project?
|
|
::2-4 SENTENCE GOAL
|
|
|
|
#### What is the scope of this project?
|
|
::2-4 SENTENCE SCOPE
|
|
|
|
#### What development methodology is being used?
|
|
::See our [software development methodology](SDM) document.
|
|
|
|
#### Where should a new team member start?
|
|
::For more information, see the [project proposal](Proposal).
|
|
|
|
### Status
|
|
|
|
*TODO: Briefly describe the status of this project. E.g., what phase are
|
|
you in? And, what is your next major milestone? Detailed project status
|
|
is written in the status reports, not here.*
|
|
|
|
::We have completed our second beta release and are currently working on
|
|
adding more of the functionality described in our product
|
|
[specification](SRS) and fixing defects.
|
|
|
|
::The next major milestone is a third beta release with nearly complete
|
|
functionality and a wider set of testers.
|
|
|
|
### Project Documents
|
|
|
|
|By Activity |Documents |
|
|
|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| Inception: | [Home](Home), [Project Proposal](Proposal), [Target Audience and Benefits](Target-and-Benefits), [Statement of User Needs](User-Needs) |
|
|
| Reference: | [Glossary](Glossary), [Software Development Methodology](SDM), [Document Cross Reference](Document-Cross-Ref), [All-in-one project summary](Summary) |
|
|
| Elaboration: | [Project Plan](Project-Plan), [Software Requirements Specification](SRS), [Feature Set](Feature-Set), [Use Case Suite](Use-Case-Suite), [Design](Design), [QA Plan](QA-Plan), [Test Suite](Test-Suite) |
|
|
| Construction: | [Review Meeting Notes](Review-Meeting-Notes), [Implementation Notes](Implementation-Notes), [User Guide](User-Guide), [FAQ / Troubleshooting Guide](FAQ) |
|
|
| Transition: | [Install / Quick Start](Installation-Guide), [Demo Script](Demo-Script), [Release notes](Release-Notes), [Release checklist](Release-Checklist), [Post Mortem](Post-Mortem) |
|
|
| Continuous: | [Status Report](Status-Report) |
|
|
|
|
|By Audience |Documents |
|
|
|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| For Everyone: | [Home](Home), [Project Proposal](Proposal), [Target Audience and Benefits](Target-and-Benefits), [Statement of User Needs](User-Needs), [Software Requirements Specification](SRS), [Project Plan](Project-plan), [Release Checklist](Release-Checklist), [Glossary](Glossary)|
|
|
| For Management: | [Project Resource Needs](Resource-Needs), [Status Report](Status-Report) |
|
|
| For Developers: | [Design](Design), [Review Meeting Notes](Review-Meeting-Notes), [Software Development Methodology](SDM) |
|
|
| For QA: | [QA Plan](QA-Plan) |
|
|
| For End Users: | [Install / Quick start](Installation-Guide), [User Guide](User-Guide), [Release Notes](Release-Notes) |
|
|
| For Support and Ops:| [Implementation Notes](Implementation-Notes), [FAQ / Troubleshooting Guide](FAQ) |
|
|
| For Sales/Legal: | [Demo Script](Demo-Script), [Legal Issues](Legal) |
|