Applications Programming (Java)

UTS

Course Description

  • Course Name

    Applications Programming (Java)

  • Host University

    UTS

  • Location

    Sydney, Australia

  • Area of Study

    Computer Engineering, Computer Info Systems, Computer Programming, Computer Science, Information Sciences, Information Technologies

  • Language Level

    Taught In English

  • Prerequisites

    48023 Programming Fundamentals OR 31267 Programming Fundamentals OR 31465 Object-oriented Programming

    Recommended studies: basic skills in Java programming

  • Course Level Recommendations

    Upper

    ISA offers course level recommendations in an effort to facilitate the determination of course levels by credential evaluators.We advice each institution to have their own credentials evaluator make the final decision regrading course levels.

    Hours & Credits

  • Credit Points

    6
  • Recommended U.S. Semester Credits
    4
  • Recommended U.S. Quarter Units
    6
  • Overview

    Description
    This subject teaches students how to design, develop and evaluate software systems to meet predefined quality characteristics of functionality (suitability) and usability (understandability, learnability, operability, compliance). Software solutions are implemented using Java. Concepts, theories and technologies underlying the methods and techniques are introduced and explained as required. Students apply all that they have learned to develop and implement the architecture of a business system.
    Subject objectives
    Upon successful completion of this subject students should be able to:
    1. Judge if a solution is well-designed
    2. Design a good OO solution from a specification.
    3. Demonstrate a working knowledge of lists in Java.
    4. Use inheritance in Java.
    5. Construct a GUI interface.
    This subject also contributes specifically to the development of the following course intended learning outcomes:
    Identify and apply relevant problem solving methodologies [EA Stage 1 Competency:1.1, 2.1, 2.2, 2.3] (B.1)
    Design components, systems and/or processes to meet required specifications [EA Stage 1 Competency: 1.3, 1.6, 2.1, 2.2, 2.3] (B.2)
    Implement and test solutions [EA Stage 1 Competency: 2.2, 2.3,] (B.5)
    Apply abstraction, mathematics and/or discipline fundamentals to analysis, design and operation [EA Stage 1 Competency:1.1, 1.2, 2.1, 2.2] (C.1)
    Develop models using appropriate tools such as computer software, laboratory equipment and other devices [EA Stage 1 Competency: 2.2,2.3, 2.4] (C.2)
    Teaching and learning strategies
    The subject has three contact hours a week. The lecture presents new material and shows working examples of code. In the two hour lab session, students write, debug, and run code.
    Content
    1. Design for reuse
    2. Design rules and notations
    3. Design and debugging processes
    4. Linked lists
    5. Files and exceptions
    6. Inheritance and polymorphism
    7. The Java event model
    8. The MVC framework
    9. The Observer pattern
    10. Swing components
    Assessment
    Assessment task 1: Labs
    Intent:
    The labs, both assessed and non-assessed, provide practise in programming.
    Objective(s):
    This assessment task addresses subject learning objectives:
    1, 2 and 3
    This assessment task contributes to the development of the following course intended learning outcomes:
    B.2
    Type: Laboratory/practical
    Groupwork: Individual
    Weight: 10%
    Length:
    The lab should take about 2 hours for the typical student.
    Criteria:
    All labs are marked for correctness only. The early labs are marked by PLATE, and the GUI lab by the Subject Co-Ordinator. The minimum essential requirement for a pass in any one lab is to pass more than half the assessed tasks. You do not have to pass the lab assessment to pass the subject.
    Criteria linkages:
    Criteria Weight (%) SLOs CILOs
    Functionality of design 25 1, 2, 3 B.2
    Correctness of system modelling 25 1, 2, 3 B.2
    Correctness of design 25 1, 2, 3 B.2
    Functionality and correctness of design 25 1, 2, 3 B.2
    SLOs: subject learning objectives
    CILOs: course intended learning outcomes
    Assessment task 2: Programming assignment 1
    Intent:
    This programming assignment provides practise and tests for the topics of system design, lists, and files.
    Objective(s):
    This assessment task addresses subject learning objectives:
    1, 2 and 3
    This assessment task contributes to the development of the following course intended learning outcomes:
    B.1, B.2, B.5, C.1 and C.2
    Type: Project
    Groupwork: Individual
    Weight: 20%
    Length:
    This assessment task has been given an estimated time of 15 hours to complete by the typical student.
    Criteria:
    The assignment is marked on correctness by PLATE, based on the match to the model solution?s IO trace.
    The minimum essential requirement for a pass is to complete the tasks worth half the mark.
    Criteria linkages:
    Criteria Weight (%) SLOs CILOs
    Application of methodology 0 1, 2, 3 B.1
    Functionality of design 20 1, 2, 3 B.2
    Correctness of system modelling 20 1, 2, 3 B.2
    Correctness of design 20 1, 2, 3 B.2
    Functionality and correctness of design 20 1, 2, 3 B.5
    Correctness of application of theory 10 1, 2, 3 C.1
    Logical design strategy 10 1, 2, 3 C.2
    SLOs: subject learning objectives
    CILOs: course intended learning outcomes
    Assessment task 3: Programming assignment 2
    Intent:
    This programming assignment provides practise and tests for the topics of system design, GUIs and MVC.
    Objective(s):
    This assessment task addresses subject learning objectives:
    1, 2, 3, 4 and 5
    This assessment task contributes to the development of the following course intended learning outcomes:
    B.1, B.2, B.5, C.1 and C.2
    Type: Project
    Groupwork: Individual
    Weight: 30%
    Length:
    The task has been estimated at about 25 hours for the typical student who has completed all the labs.
    Criteria:
    The assignment is marked on correctness. The minimum essential requirement for a pass is to complete tasks worth more half the marks.
    Criteria linkages:
    Criteria Weight (%) SLOs CILOs
    Application of methodology 0 1, 2, 3, 4, 5 B.1
    Functionality of design 20 1, 2, 3, 4, 5 B.2
    Correctness of system modelling 20 1, 2, 3, 4, 5 B.2
    Correctness of design 20 1, 2, 3, 4, 5 B.2
    Functionality and correctness of design 20 1, 2, 3, 4, 5 B.5
    Correctness of application of theory 10 1, 2, 3, 4, 5 C.1
    Logical design strategy 10 1, 2, 3, 4, 5 C.2
    SLOs: subject learning objectives
    CILOs: course intended learning outcomes
    Assessment task 4: Final Examination
    Intent:
    The exam tests the factual knowledge taught in the subject.
    Type: Examination
    Groupwork: Individual
    Weight: 40%
    Length:
    Two hours
    Criteria:
    The exam is multiple choice, so the questions are marked for correctness only.
    Minimum requirements
    A student must have a total score from all tasks >= 50% and an exam mark >= 50% to pass the subject.
    If you have a mark of >= 50% for the subject, but have failed the exam, you will be awarded a Fail (X) grade for the subject.Under the University's rules, no supplementary exam will be given.

Course Disclaimer

Courses and course hours of instruction are subject to change.

Credits earned vary according to the policies of the students' home institutions. According to ISA policy and possible visa requirements, students must maintain full-time enrollment status, as determined by their home institutions, for the duration of the program.