Curriculum The Bachelor's Degree Programme in Web Development National section. Studies

Transcription

1 Curriculum The Bachelor's Degree Programme in Web Development National section Studies

2 Curriculum Bachelor's Degree Programme in Web Development National section 1. Contents 2. Programme structure Core areas of study Core area: web programming (bridging course), back end programming Core area: web programming (bridging course), front end programming Core area: development environments Core area: databases Core area: interface design Compulsory educational components within the core areas of the study programme Number of examinations for the compulsory educational components Internship Bachelor's degree project Examination schedule Credit transfer Pre-approved credit transfer Credit transfer agreements Admission Exemption Effective date and transition provisions This is the national section of the curriculum for the Bachelor's Degree Programme in Web Development ('Professionsbachelor i webudvikling'), under Ministerial Order no. 353 of 7 April 2015 on the Bachelor's Degree Programme in Web Development. Link to the Ministerial Order (in Danish):

3 Curriculum - Bachelor's Degree Programme in Web Development National section 2. Programme structure 1st year of study 2nd year of study Web development Back end programming (10 ECTS) or (bridging course) Front end programming 10 ECTS Core areas of study (10 ECTS) Development environments (10 ECTS) 10 ECTS Databases (10 ECTS) 10 ECTS Interface design (10 ECTS) 10 ECTS Elective educational components 20 ECTS Internship 15 ECTS Bachelor's degree project 15 ECTS Total ECTS credits 60 ECTS 30 ECTS 3. Core areas of study The study programme covers the following core areas of study Web development (bridging course), o Back end programming (10 ECTS) or o Front end programming (10 ECTS) Development environments (10 ECTS) Databases (10 ECTS) Interface design (10 ECTS) 40 ECTS credits total 1

4 Curriculum - Bachelor's Degree Programme in Web Development National section 3.1 Core area: web programming (bridging course), back end programming Contents The purpose of this core area is to develop students' competencies to develop contemporary web applications using programming paradigms and taking advantage of current, standardised protocols and the possibilities of the client/server model. ECTS credits 10 ECTS Learning outcomes Knowledge Upon completion of the course, students should have acquired knowledge about: design patterns fundamental protocols of the World Wide Web the advantages and limitations of client/server architecture. Skills Upon completion of the course, students should have acquired the skills to: create web-based programs apply basic programming principles use web APIs document program structures. Competencies Upon completion of the course, students should have acquired the competencies to: analyse a development request with a view to constructing a web-based application select and apply suitable programming technologies for developing web-based applications mainly focusing on the server side. 2

5 Curriculum - Bachelor's Degree Programme in Web Development National section 3.2 Core area: Web development (bridging course), front end programming Contents The purpose of this core area is to develop students' competencies to develop contemporary web applications using programming paradigms and taking advantage of current, standardised protocols and the possibilities of the client/server model. Furthermore, students should develop an understanding of basic design and visual communication. This core area should also enable students to design simple user interfaces using aesthetic and communicative principles. ECTS credits 10 ECTS Learning outcomes Knowledge Upon completion of the course, students should have acquired knowledge about: fundamental protocols of the World Wide Web advantages and limitations of client/server architecture particular characteristics, weaknesses and strengths of different media communication strategies. Skills Upon completion of the course, students should have acquired the skills to: program and implement a dynamic web application master basic design principles apply theories on user friendliness and the skills to plan and conduct user tests document program structures. Competencies Upon completion of the course, students should have acquired the competencies to: analyse a development request with a view to constructing a web-based application select and apply suitable programming technologies for developing web-based applications mainly focusing on the client side. 3

6 Curriculum - Bachelor's Degree Programme in Web Development National section 3.3 Core area: Development environments Contents The purpose of this core area is to develop students' competencies in making a qualified choice of and applying a given development environment. ECTS credits 10 ECTS Learning outcomes Knowledge Upon completion of the course, students should have acquired knowledge about: integrated development environments (IDE) and their advantages and limitations common programming languages in a web context quality assurance and version control of applications in a web context types of content management systems and frameworks and their suitability in a web context criteria for selection of Content Management Systems or frameworks selection of relevant database technology for developing applications in a web context. Skills Upon completion of the course, students should have acquired the skills to: apply Content Management Systems or frameworks for developing applications in a web context use an integrated development environment when developing applications in a web context. Competencies Upon completion of the course, students should have acquired the competencies to: select a Content Management System or framework for developing applications for a given development assignment. 4

