Software Quality, 6 credits
Programvarukvalitet, 6 hp
TDDE46
Main field of study
Information Technology Computer Science and Engineering Computer ScienceCourse level
Second cycleCourse type
Programme courseExaminer
Kristian SandahlDirector of studies or equivalent
Ola LeiflerEducation components
Preliminary scheduled hours: 36 hRecommended self-study hours: 124 h
Available for exchange students
YesMain field of study
Information Technology, Computer Science and Engineering, Computer ScienceCourse level
Second cycleAdvancement level
A1NCourse offered for
- Computer Science and Engineering, M Sc in Engineering
- Industrial Engineering and Management - International, M Sc in Engineering
- Industrial Engineering and Management, M Sc in Engineering
- Information Technology, M Sc in Engineering
- Computer Science and Software Engineering, M Sc in Engineering
Prerequisites
Software engineering.
Project-based course in computer science or information technology
Skills in programming in multiple languages.
Knowledge of discrete mathematics and mathematical statistics
Intended learning outcomes
After completing the course the student should be able to:
- analyze the most common quality factors of software
- design models of how quality factors in software can be measured
- apply tools to improve product quality,
- apply a description language of processes
- analyze processes in a programming project
- apply methods and tools to improve processes,
- assess the product quality of a programming project
- assess the process quality of a programming project
- integrate quality evaluations in an ongoing programming project
Course content
- Metrics for product, process and resources
- The Goal-Question-Metric method
- Tools for measurement, verification and fault detection
- The Essence-standard for describing and working with software development practices
- Quality assurance methods
- Evaluation of an ongoing project
- Choaching of members of an ongoing project
- Write a quality report
Teaching and working methods
Theory is given through lectures.
Laboratory work on tools.
Students are organized into groups, each with responsibility for evaluating and improving quality and quality work with an ongoing student project in the lower years. The group will interact throughout the semester with students from lower years. In a number of seminars the groups share experience and make action plans. Theoretical knowledge is demonstrated by the students in the seminars. The mission can be likened to a consultancy work and ends with a report that participants in the lower year may have as a basis for their bachelor works. Each report contain a common part and an individual investigation.
Examination
PRA1 | Project | 4 credits | U, 3, 4, 5 |
LAB1 | Computer lab assignments | 2 credits | U, G |
Project work (4HP) requires coaching of students in TDDD96, participation in 80% of seminars and an approved report. Well-performed seminars and individual analyses can award a higher grade
Grades
Four-grade scale, LiU, U, 3, 4, 5Course literature
Announced on the course web pages
Other information
Supplementary courses
It is an advantage to read the course Software Architectures at the same time as this course.
About teaching and examination language
The teaching language is presented in the Overview tab for each course. The examination language relates to the teaching language as follows:
- If teaching language is Swedish, the course as a whole or in large parts, is taught in Swedish. Please note that although teaching language is Swedish, parts of the course could be given in English. Examination language is Swedish.
- If teaching language is Swedish/English, the course as a whole will be taught in English if students without prior knowledge of the Swedish language participate. Examination language is Swedish or English (depending on teaching language).
- If teaching language is English, the course as a whole is taught in English. Examination language is English.
Other
The course is conducted in a manner where both men's and women's experience and knowledge are made visible and developed.
The planning and implementation of a course should correspond to the course syllabus. The course evaluation should therefore be conducted with the course syllabus as a starting point.
Department
Institutionen för datavetenskapDirector of Studies or equivalent
Ola LeiflerExaminer
Kristian SandahlEducation components
Preliminary scheduled hours: 36 hRecommended self-study hours: 124 h
Course literature
Other
Code | Name | Scope | Grading scale |
---|---|---|---|
PRA1 | Project | 4 credits | U, 3, 4, 5 |
LAB1 | Computer lab assignments | 2 credits | U, G |
Project work (4HP) requires coaching of students in TDDD96, participation in 80% of seminars and an approved report. Well-performed seminars and individual analyses can award a higher grade
Other
Note: The course matrix might contain more information in Swedish.
I | U | A | Modules | Comment | ||
---|---|---|---|---|---|---|
1. DISCIPLINARY KNOWLEDGE AND REASONING | ||||||
1.1 Knowledge of underlying mathematics and science (G1X level) |
|
|
X
|
Basic statistics |
||
1.2 Fundamental engineering knowledge (G1X level) |
|
|
X
|
Software engineering proficiency, ability to work in groups in Projects. |
||
1.3 Further knowledge, methods, and tools in one or several subjects in engineering or natural science (G2X level) |
|
|
|
Methods and tools for software quality |
||
1.4 Advanced knowledge, methods, and tools in one or several subjects in engineering or natural sciences (A1X level) |
|
|
|
|||
1.5 Insight into current research and development work |
|
|
|
|||
2. PERSONAL AND PROFESSIONAL SKILLS AND ATTRIBUTES | ||||||
2.1 Analytical reasoning and problem solving |
|
X
|
X
|
PRA1
|
Use earlier skills in project courses |
|
2.2 Experimentation, investigation, and knowledge discovery |
|
X
|
X
|
PRA1
|
Assessment of quality in existing projects |
|
2.3 System thinking |
X
|
|
|
Software engineering organized as a system |
||
2.4 Attitudes, thought, and learning |
|
X
|
X
|
PRA1
|
Coaching of students in bachelor projects |
|
2.5 Ethics, equity, and other responsibilities |
|
|
X
|
PRA1
|
Cooperation necessary for the coaching part |
|
3. INTERPERSONAL SKILLS: TEAMWORK AND COMMUNICATION | ||||||
3.1 Teamwork |
|
|
X
|
PRA1
|
Cooperation in project groups |
|
3.2 Communications |
|
|
X
|
PRA1
|
Communication with students in the bachelor course |
|
3.3 Communication in foreign languages |
|
|
X
|
English is the default course language |
||
4. CONCEIVING, DESIGNING, IMPLEMENTING AND OPERATING SYSTEMS IN THE ENTERPRISE, SOCIETAL AND ENVIRONMENTAL CONTEXT | ||||||
4.1 External, societal, and environmental context |
|
X
|
|
PRA1
|
Economic sustainability with product quality |
|
4.2 Enterprise and business context |
X
|
|
|
|||
4.3 Conceiving, system engineering and management |
|
|
|
|||
4.4 Designing |
|
X
|
X
|
PRA1
|
quality processes in software development |
|
4.5 Implementing |
|
|
|
|||
4.6 Operating |
|
|
|
|||
5. PLANNING, EXECUTION AND PRESENTATION OF RESEARCH DEVELOPMENT PROJECTS WITH RESPECT TO SCIENTIFIC AND SOCIETAL NEEDS AND REQUIREMENTS | ||||||
5.1 Societal conditions, including economic, social, and ecological aspects of sustainable development for knowledge development |
|
|
|
|||
5.2 Economic conditions for knowledge development |
|
|
|
|||
5.3 Identification of needs, structuring and planning of research or development projects |
|
|
X
|
PRA1
|
||
5.4 Execution of research or development projects |
|
X
|
|
PRA1
|
||
5.5 Presentation and evaluation of research or development projects |
|
X
|
|
PRA1
|
This tab contains public material from the course room in Lisam. The information published here is not legally binding, such material can be found under the other tabs on this page.
There are no files available for this course.