SSD 1/16: README vs. IEEE [software design crash course]

preview_player
Показать описание
This lecture and the other 15 in this series were given to 3rd year BSc students of Innopolis University (Russia) in 2021.

I’m very sorry for the quality of sound in this lecture. Other lectures have better quality.

0:00 Disclaimer
9:55 The structure of the lecture
14:23 Software vs. Interiors
19:55 SDD at IEEE 1016
57:01 SAD at RUP
59:06 TS at CMMI
1:00:33 SWEBOK
1:02:45 README
1:07:47 Books, Venues, Call-to-Action
Рекомендации по теме
Комментарии
Автор

Yegor, thank you for sharing these videos.
Can't wait for left releases 🤟

daedaliusX
Автор

Огромное спасибо за расшаренные лекции, Егор - молодчина, в прекрасной форме, успехов тебе трудяга!

AlexandrChervinskiy
Автор

amazingly interesting lectures and the way of getting bold overview of software design

asanakimov
Автор

Nice! I really enjoyed the lecture. Should we expect the rest of the lectures to also be published?

andreigl
Автор

Could you please publish the presentation?

nikolai.x
Автор

Could you please fix the sound for the next lectures

pin
Автор

Simon Brown by introducing structurizr tried to solve the problem: "How to synchronize an SSD with the source code". Not ideal but some step ahead.

deniszhukovsky
Автор

Which type of documentation do you use right now in your projects? Is README quite enough now for most projects? Or in some projects (which one?) you need all this stuff with "RUP templates", maybe you have some examples in Open Source projects? Thank you.

volodya-lombrozo
Автор

Thank you for your interesting lecture. If I have an MVP project and only a few weeks and, for example, two programmers, including me as an architect. Should I spend time writing such detailed documentation (with Glossary, Languages, Stakeholders, Concerns, Viewpoints, Elements, Rationale)? This seems to me an irrational waste of money and time.

volodya-lombrozo
Автор

Please repeat the question unless the questioner has a microphone

ChrisAthanas