Software design 2 (EN)2018/2019
- Content and learning outcomes
This course is a continuation of the course Software Design 1. You will work with development of a system from an initial idea to a running program.Knowledge
The road to this is object-oriented analysis and design including modelling of system requirements with use case descriptions and realization of these in the form of relevant UML diagrams. We continue with system architecture and you will work with different design patterns.
The course is completed with a multidisciplinary project involving all 2nd semester subjects. The result is a running system documented in a project report.
The student has acquired knowledge ofSkills
1. the significance of experiments as part of or a supplement to the system development method
The student has acquired the skills needed to
1. model and design IT systems
2. use an appropriate software architecture
3. document and communicate product and process, and ensure traceability
4. quality assure product and process
5. use appropriate design patterns
6. involve users
7. work systematically on a project based on a selected system development method
The student has acquired the competencies needed to
1. participate competently in a development project
- Type of instruction
The teaching method is a mixture of classroom teaching, exercises and project work.
The learning outcomes of the exam are identical with the learning outcomes of the subject(s)/modul(es)Prerequisites for access to the examinationRequirements for taking the exam
To take the exam, the following requirements apply:
There are seven mandatory activities linked to the exam, which are described in the relevant
semester/class room on Fronter. Documentation of mandatory activities must be
submitted via Fronter. Mandatory activities are distributed as follows:
Core area Programming 2
Core area System Development 2
Core area Business 1
Core area Programming 1
Core area Technology 1
Students who fail to fulfil one or more study activities or to submit the first-year project, which constitutes the written part of the exam, in due time cannot participate in the exam and will have used one exam attempt.Exam in one or more subjectsType of examCombined written and oral examinationFormal requirementsStudents must submit a project report and a product.
The project report, which constitutes the written part of the exam, must as a minimum contain
• Front page, including title, name and date of birth, class and date
• Table of contents
• Problem statement or question
• Main section
• Bibliography (including all sources referenced in the project)
• Appendix (only appendices central to the report are to be included)
• Enclose source code and, if relevant, specify the path to the version control server
where the source code and executable product code can be retrieved
• All pages must be numbered
The written project must be at least 30 standard pages and cannot exceed 40 standard pages for one student. For each additional student, the total number of pages increases according to the table below:
1 student - min. 30 og maks. 40 pages
2 students - min. 35 og maks. 50 pages
3 students - min. 40 og maks. 55 pages
4 students - min. 45 og maks. 60 pages
Front page, table of contents, bibliography and appendices are not included in the required
number of pages. Appendices will not be assessed.
A standard page is 2,400 characters, including spaces and footnotes. Front page, table of contents,
bibliography and appendices are not included. Appendices will not be assessed.
Each figure or diagram is equivalent to 800 characters.Individual exam or group examGroup, 2-4 max participantsExam languagesEnglishDurationThe project must be presented by the project group – 10 minutes per student; however, a
maximum of 30 minutes in total. The group members are then examined individually – 30
minutes per examinee, including grading.Type of evaluation7-point grading scaleExaminersExternal censureExam criteriaThe assessment criteria for the exam correspond to the learning objectives for the compulsory programme element: Programming, System Development, Technology and Business
The learning objectives are set out in the common part of the curriculum.Deadline for submissionThe exam takes place at the end of the second semester. Further information on time and
place as well as submission of the written group project is available on Fronter.
In the subject Software design 2 (EN) you will receive 48 hours of instruction, which corresponds to 64 lessons (1 lesson = 45 min.) and 35% of your total workload for the subject.
The teaching primarily consists of the following activities: classroom teaching.
The preparation primarily consists of the following activities: reading your own notes, reading the curriculum.
Read about KEAs Study Activity Model
*KEA can deviate from the number of hours if this is justified by special circumstances