PPS0335 PROBLEM SOLVING AND PROGRAMMING

PROJECT GUIDELINES
This project carries 20% (System 10%, Presentation 10%) of your total marks for
PPS0335.
It is a group project consists of maximum 4 students per group.

OBJECTIVES
1. To build an application using a problem solving approach and guided by the
principles of system design.
2. To show excitement over exploring and lifelong learning in problem solving via
programming.
3. To communicate as a team in the process of developing an application.

DELIVERABLES
1. Progress report (Students must be able to produce a progress report when
requested):
a. Proposal (Submission date: Latest by Week 2 )
i. Group members
ii.Brief idea of the system
b. IPO Chart(when requested)
c. Data Dictionary (when requested)
d. Flowchart (when requested)
2. Proper
a.
b.
c.
d.
e.
f.
g.
h.
i.

documentation.
Introduction
Problem Analysis Chart
IPO Chart
Data Dictionary
Algorithm
Pseudocode
Flowchart
Source code
Conclusion

3. A working system written in the C++ programming language

You can create any simple system.
In your system, the requirement is, you MUSTuse all of these 3
components:
o Sequence
o Selection (if .. else)
o Loop (for loop, while loop, do while loop)
Remember: A simple system with good program flow which is easy to
navigate and is free of syntax/logic errors is better than a complicated
system with many errors.
Presentation Date: Week 5 (Tentative Week)

ASSESSMENT
The student will be marked on the rubric given below (exceeds, meets, approaching or
does not meet expectations). Final formula:

ProjectDocumentation(10 )

Presentation (10

%)

Your own work score and the system matched with the documentation score can
effectively halve or quarter your marks if you submit a program which you are unable to
explain or clarify. The best way to avoid receiving a low score is to DO THE WORK
YOURSELF. If you need help, seek help to LEARN programming, not to do the work for
you.
Own Work Score
Criteria
Own Work
Interview

4 Is Own
Work
Student able to
answer all
interview
questions. There
is no doubt in
the lecturers
mind that the
program is the
students own
work.

3 Some
Doubts
Student unable
to answer some
interview
questions. There
are segments of
the program the
student is
unable to
explain.

2 Many
Doubts
Student unable
to answer most
interview
questions.
Student unable
to explain many
parts of the
program.

1 Not Own
Work
Student unable
to provide even
a general idea of
how the
program works,
program is
clearly not
students own
significant effort.

Individual Rating of Group Member

Criteria
Co-operation
Knowledge of
subject matter

Part I: Documentation
Items
1. Introduction
2.
3.
4.
5.
6.
7.
8.
9.

Descriptions
What kind of system is this? Who is the
user? How to use the system?
Problem
analysis For overall system or individual chart
chart
for each module
IPO chart
How can the input be processed to get
the output? What are the processes?
Data Dictionary
A list of all the variables used in the
system
Algorithm
Algorithm is written in the correct
format.
Pseudocode
Pseudocode is written in the correct
format.
Flowchart is drawn correctly with the
Flowchart
correct symbols.
Any recommendation or suggestion to
Conclusion
improve the system?
Properly/Professionally prepared documentation

Marks

Total
Part 2: System
Criteria

4 Exceeding

3 Meets

Requiremen
ts

The program
employs a

The program
contains all

2
Approaching
The program
contains 1 out

1 Does Not
Meet
The program
contains 0 out of

Variables

construct outside
of notes.
(Objects / arrays /
stacks / infile /
etc)
Variables are
defined and
named correctly at
the appropriate
location (global or
private) and
matched with the
data dictionary.

Difficulty

Writing the
program requires
additional
knowledge outside
of what is taught
in the class.
Demonstrates selflearning in
programming.

Error Free
Execution

The program runs

without errors
even when given
unexpected input,
or no possible
input errors.

Part 3: User Interaction

Criteria
4 Exceeding
User
Interaction

Instructions and
commands are
very clear. Able to
recognize different
types of input.
(Capital letter,
small letter, etc).
User interface
looks professional
and screen is
cleared where
appropriate.

Part 4: System Matched

Criteria
4 Exceeding
System
Matched
with
Documentat
ion

Very well
organized.
System 100%
matched with
the
documentation

the
requirements

of the 2
requirements.

2 requirements.

Variables are
defined and
named
properly
(doesnt
matter at the
appropriate
location or
not) and
matched with
the data
dictionary.
In writing the
program, the
student
makes use of
knowledge
taught in class
in interesting
ways.
Demonstrates
deep learning
of
programming.
The program
runs without
errors for
expected
input.

Variables are
defined and
named but
does not follow
the rule of
naming the
variables.
Matched with
the data
dictionary.

There are
variables, but
the variables
name does not
match with the
data dictionary.

In writing the
program, the
student mostly
reproduced the
examples
shown in class.
Demonstrates
surface
learning of
programming.

The program
used examples
from class
poorly, or made
use of limited
programming.
Demonstrates
lack of
understanding in
programming.

The program
runs with some
errors but user
is still able to
see it in action
till the end.

Errors make the

program
unusable and
disallow the user
from seeing the
full extent of the
program.

3 Meets
Program can be
used easily.
Input and
output are
displayed
correctly. User
interface is
neat and well
designed.
Pleasing to the
eye and easy to
use.

3 Meets
The system
basically
matched the
documentation.
At least 4 of
these items (PAC

2
Approaching
Instructions are
not clear and
users are
having problem
using the
system. User
interface is
mostly neat. At
some part,
theres clear
screen.
Program is
usable.

1 Does Not
Meet
The program
requires no
user input.
User interface
is messy, and
difficult to use.
No clear
screen, so
users need to
scroll.

2
Approaching
3 of these
items (PAC / IPO
/ Data
Dictionary /
Algorithm or
Pseudocode /

1 Does Not
Meet
2 of these
items (PAC /
IPO / Data
Dictionary /
Algorithm or
Pseudocode /

including the
constant usage
of variables
name used in
charts /
pseudocode /
algorithm.

/ IPO / Data
Dictionary /
Algorithm or
Pseudocode /
Flowchart)
matched the
documentation

Flowchart)
matched the
documentation.

Flowchart)
matched the
documentation
.

SOFTWARE
C++ Programming Language

EXTRA CREDIT
Marks above and beyond the 100% will be given to projects that go beyond the
requirements of the subject to solve problems or address societal concerns. Extra credit
is on a case by case basis and will be awarded on the sole discretion of the lecturer. You
should discuss with the lecturer on ideas you wish to pursue as extra credit.