UNIVERSITY OF KENT CODE OF PRACTICE FOR QUALITY ASSURANCE

Transcription

1 SECTION 1: MODULE SPECIFICATION TEMPLATE 1 The title of the module CO548 Software Engineering Process 2 The Department which will be responsible for management of the module School of Computing 3 The Start of the Module September The number of students expected to take the module 40 5 Modules to be withdrawn on the introduction of this proposed module and consultation with other relevant Departments and Faculties regarding the withdrawal CO540 6 The level of the module I 7 The number of credits which the module represents 15 (7.5 ECTS credits) 8 Which term(s) the module is to be taught in (or other teaching pattern) Spring 9 Prerequisite modulesco320 Introduction to Object Oriented Programming CO323 Databases and the Web CO547 Agile Software Development 10 The programme(s) of study to which the module contributes BSc Computing BSc Computing (consultancy) BSc Information Technology BSc Information Technology (consultancy) BSc Business Information Technology 11 The intended subject specific learning outcomes and, as appropriate, their relationship to programme learning outcomes The aim of this module is to provide an opportunity for students to focus on the basic engineering processes: specification, design, development, verification and validation, and management that are employed in the construction of large and complex software systems. Students who successfully complete this module will be able to: 11.1 Describe, explain and carry out the processes used in the production of quality software [B1, B2, B3, B5, C2] 11.2 Describe the processes, techniques and deliverables associated with requirements engineering [B1, B3, D2]

2 11.3 Describe a variety of approaches employed in software development and indicate the circumstances where such approaches may be appropriate [A2, A4, C4] 11.4 Appreciate a range of software architectures and design processes. [A2, B5] 11.5 Understand the role of verification and validation, and the importance of testing.[a4, B4, B7, B9] 11.6 Identify the roles and responsibilities of members of a software development team and the methods of intercommunication. [A3, A11, D2, D5] 11.7 Understand project management including project scheduling, staffing, cost estimation and budgeting, configuration management, quality assurance and process improvement. [A2, C2, C4] 11.8 Discuss the professional and legal duties software engineers owe to their employers, employees, customers and the wider public [B6]; 12 The intended generic learning outcomes and, as appropriate, their relationship to programme learning outcomes Students who successfully complete this module will be able to: 12.1 Make effective use of IT facilities for scholarship and research. [D3] 12.2 Be able to manage their own time, learning and development. [D5] 12.3 Present and discuss a topic of study [B2, D2] 12.4 Recognise and be guided by social, professional and ethical issues and guidelines.[b6] 13 A synopsis of the curriculum The module studies in detail the activities and artefacts associated with software development process as performed by a development team (i.e. programming in the large). Topics covered include Software development paradigms Requirements acquisition, requirements stability Project management: planning and scheduling, staffing, cost estimation, risk assessment and mitigation, Software architectures and design processes Verification and validation, software testing Configuration management, change control, version control Software quality assurance, software metrics, Capability Maturity Model Ethics and professional responsibility 14 Indicative Reading List Sommerville,I, Software Engineering, 9e Addison Wesley, 2010 Pressman, R, Software Engineering: A Practitioner's Approach, 7e McGraw-Hill Higher Education, 2009 Pfleeger, S L; Atlee, J M, Software Engineering: International Version: Theory and Practice, 4e Pearson, 2009 Van Vliet, H Software Engineering: Principles and Practice, 3e John Wiley & Sons, Learning and Teaching Methods, including the nature and number of contact hours and the total study hours which will be expected of students, and how these relate to achievement

3 of the intended learning outcomes The module comprises 150 hours of study over one term. The content of the module will be delivered by 22 lectures in which concepts are presented. This will be consolidated by a further 11 seminars in which examples, case studies and published material will be discussed. Preparation for these seminars will involve prior investigation, prescribed reading and writing of essays. 22 hours of lectures [ , 12.4 ] 11 hours of supervised practical classes [ , ] 117 hours private study [ , ] 16 Assessment methods and how these relate to testing achievement of the intended learning outcomes The module will be assessed by 50% course work and 50% examination. A student will be required to prepare and submit 4 essays on topics distributed randomly from a list of titles that cover the module s indicative content. Each essay will represent 20% of the coursework mark and the remaining 20% will be awarded according to a student s participation in seminars focussing on the various essay titles. Poor seminar attendance or failure to prepare and engage in the seminar discussion will be penalised. Students will be awarded either 1 or 2 marks depending on their contribution to a seminar s discussion (up to a maximum total of 20 marks). Failure to attend a seminar will automatically result in a mark of zero being awarded. These marks will also reflect the attainment of the generic learning outcomes. Examination questions will be set to ensure that learning outcomes not covered by coursework are assessed. [11.1-8] Coursework will assess: [11.1-8, ] 17 Implications for learning resources, including staff, library, IT and space. Recommended texts will be acquired for library and online resources. No additional IT facilities, not already available, required. 18 The School recognises and has embedded the expectations of current disability equality legislation, and supports students with a declared disability or special educational need in its teaching. Within this module we will make reasonable adjustments wherever necessary, including additional or substitute materials, teaching modes or assessment methods for students who have declared and discussed their learning support needs. Arrangements for students with declared disabilities will be made on an individual basis, in consultation with the University s disability/dyslexia support service, and specialist support will be provided where needed. 19 Campus(es) where module will be delivered: Medway If the module is part of a programme in a Partner College or Validated Institution, please complete the following: 19. Partner College/Validated Institution: 20. University School responsible for the programme:

4 SECTION 2: MODULE IS PART OF A PROGRAMME OF STUDY IN A UNIVERSITY SCHOOL Statement by the School Director of Learning and Teaching/School Director of Graduate Studies (as appropriate): "I confirm I have been consulted on the above module proposal and have given advice on the correct procedures and required content of module proposals"... Director of Learning and Teaching/Director of Graduate Studies (delete as applicable) Statement by the Head of School: "I confirm that the School has approved the introduction of the module and, where the module is proposed by School staff, will be responsible for its resourcing"... Head of School. SECTION 3: MODULE IS PART OF A PROGRAMME IN A PARTNER COLLEGE OR VALIDATED INSTITUTION (Where the module is proposed by a Partner College/Validated Institution) Statement by the Nominated Officer of the College/Validated Institution (delete as applicable): "I confirm that the College/Validated Institution (delete as applicable) has approved the introduction of the module and will be responsible for its resourcing"... Nominated Responsible Officer of Partner College/Validated Institution... Post. Partner College/Validated Institution

5 Module Specification Template Last updated February April 2013