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.
Minimum total expected workload equals 12 hours per week comprising:
(a.) Contact hours for on-campus students:
(b.) Study schedule for off-campus students:
(c.) Additional requirements (all students):
See also Unit timetable information
Cheryl Howard
To Be Annouced
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
Changes made in S2/2014:
Comments from 2013-2014:
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
| 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) | Assignment 1 due Friday 11:59pm |
| 7 | Using lists in loops | |
| 8 | Using abstraction to represent game play | |
| 9 | Objects and Functions | |
| 10 | Cloning Multiple Objects | |
| 11 | Software development and programming environments I | Assignment 2 due Friday 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.
Examination (3 hours): 60%; In-semester assessment: 40%
| Assessment Task | Value | Due Date |
|---|---|---|
| Assignment 1: Programming Basics | 10% | Friday 11:59pm Week 6 |
| Assignment 2: Advanced Programming Application | 10% | Friday 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 |
Faculty Policy - Unit Assessment Hurdles (http://intranet.monash.edu.au/infotech/resources/staff/edgov/policies/assessment-examinations/assessment-hurdles.html)
Academic Integrity - Please see resources and tutorials at http://www.monash.edu/library/skills/resources/tutorials/academic-integrity/
Detailed assessment criteria will be provided on the unit web site along with full details of the assignment task.
Detailed assessment criteria will be provided on the unit web site along with full details of the assignment task.
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.
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 Cellular: 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) Robotics with Enchanting and LEGO® NXT: A 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
Types of feedback you can expect to receive in this unit are:
Submission must be made by the due date otherwise penalties will be enforced.
You must negotiate any extensions formally with your campus unit leader via the in-semester special consideration process: http://www.monash.edu.au/exams/special-consideration.html
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 electronic submission). Please note that it is your responsibility to retain copies of your assessments.
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/
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
Important student resources including Faculty policies are located at http://intranet.monash.edu.au/infotech/resources/students/
The University provides many different kinds of support services for you. Contact your tutor if you need advice and see the range of services available at http://www.monash.edu.au/students. For Malaysia see http://www.monash.edu.my/Student-services, and for South Africa see http://www.monash.ac.za/current/.
The Monash University Library provides a range of services, resources and programs that enable you to save time and be more effective in your learning and research. Go to www.lib.monash.edu.au or the library tab in my.monash portal for more information. At Malaysia, visit the Library and Learning Commons at http://www.lib.monash.edu.my/. At South Africa visit http://www.lib.monash.ac.za/.
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/
This unit is a core unit in the Bachelor of Software Engineering accredited by Engineers Australia. Engineers Australia Accreditation Policy of Professional Engineering Programs requires that programs demonstrate how engineering graduates are prepared for entry to the profession and achieve Stage 1 competencies. The following information describes how this unit contributes to the development of these competencies for the Bachelor of Software Engineering. (Note: not all competencies may be emphasised in this unit).
| Stage 1 competency | How the compency is developed in this unit |
| 1. Knowledge and Skills base | |
| 1.1. Comprehension, theory based understanding of the underpinning natural and physical sciences and the engineering fundamentals applicable to the engineering discipline. | The unit covers computing foundations which underpins the programming knowledge required in software engineering. The required knowledge is covered by theoretical lecture materials, and recommended reading, tutorials and laboratory tasks. |
| 1.2. Conceptual understanding of the mathematics, numerical analysis, statistics, and computer and information sciences, which underpin the engineering discipline. | Lecture materials and exercises provide conceptual understanding of computer science, in particular programming solving techniques, which underpins software engineering. |
| 1.3. In-depth understanding of specialist bodies of knowledge within the engineering discipline. | Not covered in this unit. |
| 1.4. Discernment of knowledge development and research directions within th engineering discipline. | Not covered in this unit. |
|
1.5. Knowledge of engineering design practice and contextual factors impacting the engineering discipline. |
Not covered in this unit. |
| 1.6. Understanding of the scope, principles, norms, accountabilities and bounds of sustainable engineering practice in the specific discipline. | Not covered in this unit. |
| 2. Engineering application ability | |
| 2.1. Application of established engineering methods to complex engineering problem solving. | The unit addresses programming issues and problems and how to solve these problems. It is covered by programming exercises and assessments. |
| 2.2 Fluent application of engineering techniques, tools and resources. | The fundamental aspects of programming are covered and applied in this unit. |
| 2.3. Application of systematic engineering synthesis and design processes. | Not covered in this unit. |
| 2.4. Application of systematic approaches to the conduct and management of engineering projects. | Not covered in this unit. |
| 3. Professional and personal attributes | |
| 3.1. Ethical conduct and professional accountability. | Some aspects are covered in this unit, in relation to good programming practice and ethics. |
| 3.2. Effective oral and written communication in professional and lay domains. | This is covered in the lab exercises and assignments. |
| 3.3. Creative, innovative and proactive demeanour. | Using problem solving techniques to develop programs is inherently a creative endeavour. |
| 3.4. Professional use and management of information. | Not covered in this unit. |
| 3.5. Orderly management of self, and professional conduct. | This is covered in the lab exercises and assignments, while students manage and conduct themselves during assessment. |
| 3.6. Effective team membership and team leadership. | Not covered in this unit. |
| No. | CO 1 | CO 2 | CO 3 | CO 4 | CO 5 | CO 6 | CO 7 | C0 8 | CO 9 | CO 10 | CO 11 | CO 12 | CO 13 |
| 1 | X | X | X | X | X | ||||||||
| 2 | X | X | X | X | X | ||||||||
| 3 | X | X | X | X | X | ||||||||
| 4 | X | X | X | X | X | ||||||||
| 5 | X | X | X | X | X | ||||||||
| 6 | X | X | X | X | X |
| No. | Assignments | Tests | Practical Exercises | Exam |
| 1 | X | X | X | X |
| 2 | X | X | X | X |
| 3 | X | X | X | |
| 4 | X | X | X | X |
| 5 | X | X | X | |
| 6 | X | X | X |