Unit Outline
School of Information and Communication Technology
College of Sciences and Engineering
KIT206
Software Design and Development
Spring school, 2023
Bilal Amin
CRICOS Provider Code: 00586B
 
Unit Coordinator
Bilal Amin
Email: Bilal.Amin@utas.edu.au
 
 
What is the Unit About?
Unit Description
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 desktop computer programs, focusing on ones having graphical user interfaces that communicate with data sources. Modern software tools and techniques to support designing, programming, and testing will be utilised. Students will explore the concepts of object-oriented modelling and programming and also Agile development methodologies. By the end of the unit, students will know the principles of how to design, implement and test a system from a requirements specification, and have the knowledge and skills required to conduct 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:
1
Apply the SDLC process using industry-relevant principles and practices
2
Produce an object-oriented application design using industry relevant software design tools and techniques;
3
Develop and implement a software test plan using industry relevant tools and techniques;
4
Develop a software application that implements a design specification;
5
Collaborate on a software design, development, and testing project as an effective project team member.
Requisites
REQUISITE TYPE
REQUISITES
Pre-requisite
KIT101 or KIT107
Alterations as a result of student feedback
Nil
 
 
Teaching arrangements
ATTENDANCE MODE
TEACHING TYPE
LEARNING ACTIVITY
CONTACT HOURS
FREQUENCY
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
Week 5
25 %
LO1, LO2, LO5
ASSESSMENT TASK 2:
Software design implementation
Week 9
35 %
LO1, LO4, LO5
ASSESSMENT TASK 3:
Software testing report
Week 9
25 %
LO3, LO4, LO5
ASSESSMENT TASK 4:
In-semester test
Refer to Assessment Description
15 %
LO1, LO2, LO3
Assessment details
Assessment Task 1: Software design
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:
One member of the group should submit a single PDF document, with at least one use case per team member.
DUE DATE:
Week 5
WEIGHT:
25 %
 
CRITERION #
CRITERION
MEASURES INTENDED LEARNING OUTCOME
1
Produce use case details describing the structure scenarios
LO2
2
Produce object-oriented design based on UML diagrams
LO2
3
Collaborate as a team to create a software design specification documentation that meets current Agile practices and industry standards
LO1, LO5
 
Assessment Task 2: Software design implementation
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:
All required source code and updated UML design documents in a single zipped file. A peer evaluation will be submitted individually.
DUE DATE:
Week 9
WEIGHT:
35 %
 
CRITERION #
CRITERION
MEASURES INTENDED LEARNING OUTCOME
1
Implement a desktop application that operates as specified in the design document
LO4
2
Implement a desktop application that provides a fully functional software with a clear distinction between Model, View and Controller components
LO4
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, LO5
 
Assessment Task 3: Software testing report
 
TASK DESCRIPTION:
Students will develop a test plan and report on the results of testing the developed application. Peer assessment will be employed for the evaluation of this assignment.

TASK LENGTH:
A single PDF document with no more than 10 pages
DUE DATE:
Week 9
WEIGHT:
25 %
 
CRITERION #
CRITERION
MEASURES INTENDED LEARNING OUTCOME
1
Collaborate as a team to produce a test plan that contains the required information to be useful to test the software against identified use cases
LO3, LO5
2
Individual test results and critique
LO3
3
Produce software code that implements unit tests
LO3, LO4
 
Assessment Task 4: In-semester test
TASK DESCRIPTION:
There will be a total of three in-semester quizzes which will be conducted in semester week 2 (covers SDLC module), week 5 (covers OOD module) and week 7 (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
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
2
Answer questions correctly on the OOD based on material presented in lectures and provided in learning modules
LO2
3
Answer questions correctly on the software testing based on material presented in lectures and provided in learning modules
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.
 
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.