MSc SE curriculum development : phases and tasks

1
DEVELOPING A JOINT SOFTWARE ENGINEERING MASTERS
CURRICULUM ACROSS COUNTRIES REPORT ON AN ONGOING
MULTI-NATIONAL EDUCATIONAL PROJECT K. Bothe, Z.
Budimac, R. Cortazar, H. Zedan Humboldt
University Berlin, Germany University of Novi
Sad, Serbia University of Deusto, Bilbao,
Spain De Montfort University, Leicester, UK ACM
Informatics Education Europe conference
Montpellier, Nov. 9 10, 2006
2
The consortium Beneficiary partners, EU
partners, Individual experts
De Montfort University Leicester, UK
Humboldt University Berlin, Germany
University Deusto, Bilbao, Spain
University Timisoara, Romania
University Novi Sad, Serbia
Rijeka
Banja Luka
University Belgrade, Serbia
University Plovdiv, Bulgaria
University Nis, Serbia
University Skopje, FYR Macedonia
Plovdiv
3
Goals

• Develop a joint Software Engineering (SE) Master
  programme that should
• be compliant with the Bologna declaration,
• lead to the award of Master of Science (M.Sc.)
  
• in SE common to all participating
  institutions,
• be designed to fulfill labor market needs,
• allow for teachers and students mobility and
• be implemented in four universities in
• South Eastern Europe but open to other
• universities in the EU.

4
Mission

• The MSc curriculum in software engineering is
  committed to excellence in European-wide software
  education and training of engineers to deliver
  high quality and trustworthy software systems
  that meet the local industrial needs.

5
Challenges

• Joint?
• Work-load?
• Quality measures?
• Sustainability?

6
What is a Joint Degree?

• Study programme which include periods of study
  abroad in at least two universities in two
  different countries.
• Programmes leading to the award of a double,
  multiple or joint degree are characteristically
  offered by a consortium of at least two partner
  universities from different countries and require
  student mobility as a mendatory part of the
  curriculum. Furthermore, it could be assumed
  that partners offering the study programme would,
  in advance, agree on educational goals, learning
  outcomes, i.e. competence profiles of graduates

7
Three models of joint degrees

• Identical structure and content of the complete
  curriculum in each participating university,
• ? student mobility has no added value
• Comparable courses in the study programme and
  different offers of specialisation by each
  partner university (similar core, different
  specialisation)
• Complementary courses as mandatory part of the
  study program offered by different partner
  universities

8
Principles of 'Joint'

• Joint goals and structure of the curriculum
• Joint agreement and acceptance of module list
• Distributed development of teaching materials
  across universities
• Exchange of teachers/instructors amongst the
  institutions
• Students mobility across the partners
• Common principles of quality assurance
• Coordination of all development activities

9
Structure of the Joint Masters Curriculum
Semesters, Module lists, ECTS
Induction layer 1st Semester Core modules 2nd Semester Elective modules 3rd Semester Project
Introduction to software engineering Principles of programming, coding and testing Project management System modelling and design Research methods (part 1) Requirements engineering Architecture, design, and patterns Software testing System integration Information system development process Software evolution Component-based development Formal methods engineering Software engineering for critical systems Privacy, ethics, and social responsibilities Applied system thinking Business modelling E-business Business process re-engineering Service quality management Software engineering for database systems Advanced topics in software engineering Project, e.g. Electronic Patient Records Electronic purse Flight Control Systems
1 ECTS 20 hours of total student's workload
30 ECTS 15 weeks
30 ECTS 15 weeks
30 ECTS 15 weeks
10
Module templateRequirements specification of a
module
Induction layer 1st Semester Core modules 2nd Semester Elective modules 3rd Semester Project
Introduction to software engineering Principles of programming, coding and testing Project management System modelling and design Research methods (part 1) Requirements engineering Architecture, design, and patterns Software testing System integration Information system development process Software evolution Component-based development Formal methods engineering Software engineering for critical systems Privacy, ethics, and social responsibilities Applied system thinking Business modelling E-business Business process re-engineering Service quality management Software engineering for database systems Advanced topics in software engineering Project, e.g. Electronic Patient Records Electronic purse Flight Control Systems

• Module template
• Aims
• Learning outcomes
• Syllabus
• Prerequisites
• Recommended assessment

11
Module template an example

• RESEARCH METHODS (SE-C-01)
• AIMS
• The module will introduce and develop the
  concepts, organisational structure and
  deliverables of a research project using
  qualitative and quantitative methods. To extend
  to a postgraduate level, the student's
  appreciation and understanding of how to
  organise, to plan and 'execute' a technical
  research project.
• LEARNING OUTCOMES
• Upon successful completion of this module, the
  student will be able to
• prepare, plan and monitor a research project
  using tools and skills needed for critical
  evaluation and analyses of project results
• formulate, plan and communicate a research
  project
• select and appreciate the appropriate search
  methods for collection of information
