IoT Platforms and Methodologies GITPME801
MODULE DETAILS |
IoT Platforms and Methodologies GITPME801 NOMINAL DURATION IN HOURS 72 hours total time commitment This time commitment includes the structured activities, preparation reading, attendance at each webinar, completing exercises, practical assessments, and proctored assessments. It is also expected that students spend additional time on readings, personal study, independent research, and learning, practicing on remote labs and required software and working on any projects and assignments. This module covers specialized procedures required for intricate and multilayered systems for IoT projects. |
MODULE PURPOSE |
The purpose of the module is for participants to develop enhanced knowledge of the key hardware and software platforms, processes and management considerations required in viable IoT projects. |
MODIFICATION HISTORY |
Nil |
PREREQUISITE AND/OR COREQUISITE MODULES |
Modules that must be delivered and assessed before this module:
Modules that must be delivered concurrently with this module:
|
SUMMARY OF LEARNING OUTCOMES |
On successful completion of this module students will be able to:
|
LEARNING OUTCOMES |
ASSESSMENT CRITERIA |
||
Learning outcomes specify what students will be able to do as a result of the learning. | Assessment criteria provide the criteria by which achievement of the learning outcomes will be judged. | ||
1
|
Evaluate the importance of developing robust data and environment management practices for IoT |
1.1 |
Research and assess best practices for IoT data management and environment management from reliable sources |
1.2 | Compare best practices in IoT data management to standard data management practices | ||
1.3 | Identify fundamental principles to guide the management of the IoT environment | ||
1.4 | Compare management of the IoT environment to established best practices | ||
1.5 |
Identify the potential implications of poor data management and inadequate control of the IoT environment, and propose strategies to mitigate these challenges |
||
2 | Evaluate version control types and their applications | 2.1 | Determine and compare the key elements of centralised version control systems and distributed version control systems |
2.2 | Explain the fundamental features of Subversion (SVN) version control and assess its strengths and weaknesses | ||
2.3 | Identify core features of Git version control and evaluate its strengths and weaknesses | ||
2.4 | Identify IoT projects that use either Git or SVN | ||
2.5 | Explain the rationale behind choosing Git or SVN for an IoT project | ||
3 | Establish and optimise features of the development environment for an IoT project | 3.1 | Develop a brief for a small scale IoT project, focussing on key features of the development environment |
3.2 | Develop strategy and guidelines to minimise risk and maximise outcomes in a small scale IoT development environment | ||
3.3 | Evaluate the features of the development environment for a small-scale IoT project and decide whether to accept or reject them | ||
4 | Evaluate agile software development methods | 4.1 | Review and evaluate adaptive and predictive software development methods |
4.2 | Identify and explain the core philosophy and values of agile software development | ||
4.3 | Analyse the strengths and weaknesses of contemporary agile software development frameworks | ||
4.4 | Evaluate agile software development practices for a small-scale IoT project | ||
4.5 | Propose solutions to challenges of an agile software development project | ||
5 | Evaluate continuous test and integration | 5.1 | Identify best practices for continuous testing with continuous integration |
5.2 | Explain processes used to apply continuous integration testing to IoT projects | ||
5.3 | Create a model for continuous testing and integration of a small-scale IoT project. | ||
6 | Develop and document a release management strategy | 6.1 | Determine key principles of a release management strategy for IoT projects |
6.2 | Record the potential benefits and risks associated with each phase of a release management process | ||
6.3 | Develop a release management strategy tailored for a small scale IoT project | ||
DELIVERY MODE | Online and/or face-to-face | ||
SPECIALISED RESOURCES | N/A | ||
ASSESSMENT STRATEGY |
METHODS OF ASSESSMENT Assessors should gather a range of evidence that is valid, sufficient, current, and authentic. Evidence can be gathered through a variety of ways including direct observation, supervisor's reports, project work, structured assessments, samples, and questioning. This will include short answer questions on the knowledge content, the use of remote and virtual labs, and writing tasks to apply the learning to academic tasks. CONDITIONS OF ASSESSMENT Assessor Requirements: Assessors must satisfy the assessor requirements in the standards for registered training organisations (RTOs) current at the time of assessment. Assessors must also hold a tertiary qualification in engineering or related field. The RTO must also ensure that trainers and assessors keep their industry knowledge up to date through ongoing professional development. Assessment Conditions: Questioning techniques should not require language, literacy, and numeracy skills beyond those required in this module. The candidate must have access to all tools, equipment, materials, and documentation required. The candidate must be permitted to refer to any relevant workplace procedures, product and manufacturing specifications, codes, standards, manuals, and reference materials. Assessments may be open book assessment and may be completed off campus. Invigilation software will be used for some assessments to ensure authenticity of work completed. Model answers and marking guide must be provided for all knowledge-based assessments to ensure reliability of assessment judgements when marking is undertaken by different assessors. |
Software/Hardware Used
Software
-
N/A
Hardware
- N/A