2022/3, Trimester 2, FACE-TO-FACE,
VIEW FULL DETAILS
Occurrence: | 001 |
Primary mode of delivery: | FACE-TO-FACE |
Location of delivery: | MYANMAR |
Partner: | |
Member of staff responsible for delivering module: | Kevin Sim |
Module Organiser: | |
Learning, Teaching and Assessment (LTA) Approach: |
The module will be introduced by an Edinburgh Napier lecturer who will deliver an initial 25 hours of lectures, practical work and tutorials. The additional hours will be delivered by our partner Info Myanmar College (IMC). The module will run over 5 consecutive weeks with the later four weeks being delivered by IMC staff. Lectures are used to introduce underlying principles and the practical and tutorial work is used to broaden & develop deeper understanding of the subject area. This is mixed with student-centred work, such as research questions and online exercises, as well as group activities such as discussion groups, group presentation exercises, and peer review.Key concepts will be explained in lectures, where the subject matter will be illustrated with examples and interactive demonstrations (LO1,2,5). Where possible, students should bring to the lectures a laptop with access to the Internet, with Git and Java installed. A key feature is to present the principles behind the DevOps process (LO1,2,5), and discuss the concepts with the students (LO1,2,5).Practical labs focus on developing a DevOps workflow using tools to provide practice in the application of theory (LO1-4). Students develop their own solutions although the focus is on the pipeline developed. As the module progresses, this will gradually require more independent work and research of advanced concepts. Throughout the labs, students will be encouraged to interact with staff and peers to explore concepts in depth and receive feedback on their progress and understanding.In addition to timetabled classes, students should undertake private study to work through the learning materials and gain further practice at solving conceptual and technical problems (LO1-4).As the module is delivered in a block over 5 consecutive weeks, standard Academic Calendar weeks and trimesters are not applicable for the tables below.
|
Interactive elements of lectures encourage students to test their understanding continuously. There will be additional formative challenges such as quizzes. Continuous feedback is given by staff through discussions in the labs.Each week the students will have a code review point which will provide feedback on the process development.The lab exercises that form the basis for the final assessment are scattered throughout the module; they will be highlighted when the assessment spec is introduced.
|
The module is assessed using a practical coursework (LO1-4) and an exam (LO1,2,5).The coursework is staged groupwork, with weekly reviews of progress to the delivery of the final product. This will be supported via analytics tools provided by the tools taught, face-to-face group discussion, and a code review. These are will contribute to the final coursework deliverable which will be assessed based on requirements being met. Groups will be given an overall group mark and group members individual marks based on their contribution as evidenced through the data and tools used in the module.The exam will cover the theory of DevOps and professional, ethical, and security issues associated with modern software development. This will be a long-form answer exam requiring problem-solving and evaluation of principles.
|
Student Activity (Notional Equivalent Study Hours (NESH)) |
Mode of activity | Learning & Teaching Activity | NESH (Study Hours) |
Face To Face | Lecture | 40 |
Face To Face | Practical classes and workshops | 60 |
Face To Face | Demonstration | 4 |
Independent Learning | Guided independent study | 36 |
Independent Learning | Guided independent study | 60 |
| Total Study Hours | 200 |
| Expected Total Study Hours for Module | 200 |
Assessment |
Type of Assessment | Weighting % | LOs covered | Week due | Length in Hours/Words |
Project - Practical | 60 | 1-4 | 1 | HOURS= 60, WORDS= 0 |
Centrally Time Tabled Examination | 40 | 1,2,5 | 1 | HOURS= 2, WORDS= 0 |
Component 1 subtotal: | 60 | |
Component 2 subtotal: | 40 | | | |
Module subtotal: | 100 | | | |
2022/3, Trimester 3, FACE-TO-FACE,
VIEW FULL DETAILS
Occurrence: | 001 |
Primary mode of delivery: | FACE-TO-FACE |
Location of delivery: | MYANMAR |
Partner: | |
Member of staff responsible for delivering module: | Kevin Chalmers |
Module Organiser: | |
Learning, Teaching and Assessment (LTA) Approach: |
The module will be introduced by an Edinburgh Napier lecturer who will deliver an initial 25 hours of lectures, practical work and tutorials. The additional hours will be delivered by our partner Info Myanmar College (IMC). The module will run over 5 consecutive weeks with the later four weeks being delivered by IMC staff. Lectures are used to introduce underlying principles and the practical and tutorial work is used to broaden & develop deeper understanding of the subject area. This is mixed with student-centred work, such as research questions and online exercises, as well as group activities such as discussion groups, group presentation exercises, and peer review.Key concepts will be explained in lectures, where the subject matter will be illustrated with examples and interactive demonstrations (LO1,2,5). Where possible, students should bring to the lectures a laptop with access to the Internet, with Git and Java installed. A key feature is to present the principles behind the DevOps process (LO1,2,5), and discuss the concepts with the students (LO1,2,5).Practical labs focus on developing a DevOps workflow using tools to provide practice in the application of theory (LO1-4). Students develop their own solutions although the focus is on the pipeline developed. As the module progresses, this will gradually require more independent work and research of advanced concepts. Throughout the labs, students will be encouraged to interact with staff and peers to explore concepts in depth and receive feedback on their progress and understanding.In addition to timetabled classes, students should undertake private study to work through the learning materials and gain further practice at solving conceptual and technical problems (LO1-4).As the module is delivered in a block over 5 consecutive weeks, standard Academic Calendar weeks and trimesters are not applicable for the tables below.
|
Interactive elements of lectures encourage students to test their understanding continuously. There will be additional formative challenges such as quizzes. Continuous feedback is given by staff through discussions in the labs.Each week the students will have a code review point which will provide feedback on the process development.The lab exercises that form the basis for the final assessment are scattered throughout the module; they will be highlighted when the assessment spec is introduced.
|
The module is assessed using a practical coursework (LO1-4) and an exam (LO1,2,5).The coursework is staged groupwork, with weekly reviews of progress to the delivery of the final product. This will be supported via analytics tools provided by the tools taught, face-to-face group discussion, and a code review. These are will contribute to the final coursework deliverable which will be assessed based on requirements being met. Groups will be given an overall group mark and group members individual marks based on their contribution as evidenced through the data and tools used in the module.The exam will cover the theory of DevOps and professional, ethical, and security issues associated with modern software development. This will be a long-form answer exam requiring problem-solving and evaluation of principles.
|
Student Activity (Notional Equivalent Study Hours (NESH)) |
Mode of activity | Learning & Teaching Activity | NESH (Study Hours) |
Face To Face | Lecture | 40 |
Face To Face | Practical classes and workshops | 60 |
Face To Face | Demonstration | 4 |
Independent Learning | Guided independent study | 36 |
Independent Learning | Guided independent study | 60 |
| Total Study Hours | 200 |
| Expected Total Study Hours for Module | 200 |
Assessment |
Type of Assessment | Weighting % | LOs covered | Week due | Length in Hours/Words |
Project - Practical | 60 | 1-4 | 1 | HOURS= 60, WORDS= 0 |
Centrally Time Tabled Examination | 40 | 1,2,5 | 1 | HOURS= 2, WORDS= 0 |
Component 1 subtotal: | 60 | |
Component 2 subtotal: | 40 | | | |
Module subtotal: | 100 | | | |