• demonstrate knowledge and experience on
  procedures and methods for structuring, gathering
  and handling of information and data in a
  technological environment.
• SYLLABUS CONTENT
• Project approaches project management, quality
  management.
• Communication skills presentation skills,
  literature search patents, technical report
  writing.
• Methods for research problem analyses and
  problem solving techniques methods for
  structuring a problem qualitative methods for
  system/process analyses and performance
  assessment quantitative methods for data
  gathering and data analyses experiment design
  and collection of data, performance analyses,
  variance analyses, statistical quality control,
  statistical process control plagiarism and
  referencing health and safety aspects of
  research
• PREREQUISITES None

12
From module templatesto teaching materials

• Principles
• Each module assigned to a module
  developer
• Distributed development by beneficiary
  partners, EU partners, individual
  experts
• Teacher re-training
• Quality assurance Quality team

• Module template
• Aims
• Learning outcomes
• Syllabus
• Prerequisites
• Recommended assessment

Induction layer 1st Semester Core modules 2nd Semester Elective modules 3rd Semester Project
Introduction to software engineering Principles of programming, coding and testing Project management System modelling and design Research methods (part 1) Requirements engineering Architecture, design, and patterns Software testing System integration Information system development process Software evolution Component-based development Formal methods engineering Software engineering for critical systems Privacy, ethics, and social responsibilities Applied system thinking Business modelling E-business Business process re-engineering Service quality management Software engineering for database systems Advanced topics in software engineering Project, e.g. Electronic Patient Records Electronic purse Flight Control Systems

• Teaching materials
• Presentation material (slides)
• Supporting literature for lecturers
• Lecture notes, explaining the way in which slide
  contents can be delivered to students
• Material for theoretical and practical exercises
  (assignments, solutions, tools )
• Supporting literature for students

13
Technical Editors, Developers Instructors The
Quality Team
External Examiners

• Evaluate
• Advise

• Deliver
• Evaluate
• Collate
• Communicate
• Keep Journal
• Examin

Tech. Editors
Instructors

• Liaise
• Analyse
• Ensure

Students
Developers

• Learn
• Interact
• Feedback

• Develop
• Liaise

14
Module assessments by TE

• Structure of module assessments by TE 1. Module
  title2. Date of editing3. To what extent
  does the material cover learning outcomes of
  modules (as described in template)4.
  Are tutorials/problem classes/case studies
  adequate5. Is the timeline for face-to-face
  delivery and self study adequate6. Comment on
  the suitability of books and course material
  associated with module7. Has dry run been
  completed8. Comment on overall technical
  quality of material is it of an MSc standard?
• AdvantagesA. Uniformity on reporting
  progressB. Gives us a way to draw guidelines
  for editors to follow.

15
Assessment by software industry

• April 2006 Review of the Joint MSc. curriculum
  specification by ESI (European Software
  Institute, Spain)? revision of the curriculum
  specification? ESI "The Joint MSc Curriculum
  in Software Engineering comprises an ambitious
  and determined effort. We foresee that its
  implementation will allow many students to learn
  about current software engineering theory and
  practice and become competent members of the
  profession."
• Local industry advisory board
• Levi9 (Netherlands / Novi Sad, Nis - Serbia)
• EnergoSoft (Serbian national company)

16

• Project progress and current state

17
Milestones and current state

• Workshops and coordination meetings Novi
  Sad (October 2004), Bilbao (April 2005),
  Leicester (July 2005), Novi Sad (October 2005),
  Skopje (April 2006), Nis (October
  2006) ? Rather important for face-to-face
  discussion and project progress
• October 2005 1st Version of the curriculum
  specification Definition of the curriculum
  goals, structure of the curriculum, module lists,
  and quality assurance
• October 2006 State of distributed development of
  teaching materials across universities are at
  rather different levels of completion
• February 2007 first delivery of the curriculum
  at Novi Sad with teacher and students mobility
  amongst the institutions
• June 2007 Dissemination workshop with
  representatives of universities of the region
  (Croatia, Albania, Bulgaria, Rumania, Bosnia,
  Serbia, FYR Macedonia) to discuss possibilities
  to joint the curriculum
• October 2006 Accreditation procedures in
  progress for each institution (department,
  faculty, university, country) see next slide

18
Accreditation state in September 2006
Institution Department Faculty University National accreditation
Novi Sad, Serbia OK OK, March 2006 OK, April 2006 N/A
Belgrade, Serbia OK OK, May 2006 N/A
Niš, Serbia OK Expected in October 2006 Expected in November 2006 N/A
Skopje, Macedonia OK OK, April 2006 Expected in September 2006

19
MSc SE curriculum development project model
phases, tasks, products
General aims
Laws, rules
Universities
Size
Flexibility
Requirements of the curriculum (Analysis
Definition)
Quality assurance and control Quality Assurance
and control documents
Mission excellence in European- wide
Learning outcomes, goals
Bologna- compliant
Staff (enough knowledge-able, experienced)

