Assignment 2 Instructions Summary
Assignment 2 is a team coding project.
We will take you through a waterfall-agile hybrid software engineering methodology
between Weeks 5 and 11.
Your team will only begin coding this assignment in Week 8.
This assignment is due Week 11, Friday at 11:55PM (Local Campus Time) to Moodle.
Key points of this assignment
1. Your team must complete the assessment for a given milestone or phase before moving onto the next phase or milestone. Standard late submission penalties apply for each milestone.
2. Individual students may not receive a mark for the milestone if any evidence exists that they did not contribute to the milestone submission requirements (i.e. document). Each member of the team must contribute evenly to each deliverable to receive the full mark. Your demonstrator will use the activity/revision history of the document to observe contribution. Your documents must be Google Documents and not Microsoft Word files in order to avoid any penalties from not being able to assess contribution.
3. You will be following the schedule set out as follows:
– Week 5: Project Planning Phase
– Week 6: Requirements Gathering Phase
– Week 7: Design Phase
– Week 8-11: Prototyping and Implementation Phase
4. Your team must work on the assignment progressively using the private team repository created for you (i.e. 21-T2-T#). Your team will need to set the repository up yourselves, in the same way you did earlier in the trimester.
5. Your work is subject to the scaling factors set out in the Assessment Information block on Moodle for Assignment 2.
– Interview
– Peer Assessment
– Use of Tools
– Trello (Task / Project Management)
– Git (Code)
– Google Drive (Documentation)
– Peer Evaluation
6. Here’s the mark breakdown for this assignment: – Code (14% Total)
– All Code submitted (Assessed in W12 14%) – Documentation (6% Total)
– Project Management Plan (Assessed at the end of W6 1%)
– Requirements Document (Assessed at the end of W7 2%)
– Design Document (Assessed at the end of W8 2%)
– Implementation Planning Document (Assessed at the end of W9 1%)
– Presentation (4% Total)
– Team (Assessed in W12 2%)
– Individual (Assessed in W12 2%)
You can read more information about the milestones in the project information document.
Plagiarism and Collusion Warning
This is a team assignment, so work on it within your team only. If you have any questions or need help, seek help from the unit staff.
We will use MOSS to check for plagiarism and collusion in the assignment.
Plagiarism and collusion are serious academic offenses at Monash College. Students must not share their work with others. Students should consult the policy linked below for more information.
https://www.monash.edu/students/academic/policies/academic-integrity
https://www.monash.edu/engineering/current-students/enrolment-and-re-enrolment/course- information/assessment-and-examinations/academic-integrity-and-plagiarism
Students involved in collusion or plagiarism will be subject to disciplinary penalties, which can include:
• The work not being assessed
• A zero grade for the unit
• Suspension from the College
• Exclusion from the College
Students are not allowed to refer to or use code from any online source, with the exception of:
· MDL Reference (https://getmdl.io/)
· MDN JS Reference (https://developer.mozilla.org/en-
US/docs/Web/JavaScript/Reference)
· Icons from MDL (https://material.io/resources/icons/?style=baseline)
· MDN HTML Reference (https://developer.mozilla.org/en-
US/docs/Web/HTML/Reference)
· MDL Cheatsheet (https://eng1003.monash/materials/mdl-reference.html)
· Workshop or Moodle material from this unit
Special Consideration
Special consideration applications are to be made online via the student portal on moodle.
Scaling Factors
Verification of Work (Interview)
You will be subject to an interview about your submitted work after the assignment submission.
This interview is used to verify that you have done the work yourself, and that you can demonstrate an understanding of the work submitted. The interview will be conducted during your Week 12 practical class.
If you miss your assignment interview, you may receive a 0 for the assignment part. You need to contact unit staff to reschedule (if you know in advance that you can’t make it) or to apply for special consideration (after you missed it) within two working days.
If your team has submitted the assignment late and missed the assigned timing (in-class) for the interview, you need to contact the unit staff immediately after submitting to schedule an assignment interview.
Interview marking rubric
Category
No understanding
Trivial understanding
Selective understanding
Tolerable understanding
Complete understanding
Description Penalty
The student has not prepared, cannot answer even the most basic 100% questions and likely has not even seen the code before, or was absent.
The student may have seen the code before and can answer something 30% partially relevant or correct to a question but they clearly can’t engage in a
serious discussion of the code.
The student gives answers that are partially correct or can answer 20% questions about one area correctly but another not at all. The student has
not prepared sufficiently.
The student is reasonably well prepared and can consistently provide 10% answers that are mostly correct, possibly with some prompting. The student
may lack confidence or speed in answering.
The student has clearly prepared and understands the code. They can 0% answer the questions correctly and concisely with little to no prompting.
If you miss your assignment interview, you will receive a 0 for the assignment part. You need to contact us to reschedule (if you know in advance that you can’t make it) or to apply for special consideration (after you missed it) within two working days.
If your team has submitted the assignment late and missed the assessment timeslot for the interview, you need to contact us immediately after submitting to schedule an assignment interview.
Below are the other scaling factors. Peer Assessment
You are expected to work together as a team on this assignment and contribute roughly equal amounts of work. Peer assessment will be conducted via the CATME online system. You will receive email reminders at the appropriate time.
Not completing the CATME peer assessment component may result in a score of zero for the assignment.
Do:
• Give your teammates accurate and honest feedback for improvement
• Leave a short comment at the end of the survey to justify your rating
• If there are issues/problems, raise them with your team early
• Contact your demonstrators if the problems cannot be solved amongst yourselves
Do NOT:
• Opt out of this process or give each person the same rating
• Make an agreement amongst your team to give the same range of mark
The goal of peer assessment is to evaluate the contribution and participation in the assessment throughout the assessment period. Based on your results, your marks may increase or decrease.
Use of Tools
Each team member will be individually assessed on their use of three tools for collaborative software development:
● Bitbucket (and GitKraken) for managing revisions of the app source, and handling commits by multiple team members.
● Trello for project management and issue tracking.
● Google drive for document authoring.
The history of your contribution over the entire period of the assignment, on Bitbucket, Trello and Google drive will be individually considered. For the use of each of these tools you will be given a score depending on your observed level of contribution. Students with less than the acceptable level of contribution for will incur a penalty to their assignment mark:
Score
The student made no significant (non-trivial) contribution using the prescribed Tool during the assignment period.
The student made a couple of significant contributions during the assignment period, or made more but only in a burst at the beginning or end of the assignment period.
The student demonstrated sustained use of the Tool over the assignment period, making regular significant contributions.
Penalty
10% (0.9) 5% (0.95)
0% (1.0)
Note: It is not enough to just use these tools for some dummy actions just prior to submission. This will not be counted. It is expected that you will use these tools regularly throughout the term of the assignment. You must give your demonstrator access to your team Bitbucket repository, Trello workspace and Google Drive folder for Assignment 2.
Other Penalties
You are also required to meet coding standards (See Moodle for section on Forums, Forms and Other Resources), specifically in:
· Indentation
· Naming Conventions
· Scoping of variables and functions
· Function / File header comments
· Use of Magic Numbers
You should refer to the marking rubric (available in week 8) as to the scope and penalties for the specific items relating to these items.
You will also need to start each JavaScript file with “use strict”; to use strict mode checking.
You should also adhere to good programming practices that you will learn through working on the assignment, and through examples from your demonstrator. There is a coding standards document found on Moodle under ‘Forms and other resources’.
Submission and Late Penalties Submission
The assignment is to be completed on the team private Git Repository, and submitted on Moodle as a zip file named as TeamXXX.zip (i.e. Team011.zip).
Do not zip your entire git repository up for your submission.
ONLY submit the zipped folder ‘A2’ with the app following the folder structure below. You do not need to submit the documentation again, but need to include an Assignment Group Cover Sheet and include it in the root folder (A2) of the zip file as a PDF file.
If you fail to follow instructions, we can refuse to mark your assignment.
You should have the main ‘home’ page named index.html, with any other pages named appropriately (otherPage is an example used here).
Late Submission Penalty
Unless an extension or special consideration has been granted, students who submit an assessment task after the due date will receive a late-penalty of 10% of the available marks in that task per calendar day. Assessment submitted more than 7 calendar days after the due date will receive a mark of zero (0) for that assessment task. Students may not receive feedback on any assessment that receives a mark of zero due to late-submission penalty.
I need help
The unit staff will be available should you need help.
You can also ask questions about the assignment on the Moodle ‘Forum’ section.
You can also seek early feedback between Monday and Friday for each milestone by making a question post in the appropriate A2 section on the forums and attach the PDF of your work.
If the nature of your question requires you to show us some code that you’ve written, make sure you select the private option when posting a question. This ensures that other students will not be able to see your code. Always use the code snippet block (box with the angled brackets icon) to post code, or the web snippet block (box with the globe icon).
Before asking for a clarification, please look at the Assignment FAQ and forum. Check the Helpdesk Schedule on Moodle for information on these.