Assessment 2: Planning

Assessment 2: Planning (25 points)
Due: see the course outline for a specific date
In this assignment, you will practice writing a plan to define a project requirement (Assignment 3 project).
You need materials from lesson 3, 4 and 5 to complete this assignment. Please check the instruction and
requirements to complete this assignment.
In assignment 3, you will create your first mobile-fit web application. The project is creating a mobile todo list web application. For now, we need to write a plan for that web application. You will start by
collecting requirement, design, and sketch a prototype. Please check the instruction and requirements to
complete this assignment.
◼ Instructions
1. Your plan should be organized into three sections:
a. The first section (Description Section) holds your description and understanding of the
project. This section should answer questions of “What do you want to make?” and
“What technology will you use?”. (Use Lesson 4 slides for help)
i. “What do you want to make?”
1. Steps required to accomplish the project objectives
2. Tasks needed to be done at each step (using Work Breakdown Structures)
3. An estimate of how much effort each task requires
4. The resources required for each task
ii. “What technology will you use?”
1. Languages (e.g. HTML, CSS, JavaScript)
2. Libraries (e.g. jQuery, Bootstrap)
3. Environments (e.g. cross browsers)
b. The second section (Feature Section) holds all the information about the project
(application) features. You must draw a chart for each feature and identify the process
flow between features. You only need to use features listed in assignment 3, under the
‘instructions’ section. This section should answer questions of “What features will
application include?”.
c. The third section (Prototype Section) holds all the information about the project prototype.
You must provide a design and height level chart. The prototype should show the feature
and process flow and how these processes related to each other.
2. Things to keep in mind:
a. The project features (code) should be divided into units of (tasks/steps) functionality —
modules, services, etc. Avoid the temptation to have all of your code in one
huge $(document).ready() block. This concept, loosely, is known as encapsulation.
b. Despite jQuery's DOM-centric nature, JavaScript applications are not all about the DOM.
Remember that not all pieces of functionality need to — or should — have a DOM
representation.
Page 2 of 3
c. Units of functionality should be loosely coupled, that is, a unit of functionality should be
able to exist on its own, and communication between units should be handled via a
messaging system such as custom events or pub/sub. Stay away from direct
communication between units of functionality whenever possible.
◼ Requirements
1. The project plan must include all the three sections of the project description, feature chart, and
project prototype.
2. The document should format as follows:
a. Font size must be 12 points.
b. Font type is Arial
c. Headlines should be in bold, and paragraph should not be bold.
3. The project plan should not exceed three pages.
4. Don't repeat yourself. Identify similarities among pieces of functionality and use inheritance
techniques to avoid repetitive features.
Please refer to the rubric at the end of this document for evaluation details.
Submit
1. Name your folder assignment_2_project.
2. Right-click on the folder and select ‘Send to - Compressed (zipped) folder’.
3. Upload the zipped folder to the Assignment 2 Dropbox
How to zip your project folder:
Here are some links that may help with compressing your main/root folder and only send that zip folder
• How to zip a file in Windows 10: https://www.laptopmag.com/articles/how-to-zip-files-windows-10
• Free file compressor application for Windows: http://www.7-zip.org/download.html
• How to zip a file in Mac: https://www.lifewire.com/how-to-zip-and-unzip-files-and-folders-on-amac-2260188
• Free file compressor application for Mac: https://theunarchiver.com/
• How to save a pdf in MS Word document: https://www.bettercloud.com/monitor/theacademy/save-word-doc-pdf/
Page 3 of 3
Evaluation
This assessment is graded out of 25 points and will be evaluated using the following rubric.
Learners may receive partial scores or zero for unacceptable work.
Excellent: 5 point Good: 3 point Fair: 1 point Poor: 0 point Score
Identifying
Description, feature
chart and Design
prototype sections are
identified, evaluated
and completed as
requested.
Description, Context
diagram and Design
prototype sections
are identified,
evaluated and
completed as
requested.
Description,
Context diagram
and Design
prototype sections
are identified and
evaluated but are
not completed as
requested.
Description, Context
diagram and Design
prototype sections are
identified but are not
evaluated and not
completed as
requested.
/5
Amount of
info for each
section
All relevant information
was obtained and
information for all
sections.
Most relevant
information was
obtained and
information for all
sections.
Most relevant
information was
obtained but not
information for
some of the
sections.
Few relevant
information was
obtained but not
information for most of
the sections.
/5
Application
design
related to
collected
information
Application design
considerations were
well supported by the
information.
Application design
considerations were
well supported by the
information.
Application design
considerations
were supported by
the information.
Application design
considerations were not
supported by the
information.
/5
Final
In general, there is
descriptive information
about the application.
In general, there is
enough descriptive
information about the
application.
In general, there is
descriptive
information about
the application.
However, few
inaccuracies make
it
incomprehensible.
In general, there is
almost no descriptive
information about the
application. Many
inaccuracies make it
incomprehensible.
/10
TOTAL /25