Skip to the content | Change text size
PDF unit guide

FIT1040 Programming fundamentals - Semester 2, 2014

This unit will provide students with an overview of the fundamentals required to create programs. Students will learn to develop descriptions of algorithms and program logic using pseudocode which will be implemented as working software programs using a visual procedural programming language. The unit will explore a variety of application domains including: computer games, business and science applications, computer generated arts, computer-based simulations and the control of simple robots. The topics covered will include the fundamental concepts: data types and structures, basic types of input and output, program control structures, and modular design along with the basics of event-driven programming and objects. These topics will be covered while placing an emphasis on the need to design program code that is easy to maintain, readable, tested, and well documented.

At the end of the unit students will be expected to be able to apply the knowledge and skills learned in further units that cover software development using industry strength programming languages.

Mode of Delivery

Clayton (Day)

Workload Requirements

Minimum total expected workload equals 12 hours per week comprising:

(a.) Contact hours for on-campus students:

  • 2 hours of lectures
  • One 2-hour laboratory
  • One 1-hour tutorial

(b.) Study schedule for off-campus students:

  • Off-campus students generally do not attend lecture and tutorial sessions, however should plan to spend equivalent time working through the relevant resources and participating in discussion groups each week.

(c.) Additional requirements (all students):

  • A minimum of 7 hours independent study per week for completing lab and project work, private study and revision.

Unit Relationships

Prohibitions

FIT1002

Chief Examiner

Campus Lecturer

Clayton

Dr Marc Cheong

Consultation hours: TBA

Tutors

Clayton

Mr Phil Abramson (Head Tutor)

Consultation hours: TBA

Mr Tharindu Bandaragoda

Dr Milena Mitic

Mr Ranjie Mo

Ms Vidya Saikrishna

Mr Omid Zanganeh

Ms Shuang Yu (Sherry)

Mr Luke Nickholds

Your feedback to Us

Monash is committed to excellence in education and regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through the Student Evaluation of Teaching and Units (SETU) survey. The University’s student evaluation policy requires that every unit is evaluated each year. Students are strongly encouraged to complete the surveys. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.

For more information on Monash’s educational strategy, see:

www.monash.edu.au/about/monash-directions/ and on student evaluations, see: www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html

Previous Student Evaluations of this Unit

Student feedback about this unit - which is new - has been very positive. There will be minor adjustments to the presentation of the content. One irritation that students have noted is that the tutorial exercises took longer than the hour allocated. That will be adjusted in this offering.

Staff watched the progress of students who completed this unit closely. The unit provided to be an excellent introduction to programming for students undertaking further study in units with an "industrial" language in semester 2. Staff in subsequent units noted that students in those units were a little thrown when they first had to code by typing their code in an exact syntax.

The unit content will be adjusted to help students transition a more smoothly to a real-world language.

If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp

Academic Overview

Learning Outcomes

At the completion of this unit students should be able to:
  • recognise the relationship between a problem description and program design;
  • implement problem solving strategies;
  • construct and test simple computer programs;
  • analyse and debug existing programs;
  • recognise the importance of programming and documentation;
  • apply good programming practices in accordance with industry standards and professional ethics.

Unit Schedule

Week Activities Assessment
0 Students should read the unit guide and become familiar with the assessment requirements of the unit No formal assessment or activities are undertaken in week 0
1 Introduction to programming with Scribble  
2 Finding errors in programs: testing and debugging Laboratory work and short tutorial quizzes are assessed weekly between Weeks 2 to 11 (inclusive)
3 Using variables in programs  
4 Making decisions in programs  
5 Using loops  
6 Using loops (continued)  
7 Using lists in loops Assignment 1 due Sunday 11:59pm
8 Searching and sorting algorithms  
9 Using abstraction to represent game play  
10 Using sprites and messages  
11 Software development and programming environments I Assignment 2 due Sunday 11:59pm. Laboratory Work and Short Tutorial Tests end
12 Software development and programming environments II Assignment 2 interviews held
  SWOT VAC No formal assessment is undertaken in SWOT VAC
  Examination period LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/
