Full document describing all aspects of the curriculum, release 2 (pdf)

More documents

Recommendations

Info

5. Principles for implementing the curriculum1. Number of modules. All modules are one-semester long and equallyweighted. The total number of modules will be eight. However, dueto different traditions and backgrounds some universities may chooseten modules. In such a case we insist that at least eight of those tenmodules must be chosen from the list given below.2. Module weight. The weight of each module is 7.5 ECTS credits incase of four and six ECTS credits in case of five modules persemester. In the former case additional homeworks must be given tostudents in order to reach the value of 7.5 ECTS credits per everymodule.3. Contact hours. The number of contact hours per module is four perweek.4. Induction layer. Modules in this layer can be chosen from thosedescribed below. However if an institution does have equivalent (withrespect to learning outcomes) modules then it is free to use them.5. Core modules. Every institution is obliged to choose four modulesfrom the list of core modules. The institution can change its decisionevery year and have to direct students to the core modules of otherinstitutions belonging to the joint MSc studies in softwareengineering.For those institutions that decided to choose five modules persemester, four of those five must be from the core.6. Optional modules.6.1 In the 2 nd semester, students can choose four modules fromthe rest of core modules and/or optional modules, provided tohim or her by any institution belonging to the joint MScstudies in software engineering.6.2 Institutions do not have to offer all available optional modulesevery year.6.3 Institutions can include new module(s) into the set of optionalmodules, providing that they pass through the same qualityprocedures as the originally existing modules. The consortiumof institutions implementing the joint studies should agree onthe aims and learning outcomes of new modules.7. The choice of tools. Each institution implementing the curriculum willselect appropriate technologies and products to be used forimplementation and exemplification purposes, according tosuggestions given in module templates.8. Changes. If some of the institutions wishes to suggest changes itshould address the project consortium for a final decision during theduration of the project. Otherwise, the consortium will make the finaldecision.http://perun.im.ns.ac.yu/msc-se/ 6
6. Quality assurance and controlQuality assurance and control are extremely vital for the success of anyeducational and training curriculum. To this end we have established aseries of protocols that ensure the attainment of the highest level of qualityto the proposed MSc Curriculum. These protocols address five basiccomponents: curriculum validation, module development, moduleassessment, students’ selection and quality team.1. Curriculum Validation1.1 Validation is the process by which an academic institution establishesthat a new curriculum is• academically viable,• that academic standards have been appropriately defined and• that the students have the best opportunity to learn.1.2 A validation event should be organised in which a validation panel ofacademic peers scrutinise the proposed curriculum.1.3 A panel must have external members (academics and/orindustrialists).1.4 The panel reads the curriculum documentation before the event. Thedocumentation consists of Curriculum handbook (describing the wholecurriculum dealing with rationale, curriculum, costing and resourceissues, etc.), Detailed module templates handbook (requirementsspecification of all modules in the curriculum), Staff handbook(contains all CVs of teaching staff) and Student handbook (containseverything that students need to know, from the course regulation,modules, staff, libraries, etc.).1.5 Holding a face-to-face validation puts the curriculum team to the testand ensures they can justify their proposal.2. Module DevelopmentEvery fully developed module is described by the study pack that containsthe following:• detailed module template that refines and details the moduletemplate and also contains a) requirements for the lecturer (jobdescription) for every module and b) precise rules for examinationand the course work;• supporting literature for lecturers;• presentation material preferably slides in PPT format;• lecture notes, separate or attached to slides (preferably the latter),explaining the way in which slide contents can be delivered tostudents;• material for theoretical exercises (assignments, rules, solutions…);http://perun.im.ns.ac.yu/msc-se/ 7
Page 1 and 2: Joint MSc curriculum in software en
Page 3 and 4: 2. Goals of the Joint MSc curriculu
Page 5: 4. Module listList of induction lay
Page 9 and 10: • current practitioners with adeq
Page 11 and 12: 7. Module Templateshttp://perun.im.
Page 13 and 14: PRINCIPLES OF PROGRAMMING, CODING A
Page 15 and 16: SYSTEM MODELLING AND DESIGN (SE-IN-
Page 17 and 18: REQUIREMENTS ENGINEERING (SE-C-02)A
Page 19 and 20: SOFTWARE TESTING (SE-C-04)AIMS:With
Page 21 and 22: INFORMATION SYSTEM DEVELOPMENT PROC
Page 23 and 24: SOFTWARE EVOLUTION (SE-O-01)AIMS:Wi
Page 25 and 26: FORMAL METHODS ENGINEERING (SE-O-03
Page 27 and 28: PRIVACY, ETHICS AND SOCIAL RESPONSI
Page 29 and 30: BUSINESS MODELLING (SE-O-07)AIMS:Th
Page 31 and 32: BUSINESS PROCESS RE-ENGINEERING (SE
Page 33 and 34: SOFTWARE ENGINEERING FOR DATABASE S
Page 35 and 36: PROJECTAIMS:This module is intended
Page 37 and 38: Moduleaka “course” or (in some
Page 39 and 40: The list of abbreviationsABASB2BB2C

Full document describing all aspects of the curriculum, release 2 (pdf)

Create successful ePaper yourself

Delete template?

Save as template?