|
1 |
Discipline name |
Applied systems analysis |
|
2 |
Year of study, |
3, |
|
3 |
Semester of study |
6 |
|
4 |
Number of credits |
2 |
|
5 |
Lecturer |
Perez Chernov Alex Huanovich |
|
6 |
Study objectives |
To give students the basic principles of starting-up projects, to acquaint them with the general architecture of building highly loaded services, as well as with typical architectural and business documents.
In particular – to familiarize the trainees with the requirements and tasks arising at various stages of the project related to information technology (communication with stakeholders, analysis of values, work with requirements, software design, technical consulting); – to familiarize the trainees with the requirements for the practical skills of such roles as analyst, consultant, architect, project manager, within the framework of information projects and solving the corresponding technical and business problems; – familiarize the trainees with some tools used for the tasks of analysis and project initiation, modeling of architecture and business processes.
As a result of the study, the student must know: – the most important concepts of system engineering, the main artifacts and processes of software development; – Typical approaches, methods and notations used to analyze business processes and values among stakeholders, negotiation, software design; – modern approaches to designing highly loaded Internet services;
be able to: – use system thinking at different stages of project management; – to be guided in modern software development methodologies; – design the architecture of corporate services; own: – methods of system analysis, psychological and leadership skills to support the process of identifying requirements, implementing effective communication during negotiations, team building, creative tasks, risk assessment and forecasting. |
|
7 |
Prerequisites |
|
|
8 |
Discipline contents |
Application of highly loaded technologies and deployment tools, analysis, creation and evaluation of business projects |
|
9 |
Recommended readings |
1. Фаулер М. Архитектура корпоративных программных приложений, Вильямс, 2014. 2. У. Детмер. Теория ограничений Голдратта. Системный подход к непрерывному совершенствованию, АНД Проджект, 2007 3. Грегор Хоп, Бобби Вульф, Шаблоны интеграции корпоративных приложений, Вильямс, 2006. 4. Apache Camel, URL: http://camel.apache.org/ 5. Т.ДеМарко, Т.Листер. Вальсируя с Медведями: управление рисками в проектах по разработке программного обеспечения, Изд. Компания pmOffice, 2005 6. А.И. Ильин, Планирование на предприятии, Мн. Новое знание, 2001 7. Ф. Брукс, Мифический человеко-месяц или Как создаются программные системы, Символ-Плюс, 2007 8. Х. Книберг, Scrum и XP: заметки с передовой, 2011. 9. ArchimateTool, URL: https://www.archimatetool.com/ 10. Левенчук А., Системноинженерное мышление, URL: http://techinvestlab.ru/files/systems_engineering_thinking/systems_engineering_thinking_2015.pdf 11. HighScalability, URL: http://highscalability.com 12. Twitter Open Source, URL: https://twitter.github.io 13. Apache Thrift, URL: https://thrift.apache.org 14. Swagger, URL: https://swagger.io Apache Cassandra, DataStax, URL: https://www.datastax.com |
|
10 |
Format |
Interactive, verbal, visual, problematic |
|
11 |
Teaching languages |
Russian |
|
12 |
Forms of assessment |
– testing; – verification of laboratory work; – verification of the enterprise architecture, database schemas and common interfaces between the components of the system, verification of the business model of the project; – writing essays; – Oral statements in the framework of project protection. |
|
13 |
Grading |
Credit |