COMP SCI 4414B - Software Engineering Research Project B

North Terrace Campus - Semester 2 - 2020

The final year research project is aimed at providing students with an opportunity to apply Software Engineering knowledge, understanding, and skills to an industrially sourced project. The projects are jointlysupervised by academic supervisors and the external clients, who propose projects. The students are assigned to different small teams that are expected to work collaboratively on the assigned project that will involve aspects of research and development. Students are expected to demonstrate the application of software engineering principles and practices by following defined processes, which are tracked using online repositories and communication tools. The project also provides a pathway to enrolment in a higher degree by research.

  • General Course Information
    Course Details
    Course Code COMP SCI 4414B
    Course Software Engineering Research Project B
    Coordinating Unit Computer Science
    Term Semester 2
    Level Undergraduate
    Location/s North Terrace Campus
    Units 3
    Contact Up to 3 hours per week
    Available for Study Abroad and Exchange N
    Restrictions BEng (Software) students only
    Assessment Written Exam and / or assignments
    Course Staff

    Course Coordinator: Dr Mansooreh Zahedi

    Course Timetable

    The full timetable of all activities for this course can be accessed from Course Planner.

  • Learning Outcomes
    Course Learning Outcomes
    This project consists of 2 semesters duration, with 3 units in semester 1 (part A) and 3 units in semester 2 (part B). Following on the project A, the project B will be built upon what would have been achieved during the project A. However, each part of the project has independent grading.

    At the conclusion of the course, the students are expected to be able to:

    1. Gain exposure to research in an area of software engineering.
    2. Learn to interpret and assess literature related to a current area of research.
    3. Learn to present work to an audience, both in written form and orally.
    4. Apply software engineering principles and research to industry projects
    5. Learn to work and plan in groups.
    University Graduate Attributes

    No information currently available.

  • Learning & Teaching Activities
    Learning & Teaching Modes

    No information currently available.

    Workload

    The information below is provided as a guide to assist students in engaging appropriately with the course requirements.

    As a guide, each student is expected to work on the project between 10-12 hours per week as expected for a 3 Units course.
    Learning Activities Summary
    This is a final year research project, jointly supervised by software engineering and computer science academics with external industry involvement. The research topic will be selected from CS staff research interests, while the area of application will be negotiated with industry partners. Students will be expected to learn and demonstrate the application of SE principles to conduct research for industry-based clients outside the school. The project will provide a pathway to enrolment in a higher degree by research.

    The learning activities cover:

    - Research and development on the proposed project topic.

    - Implementing Scrum Process model (e.g.,define backlog items, run sprint review and retrospectives, live demo of working produt) in pracice with real industrial clients.

    - Oral presentation to the clients and teaching staff

    - Written + Oral presentation to a larger audience through Ingenuity event 



  • Assessment

    The University's policy on Assessment for Coursework Programs is based on the following four principles:

    1. Assessment must encourage and reinforce learning.
    2. Assessment must enable robust and fair judgements about student performance.
    3. Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
    4. Assessment must maintain academic standards.

    Assessment Summary
    Assessment Components include:

    • Sprint Review Meetings (20)
    – Individual – 4 deliveries, fortnightly

    • Prototyping (25) – Group (G) and Individual (I)
    – Development process – G - (5)
    – Development process – I - (5)
    – Project quality – G - (7.5)
    – Project quality – I - (7.5)

    • Final Report – 20 (G & I)

    • Final Presentation - 10 (I)

    • Poster ingenuity – 10 (I)

    • Client Assessment – 5 (I)

    • Retrospective Reports – 10 (G)
    - 5 deliverables, fortnightly.

    Assessment Detail

    No information currently available.

    Submission

    No information currently available.

    Course Grading

    Grades for your performance in this course will be awarded in accordance with the following scheme:

    M10 (Coursework Mark Scheme)
    Grade Mark Description
    FNS   Fail No Submission
    F 1-49 Fail
    P 50-64 Pass
    C 65-74 Credit
    D 75-84 Distinction
    HD 85-100 High Distinction
    CN   Continuing
    NFE   No Formal Examination
    RP   Result Pending

    Further details of the grades/results can be obtained from Examinations.

    Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.

    Final results for this course will be made available through Access Adelaide.

  • Student Feedback

    The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.

    SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.

  • Student Support
  • Policies & Guidelines
  • Fraud Awareness

    Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.

The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.