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 have a laptop issued by the ICT School, we will need it back in order to prepare for the next cohort. Ideally by mid-March. If your internship does not provide laptops we need to know ASAP. Where we can accommodate this, a return date will be provided for the end of the internship/trimester. If computer access is needed after this, for example, to prepare presentations and reports, please use the computers provided by the university in the library.

Work Experience

Before you start

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

If you have any questions, contact the Work Experience Coordinator.

Where the work is paid, the University has a responsibility to ensure all the employment basics are covered, such as you having an employment agreement, an induction into the company, and a Health and Safety briefing. Be aware that if you choose to notify us of the work, 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. Your learning goals must be submitted within two weeks of starting your work experience. You will need to also write a Covid contingency plans under red and orange traffic lights - as laid out in the university Covid policy.

Daily Journals

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

Reflective Reports

To reflect is to think deeply on a topic looking for insights that may be useful in future. In this regard, a report merely describing your internship experience, will fall short of the expectation that you will think deeply on that experience looking for insights that may be useful in future.

  • The first reflective report is due after four weeks and should be around 500 words. Submit it with your daily journal to date.

  • The second reflective report is due after eight weeks and should be around 1000 words. It should cover the entire period of your internship, including the first four weeks. Submit it with your daily journal to date.

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 final report is due in the last week of T1.

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 practic
  • A reflective assessment of your internship and the various courses and material covered. What was useful, why was it useful - what was missing, or what would have benefited from more emphasis?
  • A Covid impact statement. This should include reflection against your intial Covid contingency plan, and how any disruption was managed, and any impact on your key deliverables.
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 in the first week of the T1 exam period. It is unclear at this time if this will be in-person, remote or a hybrid. You are expected to attend - at least virtually.

You will have 20 minutes in total of which 5 minutes are available for overhead (questions and setting up). A schedule will only be made available on the day, so come prepared to present immediately just-in-case.

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

The target audience are knowledgable professionals in the IT industry, who are interested in hearing about the internship

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
  • SWEN589 course learning objectives covered appropriately
  • consistent
  • concise

Common questions from the past:

I worked on many problems not just one. What do I do?

We understand that you may not have worked on one software engineering problem but instead many, potentially a new one 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. If a picture speaks a thousand words, a demo speaks 10,000 words.

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 course learning objectives 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. Do not expect the audience to become expert in your solution in 15 minutes.

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 course learning objective #2 in their presentation.

Some students have used the list of course learning objectives to structure the presentation. This is Meta information about your course. The presentation should be on what you did, not the course. Instead, the narrative should cover the CLOs, the CLOs should not become the narrative.

Some have omitted areas because of IP concerns. Do not do this, engage with Matt who in turn will engage with both you and your supervisor to ensure we find a path forward that allows you to graduate. Never start your presentation with "I cannot talk about what I did." It becomes very difficult to award a passing grade.

The day will be busy. Ensure it will be easy for you to start the presentation. Avoid needing to install software or download the presentation from the cloud. For instance have the presentation on a memory stick. This will also be a nice backup. We have seen a laptop die the morning of the presentation, we have seen WiFi connections fail, we have seen internet outages and presentation software incompatability. You do not need the stress, have a backup plan. We recommend a pdf version of your presentation on a memory stick. Maybe two memory sticks...

Assessment for SWEN589

Weeks are from the start of the individual's internship or the 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 Week 12 Final written report 60%
Deliverable 5 22 June 2022 Oral Presentation (20 mins) 20%