[SystemSafety] Educating the Postmodern Systems Engineer

[Derek M Jones]

Les,

>  From the SWEBOK Foreword:
> "Its objectives include the provision of guidance for learners, researchers,
> and practitioners to identify and share a common understanding of “generally
> accepted knowledge” in software engineering, defining the boundary between
> software engineering and related disciplines, and providing a foundation for
> certifications and educational curricula."
> 
> Q1: Do you feel this is a righteous mission?

I don't know about righteous, but the objectives are laudable.

> Q2: If yes how do you think the SWEBOK could be improved?

It cannot be more than the current list of talking points
because there is no body of knowledge, apart from snippets
here and there.

The current role of SWEBOK is to give box tickers a warm
fuzzy feeling that a body of knowledge exists.  When people
suggest that the answer to my question(s) can be found in
SWEBOK, I ask them if they have ever read any of it.
Invariably they have not, but they are ever so sure that
it contains the answers to my question.

> Les
> 
>> Steve,
>>
>>   > First, I am pulling the “description” of Software Engineering from
> the soon-to-be-released version 4 of the “Guide to
>> the Software Engineering Body of Knowledge” (aka “SWEBOK Guide” v4).
> The final publication version should be out in
>> October or November (fingers crossed) but you can find the public review
> draft here:
>>>
>>> https://waseda.app.box.com/s/r1j1mavf3glhtf6qh5j0xxdeb4uaws5h
>>
>> Thanks for this link.
>>
>> I have always found the SWEBOK Guide to be a very odd document.
>>
>> It started out as essential a compendium of terms, and has gradually
>> accumulated a collection of software related phrases, opinions,
>> and the briefest of examples.
>>
>> It's not so much a body a knowledge as a body of snippets to
>> throw into a conversation to appear to know something about
>> software engineering.
>>
>> -- 
>> Derek M. Jones           Evidence-based software engineering
>> blog:https://shape-of-code.com
>>
>> _______________________________________________
>> The System Safety Mailing List
>> systemsafety at TechFak.Uni-Bielefeld.DE
>> Manage your subscription: https://lists.techfak.uni-
> bielefeld.de/mailman/listinfo/systemsafety
> 
> 
> 
> --
> Les Chambers
> les at chambers.com.au
> 
> https://www.chambers.com.au
> https://www.systemsengineeringblog.com
> 
> +61 (0)412 648 992
> 
> 
> _______________________________________________
> The System Safety Mailing List
> systemsafety at TechFak.Uni-Bielefeld.DE
> Manage your subscription: https://lists.techfak.uni-bielefeld.de/mailman/listinfo/systemsafety

-- 
Derek M. Jones           Evidence-based software engineering
blog:https://shape-of-code.com