academic/education/assessment/
assessment-in-coursework-policy.html

*Unit Schedule details will be maintained and communicated to you via your learning system.

Teaching Approach

Lecture and tutorials or problem classes
This teaching and learning approach helps students to initially encounter information at lectures, discuss and explore the information during tutorials, and practice in a hands-on lab environment.

Assessment Summary

Examination (3 hours): 60%; In-semester assessment: 40%

Assessment Task Value Due Date
Assignment 1: Programming Basics 10% Sunday 11:59pm Week 7
Assignment 2: Advanced Programming Application 10% Sunday 11:59pm Week 11. Interviews held in Week 12
Laboratory work and short tutorial quizzes 20% The end of the tutorial or laboratory session in Weeks 2 to 11 in which the work is performed.
Examination 1 60% To be advised

Assessment Requirements

Assessment Policy

Assessment Tasks

Participation

  • Assessment task 1
    Title:
    Assignment 1: Programming Basics
    Description:
    This assignment will require the development of a software application with Scribble that reacts to user interface events, taking input from a user and then performing a complex calculation. The task will require creating a programming solution to a calculation-based problem, creating software that reacts to an event, makes decisions with a IF-THEN-ELSE logic, stores user input in variables, and makes calculations using variables.
    Weighting:
    10%
    Criteria for assessment:
    1. The application must run correctly. Evidence of testing is required.
    2. The application must meet the problem specification.
    3. The application logic should be documented with pseudocode/flowchart.
    4. The application sprites and scripts should be constructed in a way that makes them easy to understand and maintain.
    5. Students should be able to answer questions about their own work.

    Detailed assessment criteria will be provided on the unit web site along with full details of the assignment task.

    Due date:
    Sunday 11:59pm Week 7
  • Assessment task 2
    Title:
    Assignment 2: Advanced Programming Application
    Description:
    This assignment will require the development of a software application with Scribble that implements a single-user game. The task will require creating an abstraction of the game state and changing that state as the user plays the game. This will require the creation of appropriate data structures to store the game state, the player's movers, and scripts that represent the game rules. The software will make decisions with a IF-THEN-ELSE logic, process data using loop-based logic, and display appropriate status updates as the game is played, won or lost.

    Students will be asked to answer questions about their own work during an interview scheduled outside the lab class in Week 12.
    Weighting:
    10%
    Criteria for assessment:
    1.  The application must run correctly. Evidence of testing is required.
    2. The application must meet the problem specification.
    3. The application logic should be documented with pseudocode/flowchart.
    4. The application sprites and scripts should be constructed in a way that makes them easy to understand and maintain.
    5. Students should be able to answer questions about their own work during an interview scheduled outside the lab class.

    Detailed assessment criteria will be provided on the unit web site along with full details of the assignment task.

    Due date:
    Sunday 11:59pm Week 11. Interviews held in Week 12
  • Assessment task 3
    Title:
    Laboratory work and short tutorial quizzes
    Description:
    In Weeks 2 to 11 students will be expected to write and execute code to perform tasks specified at the start of their Laboratory session. The specified coding tasks will come from a Laboratory task specification sheet released prior to each Laboratory session allowing for preparation.

    Students will be expected to complete a very short quiz at the end of each Tutorial session. They will assess student knowledge of the lecture material for the week the Tutorial is based on.
    Weighting:
    20%
    Criteria for assessment:

    Laboratory work will be assessed during the Laboratory session. Full marks will require both working code and good coding style with the latter carrying more weight.

    Tutors will mark tutorial short quizzes after the tutorial. The questions will examine both conceptual and practical working knowledge covered in the lecture slides relevant to the tutorial.

    Due date:
    The end of the tutorial or laboratory session in Weeks 2 to 11 in which the work is performed.

