This unit aims to provide students with the basic concepts involved in the development of well structured software using a programming language. It concentrates on the development of problem solving skills applicable to all stages of the development process. Students gain experience with the translation of a problem specification into a program design, and the implementation of that design into a programming language. The subject introduces software engineering topics such as maintainability, readability, testing, documentation, modularisation, and reasoning about correctness of programs. Students are expected to read and understand existing code as well as develop new code.
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):
CSE9000
Shane Moore
Consultation hours: Contact through the discussion forums, or email: Shane.Moore@monash.edu
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
Over the past years in which the unit has been running, students have reported an overall satisfaction with the content and presentation of the unit's material.
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 | No formal assessment or activities are undertaken in week 0 | |
| 1 | Introduction to FIT9017 and expectations; introduction to programming, basic OO concepts, objects, classes, attributes, behaviour, state and identity. | |
| 2 | Class definition, fields, constructors, methods, parameter passing, variables, expressions, statements, assignment, primitive data types, arithmetic operators, strings, basic output. | |
| 3 | Selection (if and switch statements), conditions, relational & logical operators, shorthand operators, ++ operator, precedence, scope and lifetime, basic input. | |
| 4 | Object creation and interaction, abstraction, modularisation, class & object diagrams, object creation, primitive vs. object types, method calling, message passing, method signatures, method overloading. | Assignment 1 due Wednesday 26 March 2014, 11:59pm. Assignment 1 inteview during Week 4 |
| 5 | Class libraries, importing classes, collections, ArrayLists, arrays, iteration, pre and post test loops. | |
| 6 | identity vs. equality, more on strings, Class documentation, Javadoc syntax, random numbers, sets and maps, conditional operator. | |
| 7 | Information hiding, encapsulation, access modifiers, scoping, class variables, class methods, constants. | |
| 8 | Testing, unit testing, testing heuristics, regression testing, debugging, testing a program, specifying a test strategy. | Assignment 2 due Monday 28 April 2014. Assignment 2 interview during Week 8 |
| 9 | Program design considerations, responsibility-driven design, design documentation. | |
| 10 | Code quality, coupling, cohesion, refactoring, using the Java SDK. | Assignment 3 - Stage 1 due Friday 16 May 2014 |
| 11 | Inheritance, superclasses, subclasses, subtypes, substitution, polymorphic variables, protected access, casting, wrapper classes, collection hierarchy. | |
| 12 | Programming errors, exception handling, file I/O. | Assignment 3 - Final stage due Friday 30 May 2014. Assignment 3 interview to be scheduled at a mutually agreed time |
| 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 | 5% | Wednesday 26 March 2014, 11:59pm |
| Assignment 2 - Programming Task | 15% | Monday 28 April 2014 |
| Assignment 3 - Problem Solving and Programming Task | 20% (Stage 1 = 4%, Stage 2 = 16%) | Stage 1 due Friday 16 May 2014, Final stage due Friday 30 May 2014 |
| 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/
Broadly, the criteria used to assess your work will be:
Broadly, the criteria used to assess your work will be:
Broadly, the criteria used to assess your work will be:
Note that the first 2 items are assessed twice - once in each stage.
The following may provide useful extra reading for this unit. Copies of these are available in the Caulfield Library (on reserve, one day loan or in the normal circulation).
Java Foundations, Lewis, De Pasquale & Chase, (Pearson Education), 2008
Big Java (4th Edition), Cay Horstman (John Wiley & Sons), 2010
Java Programming: From Problem Analysis to Program Design (3rd Edition), D. S Malik (Thomson), 2008
Thinking in Java (4th Edition), Eckell (Prentice Hall), 2006
Absolute Java (3rd Edition), Savitch (Addison Wesley), 2008
Monash Library Unit Reading List (if applicable to the unit)
http://readinglists.lib.monash.edu/index.html
Faculty of Information Technology Style Guide
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:
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
There will be no provision for resubmission of assignments after the due date.
Students must reference material used from other sources.
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.
You must submit all your work to the relevant "Assignment" activity within Moodle before anything will be marked.
Please check with your lecturer before purchasing any Required Resources. Limited copies of prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.
In this unit we will use Java and the BlueJ development environment.
This software is available on CD with the prescribed text book and is installed in the student computer labs at Caulfield campus.
Also:
You are expected to work in the BlueJ development environment.
Limited copies of prescribed texts are available for you to borrow in the library.
David Barnes and Michael Kolling. (2011). Objects First with Java. (5th Edition) Pearson (ISBN: 0-13-283554-1).
Students are required to have regular access to an internet-connected computer. You should be checking the Moodle discussion forums and your Monash Student Email account at least twice a week in case there are important messages from the lecturer.
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:
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/.