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, with a focus on Agile methodology. The unit covers the entire lifecycle, from the requirements phase to software development and testing. In addition, it addresses the Human-Computer Interaction (HCI) 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. They produce artefacts including a Requirements Traceability Matrix (RTM), low- and high-fidelity User Interface designs, and static and dynamic designs using UML. Additionally, they write software code in C# and create functional and usability test cases based on the provided requirements specification document.

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 (On Campus)	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	Once only (4 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	Once only (3 times)
	Tutorial	A structured real-time (i.e. synchronous) activity in a small-group setting where the primary purpose is the clarification, exploration or reinforcement of subject content presented or accessed at another time or place (e.g. lecture, preparatory work). It is reliant on student-teacher and student-student interaction and dialogue for achievement of its learning outcomes. The students enrolled in the tutorial are expected to attend.	2	Once only (9 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 Requirements Engineering	Week 5	20 %	LO1
Assessment Task 2:	From RTM to Prototyping	Week 9	30 %	LO2, LO3
Assessment Task 3:	Software design and development	Week 14	30 %	LO2, LO3
Assessment Task 4:	In-semester Test	Refer to Assessment Description	20 %	LO1, LO2, LO3

Assessment details

Assessment Task 1: SDLC and Requirements Engineering

Task Description:

In this assessment, students will work in groups to review a requirement specification and recommend a suitable SDLC, supplemented by a critique. Each group will receive a specification document based on real-world software applications. They will then propose a suitable software development methodology and outline its phases. The critique will explain the reasons for the chosen methodology and compare it with other alternative approaches. In addition, each group will develop a Requirements Traceability Matrix for the provided specification.

This assessment will have group and individual tasks.

Note: Each specification will highlight the minimum acceptance criteria by the user/client.

Task Length:

~9 use cases for a group of 3 students.

Due Date:

Week 5

Weight:

20 %

CRITERION #

CRITERION

MEASURES INTENDED

LEARNING OUTCOME(S)


1	Select a development methodology that would result in a software product that meets the client’s minimum acceptance requirements	LO1
2	Critically analyse the selected software development methodologies to select the appropriate approach that meets the client’s minimum acceptable requirements	LO1
3	Identify the key phases of selected software development methodology	LO1
4	Convert a specification into a requirements traceability matrix with all requirements captured from the provided specification	LO1

Assessment Task 2: From RTM to Prototyping

Task Description:

In this assessment, students will work in groups to transform the generated RTM into a demonstrable prototype. Each group will 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 and implementations.

This assessment will have group and individual tasks.

Task Length:

3 Use cases per student

Due Date:

Week 9

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

Assessment Task 3: Software design and development

Task Description:

In this assessment, students will work in groups to create software design artefacts using UML. They will also develop code in a high-level language that showcases the functionality identified in the RTM and demonstrated in Hi-Fi Prototypes. 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. Based on these design artefacts, students will then write object-oriented code in C#.

This assessment will have group and individual tasks.

Task Length:

3 Use cases per student

Due Date:

Week 14

Weight:

30 %

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	Implement a software application that operates as specified in the design document	LO2
5	Implement functionality that reflects the Hi-Fi Prototype	LO3
6	Appraise the significance of design artefacts and software code in SDLC	LO2

Assessment Task 4: In-semester Test

Task Description:

This assessment includes ongoing evaluations during and after teaching activities during the semester. The first in-semester test is a quiz that covers the Software Engineering and SDLC aspects of the unit. This quiz, due on Friday of Week #3, is worth 5%. The second in-semester test focuses on the HCI aspect of the unit and will take place during the workshops in Weeks #5 and #7, each worth 2.5%. The third in-semester test covers design and development aspects and will occur during tutorials from Week #8 to Week #12, each worth 1%. The final in-semester test, worth 5%, covers testing aspects such as functional and usability testing. It will take place during the Week #13 tutorial.

Task Length:

30 minutes

Due Date:

Refer to Assessment Description

Weight:

20 %

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.

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.

Review of results and appeals

You are entitled to ask for a review of the marking and grading of your assessment task if there is an irregularity in the marking standards or an error in the process for determining the outcome of an assessment. Details on how to request a review of a mark for an assignment are outlined in the Review and Appeal of Academic Decisions Procedure.