SIT218 - Secure Coding
Unit details
| Year: | 2022 unit information |
|---|---|
| Important Update: | Unit delivery will be in line with the most current COVIDSafe health guidelines. We continue to tailor learning experiences for each unit to achieve the best possible mix of online and on-campus activities that successfully blend our approaches to learning, working and research. Please check your unit sites for announcements and updates. Last updated: 4 March 2022 |
| Enrolment modes: | Trimester 2: Burwood (Melbourne), Waurn Ponds (Geelong), Online |
| Credit point(s): | 1 |
| EFTSL value: | 0.125 |
| Unit Chair: | Trimester 2: Naeem Syed |
| Prerequisite: | SIT102 and SIT192 |
| Corequisite: | SIT232 |
| Incompatible with: | SIT738 |
| Typical study commitment: | Students will on average spend 150 hours over the trimester undertaking the teaching, learning and assessment activities for this unit. |
| Scheduled learning activities - campus: | 1 x 3 hour active class per week. |
| Scheduled learning activities - cloud: | Online independent and collaborative learning including optional scheduled activities as detailed in the unit site. |
Content
Security by design in the software development life cycle is essential for fool proofing contemporary software systems and platforms against the evolving cyber threats. This unit comprises the principles of security for software development. Topics covered include the Continuous Delivery (CD) model for secure software development, adoption of cutting-edge software security tools for data validation, code bug detection, web application vulnerability assessment, secure database design and cloud/API security.
| ULO | These are the Learning Outcomes (ULO) for this unit. At the completion of this unit, successful students can: | Deakin Graduate Learning Outcomes |
|---|---|---|
| ULO1 | Explain secure coding principles to a range of audiences, and apply them to software design and development activities. | GLO1: Discipline-specific knowledge and capabilities |
| ULO2 | Analyse program code and design documentation to identify common programming problems and recommend strategies to mitigate and report issues. | GLO1: Discipline-specific knowledge and capabilities |
| ULO3 | Perform static and dynamic analysis tools and techniques to find vulnerabilities within software. | GLO1: Discipline-specific knowledge and capabilities |
| ULO4 | Use proof techniques and automated theorem provers to formally verify software correctness. | GLO1: Discipline-specific knowledge and capabilities |
These Unit Learning Outcomes are applicable for all teaching periods throughout the year.
Assessment
| Assessment Description | Student output | Grading and weighting (% total mark for unit) | Indicative due week |
|---|---|---|---|
| Learning Portfolio | Tasks include the production of a range of artefacts (code, reports, presentations etc.), along with written critique and reflection. | 80% | Week 11 |
| Examination | 2-hour written examination | 20% | Examination period |
The assessment due weeks provided may change. The Unit Chair will clarify the exact assessment requirements, including the due date, at the start of the teaching period.
Hurdle requirement
To be eligible to obtain a pass in this unit, students must meet certain milestones as part of the portfolio, and must achieve a passing grade in the examination.
Learning Resource
The texts and reading list for the unit can be found on the University Library via the link below: SIT218 Note: Select the relevant trimester reading list. Please note that a future teaching period's reading list may not be available until a month prior to the start of that teaching period so you may wish to use the relevant trimester's prior year reading list as a guide only.
Unit Fee Information
Click on the fee link below which describes you: