COMP SCI 7096B - Master of Software Engineering Project Part B

North Terrace Campus - Semester 2 - 2014

A student undertaking the project component of M. SoftEng will enrol in this project course in semester 2. This is a major software project as approved by the Head of School. The number of units reflects the scope of the project. It is undertaken as a group project. The project will be assessed as a single entity - the student receiving this mark for all the project courses in which they enrolled.

  • General Course Information
    Course Details
    Course Code COMP SCI 7096B
    Course Master of Software Engineering Project Part B
    Coordinating Unit School of Computer Science
    Term Semester 2
    Level Postgraduate Coursework
    Location/s North Terrace Campus
    Units 9
    Prerequisites COMP SCI 7007, COMP SCI 7015; Must enrol in COMP SCI 7096A with a grade of Credit or higher in previous semester
    Restrictions Available to M Software Engineering students only
    Course Description A student undertaking the project component of M. SoftEng will enrol in this project course in semester 2. This is a major software project as approved by the Head of School. The number of units reflects the scope of the project. It is undertaken as a group project. The project will be assessed as a single entity - the student receiving this mark for all the project courses in which they enrolled.
    Course Staff

    Course Coordinator: Professor Ali Babar

    Course Timetable

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

  • Learning Outcomes
    Course Learning Outcomes
    1. An understanding of core software engineering processes including agile processes
    2. The ability to produce structured project documentation and reporting software artefacts.
    3. An ability to work productively in a team to produce software artefacts.
    4. An ability to work productively with clients on a regular basis and document meetings
    5. The ability to produce substantial software that meets user requirements and integrate that software to be usable by clients.
    6. The ability to demonstrate and present clear plans and outomes for your software project to a range of stakeholders.
    7. Ability to locate  and usefully apply resources and infomation and resources for guiding the project and its process as required
    University Graduate Attributes

    This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:

    University Graduate Attribute Course Learning Outcome(s)
    Knowledge and understanding of the content and techniques of a chosen discipline at advanced levels that are internationally recognised. 1,5
    The ability to locate, analyse, evaluate and synthesise information from a wide variety of sources in a planned and timely manner. 1,5
    An ability to apply effective, creative and innovative solutions, both independently and cooperatively, to current and future problems. 5
    Skills of a high order in interpersonal understanding, teamwork and communication. 2,3,4,6
    A proficiency in the appropriate use of contemporary technologies. 1,5
    A commitment to continuous learning and the capacity to maintain intellectual curiosity throughout life. 1
    A commitment to the highest standards of professional endeavour and the ability to take a leadership role in the community. 1,4,7
    An awareness of ethical, social and cultural issues within a global context and their importance in the exercise of professional skills and responsibilities. 1
  • Learning Resources
    Required Resources
    The School will provision resources as required by the project.
  • Learning & Teaching Activities
    Learning & Teaching Modes
    Weekly client meetings plus presentations as required.
    Workload

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

    20 hours per week per team member.
    Learning Activities Summary

    No information currently available.

  • 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
    Deliverables and Dates for Assessment
    - Platform development: 50%
    - Poster: 10%
    - Final Report: 20%
    - Presentation and Demonstration: 10%
    - Improvements to research work: 10%
    Assessment Detail
    Customization and Development Tasks
    - Features: relevance and completeness: 20%
    - Code Quality: 10%
    - Version Control Usage documentation: 10%
    Presentation, Demonstration and Examination
    Group presentation for demonstrating the developed prototype. You should
    expect individual questions for individual assessment. Each group is
    allocated a 30 minutes timeslot.
    Poster
    - Academic Content: 5%
    - Contents: Does the poster contain Title, Authors,
    Abstract, Introduction, Methods, Results, Conclusions, and
    Acknowledgements?
    - Context/Background: To what extent is there critical
    engagement with the literature and/or connection to previous research? Is
    it made clear to a broad audience?
    - Layout & Creativity: 5%
    -Layout: How coherent and well structured is the
    poster?
    - Creativity: How well does the poster engage the
    viewer’s interest?
    - Images: How well do the images (photographs,
    diagrams, figures and charts) support and enhance the factual content?
    - Overall: Is the overall appearance of the poster
    professional?
    Final Report
    This detailed document will include your project specification, design,
    and description of implementation (technologies, design, architecture).
    The report main part (i.e., excluding the appendix) should be around 20
    pages with 2cm margins all around, using an 11-point font with normal
    (single) line spacing.
    Improvement of research work
    Most of you have been asked to revise the research work done during the
    first semester. Your final assessment will include 10% satisfactory
    completion of the revised work for improved quality and presentation. If
    you have been assigned that task, then you can incorporate that 10% in
    your implementation work. This can be negotiated with your group.
    Deadline: All the tasks need to be completed by November 10, 2014.
    Poster is due by October 10, 2014 as per the schedule given. Poster
    display will be on October 30, 2014 if selected for presentation during
    the faculty event.
    Software development and associated reports can be submitted by November
    10, 2014.
    Presentation will be held during the week of November 10, 2014.
    Improved research work can be submitted by November 1, 2014.
    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.