There are five assessment items due for SWEN589. Some learning goals, two reflective reports, a report that demonstrates your capacity for critical thinking and communication at the level of a Masters student and an oral presentation.

If you are provided by computer access during your internship laptops issued by the ICT School needs to be returned by Friday 15th of March. If your internship does not provide laptop access (e.g. the entrepreneurship internship) then a date will be provided at the end of the internship. If computer access is needed after this, e.g. to prepare presentations and reports, please use the computers provided by the university in the library.

Work Experience or Entrepreneurs

Before you start

You need to advise the Work Experience Coordinator of the work you are about to start.

If in doubt, contact the Work Experience Coordinator.

Note that the University has a responsibility to students to ensure all the employment basics are covered, such as having an employment agreement, an induction into the company, and a Health and Safety briefing. Be aware that if you choose to seek approval after the fact, you will be compromising the University's duty of care and you may be disappointed if your work experience cannot be approved.

Learning Goals

You should brainstorm your learning goals and discuss these with your work supervisor and/or mentor. Your learning goals will identify your current skill level in three to four key areas, of which at least two should be soft skills from either the BE Graduate Attributes or the Victoria University Graduate Profile. Your learning goals should articulate your aspirations for improvement over the course of your work experience. When you start your final reflective report, this will form part of the evidence you will refer to in your reflections. Your learning goals must be submitted within two weeks of starting your work experience.

Daily Journals

You will also keep a daily journal noting activities, challenges and events of interest during the day. This should take less than 10 minutes per day and will result in a second source of evidence to support your final reflective report.

Nearing completion

Go back to your work experience form to complete it. This will generate a pdf which you should get your supervisor to sign on your last day so that you can then scan and submit it online:

Start your final report as soon as you can.

Final report

The expectation is that the report clearly describes the following:

  • Project background/research into related literature
  • Project goals/objectives
  • The work that was undertaken along with project development processes
  • Professional attributes that have been developed and applied in the company/project
  • Project results, reflections, lessons learned, application of theory and knowledge acquired from taught courses to practice
It should be using the IEEE 2 column format styleguide and be maximum 10 pages long.

There is no required report structure, because this clearly depends on your personal project and will need to reflect this. However an example could be:

  1. Introduction (purpose, goal, overall description)
  2. Software System
    1. Related systems
    2. System requirements
    3. System design
    4. System implementation
  3. Software engineering aspects
    1. Related software engineering processes
    2. Followed software engineering process
    3. Developed professional attributes
    4. Reflection (lessons, results, problems, positive aspects)
  4. Conclusions
To reiterate, this is not a required structure, you must modify it to fit your specific situation.

Final presentation

The presentations will happen on 07/06 in the new facilities on Level 3 in the NEC house on the corner of Taranaki St and Courtney. You will have 20 minutes in total of which 5 minutes are available for overhead (questions and setting up). A schedule will be made available on the day, so come prepared to present at any time of the day.

The presentation should target what you have done during your project, especially targeting what you have learned in the context of the CLOs for SWEN589.

The presentation will be evaluated on:

  • Quality e.g.
    • professional attitude
    • flow of presentation
    • presentation aids
  • Clear and understandable presentation of what was done and learned during the project
  • CLOs of SWEN589 covered appropriately
  • consistent
  • concise
Common questions from the past:

I worked on many problems not just one. What do I do?
We understand that some of you might not have worked on one software engineering problem but instead many, potentially a new every day. This is not an issue, you just describe what you have done in broader terms and compare and contrast the various problems you worked on and what you learned from this.

Do I need to show a demo?
No, you don’t. Not everyone will be able to, for instance if you worked on many small problems or you working on a big project that isn’t finished yet. However, if you can, a demo can be used to show what you worked on. It can be a good introduction for the audience.

How do I structure my presentation?
It is generally best to present a high level narrative of what you did and what you learned. Make sure to cover aspects of all 3 CLOs during the narrative. Many students have in the past focused too much on the technicalities of what they did and provided too much detail, even down to code level. Focus more on what you achieved and what you learned at a higher level, the detailed technical aspects are better covered in the report, after all you only have 15 minutes available so we do not expect to be experts in your solution.

What about IP issues?
If you are concerned about this, talk to Matt, now! As above we are not interested in minute detail. We do not need specifics about clients or specific technical level detail. You can also make up “dummy” data if you want to show something that otherwise couldn’t be shown.

Common issues in the past:

Many students have in the past forgotten to mention anything about CLO #2 in their presentation.

Some have omitted areas because of IP concerns that were not discussed with Matt. Please do so asap if you have any concerns.

The day will be busy. It should be easy for you to start the presentation, e.g. so that you do not need to install software or download the presentation. For instance have the presentation on a memory stick. This will also be a nice back up. We have seen a laptop die in the morning of the presentations, which was very stressful for the student.

Assessment for SWEN589

Weeks are from the start of the individual's internship or start of the entrepreneurship program. This may vary from student to student.

Deliverable 1 Week 2 Learning Goals 5%
Deliverable 2 Week 4 Submission of Logbook with reflective summary of 500 words 5%
Deliverable 3 Week 8 Submission of Logbook with reflective summary of 1000 words 10%
Deliverable 4 Fri 14th June at 12:00 (noon). Final written report 60%
Deliverable 5 Exam period, Fri 7th June Oral Presentation (20 mins) 20%