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

Nil

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.	1	StudyPeriod 11 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.	3	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:	Requirements Analysis & Design Strategy	Week 4	30 %	LO1
Assessment Task 2:	Prototyping, Modelling & Design Evaluation	Week 8	30 %	LO2, LO3
Assessment Task 3:	Final Project Evaluation & Professional Defence	Week 12	35 %	LO1, LO3
Assessment Task 4:	In-semester Test	Refer to Assessment Description	5 %	LO1, LO2, LO3

Assessment details

Assessment Task 1: Requirements Analysis & Design Strategy

Task Description:

Students will critically analyse a provided software specification and develop a design strategy that integrates both Human–Computer Interaction (HCI) and Software Engineering principles. Teams will identify stakeholders, elicit and analyse requirements, evaluate alternative Software Development Life Cycle (SDLC) methodologies, and justify the selection of an appropriate development approach. Students will develop a Requirements Traceability Matrix (RTM) and create initial design concepts that demonstrate alignment between stakeholder needs, user requirements, and project objectives.

Presentation:

Groups will deliver a 10-minute presentation outlining:

* Stakeholder analysis and project context.
* Requirements elicitation and analysis.
* Evaluation and justification of the chosen SDLC.
* Requirements traceability approach.
* Initial design concepts and rationale.

Following the presentation, assessors will ask questions relating to project decisions, theoretical foundations, and individual contributions. Each group member must respond to at least one question.

Students will be assessed on their ability to:

* Critically analyse stakeholder and user requirements.
* Evaluate and justify software development methodologies.
* Apply HCI and software engineering principles to design planning.
* Demonstrate traceability between requirements and proposed solutions.
* Communicate and defend design decisions using evidence.

Supporting Artefacts:

* Requirements analysis.
* SDLC evaluation and justification.
* Requirements Traceability Matrix (RTM).
* Initial design concepts and sketches.

Weighting:

* Group presentation and questioning: 25%
* Supporting artefacts: 5%

Peer Review will be used to adjust individual marks.

Task Length:

1000 words (max.) + Design Sketches & RTM + 10 minute presentation and questions

Due Date:

Week 4

Weight:

30 %

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: Prototyping, Modelling & Design Evaluation

Task Description:

Students will develop low-fidelity and high-fidelity prototypes and create software design artefacts that communicate the structure, behaviour, and intended functionality of the proposed system. Teams will apply HCI theories, design principles, and evaluation methods to assess the effectiveness of their designs. Students will critically evaluate prototype performance and demonstrate how findings have informed design refinements.

Demonstration:

Groups will deliver a 15-minute demonstration outlining:

* Design evolution from requirements to prototype.
* Application of HCI principles and usability considerations.
* UML and software design artefacts.
* Evaluation methods and findings.
* Design refinements informed by evaluation outcomes.

Following the demonstration, assessors will ask questions relating to design rationale, evaluation approaches, and project contributions. Each group member must respond to at least one question.

Students will be assessed on their ability to:

* Translate requirements into coherent design solutions.
* Apply advanced HCI and UX principles.
* Create and communicate software design artefacts.
* Select and apply appropriate evaluation methodologies.
* Critically analyse evaluation findings and justify refinements.

Supporting Artefacts:

* Low-fidelity prototype.
* High-fidelity prototype.
* UML design artefacts.
* Evaluation findings.
* Updated RTM.

Weighting:

* Group demonstration and questioning: 25%
* Supporting artefacts: 5%

Peer Review will be used to adjust individual marks.

Task Length:

1500 words (max.) + Lo-Fi & Hi-Fi Prototypes + 15 minute presentation and questions

Due Date:

Week 8

Weight:

30 %

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: Final Project Evaluation & Professional Defence

Task Description:

Students will conduct a comprehensive evaluation of their final prototype and analyse the resulting findings using recognised HCI and UX evaluation approaches. Teams will refine their solution based on evidence gathered throughout the project and present a professional justification of their design process, project outcomes, and recommendations. Students will demonstrate how HCI and software engineering principles informed decision-making throughout the project lifecycle.

Presentation and Demonstration:

Groups will deliver a 20-minute presentation and demonstration outlining:

* Final prototype and key functionality.
* Evaluation methodology and findings.
* Design refinements and outcomes.
* Traceability from requirements to solution.
* Critical reflection on project decisions.
* Recommendations for future development.

Following the presentation, assessors will ask questions regarding methodology selection, design decisions, evaluation outcomes, limitations, and individual contributions. Each group member must respond to at least one question.

Students will be assessed on their ability to:

* Critically evaluate interactive systems using appropriate methodologies.
* Synthesise evidence from design, evaluation, and stakeholder requirements.
* Justify design decisions using theory and evidence.
* Reflect on strengths, limitations, and future opportunities.
* Communicate professionally with technical and non-technical audiences.

Supporting Artefacts:

* Final high-fidelity prototype.
* Final Requirements Traceability Matrix (RTM).
* Final UML design artefacts.
* Evaluation findings and recommendations.

Weighting:

* Group presentation, demonstration and questioning: 30%
* Supporting artefacts: 5%

Peer Review will be used to adjust individual marks.

Task Length:

2000 words (max.) + Hi-Fi Prototype, RTM & UML + 20 minute presentation and questions

Due Date:

Week 12

Weight:

35 %

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 4: 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.