• Length of study
• 3 semesters
• 90 credits

Open for new SE developments
Entry requirements of students
Useful for local industry needs
Compliant with national laws
Laboratory (well-equipped)
1 year 2 semesters
Local variants possible
Program validation
Library (well-equipped)
Structure of the curriculum (Design)
Module templates (one for each module)
Module development
Module name Aims Learning outcomes Syllabus
content Entry requirements Learning
approaches Suggested reading Credits Exam
Induction layer 1st Semester Core modules 2nd Semester Elective modules 3rd Semester Project
Introduction to software engineering (SE-IN-01) Principles of programming, coding and testing (SE-IN-02) Project management (SE-IN-03) System integration and reuse (SE-I-01) Privacy, ethics and social responsibilities (SE-I-02) Requirement engineering (SE-I-03) Software Engineering for Critical Systems (SE-II-01) Software evolution (SE-II-02) Formal Methods Engineering (SE-II-03) Project, e.g. Electronic Patient Records Electronic purse Flight Control Systems
Module assessment
Students selection
Quality assurance of study packs
Module development (Implementation)
Teaching materials for modules and projects
produce new ones reuse, adapt, extend existing
materials
Build teams and let them work
Slides
Lecture notes
Exercises (theoretical, practical)
Exams
Literature for lecturers
Case studies
Reading material for students
Literature list for students
Advisory board (Panel)
Lab exercises case studies, assignemnts, project
materials
Requirements for lecturers (job description)
Quality team
Introduction of the curriculum at 1-4
universities Novi Sad, Nis,Belgrade,
Skopje (Installation and Use)
Documentation of the curriculum
Run the curriculum
Legal issues
Equipment
Teachers
Students
Teaching team
National accreditation
Program handbook
Module template handbook
Built-up Laboratory
Select Teachers
Select Students
Deliver modules in classes

• Assessment
• Internal moderator
• External examiner

Mutual recognition Serbia, Mecedonia
Students handbook
Staff handbook
Built-up Library
Teacher Reraining )
Possible Student mobility
ECTS documents
) Dry-run, chain-training
Possible Teacher mobility
Sustainability (Maintenance)
Module feedback forms for students
Continual / annual assessment and revision
20
MSc SE curriculum development project model
phases, tasks, products
General aims
Laws, rules
Universities
Size
Flexibility
Requirements of the curriculum (Analysis
Definition)
Quality assurance and control Quality Assurance
and control documents
Mission excellence in European- wide
Learning outcomes, goals
Bologna- compliant
Staff (enough knowledge-able, experienced)

• Length of study
• 3 semesters
• 90 credits

Open for new SE developments
Entry requirements of students
Useful for local industry needs
Compliant with national laws
Laboratory (well-equipped)
1 year 2 semesters
Local variants possible
Program validation
Library (well-equipped)
Structure of the curriculum (Design)
Module templates (one for each module)
Module development
Module name Aims Learning outcomes Syllabus
content Entry requirements Learning
approaches Suggested reading Credits Exam
Induction layer 1st Semester Core modules 2nd Semester Elective modules 3rd Semester Project
Introduction to software engineering (SE-IN-01) Principles of programming, coding and testing (SE-IN-02) Project management (SE-IN-03) System integration and reuse (SE-I-01) Privacy, ethics and social responsibilities (SE-I-02) Requirement engineering (SE-I-03) Software Engineering for Critical Systems (SE-II-01) Software evolution (SE-II-02) Formal Methods Engineering (SE-II-03) Project, e.g. Electronic Patient Records Electronic purse Flight Control Systems
Module assessment
Students selection
Quality assurance of study packs
Project Model overview of activities, phases,
and products

• Useful for
• analyzing current state
• planning next activities

Module development (Implementation)
Teaching materials for modules and projects
produce new ones reuse, adapt, extend existing
materials
Build teams and let them work
Slides
Lecture notes
Exercises (theoretical, practical)
Exams
Literature for lecturers
Case studies
Reading material for students
Literature list for students
Advisory board (Panel)
Lab exercises case studies, assignemnts, project
materials
Requirements for lecturers (job description)
Quality team
Introduction of the curriculum at 1-4
universities Novi Sad, Nis,Belgrade,
Skopje (Installation and Use)
Documentation of the curriculum
Run the curriculum
Legal issues
Equipment
Teachers
Students
Teaching team
National accreditation
Program handbook
Module template handbook
Built-up Laboratory
Select Teachers
Select Students
Deliver modules in classes

• Assessment
• Internal moderator
• External examiner

Mutual recognition Serbia, Mecedonia
Students handbook
Staff handbook
Built-up Library
Teacher Reraining )
Possible Student mobility
ECTS documents
) Dry-run, chain-training
Possible Teacher mobility
Sustainability (Maintenance)
Module feedback forms for students
Continual / annual assessment and revision