Examinations

  • Examination 1
    Weighting:
    60%
    Length:
    3 hours
    Type (open/closed book):
    Closed book
    Electronic devices allowed in the exam:
    None

Learning resources

Reading list

Armoni, M. and M. Ben-Ari (2013) Computer Science Concepts in Scratch. Weizmann Institute of Science. [on-line] http://stwww.weizmann.ac.il/g-cs/scratch/scratch_en.html.

Gaddis, T. (2012) Starting out with programming logic and design. 3rd Edition. Addison Wesley.

Lane, A., B. Meyer and J. Mullins (2012) Generative Art with Scribble: A Project Based Introduction to Programming. Monash BlockBooks Series. [on-line] via Apple iTunes Store and http://monash-blockbooks.appspot.com

Lane, A., B. Meyer and J. Mullins (2012) Simulation with CellularA Project Based Introduction to Programming. Monash BlockBooks Series. [on-line] via Apple iTunes Store and http://monash-blockbooks.appspot.com

Lane, A., B. Meyer and J. Mullins (2012) Robotics with Enchanting and LEGO® NXTA Project Based Introduction to Programming. Monash BlockBooks Series. [on-line] via Apple iTunes Store and http://monash-blockbooks.appspot.com

Sprankle, M & J. Hubbard (2012) Problem solving and programming concepts. 9th Edition. Prentice Hall.

Venit, S. & E. Drake (2011) Prelude to programming: Concepts and design. 5th Edition. Addison Wesley.

Monash Library Unit Reading List (if applicable to the unit)
http://readinglists.lib.monash.edu/index.html

Faculty of Information Technology Style Guide

Feedback to you

Examination/other end-of-semester assessment feedback may take the form of feedback classes, provision of sample answers or other group feedback after official results have been published. Please check with your lecturer on the feedback provided and take advantage of this prior to requesting individual consultations with staff. If your unit has an examination, you may request to view your examination script booklet, see http://intranet.monash.edu.au/infotech/resources/students/procedures/request-to-view-exam-scripts.html

Types of feedback you can expect to receive in this unit are:

  • Informal feedback on progress in labs/tutes
  • Graded assignments with comments
  • Interviews
  • Test results and feedback
  • Quiz results
  • Solutions to tutes, labs and assignments

Extensions and penalties

Returning assignments

Assignment submission

It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/student-academic-integrity-managing-plagiarism-collusion-procedures.html) for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at http://www.infotech.monash.edu.au/resources/student/forms/. Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an online quiz). Please note that it is your responsibility to retain copies of your assessments.

Online submission

If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.

Recommended Resources

BYOB (Build Your Own Blocks), “Scribble” Edition. This free software development tool is available for MacOS, Windows. It is available for download at: http://monofonik.github.com/scribble/

Other Information

Policies

Monash has educational policies, procedures and guidelines, which are designed to ensure that staff and students are aware of the University’s academic standards, and to provide advice on how they might uphold them. You can find Monash’s Education Policies at: www.policy.monash.edu.au/policy-bank/academic/education/index.html

Key educational policies include:

Faculty resources and policies

Important student resources including Faculty policies are located at http://intranet.monash.edu.au/infotech/resources/students/

Graduate Attributes Policy

Student Charter

Student services

Monash University Library

Disability Liaison Unit

Students who have a disability or medical condition are welcome to contact the Disability Liaison Unit to discuss academic support services. Disability Liaison Officers (DLOs) visit all Victorian campuses on a regular basis.

Other

Recognition of Prior Learning

Prior to the start of semester, students who have advanced programming skills are invited to attempt an on-line based assessment of their existing skills, knowledge and ability. Students who obtain a pass grade may choose to enroll in a more advanced programming unit in place of FIT1040 and receive an exemption (but not credit) for FIT1040.

The on-line test can be found at http://dsslab.infotech.monash.edu.au:8080/moodle/