Programme Specification ( )

Transcription

1 Date of Revision Date of Previous Revision Programme Specification ( ) A programme specification is required for any programme on which a student may be registered. All programmes of the University are subject to the University s Quality Assurance and Enhancement processes as set out in the DASA Policies and Procedures Manual. Programme Title BEng in Software Engineering Final Award (exit route if applicable for Postgraduate Taught Programmes) Programme Code SOE-BENG UCAS Code Criteria for Admissions (Please see General Regulations) Mode of Study (Full-time, Part-time, other) Type of Programme Single subject I300 JACS Code BEng G600 A-level: BBB including Computing, Mathematics or Software Systems Development + GCSE Mathematics OR ABB including Chemistry, GCE A-level ICT (not Single Award Applied ICT), Physics, Technology or Double Award Applied ICT + GCSE Mathematics. BTEC Extended Diploma: a relevant computing, engineering or scientific BTEC Extended Diploma with 10 Distinctions and 8 Merits + GCSE Mathematics. BTEC Higher National Diploma/Foundation Degree: those with good grades in a relevant Higher National Diploma/Foundation Degree will be considered individually on their merits for entry to Stage 2. Irish Leaving Certificate: B2B2B2B2CC/B2B2B2B2B2 including Higher Level grade B2 Mathematics OR B2B2B2B2B2B2/AB2B2B2B2 including Higher Level grade B2 in Chemistry or Physics + Ordinary Level grade C in Mathematics Direct admission onto this programme is not permitted. Transfer onto this programme is permitted for students enrolled on the BEng Software Engineering (4 Year Sandwich) programme who either fail to secure a placement or are granted exemption from the placement. Full-TIme Length of Programme 3 Total Credits for Programme 360 Awarding Institution/Body Teaching Institution School/Department Framework for Higher Education Qualification Level dguidance Queen s University Belfast Queen s University Belfast Electronics, Electrical Engineering and Computer Science Level 6

2 QAA Benchmark Group y/subject-guidance/pages/subject-benchmarkstatements Collaborative Organisation and form of Collaboration (if applicable) Accreditations (PSRB) ATAS Clearance External Examiner Name: Professor Faron G Moller Accredited by British Computing Society Not required Computing N/A Date of next scheduled accreditation visit 2018 External Examiner Institution/Organisation Swansea University Does the Programme have any approved exemptions from the University General Regulations (Please see General Regulations) Programme Specific Regulations Yes No x (If yes, please state here any exemptions to regulations which have been approved for this programme) Examinations The programme is subject to the University General Regulations which can be found at: caffairs/ Progression from Stage 1 to Stage 2: In order to proceed to Stage 2, Stage 1 students must have passed a minimum of 5 Level 1 modules and have passed CSC1012. Progression from Stage 2 to Stage 3: In order to proceed to Stage 3, Stage 2 students must have passed a minimum of 5 Level 2 modules (taking account of any prerequisites) and have passed 6 modules at Level 1. Award of Degrees For the award of a BEng Honours Degree students must normally have passed at least 16 modules. The classification of the Honours degree is determined by a straight aggregate of the weighted marks for the individual modules which contribute to the classification. The classification is based on the compulsory Level 3 modules plus sufficient optional modules to a total of 6 taken in Stage 3, of equal weight = 60% of final mark, the compulsory Level 2 modules of equal weight = 30% of final mark and the compulsory Level 1 modules of equal weight = 10% of final mark. Students with protected characteristics Are students subject to Fitness to Practise Regulations (Please see General Regulations) Length of Programme N/A Please indicate No Fitness to Practise programmes are those which permit students to enter a profession which is itself subject to Fitness to Practise rules 3 years

