_GRADE.md 4.21 KB
Newer Older
Preston Carman's avatar
Preston Carman committed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
# CPTR 142: Group Project

The sections below outline the initial requirments.
The grade sub-section lists your current grade and feedback to improve your grade.

## Proposal

The proposal states the basic idea and who will be working on the project.

* List of __group members__.
* Provide a __clear problem definition__.
  What is required of the system?
  What must it accomplish or provide?
  Do you make any assumptions?
* Create a __repository in gitlab__ and give all group members access.
  Please name the repository "cptr142\_group\_project".

___Submission___
Create a _PROPOSAL.md_ file in your repository with the above information.

### Grade 

_Feedback_
* Listed members __complete__
* Clear problem definition __complete__
* Repository created __complete__

__PROJECT APPROVED__

## Specifications

The specifications outlines the project design specifications and project management.

* ___Complete UML diagrams___ of classes, member variables, member functions, and relationships between classes.
  What structures and menus will be required?  
* ___Procedural Flow Diagram___ The logical flow of your program
* ___Anticipated challenges___ and how will you address them?  
* ___Project Management Plan___
  * Name __individual group member tasks/responsibilities__. 
    Split up the tasks and implementation into portions per group member. 
  * __Timeline__ of individual and group delivery dates.


___Submission___
Create a _SPECIFICATIONS.md_ file in your repository with the above information.

### Grade

_Feedback_
* Included complete UML diagrams __complete__
* Included a procedural flow diagram __incomplete__
  * Please make this into a diagram
* Listed anticipated challenges __complete__
* Detailed project management plan __incomplete__
  * Please break down each deadline into taks for each person.

Grade: __M__ 3/1/2018

Preston Carman's avatar
Preston Carman committed
59 60 61 62 63 64 65 66 67

_Feedback_
* Included complete UML diagrams __complete__
* Included a procedural flow diagram __complete__
* Listed anticipated challenges __complete__
* Detailed project management plan __complete__

Grade: __E__ 3/11/2018

Preston Carman's avatar
Preston Carman committed
68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110

## Project Implementation

* Your project implementation MUST include the following:
  * Use the [CS Department GIT Repository](http://gitlab.cs.wallawalla.edu) for version control and submission.
  * __Object-oriented programming__ with classes.
  * __Separate interfaces (headers)__, __implementation files__, a __main driver__, and  __test driver__.
  * __File I/O__. 
    Include some form of file use even if only to capture results.
  * __Well-commented, “clean”, and well-organized code__.
  * __Well-tested code__ with a driver file.
  * __README.md file__ complete with known bugs and user operation instructions.
  * You should __employ__ the following concepts _as appropriate_ to the program: vectors, pointers, dynamic memory, string manipulation. 
* __Quality of the code__ and the problem __level of difficulty__ will be considered.
* __To make an E on this project__, you must reach into advanced concepts and present quality code solution. 
  Top projects designs show ingenuity, creativity, and efficiency. 
  Demonstration that you have shown initiative, going above and beyond basic course coverage into utilization of advanced concepts. 
  For instance, inheritance, polymorphism, recursion, graphics libraries, some other more advanced data structures of the STL Library (e.g. linked lists, stacks, queues, binary trees, etc.) 

___Submission___
Gitlab project code will be up-to-date per the due date.

### Grade

_Feedback_
* Group project is saved in Gitlab __complete__
* Object-oriented programming __complete__
* Separate interfaces, implementation, main, and test code __complete__
* Uses file I/O  __incomplete__ 
  * No file i/o
* Well-commented, “clean”, and well-organized code  __incomplete__
  * Minimal comments for interfaces. Please fill in.
* Well-tested code with a driver file __incomplete__
  * More tests. One is not enough.
* README.md file with known bugs and user operation instructions __incomplete__
  * Missing.
* Used appropriate concepts to the program __complete__
  * Examples: vectors, pointers, dynamic memory, string manipulation
* Quality of the code __complete__
* Use of advanced concepts __complete__
  * Please explain what concepts. 

Grade: __R__ 3/19/2018