7 Curriculum - Bachelor's Degree Programme in Web Development National section 3.4 Core area: Databases Contents The purpose of this core area is to develop students' competencies in analysing and applying relevant dataprocessing models. ECTS credits 10 ECTS Learning outcomes Knowledge Upon completion of the course, students should have acquired knowledge about: at least one widely-used modelling language for data modelling distributed databases and their prevalence and use in web contexts describing problems concerning data exchange and the use of data formats in developing in web contexts. Skills Upon completion of the course, students should have acquired the skills to: apply data models for development and maintenance in web contexts apply complex database queries apply transactions embed business logic in the database layer use data formats for data integration. Competencies Upon completion of the course, students should have acquired the competencies to: analyse and select the tasks that would be suitably placed in the database layer and those that should be placed in the application layer analyse and select a database technology/technologies that will resolve a given development task in a web context suitably. 5

8 Curriculum - Bachelor's Degree Programme in Web Development National section 3.5 Core area: Interface design Contents The purpose of this core area is to develop students' competencies to enter complex usage scenarios and independently take part in the design process concerning the design of complex user interfaces. ECTS credits 10 ECTS Learning outcomes Knowledge Upon completion of the course, students should have acquired knowledge about: common interface design development methods human-computer interaction communication theory. Skills Upon completion of the course, students should have acquired the skills to: create convenient user interfaces adapted to relevant target groups based on the theory and methods of the relevant subject area apply design methods pertaining to visual design, interaction design and information architecture when designing user interfaces, including prototyping work on the development of communications solutions across platforms and media. Competencies Upon completion of the course, students should have acquired the competencies to: analyse choices of devices and effects in user interfaces and situate these choices in a context manage design processes based on analysis and planning take part in complex usage situations and independently manage the design process when designing complex user interfaces. 6