3 Educational Aims of Programme The overall aim of the programme is to provide a broadly-based education in Software Engineering, supported by fundamental topics in Computing Science, which will produce graduates equipped to apply best practice in software engineering to the design and development of a wide range of information systems in organisations. On completion of the programme the student will be able to: The necessary skills, tools and techniques needed to embark on careers as professional Software Engineers or undertake research and teaching in Software Engineering. Knowledge and understanding of the fundamental principles of Software Engineering and Computer Science. A rigorous approach to the design and development of software systems and the analysis of their correctness and complexity, which will remain applicable through changes in technology. A broad understanding and experience of the professional context and the wider business and legal environment in which Software Engineers operate. The skills necessary to critically evaluate new developments in technology and take advantage of them where appropriate. The values, attitudes and competencies needed to undertake CPD and self-directed learning throughout their careers. Timely exposure to, and practical experience in, a range of current, emerging, novel and exciting developments in software development. Consistent with the general Educational Aims of the Programme and the specific requirements of the Benchmarking Statement for Computing, this specification provides a concise summary of the main features of the Single Masters Software Engineering programme, and the learning outcomes that a typical student might reasonably be expected to achieve and demonstrate if he/she takes advantage of the learning opportunities that are provided. Specifically, students graduating from the Single Masters Software Engineering programme will have achieved the following learning outcomes, commensurate with degree classification, relating to subject specific knowledge and understanding; intellectual, practical and key transferable skills Learning Outcomes: Cognitive Skills be able to: I1. Analyse, evaluate, interpret and synthesise information. pervasive across all modules and comprises the forms of thinking needed to specify, design, implement, evaluate or maintain software systems. I2. Critically evaluate and balance quality indicators in the design and development of software solutions. I3. Critically evaluate a given software design, component or project, identifying and resolving deficiencies. I4. Appraise the professional, legal and ethical framework within which a Software Engineer must operate. and programming/project based modules.. explicitly developed within the CSC2011 professional practice module, although, modules that explore software quality and capstone projects also permit Combination of unseen written examinations (I1), assessed practical work (I1, I2), practical examinations (I1), online MCQs (I1), assignments (I1, I2, I3, I4), projects (I2, I4), technical reports (I1, I2, I3, I4) and dissertations (I1, I2, I3, I4).

4 development of this learning outcome. Learning Outcomes: Transferable Skills be able to: TE1. Work effectively with and for others, including as part of a team. primarily developed within modules that involve a team-based project element and to a lesser degree within all modules. TE2. Retrieve information from a variety of sources and by a variety of techniques. developed within all modules and strongly embedded as part of modules that include a strong investigative element. TE3. Use information technology effectively. pervasive across all modules and comprises a core competency needed within all computing modules. TE4. Communicate effectively using various modes/media and with a variety of audiences. primarily developed within modules that involve either a presentation/demonstration element or a strong multi-media component. To a lesser degree it is embedded within the submissions required for all modules. TE5. Understand and present information involving a quantitative dimension. pervasive across all modules and comprises a core TE6. TE7. Manage one s own learning and development including time management and organisational skills. Learn independently in familiar and unfamiliar situations with open-mindedness and a spirit of critical enquiry. competency needed within all computing modules. pervasive across all modules and comprises a core competency needed to successfully complete computing modules, particularly for those after Stage 1. pervasive across all modules and comprises a core competency needed within all computing modules. TE8. Plan and manage their career. explicitly developed within the CSC2011 professional practice module and to a lesser degree within modules that require the student to actively consider and explore roles that map onto a range of software engineering career paths. TE9. Appreciate the need for continuing professional development in recognition of the need for lifelong learning. Learning Outcomes: Knowledge and Understanding be able to: KU1. The underpinning mathematics and theoretical framework of Software Engineering. KU2. The essential principles, theories, practices, languages and tools that may be deployed for the specification, design, implementation, evaluation and maintenance of software systems. primarily developed within modules that illustrate the evolution and development of software engineering. primarily developed through programming modules (including those that primarily focus on algorithms) alongside software design modules. The theoretical frameworks underpinning software engineering are developed and expanded throughout the degree. forms a core component of the degree and is developed throughout all modules that involve the specification, design, implementation, evaluation or combination of unseen written examinations (TE2, TE4, TE5), assessed practical work (TE2, TE3, TE5), practical examinations (TE2, TE5), online MCQs (TE2, TE5), assignments (TE2, TE3, TE4, TE5, TE6, TE7, TE8, TE9), projects (TE1, TE2, TE3, TE4, TE5, TE6, TE7, TE8, TE9), presentations (TE1, TE2, TE3, TE4, TE5), demonstrations (TE1, TE2, TE3, TE4, TE5), technical reports (TE1, TE2, TE3, TE4, TE5, TE6, TE7) and dissertations (TE1, TE2, TE3, TE4, TE5, TE6, TE7, TE9). Combination of unseen written examinations (KU1, KU2, KU5), assessed practical work (KU2, KU3), online MCQs (KU1, KU2), assignments (KU2, KU3, KU4), presentations (KU3, KU4), demonstrations (KU3, KU4), technical reports (KU2, KU3, KU4) and dissertations (KU3, KU4, KU5).

