SENG402-16W (C) Whole Year 2016

Software Engineering Research Project

30 points

Details:
Start Date: Monday, 22 February 2016
End Date: Sunday, 13 November 2016
Withdrawal Dates
Last Day to withdraw from this course:
  • Without financial penalty (full fee refund): Sunday, 6 March 2016
  • Without academic penalty (including no fee refund): Sunday, 4 September 2016

Description

The Software Engineering research project gives students in-depth experience in researching complex, open-ended Software Engineering problems, and developing and evaluating potential solutions. Participants work individually to investigate and develop solutions for a complex real-world problem. At the end of this course you will have practiced the skills required to be a senior Software Engineer, capable of leading a team of engineers to develop solutions for complex problems involving the development of substantial software solutions of significant complexity. You will also be comfortable with dealing with vague (and often conflicting) customer requirements, working under pressure and providing technical leadership.

For more information see the course Learn site.

Learning Outcomes

● Knowledge outcomes
In this course students will learn how to analyse open ended software engineering problems and design, implement and evaluate potential solutions. Having completed the course students will be able to:
○ Demonstrate the research and problem solving qualities and abilities of a senior Software Engineer
○ Evaluate existing solutions and approaches
○ Evaluate and, where appropriate utilize, up to date open source software development projects to solve complex software problems
○ Identify risks and benefits posed by integrating open source software versus developing bespoke solutions, and apply techniques for risk mitigation
● Skill outcomes
Through practical experience the course will develop advanced industry skills. The successful student will be able to:
○ Demonstrate an understanding of, apply and communicate complex research and analysis techniques
○ Apply scientific evaluation to the analysis of complex problems and development of solutions
○ Delivering solutions given the constraints of the project
○ Ability to communicate complex information to a range of stakeholders
○ Planning and logging effort
● Personal Attributes developed
○ The key personal attributes that will be developed are problem solving ability and research skills. Students will also develop their ability to apply creative thinking to the solving of complex problems.

Prerequisites

Timetable Note

There is one hour per week reserved for occasional lectures, and there are four hours of labs per week to provide guaranteed time for students to focus on their project, for example to meet with stakeholders, or a group if you are involved in a project that interacts with that of another student.  Students are also expected to meet regularly with their supervisor/s.

Course Coordinator

Austen Rainer

Assessment

Assessment Due Date Percentage  Description
Progress Report 1 15% This will reflect initial work on the project, and by this stage can be expected to give possible solutions that are under consideration. The content of each progress report is expected to become integrated into the final report.
Progress Report 2 15% At this point the project would normally have a solution or final product well underway.
Project Presentation 10% As part of departmental postgrad conference (date to be announced, but in the term 3/4 break.)
Final Report and Practical Demo 60% This will be marked on the quality of the process that you went through, the outcomes, as well as the quality of presentation (grammar, style etc.) You will also need to demonstrate your work, either as a software/hardware demonstration, a poster, web page, or some other artefact that your examiners can use and discuss with you.


You will be assessed on the process as well as the final product. For this reason, you are required to keep a log of your time, and there are intermediate progress reports.

The "log book" can be digital or paper, but must be kept on a regular basis, and not written at the end of the course! You supervisor will need to have access to it on a weekly basis, so an online shared document or system is best. If your supervisor agrees, a properly used version control system with regular well documented commits would be suitable.

The progress reports are intended to check that your work is going in the right direction, but also because your final report will be about the process you went through, these progress reports can also be considered as early drafts of parts of your final report.

Additional Course Outline Information

Grade moderation

The Computer Science department's grading policy states that in order to pass a course you must meet two requirements:
1. You must achieve an average grade of at least 50% over all assessment items.
2. You must achieve an average mark of at least 45% on invigilated assessment items.
If you satisfy both these criteria, your grade will be determined by the following University- wide scale for converting marks to grades: an average mark of 50% is sufficient for a C- grade, an average mark of 55% earns a C grade, 60% earns a B- grade and so forth. However if you do not satisfy both the passing criteria you will be given either a D or E grade depending on marks. Marks are sometimes scaled to achieve consistency between courses from year to year.

Students may apply for special consideration if their performance in an assessment is affected by extenuating circumstances beyond their control.

Applications for special consideration should be submitted via the Examinations Office website within five days of the assessment.

Where an extension may be granted for an assessment, this will be decided by direct application to the Department and an application to the Examinations Office may not be required.

Special consideration is not available for items worth less than 10% of the course.

Students prevented by extenuating circumstances from completing the course after the final date for withdrawing, may apply for special consideration for late discontinuation of the course. Applications must be submitted to the Examinations Office within five days of the end of the main examination period for the semester.

Course Format

Apart from occasional lectures (see below), this course is almost entirely practical. It requires self-directed work by students, with supervisors being available for consultation, and regular supervisory meetings (typically weekly or fortnightly). Day to day input (as required) can be provided by a workplace advisor (if the project is an industry project) or by the academic supervisor from the CSSE department.

The project will require students to prepare a detailed project proposal (including the identification and description of a problem statement and the definition of the objectives of the work), study literature or technologies, identify candidate solutions (technologies, processes etc) and select the most appropriate solutions, typically implementing a solution. Students will write intermediate reports, and the main result of the project will be a final report and other artifacts developed in the project (e.g., a software system). The report must describe the background to the work, methods, processes, techniques or practices applied, a description of the solution, results obtained, and so on.

Students will be responsible for arranging meetings with their supervisor(s), getting feedback from other sources (if needed), and meeting the deadlines and milestones of the project. Thus, most work will be done on the students’ own time. However, students are urged to have one on one meetings with supervisors to discuss progress as required. Students are expected to see their supervisor(s) regularly to report progress and to get feedback.

Indicative Fees

Domestic fee $1,888.00

* All fees are inclusive of NZ GST or any equivalent overseas tax, and do not include any programme level discount or additional course-related expenses.

Limited Entry Course

Maximum enrolment is 30

For further information see Computer Science and Software Engineering .

All SENG402 Occurrences

  • SENG402-16W (C) Whole Year 2016