9 Curriculum - Bachelor's Degree Programme in Web Development National section 4. Compulsory educational components within the core areas of the study programme The study programme's compulsory educational elements 1. Web development (bridging course), a. Back end programming (10 ECTS) or b. Front end programming (10 ECTS) 2. Development environments (10 ECTS) 3. Databases (10 ECTS) 4. Interface design (10 ECTS) 40 ECTS credits total The four compulsory educational components are equivalent to the four core areas of study, have the same name, contents, are worth the same number of ECTS credits and have the same learning objectives. The four compulsory educational components are all finalised by examination. Assessment Each examination is assessed and graded according to the 7-point grading scale and is worth 10 ECTS credits. The learning objectives for the educational component are identical to the learning objectives for the examination. For the examination type and exam procedure, please see the institutional section of this Curriculum. 5. Number of examinations for the compulsory educational components The four compulsory educational components are each finalised by a single examination. See the examinations for the study programme in the "Examination schedule" section. ECTS credits for the core areas and the compulsory educational components are shown in the schedule below. Compulsory educational components course), Back end program- Web development (bridging ming or back Front end programming Development environments Databases Interface design Core areas of study Web development (bridging course), back end programming or front end programming 10 ECTS 10 ECTS Development environments 10 ECTS 10 ECTS Databases 10 ECTS 10 ECTS Interface design 10 ECTS 10 ECTS Total ECTS credits 10 ECTS 10 ECTS 10 ECTS 10 ECTS 40 ECTS 7

10 Curriculum - Bachelor's Degree Programme in Web Development National section 6. Internship The internship is organised in order to contributes, in combination with the other elements of the study programme, to the student's development of practical competencies. The purpose of the internship is to enable the student to apply the methods, theories and tools acquired during the course of the study programme in the solution of specific, practical tasks in web development. ECTS credits 15 ECTS Learning outcomes Knowledge Upon completion of the course, students should have acquired knowledge about: daily operations in the whole of the internship host company. Skills Upon completion of the course, students should have acquired the skills to: apply versatile technical and analytical working methods related to the occupation evaluate practical problems and propose possible solutions structure and plan daily tasks relevant to the occupation communicate and convey practical problems and issues and well-argued solution proposals. Competencies Upon completion of the course, students should have acquired the competencies to: manage the practical and discipline-related situations of the occupation acquire new knowledge, skills and competencies related to the occupation take a professional approach to professional and multidisciplinary collaboration with others. The internship is finalised by examination. The learning objectives for the educational component are identical to the learning objectives for the examination. For the examination type and exam procedure, please see the institutional section of this Curriculum. 8

11 Curriculum - Bachelor's Degree Programme in Web Development National section 7. Bachelor's degree project ECTS credits 15 ECTS Requirements for the bachelor's degree project In the bachelor's degree project, the student must demonstrate the ability to process a complex, practiserelated problem related to a specific web development task in an analytical and methodical way. The problem statement, which must be central to the education and the profession, must be formulated by the student, in collaboration with a private or public company or business if possible. The educational institution must approve the problem statement. The student must submit a project report and in some cases also a product. The project report, which makes up the written element of the examination, must as a minimum contain the following: cover page with title contents introduction including problem statement research method analysis solution proposals conclusion reference list (including all sources that are referred to in the project) appendix (only including appendices that are central to the report). The maximum allowed length of the report is 20 standard pages + 20 standard pages per student. The cover page, table of contents, reference list and appendices are not included in the required number of pages. Appendices are not assessed. One standard page is 2,400 characters including spaces and foot notes. Writing and spelling skills Writing and spelling skills will be assessed as part of the assessment and grading of the final degree project. The assessment is expressed as an overall assessment of the professional and academic content as well as the student's spelling and writing skills. Students may apply for an exemption from the requirement that spelling and writing skills form part of the assessment criteria if the application is supported by documentary evidence of a specific, relevant physical or mental impairment The application should be submitted to the study programme and directed to the attention of the programme director not later than 4 weeks before the exam is to be held. Learning outcomes The bachelor's degree project is to demonstrate that the student has achieved the expected level of graduate competence, please see Schedule 1 to Ministerial Order no. 353 of 7 April 2015 on the Bachelor's Degree Programme in Web Development. Knowledge Upon completion of the course, graduates should have acquired knowledge of: 1) the formal and de facto standardisation of the World Wide Web 9

12 Curriculum - Bachelor's Degree Programme in Web Development National section 2) the Word Wide Web's standards as a platform for applications 3) development environments for web development 4) Content Management Systems 5) the role of web applications in society and its development, and 6) common development methods in web development, and graduates should be able to reflect on the suitability of such methods for different development scenarios. Skills Upon completion of the course, students should have acquired the skills to: 1) plan and develop applications based on specific development requests 2) evaluate and select a suitable programming language for the performance of development requests 3) evaluate and select a suitable database system to ensure data and application persistence 4) create user interfaces adapted to relevant target groups based on the theory and methods of the relevant subject area 5) create user interfaces that make use of the World Wide Web's particular possibilities in terms of design and aesthetics 6) prepare documentation adapted to the target audience and to the extent of the project of the functionality and development process of a project, and 7) use a suitable development environment to perform the development process. Competencies Upon completion of the course, students should have acquired the competencies to: 1) handle complex situations aimed for progression in web development 2) take a professional approach to disciplinary and multidisciplinary collaboration with others. 3) identify their learning needs and structure their learning in different learning environments. Assessment The examination is externally assessed and will be graded according to the 7-point grading scale. The exam is made up of a project and an oral examination. The student will receive a single, joint grade for the written project and the oral examination. The exam cannot take place until the internship exam and the other exams of the study programme have been passed. For the examination type and exam procedure, please see the institutional section of this Curriculum. 10

13 Curriculum - Bachelor's Degree Programme in Web Development National section 8. Examination schedule Overview of all examinations and their scheduled semesters Examination 90 ECTS credits distributed across exams Assessment 1) Possible academic aptitude examination 1 Pass/fail 2) Web development (bridging course), 10 7-point grading scale Back end programming (10 ECTS) or Front end programming (10 ECTS) 3) Development environments (10 ECTS) 10 7-point grading scale 4) Databases (10 ECTS) 10 7-point grading scale 5) Interface design (10 ECTS) 10 7-point grading scale 6) Elective component examination(s) point grading scale 7) Internship examination 15 7-point grading scale 8) Bachelor s degree project 15 7-point grading scale 9. Credit transfer Passed educational components are equivalent to corresponding educational components offered by other educational institutions providing the programme. The student has a duty to inform the educational institution about educational components that were studied and passed at other Danish or foreign higher education institutions and to inform about occupations that can be assumed to earn the student transfer credit. The educational institution will grant transfer credit in each individual case based on completed/passed educational components and occupations that match course units, parts of the study programme or parts of the internship. The decision to award transfer credit is based on an assessment of academic elements. 9.1 Pre-approved credit transfer The student can apply for pre-approval of credit transfer. In cases of pre-approved credit transfer of studies in Denmark or abroad, the student is under a duty to document completion of the pre-approved educational components, upon completion of the study-abroad period. When applying for pre-approval, the student must consent to allow the educational institution to collect any required information upon the student s completion of the study-abroad period. For the final approval of pre-approved credit transfer, the educational component is considered completed if it is passed in accordance with the regulations applying to the study programme. 9.2 Credit transfer agreements None 1. If an academic aptitude examination is held, the examination will be described in the institutional section of this Curriculum. 2. The elective component(s) and the related examination(s) are described in the institutional section of this Curriculum. 11

