Study Guide

Objective

After completing the course, student
- is able to apply a formal production method in a software project
- recognizes vital operations in version management
- is familiar with the focal tools of project management software (tasks, scheduling, resourcing, follow-up)
- is able to devise a feasibility study
- is able to make a risk management plan and control risks in a software project
- is able to apply UML in requirements engineering and technical design
- is able to plan and implement process metrics (dashboards, key performance indicators) and is able to control changing requirements
- is familiar with test-driven development
- realizes the importance of testing in software quality assurance
- is able to apply focal testing methods in different phases of a software production process
- is able to make a test plan and put it into practice
- understands the role of architecture in software engineering
- is able to model architectures
- is familiar with software architecture models

Content

UML
Version management
Project Management software
Testing
Iterative (agile) methods
Project monitoring and control – measuring software process
Architectural design
Analysis
Project: external customer/own subject of the project group

Materials

To be announced at the start of the course.

Evaluation scale

H-5

Qualifications

Software Engineering I

Objective

After completing the course, student
- is able to apply a formal production method in a software project
- recognizes vital operations in version management
- is familiar with the focal tools of project management software (tasks, scheduling, resourcing, follow-up)
- is able to devise a feasibility study
- is able to make a risk management plan and control risks in a software project
- is able to apply UML in requirements engineering and technical design
- is able to plan and implement process metrics (dashboards, key performance indicators) and is able to control changing requirements
- is familiar with test-driven development
- realizes the importance of testing in software quality assurance
- is able to apply focal testing methods in different phases of a software production process
- is able to make a test plan and put it into practice
- understands the role of architecture in software engineering
- is able to model architectures
- is familiar with software architecture models

Content

UML
Version management
Project Management software
Testing
Iterative (agile) methods
Project monitoring and control – measuring software process
Architectural design
Analysis
Project: external customer/own subject of the project group

Materials

To be announced at the start of the course.

Evaluation scale

H-5

Qualifications

Software Engineering I

Objective

After completing the course, student
- is able to apply a formal production method in a software project
- recognizes vital operations in version management
- is familiar with the focal tools of project management software (tasks, scheduling, resourcing, follow-up)
- is able to devise a feasibility study
- is able to make a risk management plan and control risks in a software project
- is able to apply UML in requirements engineering and technical design
- is able to plan and implement process metrics (dashboards, key performance indicators) and is able to control changing requirements
- is familiar with test-driven development
- realizes the importance of testing in software quality assurance
- is able to apply focal testing methods in different phases of a software production process
- is able to make a test plan and put it into practice
- understands the role of architecture in software engineering
- is able to model architectures
- is familiar with software architecture models

Content

UML
Version management
Project Management software
Testing
Iterative (agile) methods
Project monitoring and control – measuring software process
Architectural design
Analysis
Project: external customer/own subject of the project group

Evaluation scale

H-5

Qualifications

Software Engineering I

Objective

After completing the course, student
- is able to apply a formal production method in a software project
- recognizes vital operations in version management
- is familiar with the focal tools of project management software (tasks, scheduling, resourcing, follow-up)
- is able to devise a feasibility study
- is able to make a risk management plan and control risks in a software project
- is able to apply UML in requirements engineering and technical design
- is able to plan and implement process metrics (dashboards, key performance indicators) and is able to control changing requirements
- is familiar with test-driven development
- realizes the importance of testing in software quality assurance
- is able to apply focal testing methods in different phases of a software production process
- is able to make a test plan and put it into practice
- understands the role of architecture in software engineering
- is able to model architectures
- is familiar with software architecture models

Content

UML
Version management
Project Management software
Testing
Iterative (agile) methods
Project monitoring and control – measuring software process
Architectural design
Analysis
Project: external customer/own subject of the project group

Evaluation scale

H-5

Qualifications

Software Engineering I