Software Engineering is the systematic and engineered development of software in
all its life cycle. — # Rules 1. Keep related to software engineering 1. Keep
comments on-topic of the post 1. Try to post free/open access content 1. Try to
post content from reliable sources (ACM, IEEE, SEI, NN/G, …) 1. Be genuinely
respectful, kind, helpful; act in and assume good faith 1. No discrimination 1.
No personal attacks, no personal questions 1. No attention stealing
[https://en.wikipedia.org/wiki/Attention_economy]: no ads, spam, influencers
influencing, memes, trolling, emotional manipulation/advertising (e.g.
engagement through enragement or other negative emotions), jokes that dissipate
the focus of the topic, … — # Resources - Guide to the Software Engineering Body
of Knowledge (SWEBOK) by IEEE Computer Society - SWEBOK V4 PDF
[https://waseda.app.box.com/v/ieee-cs-swebok] - SWEBOK V4 Review
- SWEBOK V3 PDF
SWEBOK V3 Wiki [http://swebokwiki.org/Main_Page] - ISO/IEC - ISO/IEC JTC 1/SC 7
Software and systems engineering [https://www.iso.org/committee/45086.html] -
Standards by ISO/IEC JTC 1/SC 7
[https://www.iso.org/committee/45086/x/catalogue/p/1/u/1/w/0/d/0] - ISO ICS 35
Information technology [https://www.iso.org/ics/35/x/] - ISO ICS 35.080 Software
[https://www.iso.org/ics/35.080/x/] - Free licensed resources - A Beginner’s
Guide to Finding User Needs [https://jdittrich.github.io/userNeedResearchBook/]
We post and discuss software engineering related information: be it programming/construction, UX/UI, software architecture, DevSecOps, software economics, research, management, requirements, AI, … It is meant as a serious, focused community that strives for sharing content from reliable sources, and free/open access as well.