14 Curriculum - Bachelor's Degree Programme in Web Development National section 10. Admission If all applicants applying for the education cannot be admitted for reasons of capacity, one or more of the following criteria will be considered important (not listed in order of priority): the grade average from the completed education that allows the applicant to apply for admission to the study programme the applicant's previous experience relevant to the study programme a personal talk where the applicant's motivation and academic ability will be identified. 11. Exemption The educational institution may grant exemption from those rules in the national section of this Curriculum that were laid down solely by the educational institutions, when exemption is substantiated by exceptional circumstances. The educational institutions co-operate on a uniform exemption practice. 12. Effective date and transition regulations This institutional section of this Curriculum comes into effect on 01 August 2015 and applies to all students who are and will be registered for the programme and to all examinations commenced on said date or thereafter. Any transition regulations applying to students registered for studies prior to August 2015 can be found in the institutional section of this Curriculum. 12

15 Curriculum The Bachelor's Degree Programme in Web Development Institutional component of the curriculum for Lillebaelt Academy of Professional Higher Education 2016 Approved by principal Jens Mejer Pedersen 23/ del

16 Bachelor's Degree Programme in Web Development - Institutional component of the curriculum 1. Table of Content 2. Effective date and transition period Examination schedule Participation in the programme and mandatory hand-ins Re-examinations Re-examinations of tests based on project work Scheduling of tests and exams Elective subjects Internship Requirements and expectations of the internship period Tests and Exams Test: Web Development, Backend-programming Test: Web Development, Frontend-programming Test: Development environments Test: Databases Test: Interface Design Elective subject exams Internship exam Bachelor degree project Credits for educational elements undertaken abroad Credits for elective educational elements Language Languages in tests and exams Appendix 1, Examination Regulations for the Lillebaelt Academy Contents General regulations Admission to exams Ordinary exams Re-examination Illness Absence from an exam Exam procedure Exam participation Types of exams Identification Use of aids During the exam Handing in written exam papers Cheating and use of sources Violation of the Examination Regulations Language used in the exam... 21

17 3.10 Special conditions Late attendance Errors and omissions in exams Spelling and writing skills are included in the overall assessment of the exam Complaints and appeals Appeal against decision of complaint Exam results Implementation and transitional provision Effective date and transition period This institutional component of the curriculum will come into effect on February 1 st 2016 and will apply to all students who are either already enrolled in, or who commence this study programme, as well as to all tests and exams held from this date and forward. The former institutional component of August 1 st 2009 is revoked by the 31 st of January However, tests and exams, that were initiated prior to February 1 st 2016 are to be concluded by the rules of the 2009 institutional component by January 31rd semesters at the latest. This study programme is governed by the current acts and orders for Academy Profession and Professional Bachelor programmes, as detailed in the common component of the curriculum. 1

18 3. Examination schedule Overview of all examinations and their scheduled semesters Placement Examination 90 ECTS credits distributed across exams Internal/External Assessment 1st study year Web development (bridging course), a. Back end programming (10 ECTS) or b. Front end programming (10 ECTS) 10 Internal 7-point grading scale 1st study year Development environments (10 ECTS) 10 External 7-point grading scale 1st study year Databases (10 ECTS) 10 Internal 7-point grading scale 1st study year Interface design (10 ECTS) 10 Internal 7-point grading scale 1st study year Elective component examination(s) 1 20 Internal/External 7-point grading scale 3rd semester Internship examination 15 Internal 7-point grading scale 3rd semester Bachelor s degree project 15 External 7-point grading scale All information on time and place of the tests can be found on Fronter 1. The elective component(s) and the related examination(s) are described in the elective course catalogue. 2

