Inhalt
[ 526SENGSENV14 ] VL Software Engineering
|
|
|
|
| (*) Unfortunately this information is not available in english. |
 |
| Workload |
Education level |
Study areas |
Responsible person |
Hours per week |
Coordinating university |
| 3 ECTS |
B2 - Bachelor's programme 2. year |
Business Informatics |
Reinhold Plösch |
2 hpw |
Johannes Kepler University Linz |
|
|
|
| Detailed information |
| Pre-requisites |
(*)Erwartete Vorkenntnisse: Einführung in die Wirtschaftsinformatik und Algorithmen und Datenstrukturen, Grundlagen der Informatik, Mathematik und Logik und Formale Grundlagen
|
| Original study plan |
Bachelor's programme Business Informatics 2025W |
| Learning Outcomes |
Competences |
| They are familiar with the state of the art in software engineering and can apply this knowledge in the initiation, execution, monitoring, and management of software projects.
|
|
| Skills |
Knowledge |
- LO2: Students can systematically select software development models based on defined project characteristics (K3).
- LO3: They can write requirements specifications (stakeholder requirements) (K4).
- LO4: They can build exploratory user interface prototypes (K3).
- LO5: They can design and implement systems in a data-oriented manner using context-free and attributed grammars (K3).
- LO6: They can solve design problems using object-oriented design principles and design patterns (K4).
- LO7: They develop object-oriented solutions of subsystems based on an object-oriented design (K3).
- LO8: They can apply scenario-based black-box and white-box testing methods (K3).
|
LO1: Fundamental concepts of software engineering; classical process models; prototypes and prototyping; agile process models in general and Scrum in particular; selected agile practices; understanding and specifying requirements; user stories and acceptance criteria; software quality (concepts, quality models); constructive and analytical measures for quality improvement; data-oriented decomposition (context-free grammars, attributed grammars); principles of object-oriented programming; object-oriented design patterns and design principles; implementation of software systems (programming paradigms, programming guidelines, version control, documentation); testing of software systems (unit tests, integration tests, system testing).
|
|
| Criteria for evaluation |
Written final exam (theory questions, small practical examples from the areas of specification, prototyping, design, implementation, and testing).
|
| Methods |
- Independent study of the content by students (videos, sample examples)
- In-person sessions for reflection and deepening
- Self-assessments for progress evaluation
|
| Language |
German |
| Study material |
Basic literature
- Ian Sommerville: Software Engineering, 9th revised edition, Addison-Wesley Longman, 2010
- Bertrand Meyer: Object-Oriented Software Construction, 2nd edition, Prentice Hall, 1998
- Erich Gamma, Richard Helm, Richard Johnson, John Vlissides: Design Patterns – Elements of Reusable Object-Oriented Software. AddisonWesley, 1995
- Kenneth S. Rubin: Essential Scrum: A Practical Guide to the Most Popular Agile Process, Addison-Wesely, 2012
- V-Model XT – see http://www.v-modell.iabg.de/ (englisch version is available)
- Dan Pilone: UML 2.0 in a Nutshell, O’Reilly, 2005
Supplementary literature will be announced at the begin of the semester.
|
| Changing subject? |
No |
| Further information |
VL and UE Software Engineering form an inseparable didactic unit. The learning outcomes described are achieved through the interaction of both.
|
| Earlier variants |
They also cover the requirements of the curriculum (from - to)
2WSEV: VL Software Engineering (2002W-2014S)
|
|
|
|
| On-site course |
| Maximum number of participants |
200 |
| Assignment procedure |
Assignment according to priority |
|
|
|