5 KU3. KU4. KU5. Good engineering practice in the specification, design, implementation, evaluation and maintenance of software solutions. The importance of quality and fitness for purpose of the software engineering process and resulting artefacts. The professional, legal and ethical responsibilities of Software Engineers and their role within an organisation. Learning Outcomes: Subject Specific Skills be able to P1. Apply a range of software engineering concepts, tools and techniques to the solution of complex software engineering problems. P2. Deploy appropriate theory, practices and tools for the specification, design, implementation, and evaluation of computer based systems. P3. Deploy effectively the tools used for software development and documentation of software systems. P4. Work effectively as a member of a software development team, recognising the different roles within a team and the different ways of organising teams. P5. Employ appropriate project management approaches within complex software engineering environments. P6. Articulate and effectively communicate the design and technological rationale for a given software component or project through appropriate technical reports and presentations. maintenance of software systems. and project based modules. and capstone projects, although, this learning outcome is developed, to a lesser degree, within all programing modules. explicitly developed within the CSC2011 professional practice module, although, modules that explore software quality and capstone projects also permit development of this learning outcome. developed within most modules and reflects the practical and problem-based nature of software engineering. embedded within most modules with the strongest development of this learning outcome with development oriented modules. and programming/project based modules and to a lesser degree within most modules. developed within modules that involve a team-based project element. developed within modules that either involve a software development project element or provide specific coverage of this aspect of software engineering. developed within modules that involved the justification of design or related technical aspects through appropriate reports, presentations or demonstrations. Combination of unseen written examinations (P2), assessed practical work (P2), practical examinations (P2), online MCQs (), assignments (P1, P2, P3), projects (P1, P2, P3, P4, P5), presentations (P4, P6), demonstrations (P4, P6), technical reports (P1, P2, P3, P4, P6) and dissertations (P1, P2, P3, P6)

6 Programme Requirements Module Title Introduction to Software Engineering and Project Management Module Code Level/ stage Credits Availability Duration Pre-requisite Assessment S1 S2 Core Option Coursework % Examination % CSC X 12 weeks X Fundamentals of Programming CSC X X 24 weeks X Programming Challenges CSC X X 24 weeks X Reasoning for Problem Solving CSC X 12 weeks X Foundations of Computing Systems CSC X X 24 weeks X Tournaments in Computing I CSC X X 100 Data Structures and Algorithms CSC X 12 weeks CSC1011 and X CSC1012 Networks and Communications CSC X 12 weeks CSC1011 X Professional Computing Practice CSC X X 24 weeks X Software Engineering and Group Project Advance Programming using C# and C++ CSC X 12 weeks CSC1011 and CSC1012 X CSC X X 24 weeks CSC1011, CSC1012 X Database Systems CSC X 12 weeks CSC1011 and 1012 X Tournaments in Computing II CSC X X 100 Software Engineering Project CSC X X 24 weeks X Software Design Principles and Patterns CSC X 12 weeks X Software Testing and Verification CSC X 12 weeks X Information System Security CSC X 12 weeks CSC2008 X Concurrent Programming CSC X 12 weeks Agile & Component Based Development using.net CSC X 12 weeks CSC2001 CSC2001 X X Advanced Computer Architecture CSC X 12 weeks X Tournaments in Computing III CSC X X 100 Approved by Director of Education: Print Name: Dr Phil Hanna.. Signature: Philip Hanna Date: 29/05/15