19 3.1. Participation in the programme and mandatory hand-ins. Study activity in the Bachelor's Degree Programme in Web Development entails active participation in both the lessons, and in the solving of group assignments. In order for a student to be considered active in their studies, they must participate in all obligatory study activities, as well as in all tests and exams in referral to the terms that are listed in this curriculum and in the current acts and orders for the programme. The compulsory participation requirements for the participation in the tests and exams of the programme are listed in the paragraphs below. The following compulsory participation requirements are mandatory in the entire programme: The student must participate in all obligatory study activities for each semester, including participation in the presentation of project work. The student must have handed in and gotten approved all obligatory assignments and study activities for a semester at the latest by the 15 th of May for the spring semester and at the latest by the 15 th of December for the autumn semester. At the beginning of each semester the teachers inform the students of the number of, the time for and the date of each of the semester s obligatory study activities, including assignments and projects. This information can also be found in the lecture plan for each subject or semester on Fronter. The teacher is responsible for assessing the student s obligatory assignments as well as their participation in study activities. If the teacher does not approve an obligatory assignment or project, the student has one further chance to hand in the assignment before the semester s tests and exams by special arrangement with their teacher. If the student did not participate in an obligatory study activity, the student must carry out a replacement activity with a similar workload and learning objectives as a requirement for participation in the semester s test and exams by special arrangement with their teacher. If a student s compulsory participation requirements for a semester are not fulfilled, the student is not allowed to participate in the respective test or exam and one examination attempt has then been used. Furthermore if the student still hasn t fulfilled the compulsory participation requirements for the semester by the time of the re-examination the student is not allowed to participate in re-examination either, and has then used two examination attempts as the student is automatically registered for both the exam and the re-examination when they enroll in a semester. If a student exhausts all three of their examination attempts, their enrolment in the programme will be terminated unless a dispensation from the dispensation committee is obtained. If a student cannot participate in an obligatory study activity due to illness or other unavoidable issues the student must inform the Lillebaelt Academy Study Administration within 2 days of the activity, if a student falls ill during the activity itself, the student must notify a supervisor or examiner before leaving the activity. 3

20 If a doctor s certificate is submitted, the activity will not count as an attempt. The student must cover the costs for the doctor s certificate that must be submitted to the Student Administration no later than one week after the activity. If the student despite ill health completes an activity, it counts as an attempt. The dispensation committee can grant an exemption for a student from the dates set for the approval of an obligatory study activity or for the participation therein if it is due to illness, maternity leave or other unavoidable issues Re-examinations The rules and regulations for re-examinations can be found in appendix 1 Examination Regulations for the Lillebaelt Academy Re-examinations of tests based on project work. If the Lillebaelt Academy estimates that the student has been a part of the group project work on an approxi-mately full scale, the re-examination is based on the original group project work. If the Lillebaelt Academy estimates that the student has not been a part of the group project work on an approximately full scale, the re-examination is based on a new project. The dispensation committee can grant an exemption for a student for the above-mentioned rules, if it is due to illness, maternity leave or other unavoidable issues Scheduling of tests and exams It follows from paragraph 4 below which tests and exams are individual, which tests and exams are group based and which test and exams are externally assessed. Furthermore, it follows how many ECTS-points are tested in each of the test or exams. Information about the time and place for each test and exam is published on Fronter at the latest 14 days before the test or exam at hand. For further information on the subject please see appendix 1 Examination Regulations for the Lillebaelt Academy Elective subjects The elective subjects allow students to specialize their skills in a field of study of their choice. The elective subjects are published in an elective subject catalogue, which contains a description of each elective subject, their ECTS scope, learning objectives, compulsory participation requirements and test forms. The Lillebaelt Academy retains the right to cancel any elective subject course, which does not reach the required amount of participants, as well as the right to limit the number of participants in a course. Students who are affected by either of these exemptions will be offered another elective subject of their choice. 4

21 3.6. Internship The internship is based on the business conditions and competence requirements of the subject areas in the programme. In combination with the other parts of the course programme the internship contributes to the development of the student s practical skills and competences. The purpose of the internship is to enable the student to work independently with the methods, theories and tools of the course programme in the solution of tangible tasks in the media and communication business in Denmark, as well as abroad. During the internship, the student is guided and advised by the internship counsellor, who is designated by the course programmes internship coordinator. Based on the learning objectives of the internship, which can be found in paragraph 6 in the common part of the curriculum, the student and the internship counsellor work out concrete goals for the student s internship. The goals are recorded in the Lillebaelt Academy s CRM-system and are sent to both the student and the internship host, and then act as the guiding principles of the students work in the internship period. The intern counsellor is responsible for: Helping the student work out goals for the internship. Inspiring and stimulating the student towards working with dedication during the internship. Inspiring the student to reflect on the experiences from the internship in regards to their future vocational plans. Being in contact with the student and the internship host before, during and after the internship period and to ensure that the internship is carried out according to plan. Carrying out internship visits in the Lillebaelt Academy s coverage area. Alternatively, contact can be carried out by digital aids. Evaluating the internship with the internship host. Assessing the student s internship report at the internship test. It is the student s own responsibility to find a suitable internship that can be approved by the internship coordinator. By approving the internship agreement, the internship coordinator ensures that the internship fulfills the curriculums requirements of the internship period. The internship agreement is filled out electronically in the standard template of the Lillebaelt Academy. In the internship agreement, the contents of the internship are defined. The student and the business hosting the internship sign the agreement electronically. It is possible for a student to do their internship abroad or in their own business. If a student chooses to do the internship in their own business it s a requirement that they find a relevant external mentor or counsellor from the business sector to spar with. The student must then present budgets and business plans to the internship counsellor for approval, before they then work out concrete goals and tasks for the student s internship period. 5

