Difference between revisions of "IU:TestPage"
Jump to navigation
Jump to search
R.sirgalina (talk | contribs) |
R.sirgalina (talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | = Software Project (Fundamentals to Software Engineering from 2021 check another syllabus) = |
||
| − | = Cross-Cultural Communication for IT-Specialists = |
||
| + | * Course name: Software Project (Fundamentals to Software Engineering from 2021 check another syllabus) |
||
| − | * Course name: Cross-Cultural Communication for IT-Specialists |
||
| − | * Course number: |
+ | * Course number: S20-SP |
== Course Characteristics == |
== Course Characteristics == |
||
=== Key concepts of the class === |
=== Key concepts of the class === |
||
| + | * To understand agile models of interaction design, development, and project management and put those concepts in practice in real software development. |
||
| − | |||
| + | * To get acquainted with processes, technologies, and activities involved eliciting, analyzing, validating, specifying, and managing functional and non-functional requirements of software systems. |
||
| + | * To manage risks and decisions making based on the risk management |
||
| + | * To be able design software, and to write code that sticks to good practices of cohesion, coupling, modularity, reusing, and encapsulation. |
||
| + | * To get familiar with standard reliability techniques such as validation (testing) and verification. |
||
| + | * To gain practical experience with refactoring techniques to improve the quality of existing code. |
||
=== What is the purpose of this course? === |
=== What is the purpose of this course? === |
||
| + | The main objectives of this course are the following: \begin{itemize} \item To understand agile models of interaction design, development, and project management and put those concepts in practice in real software development. \item To get acquainted with processes, technologies, and activities involved eliciting, analyzing, validating, specifying, and managing functional and non-functional requirements of software systems. \item To manage risks and decisions making based on the risk management \item To be able design software, and to write code that sticks to good practices of cohesion, coupling, modularity, reusing, and encapsulation. \item To get familiar with standard reliability techniques such as validation (testing) and verification. \item To gain practical experience with refactoring techniques to improve the quality of existing code. \end{itemize} |
||
| − | === Course objectives based on Bloom’s taxonomy === |
||
| − | |||
| − | ==== - What should a student remember at the end of the course? ==== |
||
| − | By the end of the course, the students should be able to |
||
| − | * key conditions for fruitful communication across cultures; |
||
| − | * stereotypes and prejudice in different cultures; |
||
| − | * non-verbal methods of communication in different cultures; |
||
| − | * cultural taboos in formal/informal conversations; |
||
| − | * strategies of dealing with cross-cultural misunderstandings. |
||
| − | |||
| − | ==== - What should a student be able to understand at the end of the course? ==== |
||
| − | By the end of the course, the students should be able to |
||
| − | * competences necessary for working in cross-cultural environment; |
||
| − | * differences in various cross-cultural dimensions; |
||
| − | * strategies of dealing with cross-cultural misunderstandings; |
||
| − | * general aspects of formal/informal verbal communication in cross-cultural environment. |
||
| − | |||
| − | ==== - What should a student be able to apply at the end of the course? ==== |
||
| − | By the end of the course, the students should be able to |
||
| − | * methods to identify and combat with cultural shock; |
||
| − | * techniques to interpret correctly the cultural values of interlocutors; |
||
| − | * strategies of spelling out non-verbal cultural signs typical of their interlocutors; |
||
| − | * techniques to overcome cultural bias in themselves and their interlocutors/opponents. |
||
| − | * What should a student be able to evaluate at the end of the course? By the |
||
| − | * end of the course, the students should be able to evaluate: |
||
| − | * level of cultural shock they experience (can experience) in different countries; |
||
| − | * their current cross-cultural competence and the way to improve it; |
||
| − | * non-verbal signs and symbols to help understand interlocutors from other cultures; |
||
| − | * cultural norms and values of interlocutors; |
||
| − | * cultural intentions of the parties during negotiations. |
||
| − | === Course evaluation === |
||
| − | {| class="wikitable" |
||
| − | |+ Course grade breakdown |
||
| − | |- |
||
| − | ! type !! points |
||
| − | |- |
||
| − | | In-class work (including exercises) || 85 |
||
| − | |- |
||
| − | | Exams || 15 |
||
| − | |} |
||
| − | |||
| − | === Grades range === |
||
| − | {| class="wikitable" |
||
| − | |+ Course grading range |
||
| − | |- |
||
| − | ! grade !! low !! high |
||
| − | |- |
||
| − | | A. Excellent || 90 || 100 |
||
| − | |- |
||
| − | | B. Good || 80 || 89 |
||
| − | |- |
||
| − | | C. Satisfactory || 70 || 79 |
||
| − | |- |
||
| − | | D. Poor || 0 || 69 |
||
| − | |} |
||
| − | === Resources and reference material === |
||
| − | == Course Sections == |
||
| − | The main sections of the course and approximate hour distribution between them is as follows: |
||
Revision as of 17:16, 9 March 2022
Software Project (Fundamentals to Software Engineering from 2021 check another syllabus)
- Course name: Software Project (Fundamentals to Software Engineering from 2021 check another syllabus)
- Course number: S20-SP
Course Characteristics
Key concepts of the class
- To understand agile models of interaction design, development, and project management and put those concepts in practice in real software development.
- To get acquainted with processes, technologies, and activities involved eliciting, analyzing, validating, specifying, and managing functional and non-functional requirements of software systems.
- To manage risks and decisions making based on the risk management
- To be able design software, and to write code that sticks to good practices of cohesion, coupling, modularity, reusing, and encapsulation.
- To get familiar with standard reliability techniques such as validation (testing) and verification.
- To gain practical experience with refactoring techniques to improve the quality of existing code.
What is the purpose of this course?
The main objectives of this course are the following: \begin{itemize} \item To understand agile models of interaction design, development, and project management and put those concepts in practice in real software development. \item To get acquainted with processes, technologies, and activities involved eliciting, analyzing, validating, specifying, and managing functional and non-functional requirements of software systems. \item To manage risks and decisions making based on the risk management \item To be able design software, and to write code that sticks to good practices of cohesion, coupling, modularity, reusing, and encapsulation. \item To get familiar with standard reliability techniques such as validation (testing) and verification. \item To gain practical experience with refactoring techniques to improve the quality of existing code. \end{itemize}