News for hackers. Stuff that matters.
Re:Software Engineering Body of Knowledge by veltas on Thursday April 22, 2021 @08:36AM (#26902024)
Not attacking this association, but just wanted to say I really dislike the term "body of knowledge".

Areas of knowledge are certainly some kind of 'body', but the term always sounds to me like something you just keep adding more stuff onto the outside as you go, like a big snowball of ideas. And knowledge can become defunct, irrelevant, or disproven over time.

And there's something about the way it tries to sound almost authoritative, without claiming to be scientific.

Re:Software Engineering Body of Knowledge by ubermonkey on Thursday April 22, 2021 @10:42AM (#26903303)
I suspect the inspiration for the title is the very well regarded "Project Management Body of Knowledge" document maintained/published by the PMI.

People in the industry refer to the PMBOK ("Pimbock") pretty frequently. There are lots of people in big-time project management that disdain aspects of the PMI (including and especially the PMP certification, which is often re-named as "pretty much pointless"), but the PMBOK is a valuable document -- ESPECIALLY for people new to the field.

We could do worse, in software, than to emulate that particular success.

Re:Software Engineering Body of Knowledge by ThrowawayR2 on Thursday April 22, 2021 @04:17PM (#26907638)
> "I suspect the inspiration for the title is the very well regarded "Project Management Body of Knowledge" document maintained/published by the PMI."

While that's not impossible, it must be noted other STEM organizations that predate the PMI have their own "body of knowledge" definitions, for example:

- https://www.nspe.org/resources/licensure/resources/professio...

- https://www.asce.org/civil_engineering_body_of_knowledge/

- https://www.iise.org/details.aspx?id=43631

Re:Software Engineering Body of Knowledge by jimmySixDOF on Friday April 23, 2021 @03:41AM (#26912116)
The PMBOK is in it's 6th Edition with a 7th expected this year. It is also a 756 page document at the moment.

I look forward to seeing the SWEBOK also improve over time.

Also, I'm not sure why some of the comments fail to acknowledge the benefit of having a collection of best practices intended to be tailored for each individual use case. That's what the PMBOK is and how it is used when used properly.

Re:Software Engineering Body of Knowledge by marcosdumay on Thursday April 22, 2021 @11:17AM (#26903698)
The PMBOK is a very good source for your vocabulary searches. But, especially for people new to the field, it's an incredibly harmful document. And the harm is entirely caused by the "it misleadingly looks authoritative while it's not and really shouldn't be" issue the GP stated.
Re:Software Engineering Body of Knowledge by ubermonkey on Thursday April 22, 2021 @02:07PM (#26905896)
I'm going to guess you haven't spent much time in the PM world if you think the PMBOK is harmful to new people instead of educational.
Re:Software Engineering Body of Knowledge by marcosdumay on Thursday April 22, 2021 @04:10PM (#26907570)
Oh, yes, I've spent enough time in the PM world to get tired of people justifying their procedures by claiming the PMBOK says it's the correct set of them (the PMBOK explicitly says it's not prescriptive, but it misleads people new people into thinking it is).
Re:Software Engineering Body of Knowledge by jtdev on Thursday April 22, 2021 @02:14PM (#26905998)
If nothing else, the PMBOK is valuable for PMs purely as a reference to the poisonous bullshit that is contained within it? Somewhat like the value of knowing about flat earth hypotheses and believers.
Re:Software Engineering Body of Knowledge by r00fus on Thursday April 22, 2021 @06:46PM (#26909036)
Got an example where PMBOK led someone astray?
Re:Software Engineering Body of Knowledge by crispyambulance on Thursday April 22, 2021 @11:18AM (#26903713)
> We could do worse, in software, than to emulate that particular success.

Perhaps, but couldn't we could do better instead?

There's already more than enough project management in software teams. Do we also have to emulate the all the turgid rules and mindless checklists that PM's use?

I suspect this is yet another attempt at forcing software engineering workflows into something that's more compatible with PM mentality. Or possibly to commoditize the practice of software engineering. IMHO, it's just a different kind of crack for some management consultants to offer to their c-suite clients.

Re:Software Engineering Body of Knowledge by ubermonkey on Thursday April 22, 2021 @02:07PM (#26905886)
"There's already more than enough project management in software teams. "

Given how poorly most software teams are run, I do not think this is demonstrably true.

"Do we also have to emulate the all the turgid rules and mindless checklists that PM's use?"

Programmers have a terrible reputation for refusing to entertain anything outside the process of programming. This kind of comment is emblematic of that mindset.

Re:Software Engineering Body of Knowledge by crispyambulance on Thursday April 22, 2021 @03:18PM (#26906957)
> Given how poorly most software teams are run, I do not think this is demonstrably true.

OK, but one does not "fix" organizational problems by adding more layers of PM.

Re:Software Engineering Body of Knowledge by davidivadavid on Thursday April 22, 2021 @09:35PM (#26910128)
I think many software engineers could get benefits out of learning some project management skills, but I must say I'm also skeptical of the benefits they'd get from more theoretical knowledge of project management in themselves.

But I also have an immediate reaction to the term "body of knowledge" in the context of PM, which is to reinterpret it as "cargo cult." Hopefully they have something different in mind here, but that's often what it ends up as in practice.

Re:Software Engineering Body of Knowledge by TomOwens on Thursday April 22, 2021 @09:00AM (#26902238)
I think this is why the PDF is actually the "Guide to the Software Engineering Body of Knowledge". It's not a representation of the complete body of knowledge itself, but extracting key concepts and terms and provides pointers to things that are most relevant. If things are irrelevant or disproven over time, the guide to the body of knowledge would remove those terms, concepts, or references and point to something else.
Re:Software Engineering Body of Knowledge by LegitShady on Thursday April 22, 2021 @10:35AM (#26903221)
It actually apes the Project Management Institute's terminology exactly. The PMBOK guide and the PMBOK are the same thing (as far as I know). This takes exactly the same approach. The guide is the entire book, it just has a funny name as if there was another larger book that this is a guide to. There isn't.

https://www.pmi.org/pmbok-guide-standards/foundational/pmbok

Re:Software Engineering Body of Knowledge by Silhouette on Thursday April 22, 2021 @09:35AM (#26902544)
Unfortunately, where it does present "key concepts and terms", that presentation is often flawed. I think it would be more useful as a guide to the field of software engineering if that's the only thing it tried to be, setting out a well-considered structure but then referring to other reliable sources for details. It could be a lot shorter and more accessible, and it wouldn't keep saying things that are misleading or incorrect.
Re:Software Engineering Body of Knowledge by Cullinet on Thursday April 22, 2021 @11:34AM (#26903922)
I'm thinking of a distinction between eg body of knowledge to mean the arrangement of muscle, skeleton and organs, versus a corpus of knowledge that you presume to be a representative collection of body parts making up a adequate whole.
Re:Software Engineering Body of Knowledge by kper on Thursday April 22, 2021 @11:59AM (#26904268)
I think it comes from the latin word 'corpus', which also means body. This wording came from the romans.

https://en.wikipedia.org/wiki/Corpus_Juris_Civilis

Re:Software Engineering Body of Knowledge by veltas on Thursday April 22, 2021 @01:17PM (#26905253)
That actually makes me feel better, and is quite interesting, thank you.
Re:Software Engineering Body of Knowledge by Cthulhu_ on Thursday April 22, 2021 @10:04AM (#26902867)
> knowledge can become defunct, irrelevant, or disproven over time.

True, but at the same time, old software is still around; if you can look up the terms and practices from 'back when' using an overview like this, or at the very least have enough broad knowledge to recognize what it is, you're already ahead.

I've only skimmed it (the PDF is linked elsewhere), but it looks like just the resource for a professor of software engineering and -design to have and become acquainted with - know a little about a lot of things, then go from there.

Re:Software Engineering Body of Knowledge by benjaminjosephw on Thursday April 22, 2021 @08:49AM (#26902134)
This sounds like a fair description of how software engineering and computer science has progressed over the years so maybe it's a fair term ;)
Re:Software Engineering Body of Knowledge by sas224dbm on Thursday April 22, 2021 @09:29AM (#26902488)
Maybe. I've worked in the defense industry in and around software as a developer, designer etc for around 30 years. There's some good detail in there, but i think it's a little dated. Try looking for any material on REST in there. If it got refreshed somewhat i'd have it on my virtual bookshelf for sure.
Re:Software Engineering Body of Knowledge by twangist on Thursday April 22, 2021 @09:40PM (#26910159)
The title should also drop the "the", which makes you brace for a document by a non-native speaker.