22 3.7. Requirements and expectations of the internship period. The internship period is comparable to a full time job, with the same requirements for working hours, effort, engagement and flexibility that a fully trained bachelor in web development can expect to encounter in their first job. The internship must amount to 3 months of full time work, but the internship period can be flexibly arranged, if the internship host and the student agree upon it. Throughout the internship period the student keeps a logbook of the tasks that the student solves and the knowledge that the student gains. The logbook forms the basis of the internship test, which is a written internship report of minimum 5 and maximum 10 standard pages with an account of the events of the internship period, as well as a reflection on the fulfilment of the student s learning objectives. The internship period concludes when the student hands in their internship test, which is then assessed by the internship counselor by the 7-point grading scale. For more information on the requirements of the report, see paragraph 3.4 about the internship test. 6

23 4. Tests and Exams 4.1. Test: Web Development, Backend-programming ECTS credits: 10 ECTS Compulsory participation requirements for the test: The student must participate in all obligatory study activities for each semester, including participation in the presentation of project work. The student must have handed in and gotten approved all obligatory assignments and study activities for a semester at the latest by the 15 th of May for the spring semester and at the latest by the 15 th of December for the autumn semester. If one or more of the above mentioned compulsory participation requirements is not met, the student is not allowed to participate in the test and one examination attempt has then been used as per paragraph 3.1 of this curriculum. More information on the compulsory participation requirements can be found in the lecture plan of the course. Formal requirements The students are to work in groups and create a group report of minimum 10 and maximum 15 standard pages for a group. A group may consist of up to 4 people. By a written and substantiated application to the dispensation committee an exemption can be made for the creation of a larger group. Formal rules: A standard page is 2400 characters, including spaces and footnotes. The front page, table of contents, models, illustrations, bibliography and appendices are not included in the 2400 characters and does not count towards the maximum amount of pages. Appendices are not included in the grading evaluation. In order to assess the student s individual performances it must be evident from the table of contents which paragraphs each individual student has composed. Learning objectives: The learning objectives of the test are identical to the learning objectives of the mandatory element Web Development, Backend-programming, that can be found in the common part of the curriculum. The exam: The exam is individual and oral and is based on the group s report as well as questions from the syllabus. Each examinee is tested for 30 minutes, the distribution of which is 10 minutes for presentation, 15 minutes for examination and 5 minutes for assessment. Evaluation: One combined grade for each student based on an overall assessment of the report and the oral examination. The exam is assessed internally by the 7-point grade scale. 7

24 4.2. Test: Web Development, Frontend-programming ECTS credits: 10 ECTS Compulsory participation requirements for the test: The student must participate in all obligatory study activities for each semester, including participation in the presentation of project work. The student must have handed in and gotten approved all obligatory assignments and study activities for a semester at the latest by the 15 th of May for the spring semester and at the latest by the 15 th of December for the autumn semester. If one or more of the above mentioned compulsory participation requirements is not met, the student is not allowed to participate in the test and one examination attempt has then been used as per paragraph 3.1 of this curriculum. More information on the compulsory participation requirements can be found in the lecture plan of the course. Formal requirements The students are to work in groups and create a group report of minimum 10 and maximum 15 standard pages for a group. A group may consist of up to 4 people. By a written and substantiated application to the dispensation committee an exemption can be made for the creation of a larger group. Formal rules: A standard page is 2400 characters, including spaces and footnotes. The front page, table of contents, models, illustrations, bibliography and appendices are not included in the 2400 characters and does not count towards the maximum amount of pages. Appendices are not included in the grading evaluation. In order to assess the student s individual performances it must be evident from the table of contents which paragraphs each individual student has composed. Learning objectives: The learning objectives of the test are identical to the learning objectives of the mandatory element Web Development, Frontend-programming, that can be found in the common part of the curriculum. The exam: The exam is individual and oral and is based on the group s report as well as questions from the syllabus. Each examinee is tested for 30 minutes, the distribution of which is 10 minutes for presentation, 15 minutes for examination and 5 minutes for assessment. Evaluation: One combined grade for each student based on an overall assessment of the report and the oral examination. The exam is assessed internally by the 7-point grade scale. 8

