Unit Outline

This unit focuses on the design, implementation, and testing phases of the Software Development Lifecycle (SDLC). The unit develops practical skills in designing, implementing, and testing computer programs, focusing on ones having graphical user interfaces that communicate with data sources. Students will also develop and demonstrate advisory capacity and an understanding of the business context of systems design and implementation. Modern software tools and techniques to support designing, programming, and testing will be utilised. Students will explore the concepts of object-oriented modelling and testing. By the end of the unit, students will have applied the principles of how to design, implement and test a system from a requirements specification, and have the knowledge and skills required to justify and implement a user-centred approach to the main tasks typically required in these phases.

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:


5	Critique software development processes and provide recommendations for improvement
1	Apply the SDLC process using industry-relevant principles and practices
2	Produce an application design and test plan using industry-relevant software design tools and techniques;
3	Develop an interactive software application that implements a design specification;
4	Collaborate on a project across the software development lifecycle from design to testing as an effective team member and project manager;

Requisites


REQUISITE TYPE	REQUISITES

Alterations as a result of student feedback

Nil

Teaching arrangements


ATTENDANCE MODE	TEACHING TYPE	LEARNING ACTIVITY	CONTACT HOURS	FREQUENCY
On Campus	Lecture	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
	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 (5 times)
	Computer Laboratory	A structured real-time (i.e. synchronous) computer-based 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 teacher supported and may involve student-teacher and/or student-student interaction and dialogue for achievement of its learning outcomes. The students enrolled in the class are expected to attend.	2	Once only (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

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 miss a learning activity for a legitimate reason (e.g., illness, family commitments) teaching staff will attempt to provide alternative activities (e.g., make up readings) where it is possible.

If you are unable to attend regularly, please discuss the situation with your course coordinator and/or our UConnect support team.

How will I be Assessed?

Assessment schedule


ASSESSMENT TASK #	ASSESSMENT TASK NAME	DATE DUE	WEIGHT	LINKS TO INTENDED LEARNING OUTCOMES
ASSESSMENT TASK 1:	Software design specification	Week 6	20 %	LO1, LO2, LO4, LO5
ASSESSMENT TASK 2:	Software test plan	Week 8	20 %	LO1, LO2, LO3, LO4, LO5
ASSESSMENT TASK 3:	Software solution	Week 13	20 %	LO1, LO3, LO4, LO5
ASSESSMENT TASK 4:	Software design and test plan critique	Week 13	25 %	LO4, LO5
ASSESSMENT TASK 5:	Quiz	Refer to Assessment Description	15 %	LO1, LO2, LO3, LO5

Assessment details

Assessment Task 1: Software design specification

TASK DESCRIPTION:

Students will work in a group to develop a UML-based object-oriented design document for a provided requirement specification. Peer assessment will be employed for the evaluation of this assignment.

TASK LENGTH:

A single PDF document containing the structured scenarios and UML models.

DUE DATE:

Week 6

WEIGHT:

20 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Document a complete software design that matches the provided requirements specification	LO2
2	Produce use case details describing the structure scenarios	LO2
3	Produce object-oriented design based on UML diagrams including use case, sequence, class, and component diagrams	LO2
4	Collaborate as a team to create a software design specification documentation that meets current Agile practices and industry standards	LO1, LO4, LO5

Assessment Task 2: Software test plan

TASK DESCRIPTION:

Students will work in a group to develop a comprehensive testing plan that follows a use-case based testing template and applies a wide range of testing types. Peer assessment will be employed for the evaluation of this assignment.

TASK LENGTH:

A single PDF document of no more than 10 pages containing the group's response to the assessment item.

DUE DATE:

Week 8

WEIGHT:

20 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Produce a complete test plan that uses a range of testing types and tests all aspects of the application to be developed	LO2, LO3
2	Document a test plan using appropriate terminology to facilitate application in subsequent phases.	LO1, LO4, LO5

Assessment Task 3: Software solution

TASK DESCRIPTION:

Students will work in a group to implement a design in C# programming language and deliver a functioning desktop software application. The development of the application will follow industry-based MVC software architecture. Peer assessment will be employed for the evaluation of this assignment.

TASK LENGTH:

N/A (source code and updated RTM with requirements implementation status)

DUE DATE:

Week 13

WEIGHT:

20 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Implement a desktop application that operates as specified in the design document	LO3
2	Implement a desktop application that produces fully functional software with a clear distinction between Model, View and Controller components	LO3
3	Document evidence of communication and collaboration with team members and capacity to work as an effective team member throughout the development of the application	LO1, LO4, LO5

Assessment Task 4: Software design and test plan critique

TASK DESCRIPTION:

Students will work in groups to evaluate and critique the software design and test plan. Based on their learning in this unit, they will update the design with the required changes and implement white-box testing. They will also discuss the impact of changes on the implemented product.
Peer assessment will be employed for the evaluation of this task.

TASK LENGTH:

A single PDF document containing the group's response to the assessment items

DUE DATE:

Week 13

WEIGHT:

25 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Produce a detailed report reflecting on the software development lifecycle and the importance of design and testing	LO4, LO5
2	Produce a report that details a critical analysis of the artefacts produced throughout this unit and provides a set of recommendations based on skills and knowledge gained	LO5

Assessment Task 5: Quiz

TASK DESCRIPTION:

There will be a total of three in-semester quizzes which will be conducted in semester week 3 (covers SDLC module), week 7 (covers fundamentals of programming and OOD module) and week 10 (covers testing module). Each quiz will contain 10 multiple-choice questions, which must be completed in one attempt, and within 30 minutes of total time.

TASK LENGTH:

30 minutes for each quiz

DUE DATE:

Refer to Assessment Description

WEIGHT:

15 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Answer questions correctly on the SDLC based on material presented in lectures and provided in learning modules	LO1, LO5
2	Answer questions correctly on the programming fundamentals and OOD based on material presented in lectures and provided in learning modules	LO2, LO3
3	Answer questions correctly on the software testing based on material presented in lectures and provided in learning modules	LO2

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.

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.