Contents

Preface

This page presents an example portfolio review specification and an example of a submission. This should be used exclusively as an example and nothing more.

Example specification

Primary skills assessed

The review will focus mostly on the following skills:

Materials

The following materials are required unless otherwise noted.

Example submission

Here is an example portfolio as a zip file: portfolio-example.zip. The README and report are below.

README

README
Portfolio Review Example
Hank Feild
05-Aug-2014

The contents of this portfolio are as follows:

    labs/
        lab1/
            flowchart.pdf  -- Sketch/flow chart for Lab 1.
            planning.txt   -- Requirements, use cases, & pseudo code for Lab 1. 
            reflection.txt -- A reflection on Lab 1.

        lab2/
            flowchart.pdf  -- Sketch/flow chart for Lab 2.
            planning.txt   -- Requirements, use cases, & pseudo code for Lab 2. 
            lab2.cpp       -- Lab 2 program to display formatted number and 
                              strings.
            reflection.txt -- A reflection on Lab 2.

    extra/
        mad-libs
            README         -- an overview of the program and how to run it
            flowchart.pdf  -- Sketch/flow chart for mad-libs.
            planning.txt   -- Requirements, use cases, & pseudo code.
            mad-libs.cpp   -- An extra credit program that prints out an mad-lib
                              using pre-set values.
            reflection.txt -- A reflection on the project.

    topic-questions.txt    -- A set of solutions to the topic questions for this
                              review.

    README                 -- This file.

    report.txt             -- A justification for skill points sought, a
                              reflection on the material, and a PPF.

Report

Report
Portfolio Review Example
Hank Feild
05-Aug-2014


Skill justification
-------------------
I have demonstrated planning using flow charts and pseudo-code in Lab 1, Lab 2, 
and the optional mad-libs project.

I demonstrated my ability to communicate through all the reports and reflections
included, as well as in the comments in the three programs included.

Both labs and the extra credit assignment use variables, constants, and C++
output, including cout.

I demonstrated creativity and effort by submitting an optional assignment that
I designed (mad-libs).

Finally, I have contributed questions, answers, and discussion in all of our 
classes, which I would like you to consider with regards to participation.


Reflection
----------
I am also not sure why it matters where variables are declared or why use
a constant over a variable.

I found the use of cout and declaring variables to be easy.

I've had no real epiphanies.


PPD
---
Past: I had no goals for this review (this is the first one!).

Present: I learned how to use cout and how to declare, initialize, 
update, and use variables and constants.

Future: My goals for next time are to:
1. understand the difference between variables and constants better
2. understand why it matter where variables are declared
3. learn how to read from the user (I want to make my mad-lib program 
   interactive) 
(Back to top)