25 4.3. Test: Development environments ECTS credits: 10 ECTS Compulsory participation requirements for the test: The student must participate in all obligatory study activities for each semester, including participation in the presentation of project work. The student must have handed in and gotten approved all obligatory assignments and study activities for a semester at the latest by the 15 th of May for the spring semester and at the latest by the 15 th of December for the autumn semester. If one or more of the above mentioned compulsory participation requirements is not met, the student is not allowed to participate in the test and one examination attempt has then been used as per paragraph 3..1 of this curriculum. More information on the compulsory participation requirements can be found in the lecture plan of the course. Formal requirements The students are to work in groups and create a web application and a group report of minimum 10 and maximum 15 standard pages for a group. A group may consist of up to 4 people. By a written and substantiated application to the dispensation committee an exemption can be made for the creation of a larger group. Formal rules: A standard page is 2400 characters, including spaces and footnotes. The front page, table of contents, models, illustrations, bibliography and appendices are not included in the 2400 characters and does not count towards the maximum amount of pages. Appendices are not included in the grading evaluation. In order to assess the student s individual performances it must be evident from the table of contents which paragraphs each individual student has composed. The web application and any code developed by the students must be made available online for the examiners. Learning objectives: The learning objectives of the test are identical to the learning objectives of the mandatory element Development environments, which can be found in the common part of the curriculum. The exam: The exam is individual and oral and is based on the group s web application and report as well as questions from the syllabus. Each examinee is tested for 30 minutes, the distribution of which is 10 minutes for presentation, 15 minutes for examination and 5 minutes for assessment. Evaluation: One combined grade for each student based on an overall assessment of the web application, the report and the oral examination. The exam is assessed externally by the 7-point grade scale. 9

26 4.4. Test: Databases ECTS credits: 10 ECTS Compulsory participation requirements for the test: The student must participate in all obligatory study activities for each semester, including participation in the presentation of project work. The student must have handed in and gotten approved all obligatory assignments and study activities for a semester at the latest by the 15 th of May for the spring semester and at the latest by the 15 th of December for the autumn semester. If one or more of the above mentioned compulsory participation requirements is not met, the student is not allowed to participate in the test and one examination attempt has then been used as per paragraph 3..1 of this curriculum. More information on the compulsory participation requirements can be found in the lecture plan of the course. Learning objectives: The learning objectives of the test are identical to the learning objectives of the mandatory element Databases, which can be found in the common part of the curriculum. The exam: The exam is individual and written and is based on the syllabus. All supplementary materials are allowed. Evaluation: One individual grade by the 7-point grade scale. The exam is assessed internally. 10

27 4.5. Test: Interface Design ECTS credits: 10 ECTS Compulsory participation requirements for the test: The student must participate in all obligatory study activities for each semester, including participation in the presentation of project work. The student must have handed in and gotten approved all obligatory assignments and study activities for a semester at the latest by the 15 th of May for the spring semester and at the latest by the 15 th of December for the autumn semester. If one or more of the above mentioned compulsory participation requirements is not met, the student is not allowed to participate in the test and one examination attempt has then been used as per paragraph 3..1 of this curriculum. More information on the compulsory participation requirements can be found in the lecture plan of the course. Formal requirements The students are to work in groups and create a prototype of a web application and a group report of minimum 10 and maximum 15 standard pages for a group. A group may consist of up to 4 people. By a written and substantiated application to the dispensation committee an exemption can be made for the creation of a larger group. Formal rules: A standard page is 2400 characters, including spaces and footnotes. The front page, table of contents, models, illustrations, bibliography and appendices are not included in the 2400 characters and does not count towards the maximum amount of pages. Appendices are not included in the grading evaluation. In order to assess the student s individual performances it must be evident from the table of contents which paragraphs each individual student has composed. The prototype of the web application must be made available online for the examiners. Learning objectives: The learning objectives of the test are identical to the learning objectives of the mandatory element Development enviroments, which can be found in the common part of the curriculum. The exam: The exam is individual and oral and is based on the group s prototype of a web application and report as well as questions from the syllabus. Each examinee is tested for 30 minutes, the distribution of which is 10 minutes for presentation, 15 minutes for examination and 5 minutes for assessment. Evaluation: One combined grade for each student based on an overall assessment of the prototype of the web application, the report and the oral examination. The exam is assessed internally by the 7-point grade scale. 11

