diff options
| -rw-r--r-- | README.md | 7 | ||||
| -rw-r--r-- | docs/Checkpoint.md | 9 | ||||
| -rw-r--r-- | docs/Final.md | 9 | ||||
| -rw-r--r-- | docs/Proposal.adoc | 21 | ||||
| -rw-r--r-- | docs/Proposal.md | 15 |
5 files changed, 22 insertions, 39 deletions
@@ -2,6 +2,7 @@ Team members: -- Name1 -- Name2 -- Name3 +- Freya Murphy <freya@freyacat.org> +- Audrey Fuller <alf9310@rit.edu> +- Yusif Elsharawy <yse2561@rit.edu> +- Ryan Symons <ras1178@rit.edu> diff --git a/docs/Checkpoint.md b/docs/Checkpoint.md index b5454e4..f6d87f3 100644 --- a/docs/Checkpoint.md +++ b/docs/Checkpoint.md @@ -2,9 +2,10 @@ Team members: -- Name1 -- Name2 -- Name3 +- Freya Murphy <freya@freyacat.org> +- Audrey Fuller <alf9310@rit.edu> +- Yusif Elsharawy <yse2561@rit.edu> +- Ryan Symons <ras1178@rit.edu> ## Summary Description @@ -49,7 +50,7 @@ The following should be deleted from the checkpoint document, but is included in - An “easy” project that required trivial data structures and algorithms. Feedback about how to extend the project was ignored. (Projects falling into this category are likely to lose points in Style/Design as well.) - A “moderate” project that applied basic course concepts, but did not require the group members to significantly challenge themselves or to learn something new. - A “challenging” project that demonstrates significant thought in design and implementation. Clear that the group members challenged themselves and learned something new by undertaking the project. - - What work was done for the project? (This includes both the work embodied by the final submission and work not obvious from the final submission (e.g., approaches attempted but then abandoned, suitably described).) + - What work was done for the project? (This includes both the work embodied by the final submission and work not obvious from the final submission (e.g., approaches attempted but then abandoned, suitably described).) - Did the project require learning advanced features? - Did all team members contribute to the project? - Presentation (10\%) diff --git a/docs/Final.md b/docs/Final.md index a08ba3a..7332d1e 100644 --- a/docs/Final.md +++ b/docs/Final.md @@ -2,9 +2,10 @@ Team members: -- Name1 -- Name2 -- Name3 +- Freya Murphy <freya@freyacat.org> +- Audrey Fuller <alf9310@rit.edu> +- Yusif Elsharawy <yse2561@rit.edu> +- Ryan Symons <ras1178@rit.edu> ## Summary Description @@ -56,7 +57,7 @@ The following should be deleted from the final project report, but is included i - An “easy” project that required trivial data structures and algorithms. Feedback about how to extend the project was ignored. (Projects falling into this category are likely to lose points in Style/Design as well.) - A “moderate” project that applied basic course concepts, but did not require the group members to significantly challenge themselves or to learn something new. - A “challenging” project that demonstrates significant thought in design and implementation. Clear that the group members challenged themselves and learned something new by undertaking the project. - - What work was done for the project? (This includes both the work embodied by the final submission and work not obvious from the final submission (e.g., approaches attempted but then abandoned, suitably described).) + - What work was done for the project? (This includes both the work embodied by the final submission and work not obvious from the final submission (e.g., approaches attempted but then abandoned, suitably described).) - Did the project require learning advanced features? - Did all team members contribute to the project? - Presentation (10\%) diff --git a/docs/Proposal.adoc b/docs/Proposal.adoc deleted file mode 100644 index b1ec2fb..0000000 --- a/docs/Proposal.adoc +++ /dev/null @@ -1,21 +0,0 @@ -= Dungeon Crawler
-Freya Murphy <tam2214@rit.edu>
-Audrey Fuller <alf9310@rit.edu>
-Yusif Elsharawy <yse2561@rit.edu>
-Ryan Symons <ras1178@rit.edu>
-
-:toc:
-
-== Summary
-
-== Use Cases
-
-== Components
-
-== Testing
-
-== MVP
-
-== Stretch Goals
-
-== Timeline
\ No newline at end of file diff --git a/docs/Proposal.md b/docs/Proposal.md index d6cec75..aea91cd 100644 --- a/docs/Proposal.md +++ b/docs/Proposal.md @@ -2,9 +2,10 @@ Team members: -- Name1 -- Name2 -- Name3 +- Freya Murphy <freya@freyacat.org> +- Audrey Fuller <alf9310@rit.edu> +- Yusif Elsharawy <yse2561@rit.edu> +- Ryan Symons <ras1178@rit.edu> ## Summary Description @@ -19,9 +20,9 @@ A summary description of the overall goal of the project. modules). - Thoughts on testing. These might include critical functions or data structures that will be given `#[test]` functions. Also consider using the - [`insta`](https://crates.io/crates/insta) crate, - [`mockall`](https://crates.io/crates/mockall) crate, - [`proptest`](https://crates.io/crates/proptest) crate, + [`insta`](https://crates.io/crates/insta) crate, + [`mockall`](https://crates.io/crates/mockall) crate, + [`proptest`](https://crates.io/crates/proptest) crate, [`quickcheck`](https://crates.io/crates/quickcheck) crate, [`test_case`](https://crates.io/crates/test-case) crate, or [`cargo fuzz`](https://rust-fuzz.github.io/book/cargo-fuzz.html) tool. @@ -56,7 +57,7 @@ The following should be deleted from the proposal document, but is included in t - An “easy” project that required trivial data structures and algorithms. Feedback about how to extend the project was ignored. (Projects falling into this category are likely to lose points in Style/Design as well.) - A “moderate” project that applied basic course concepts, but did not require the group members to significantly challenge themselves or to learn something new. - A “challenging” project that demonstrates significant thought in design and implementation. Clear that the group members challenged themselves and learned something new by undertaking the project. - - What work was done for the project? (This includes both the work embodied by the final submission and work not obvious from the final submission (e.g., approaches attempted but then abandoned, suitably described).) + - What work was done for the project? (This includes both the work embodied by the final submission and work not obvious from the final submission (e.g., approaches attempted but then abandoned, suitably described).) - Did the project require learning advanced features? - Did all team members contribute to the project? - Presentation (10\%) |