|
Lecturer(s)
|
-
Šilhavý Petr, doc. Ing. Ph.D.
-
Prokopová Zdenka, doc. Ing. CSc.
-
Šilhavý Radek, doc. Ing. Ph.D.
|
|
Course content
|
- Project topic selection, project requirements. - Project goal definition, feasibility study. - Software processes. Software process Models. - Requirement engineering. - Software modelling - Unified Modelling Language - Use Case Models. - Software effort estimation, estimation methods. - Architecture design, development plan. - User interface design, prototyping - Software implementation (coding), project consultation.
|
|
Learning activities and teaching methods
|
|
Dialogic (Discussion, conversation, brainstorming), Demonstration, Simple experiments, Teamwork
|
| learning outcomes |
|---|
| Knowledge |
|---|
| The student has knowledge about software engineering. The student is able to implement object modelling to real software project. The student can interpret unified modelling language diagrams. The student takes advantage of unified modelling language for software design. The student knows how to analyse and design software products. The student is well informed about software processes and about their models. The student is able to document software project. |
| The student has knowledge about software engineering. The student is able to implement object modelling to real software project. The student can interpret unified modelling language diagrams. The student takes advantage of unified modelling language for software design. The student knows how to analyse and design software products. The student is well informed about software processes and about their models. The student is able to document software project. |
| Skills |
|---|
| The skill to effectively create various UML diagrams for visualizing software systems. |
| The skill to effectively create various UML diagrams for visualizing software systems. |
| The ability to interpret UML diagrams is crucial for analyzing software designs. |
| The ability to interpret UML diagrams is crucial for analyzing software designs. |
| The knowledge to modify and update UML diagrams in response to changing requirements. |
| The knowledge to modify and update UML diagrams in response to changing requirements. |
| Applying UML for modelling specific, real-world situations in software engineering. |
| Applying UML for modelling specific, real-world situations in software engineering. |
| The ability to work in the software project team. |
| The ability to work in the software project team. |
| teaching methods |
|---|
| Knowledge |
|---|
| Demonstration |
| Dialogic (Discussion, conversation, brainstorming) |
| Dialogic (Discussion, conversation, brainstorming) |
| Simple experiments |
| Simple experiments |
| Demonstration |
| Teamwork |
| Teamwork |
| assessment methods |
|---|
| Qualifying examination |
| Analysis of works made by the student (Technical products) |
| Analysis of works made by the student (Technical products) |
| Qualifying examination |
|
Recommended literature
|
-
Elektronické studijní opory.
-
Arlow, Jim. UML a unifikovaný proces vývoje aplikací : průvodce analýzou a návrhem objektově orientovaného softwaru. Vyd. 1. Brno : Computer Press, 2003. ISBN 807226947X.
-
Pilone, Dan. UML 2.0 in a nutshell Sebastopol, Calif. O'Reilly, 2005.
-
Pilone, Dan. UML 2.0 pocket reference Beijing. O'Reilly, 2006.
|