28 4.6. Elective subject exams ECTS credits: In total 20 ECTS Learning objectives: The elective subjects are meant to allow the students to individualize their professional profile through an academic specialization in one or more of the programme s mandatory elements. The elective subjects are planned by the Lillebaelt Academy and are adjusted on a yearly basis. The elective subjects are published in an elective subject catalogue that contains a description of each elective subject and its scope, learning objectives and its form of examination. The exam: The type of test depends on the elective subject and can be found in the elective subject catalogue. Evaluation: The type of evaluation depends on the elective subject and can be found in the elective subject catalogue. 12

29 4.7. Internship exam ECTS credits: 15 ECTS Compulsory participation requirements for the exam: The student must have completed a 3-month internship. The internship report must be handed in before the deadline. If one or more of the above mentioned compulsory participation requirements is not met, the student is not allowed to participate in the exam and one examination attempt has then been used as per paragraph 3.1. of this curriculum. Formal requirements for the internship exam: Throughout the internship period the student keeps a logbook of the tasks that the student solves and the knowledge that the student gains. The logbook forms the basis of the internship test, which is a written internship report of minimum 5 and maximum 10 standard pages with an account of the events of the internship period, as well as a reflection on the fulfilment of the students learning objectives. Formal rules: A standard page is 2400 characters, including spaces and footnotes. The front page, table of contents, models, illustrations, bibliography and appendices are not included in the 2400 characters and does not count towards the maximum amount of pages. Appendices are not included in the grading evaluation. Learning objectives: The learning objectives of the internship exam is identical to the individual learning objectives that the student and the internship counsellor work out prior to the internship, and which are based on the learning objectives for the internship, which can be found in paragraph 6 in the common part of the curriculum. The exam: The exam is individual and written. The internship report is to be handed in at the end of the internship period by arrangement with the student s internship counselor. Evaluation: One individual grade for each student based on an assessment of the report. The exam is assessed internally by the 7-point grade scale. 13

30 4.8. Bachelor degree project ECTS credits: 15 ECTS Bundne forudsætninger for at deltage i prøven: The student must have passed all prior tests and exams of the programme. The bachelor project must be handed in before the deadline. If one or more of the above mentioned compulsory participation requirements is not met, the student is not allowed to participate in the exam and one examination attempt has then been used as per paragraph 3.1 of this curriculum. Formal requirements for the bachelor project: The students are to work in groups and create a project report and if desired a product. The project report may have a maximum of 20 standard pages + 20 standard pages pr. student in the group. A group may consist of up to 4 people. By a written and substantiated application to the dispensation committee an exemption can be made for the creation of a larger group. Formal rules: A standard page is 2400 characters, including spaces and footnotes. The front page, table of contents, models, illustrations, bibliography and appendices are not included in the 2400 characters and does not count towards the maximum amount of pages. Appendices are not included in the grading evaluation. In order to assess the student s individual performances it must be evident from the table of contents which paragraphs each individual student has composed. Learning objectives: For more information on the requirements of the bachelor project as well as its learning objectives see paragraph 7 of the common part of the curriculum. The exam: The exam is an individual oral project exam. First, the group has up to 15 minutes to present the project. Then each member of the group is tested. Each examinee is tested for 35 minutes, the distribution of which is 25 minutes for examination and 10 minutes for assessment. If the exam is passed the student has graduated the programme. Evaluation: One combined grade for each student based on an overall assessment of the project and the oral examination. The exam is assessed externally by the 7-point grade scale. Spelling and writing skills are included in the overall assessment of the exam and is weighted 10 %. 14

31 Students who can document a relevant physical or mental impairment can apply for an exemption from the inclusion of spelling and writing skills in the assessment of the exam. This application must be submitted to the dispensation committee at least four weeks prior to the date of the examination. 5. Credits for educational elements undertaken abroad For information on credit transfer for educational elements undertaken abroad, see paragraph 9.1. in the common part of the curriculum. 6. Credits for elective educational elements Any elective educational element that has been passed is considered to be equivalent to the corresponding educational element offered by other educational institutions offering the Bachelor s Degree Programme in Web development or other educations. The student is to apply for prior approval if they wish to be credited for educational elements that are not included in the Bachelor s Degree Programme in Web development. 7. Language All educational material on the Bachelor s Degree Programme in Web development is in English and all classes may be taught in English. Other than what is stated in the admission act no further knowledge of foreign languages is required Languages in tests and exams All test and exams are to submitted/presented in English. The dispensation committee may grant an exemption from this demand for a student if the examiners allow that a test or exam can be submitted/presented in Danish. 15