Update course outline for challenge level and extra tasks

CourseOutline/CAS741_Outline.tex

@@ -224,7 +224,7 @@ documentation and code.
 
 \item (Traditional and Drasil) Presentations and class discussion 5\%
 
-\item (Traditional and Drasil) ``Domain Expert'' and secondary reviewer roles 10\%
+\item (Traditional and Drasil) ``Domain Expert'' reviewer role 5\%
 
 \item (Traditional and Drasil) Problem Statement, Risk, Proof of Concept (POC) Plan 0\%
 
@@ -236,7 +236,7 @@ documentation and code.
 
 \item (Drasil) Drasil code and Code Explanation Document 10\%
 
-\item (Traditional and Drasil) Final Documentation 55\%
+\item (Traditional and Drasil) Final Documentation 60\%
 \begin{enumerate}
 \item Problem Statement (Revised)
 \item SRS (Revised)
@@ -249,6 +249,7 @@ documentation and code.
 \item System VnV Report
 \item Unit VnV Report
 \item Reflection Report
+\item Extra task (for non-research projects, see below)
 \end{enumerate}
 
 \end {enumerate}
@@ -260,22 +261,23 @@ compelling reason (agreed on with the instructor) why CI is not an option.
 
 Each student will be assigned as a ``Domain Expert'' (DE) for one of their
 classmates.  The DE will review (via GitHub issues) their assigned project. %
-In % addition, they will write the code for one of the modules of their assigned
+%In  addition, they will write the code for one of the modules of their assigned
 % project and issue a pull request through GitHub.  For the secondary reviewer
-role, the instructor will assign various review tasks throughout the term.  The
-secondary reviewers feedback will focus more on the structure and format of the
-documentation, rather than on issues related to domain knowledge.
+% role, the instructor will assign various review tasks throughout the term.  The
+% secondary reviewers feedback will focus more on the structure and format of the
+% documentation, rather than on issues related to domain knowledge.
 
-\subsection{Challenge Level and Extras}
+\subsection{Challenge Level and Extra Tasks}
 
 Due to differences in interests and background, students in this course will
-select topics with varying levels of complexity in both the required domain
-knowledge and in the implementation.  Less advanced projects are an option, but
-to get full grades for a lower challenge project, students should add extra work
-to the scope of their project.  Examples of extra work include usability
-testing, rigorous code walkthroughs, user manual documentation, formal proof,
-GenderMag personas, design thinking, etc.  If advanced projects do extra work,
-the extra work is graded as a bonus.
+select topics with varying levels of complexity in the required domain knowledge
+and possibly in the implementation.  If a project requires graduate-level domain
+knowledge, it is classified as a ``research'' project.  For projects that are
+not ``research'' projects, an extra task required.  Examples of extra tasks
+include usability testing, rigorous code walkthroughs, user manual
+documentation, formal proof, etc.  If a research project does extra work, the
+extra work is graded as a bonus.  The extra task is evaluated as part of the
+final documentation.
 
 \section {Policy Statements}