Project Plan Document [18 pts]

Your Team "Pitch"

The purpose of this project plan is to get you thinking about what you will do for the year-long project. Although you have a project option, the details of the project can vary widely, so it is important you decide on an appropriate scope for your team. This document serves as your "pitch" to the client so you can "sell" your ideas and features. Be creative and unique! Use this opportunity to impress your client.

What to Submit:

Expected Deliverable

You will create an .md file in your repo. All the content of your project plan will be there. When you are done, submit a PDF of the document on Canvas (for easier grading reasons - thank you!).

As you flush out the details of your project, you will need to scope the features and plan out who does what (at least at a high level). The goal is for you to go through the exercise of developing detailed requirements, talking with your teammates to identify what everyone wants to work on, and figure out how each requirement should be tested. You will inevitably come across questions -- this is your chance to gather your questions and ask the client during the first Q&A session. Use those responses to fix up the report before submitting it.

After you submit the report -- I will gather the requirements from each team, pool them together, and discuss them with the client (repeated for each option). We will then come up with a set of core requirements and a set of bonus requirements. Each requirement will be assigned an estimated difficulty level. The requirements will also be aligned to specific milestone due dates (there are 4 in our schedule). You can augment your task assignment based on the consolidated requirements.

Use the following document template as your starting point. Be sure to adhere to the same section headings and expected length requirements. Read the instructions carefully and follow them closely. Don't include the instructions and examples in your report (I just want to read your project, not my instructions and examples again).

Evaluation Rubric

Total marks possible: 18 points.

Criteria Exceeds Expectations Meets Expectations Below Expectations No Submission
Scope, Usage Scenario, Proposed Solution
 [3 pts] The scope is clear and covers the minimal usage scenario completely for the intended user groups. The proposed solution has interesting and unique features. The solution has a strong value proposition. The requirements align with the scope of the proposed solution. The solution is entirely feasible using today's technology. [2 pts] The scope is clear and covers the minimal usage scenario completely for the intended user groups. The proposed solution involves the required features to build a technical solution that addresses the client's challenge. The requirements align with the scope of the proposed solution. The solution is entirely feasible using today's technology. [1 pt] The scope is not clear or the description does not fully cover a usage scenario from start to end. Usage scenario for certain user groups are missing. The proposed solution seems incomplete or cannot feasibly address the client's challenge using today's technology. [0 pt] Not provided
Use Cases
 [3 pts] The use case diagram has excellent coverage and follows the UML syntax. Use cases are extensive and well thought out. All the pre/post conditions for the use cases are clear and correct, the steps in the use case make sense, and the extensions considered are thorough. [2 pts] The use case diagram has good coverage and follows the UML syntax. Use cases are present and well thought out, although more could be added. Each use case has the appropriate pre/post conditions, steps in the use case, and the common extensions are mentioned. [1 pt] The use case diagram has poor coverage and has syntax mistakes. [0 pt] Not provided, low quality, or is largely missing
Requirements, Testing Approach, and Requirements Verification
[6 pts] A test framework has been identified. All or most of the requirements have associated test cases that are well defined, tstable, and automatable. The test cases have good coverage for each requirement and collectively for the system. [4 pts] A test framework has been identified. All the requirements have associated test cases that are well defined and testable. Most of the requirements have test cases that can be automated in that framework. [2 pts] A test framework has not been identified. Most requirements have associated test cases that are well defined and testable. However, most of the tests are manual. [0 pt] Not provided or largely missing
Proposed Teamwork Distribution
[3 pts] Everyone is assigned to a similar number of requirements for each level of difficulty. [2 pts] Everyone is assigned to a similar number of requirements, but of varying levels of difficulties. [1 pt] Not everyone is assigned to requirements, or not all requirements have people assigned to them. [0 pt] Not provided or largely missing
Writing Quality
 [3 pts] Very professionally and concisely written. [2 pts] The report generally reads well and is coherent. [1 pt] The report has many mistakes (technical and grammatical). [0 pt] Not clear at all