External Panel Review Group Feedback Programme(s): Bachelor of Engineering (Hons) in Engineering Software NFQ Level: 8 Credits: 240 Programme(s): Bachelor of Engineering in Engineering Software NFQ Level: 7 Credits: 180 Programme(s): Bachelor of Engineering (Hons) in Engineering Software (add-on) NFQ Level: 8 Credits: 60 School: Department: School of Engineering Department of Mechanical Engineering Venue: Time/date: Boardroom; Main Building Friday 17 th June 2016, 9.15 am. External Panel: Richard Gallery, Registrar ITB (Chair) Frank Duignan (DIT) David Powell (ITB) Derek Harnett (Software Architect, IWG Intel Ireland) John Ó Néill, ITT (Secretary) Programme Team: Fiona Cranley, Head of School of Business and Humanities James Wright, Head of Department of Electronic Engineering Andrew Donnellan Dick Gahan Traolach O Brien 1
Paul Farrell Brian Keogh Michael Craig John Sexton Michael Gill Tom Murray Pat O Friel Damien Doheny Aideen Darker 2
Summary of Discussions Preliminary meeting with John Vickery (Registrar), Fiona Cranley (Head of School), James Wright (Head of Department) and the panel. Panel held a preliminary meeting with John, Fiona and James who gave an overview of the programme and its context. Summary of discussions with panel: The panel raised a number of issues which were discussed, including: Clarification of the awards being presented for consideration (James Wright, as Head of Department, indicated that these include Higher Certificate in Electronic Engineering as an exit award, Bachelor of Engineering in Software Engineering as an ab initio Level 7, Bachelor of Engineering (Honours) in Software Engineering as an ab initio Level 8 and a one year addon Bachelor of Engineering (Honours) in Software Engineering as an ab initio Level 8). Progression rules from the ab initio Level 7 to the ab initio Level 8. General issues around progression and non-progression of students, particularly with reference to entry requirements and levels of mathematics. Resources, including access to labs for independent learning. Demand for the programme. Meeting with Programme Development Team and full Programme Team The Panel meet with the Programme Development Team and full Programme Team including the Head of Department. The panel then discussed a mixture of content issues alongside discussion of specific modules including: Mathematics 8: discussion of the content and the amount of numerical content, including the possibility of introducing an elective to cover this area. A more general discussion on the amount of testing (and integration) included across various modules, followed by a discussion of automated testing. Embedded Systems programming module was discussed in terms of matching the content to the title and whether a stronger software process module was needed rather than content distributed across other modules. Regulated software. Appropriateness of some learning outcomes and whether they are capable of being assessed: o Learning to Learn: Learning Outcome 1 is not assessed and total assessment amounts to 60% only. o DIGT H2006: Learning Outcome 5 is not assessed. o WIRE SEM3: No breakdown of continuous assessment or mapping of Learning Outcomes to assessment. o DIGT H2065: No detail given on the continuous assessment, Learning Outcomes 2 and 6 not assessed. o GUI Development: Learning Outcome 5 not assessed. 3
o Object Orientated Software Design: No Learning Outcomes given for the terminal exam. o STRA H4060 Management Practice: No Learning Outcomes given for the terminal exam. o ENSW H4001 Software Development: Learning Outcome 7 is not assessed. o PROJ H4018 Project 1: Learning Outcome 15 is not assessed. o OPER H4000 Operating Systems: Learning Outcome 4 is not assessed. Embedded systems content was also discussed. Where C programming is introduced into the course and whether there should be a conscious division into an introductory level and a more advanced level. Software methodologies content across various modules doesn t specify agile, although it does appear in various modules identified by the programme team (eg Object Orientated Software Design). The level of software engineering was discussed briefly. The content on control systems, standards and industry standards was raised and discussed with the programme team. There was a discussion of whether databases should be included and the reasons for it not being included in the programme. The panel and programme team reviewed the reasons for inclusion/exclusion. The Internet of Things module was discussed, including whether the title reflects the content accurately. The Programme Team expanded on the module content and there was a discussion of constraining the name. The discussion returned to Embedded Systems and the relative amount of content on real time systems. This led onto a discussion on Edge Processing. Industry and Technology trends were discussed, in terms of where this is currently dealt with within the programme and whether there would be value in including a specific module focussing on trends. There was a discussion of the general themes around the inclusion of projects on the programme, including the purpose of individual project modules in each Stage of the programme. The issue of whether elements of the programme should be drawn into a specific Design stream was discussed. The difference in the graduate attributes at Level 7, Level 8 and Level 9 were then discussed. Self-directed learning and student access off-site was discussed with the panel and programme team. The new modules were then reviewed by the panel and programme team. Introduction to Smart Sensors: discussion of module content. No breakdown of continuous assessment or mapping of Learning Outcomes to assessment. GUI Development: discussed previously (including the implications of some elective choices). The delivery of the module was also discussed including delivery in a lab rather than a lecture theatre. Object Oriented Software Design: panel and programme team discussed whether a concept or C programming is more appropriate for the module. Project 1: discussed previously. 4
Management Practice: no further discussion. Network Security and Administration: background to module and Cisco links were discussed. Secure programming was also discussed, including design of software and protocols. Data Structures and Algorithms: Scope of module content was discussed, including whether memory allocation should be included. Project 2: discussed previously. Embedded System Software Design: discussed previously. Digital Signal Processing: discussed previously. Mobile System Programming: programme team gave practical examples of work done with students on the module. 5
Panel Responses: Programme(s): Bachelor of Engineering (Hons) in Engineering Software Bachelor of Engineering in Engineering Software Bachelor of Engineering (Hons) in Engineering Software (add-on) Does the proposed course accord with the Institute s Mission Statement and Strategic Plan? Will it have a positive impact on the host department(s) and the Institute? Does the proposal make a strong case that there is an unidentified need for the course? Is this backed up by evidence of structured consultation with industry, students and social partners? Will the course meet the identified need, in terms of level of qualification, curriculum, learning experiences and throughput? What is the likely employment potential for graduates? Is the course structure logical and well designed, in terms of programme schedules, syllabi, teaching and learning strategies and assessment methodologies? See conditions and recommendations below Are the entry mechanisms, modes of study and progression mechanisms clear and appropriate for the programme? Are the entry mechanisms designed to facilitate access, transfer and progression? Are course management arrangements and quality assurance arrangements in place? Will they ensure the proper management and operation of the programme? Is there a sufficient number of appropriately qualified staff to support the expected number of students to be recruited? 6
Overall response: The panel commends the department and programme team on the quality of the proposed programmes and the development of an exciting and relevant programme largely using existing resources. The panel is happy to approve the programmes for delivery subject to the following conditions and recommendations to strengthen and enhance the programme. Conditions: o Learning outcomes in modules are reviewed to ensure all are appropriate and assessment is fully and accurately described. These include: Learning to Learn: Learning Outcome 1 is not assessed and total assessment amounts to 60% only. DIGT H2006: Learning Outcome 5 is not assessed. WIRE SEM3: No breakdown of continuous assessment or mapping of Learning Outcomes to assessment. DIGT H2065: No detail given on the continuous assessment, Learning Outcomes 2 and 6 not assessed. GUI Development: Learning Outcome 5 not assessed. Object Orientated Software Design: No Learning Outcomes given for the terminal exam. STRA H4060 Management Practice: No Learning Outcomes given for the terminal exam. ENSW H4001 Software Development: Learning Outcome 7 is not assessed. PROJ H4018 Project 1: Learning Outcome 15 is not assessed. OPER H4000 Operating Systems: Learning Outcome 4 is not assessed. Recommendations: o Articulate the difference between graduate attributes for the Level 7 and Level 8 award. o Review module content to ensure that Industry and technology trends are visibly and specifically covered in an appropriate module. o Review how the content on source control, project management and software development practices are identified to students. o Consider how linkages between the content relevant to the regulatory environment, documenting, testing and constraints are presented to students throughout the programme. o Consider the ordering of software modules throughout the four years of the programme. o Consider putting the real time implementation in DSPG H4000 Digital Signal Processing. 7
Programme Schedules Programme Schedule for Year 1 Name of Provider Programme Codes TA_EENGS_B Programme Title (i.e. named award) Bachelor of Engineering (Hons) in Engineering Software Award Title (HETAC named award) Honours Bachelor Degree Stage Exit Award Title Modes of Delivery (FT/PT/ACCS/BLENDED/OC etc), Stage 1 Number of Stages 1 Award Class Award NQF Level 8 Award EQF Level 6 Stage Credits (ECTS) 0 Stage NQF Level Stage EQF Level Date Effective 14/09/16 ISCED Subject Code Ref Module Title Semester Module ECTS Total Student Effort Allocation of Marks Status (M/E) NQF Level Credit Number Total Hours Contact Hours Independent Learning Course Work % End of Module Formal Examination % 1.1 Mathematics 7 1 M 8 5 30.00 12.00 18.00 20 80 100.00 1.2 Internet 1 M 8 5 24.00 8.00 16.00 30 70 100.00 Systems 1.3 Software 1 M 8 5 17.00 1.00 16.00 100 0 100.00 Project 5 1.4 Software 1 M 8 5 24.00 8.00 16.00 50 50 100.00 Development 1 (C++) 1.5 Embedded System Software 1 M 8 5 24.00 8.00 16.00 50 50 100.00 Total % 8
Design 1.6 Mobile 1 E 8 5 24.00 8.00 16.00 50 50 100.00 Systems Programming 1.7 Digital Signal 1 E 8 5 22.00 7.00 15.00 30 70 100.00 Processing 1.8 Operating 2 M 8 5 24.00 8.00 16.00 30 70 100.00 Systems 1.9 Internet of 2 M 8 5 24.00 8.00 16.00 40 60 100.00 Things 1.10 Software 2 M 8 5 24.00 8.00 16.00 50 50 100.00 Development 2 1.11 Software 2 M 8 5 17.00 1.00 16.00 100 0 100.00 Project 6 1.12 Mathematics 8 2 M 8 5 22.00 8.00 14.00 20 80 100.00 1.13 Network 2 E 8 5 24.00 8.00 16.00 30 70 100.00 Engineering 1.14 Digital Microprocessor Design 2 E 8 5 22.00 8.00 14.00 30 70 100.00 Special Regulations: None 9