Unit Outline

This unit explores the System Development Life Cycle (SDLC) guided by Software Engineering principles and practices. It elaborates on the understanding of various software development methodologies currently in practice. The unit covers the entire lifecycle as it aligns with Human-Computer Interaction (HCI) and User Experience (UX) components, emphasising development from a usability perspective.

The unit includes requirement specifications inspired by real-world software applications. Students work in teams, progressing through each phase of the SDLC and HCI/UX process. You will produce artefacts including a Requirements Traceability Matrix (RTM), low- and high-fidelity User Interface designs, and static and dynamic designs using UML. Additionally, you will evaluate and present your final design based on HCI/UX methodologies.

Intended Learning Outcomes

As per the Assessment and Results Policy 1.3, your results will reflect your achievement against specified learning outcomes.

On completion of this unit, you will be able to:


1	Analyse and critique alternative system development methodologies to select the most appropriate for a given software development project
2	Design, develop and appraise artefacts typically identified within the systems development life cycle that reflect a technical- and user-centric approach
3	Create and evaluate high-fidelity prototypes based on user experience principles to express application designs

Alterations as a result of student feedback

Description, ILOs and assessments amended and approved based on feedback.

Teaching arrangements


ATTENDANCE MODE	TEACHING TYPE	LEARNING ACTIVITY	CONTACT HOURS	FREQUENCY
On Campus	Lecture (Online)	A real-time (i.e. synchronous) interactive activity involving the whole class whose primary purpose is the presentation and structuring of information/ideas/skills to facilitate student learning. All students are expected to attend.	2	Study Period 5 times
	Workshop	A structured real-time (i.e. synchronous) activity that involves a mix of presentation of new information/ideas/skills and guided activities related to that information/ideas/skills. All students are expected to attend.	2	StudyPeriod 12 times
	Independent Learning	Involving reading, listening to audio, watching video, and/or completing exercises and/or quizzes, self-study is individual work undertaken when the student chooses (i.e. asynchronous), most likely through engagement with MyLO. The content is examinable, and may need to be completed prior to attending classes and/or attempting assessment tasks.	2	Weekly

Attendance / engagement expectations

If your unit is offered On campus, it is expected that you will attend all on-campus and onsite learning activities. This is to support your own learning and the development of a learning community within the unit. If you are unable to attend regularly, please discuss the situation with your course coordinator and/or our UConnect support team.

If your unit is offered Online or includes online activities, it is expected you will engage in all those activities as indicated in the Unit Outline or MyLO, including any self-directed learning.

If you miss a learning activity for a legitimate reason (e.g., illness, carer responsibilities) teaching staff will attempt to provide alternative activities (e.g., make up readings) where it is possible.

How will I be Assessed?

For more detailed assessment information please see MyLO.

Assessment schedule


ASSESSMENT TASK #	ASSESSMENT TASK NAME	DATE DUE	WEIGHT	LINKS TO INTENDED LEARNING OUTCOMES
Assessment Task 1:	SDLC and Design Plan	Week 4	20 %	LO1
Assessment Task 2:	From RTM to Prototyping	Week 7	25 %	LO2, LO3
Assessment Task 3:	Software design artefacts, evaluation & iterative design	Week 10	20 %	LO2, LO3
Assessment Task 4:	Final Evaluation Presentation	Week 13	30 %	LO1, LO3
Assessment Task 5:	In-semester Test	Refer to Assessment Description	5 %	LO1, LO2, LO3

Assessment details

Assessment Task 1: SDLC and Design Plan

Task Description:

In this assessment, students will work individually to review a requirement specification and recommend a suitable SDLC with rationale, create an HCI/UX design plan and complete a sketch design. Each student will receive a specification document based on real-world software applications. They will then propose a suitable software development methodology and outline its phases aligned with HCI/UX requirements. The rationale will explain the reasons for the chosen methodology, and the HCI/UX plan will detail how the design captures the client requirements. In addition, each group will develop a Requirements Traceability Matrix (RTM) for the provided software specification, and create a sketch-level design of the UI.

Task Length:

2500 words + Design Sketch & RTM

Due Date:

Week 4

Weight:

20 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Select a development methodology and create an HCI/UX design plan that would result in a software product that meets the client’s requirements	LO1
2	Critically analyse the selected software development and HCI/UX methodologies to select the appropriate approach that meets the client’s requirements	LO1
3	Identify the key phases of selected software development methodology and align with the HCI/UX process	LO1
4	Convert a specification into a requirements traceability matrix with all requirements captured from the provided specification and develop a sketch design of the UI	LO1

Assessment Task 2: From RTM to Prototyping

Task Description:

In this assessment, students will work in groups to apply a design methodology, and then transform the generated RTM and sketch designs into demonstrable prototypes using industry-proven tools and usability methods. Each group will collate the individual contriubutions from assignment 1 to create a single RTM, then continue working on their specification by converting the RTM into low- and high-fidelity prototypes. These prototypes will embody HCI principles and practices drawn from real-world scenarios.

Peer Review will be used to adjust individual marks.

Task Length:

3000 words + Lo-Fi & Hi-Fi Prototypes

Due Date:

Week 7

Weight:

25 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Convert an RTM into Lo-Fi Prototype	LO3
2	Evaluate the Lo-Fi prototype based on HCI principles and practices	LO3
3	Develop the Hi-Fi prototype based on Lo-Fi and RTM	LO3
4	Evaluate Hi-Fi prototype based on HCI principles and practices	LO3
5	Appraise the significance of Prototyping in SDLC	LO2
6	Design the Low-Fi prototype using HCI principles and practices	LO2

Assessment Task 3: Software design artefacts, evaluation & iterative design

Task Description:

In this assessment, students will work in groups to create software design artefacts using UML, and refine their hi-fidelity prototypes based on chosen evaluation methods. Students will continue to work with their specification document, developing high-level use cases, interaction diagrams, and a conceptual model that brings the prototype closer to implementation. Students will then evaluate aspects of their design using HCI evaluation techniques, and refine their prototypes based on feedback.

Peer Review will be used to adjust individual marks.

Task Length:

3000 words + Hi-Fi Designs & UML

Due Date:

Week 10

Weight:

20 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Document a complete software design that matches the requirements specification	LO2
2	Produce use case details describing the structure scenarios	LO2
3	Produce design artefacts based on UML	LO2
4	Represent functionality of design that reflects the Hi-Fi Prototype	LO2
5	Evaluate design artefacts using HCI principles and practices including iterative refining of the hi-fi prototype	LO3
6	Appraise the significance of design artefacts and software code in SDLC	LO2

Assessment Task 4: Final Evaluation Presentation

Task Description:

In this assessment, students will work in their groups to finalise their hi-fidelity prototpe and evaluate this prototype with users. They will then analyse the findings using HCI/UX methods and make any further alterations necessary to the prototype, RTM or UML based on user feedback. Students will document their evaluation process, and create a group presentation which will be given in the Week 13 tutorial.

Peer Review will be used to adjust individual marks.

Task Length:

3500 words + Hi-Fi Prototype, RTM & Presentation

Due Date:

Week 13

Weight:

30 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Refine a hi-fidelity prototype based on user feedback	LO3
2	Present a finished hi-fidelity prototype	LO1
3	Document a complete design, prototyping and evaluation process, incorporating software development methodologies, in a professionally presented report	LO3
4	Conduct a comprehensive evaluation of the hi-fidelity prototype with all functionality demonstrated as per a logically chosen and documented HCI/UX method	LO3

Assessment Task 5: In-semester Test

Task Description:

This assessment includes ongoing evaluations during and after teaching activities during the semester. There will be 5 quizzes (Weeks 3, 5, 7, 9, 11) each worth 1% that will test students on aspects of design theory using scenario-based questions.

Task Length:

30 minutes

Due Date:

Refer to Assessment Description

Weight:

5 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Answer questions correctly on the software engineering and SDLC based on provided information and discussions during the sessions	LO1
2	Answer questions correctly on HCI principles and applied aspects based on provided information and discussions during the sessions	LO3
3	Answer questions correctly on software design and development based on provided information and discussions during the sessions	LO2
4	Answer questions correctly on functional and usability testing based on provided information and discussions during the sessions	LO2, LO3

How your final result is determined

To pass this unit, you need to demonstrate your attainment of each of the Intended Learning Outcomes, achieve a final unit grade of 50% or greater, and pass any hurdle tasks.

Academic progress review

The results for this unit may be included in a review of your academic progress. For information about progress reviews and what they mean for all students, see Academic Progress Review in the Student Portal.

Submission of assignments

Where practicable, assignments should be submitted to an assignment submission folder in MYLO. You must submit assignments by the due date or receive a penalty (unless an extension of time has been approved by the Unit Coordinator). Students submitting any assignment in hard copy, or because of a practicum finalisation, must attach a student cover sheet and signed declaration for the submission to be accepted for marking.

Academic integrity

Academic integrity is about acting responsibly, honestly, ethically, and collegially when using, producing, and communicating information with other students and staff members.

In written work, you must correctly reference the work of others to maintain academic integrity. To find out the referencing style for this unit, see the assessment information in the MyLO site, or contact your teaching staff. For more detail about Academic Integrity, see Important Guidelines & Support.

Requests for extensions

If you are unable to submit an assessment task by the due date, you should apply for an extension.

A request for an extension should first be discussed with your Unit Coordinator or teaching support team where possible. A request for an extension must be submitted by the assessment due date, except where you can provide evidence it was not possible to do so. Typically, an application for an extension will be supported by documentary evidence: however, where it is not possible for you to provide evidence please contact your Unit Coordinator.

The Unit Coordinator must notify you of the outcome of an extension request within 3 working days of receiving the request.

Late penalties

Assignments submitted after the deadline will receive a late penalty of 5% of the original available mark for each calendar day (or part day) that the assignment is late. Late submissions will not be accepted more than 10 calendar days after the due date, or after assignments have been returned to other students on a scheduled date, whichever occurs first. Further information on Late Penalties can be found on the Assessments and Results Procedure.