[SystemSafety] Logic

[Steve Tockey]

All,
I should have added that a new version of the "Guide to the Software Engineering Body of Knowledge" (aka "SWEBOK Guide", in this case SWEBOK Guide V3) has recently been released by the IEEE Computer Society. You can get your own PDF copy by going to http://www.swebok.org and then clicking on the "PDF (free)" link under "Get the SWEBOK Guide". This new version is a significant update from the previous 2003 version. Among other things, several new "Knowledge Areas" have been added.

A quick survey shows the following sections talking about formal methods of one sort or another:
Chapter 1: Software Requirements
    Section 1.4.5: Formal Analysis
    Possibly Section 1.6.3: Model Validation

Chapter 9: Software Engineering Models and Methods
    Section 9.1.4: Preconditions, postconditions, and invariants
    Possibly Section 9.3: Analysis of models
    Section 9.4.2: Formal Methods

Chapter 14: Mathematical Foundations


So my point is that the SWEBOK Guide people have at least recognized the need for formality in professional software development. Hopefully, as industry and academia adopt SWEBOK Guide as a description/definition of "what software engineering is" then there will necessarily be an increased emphasis on formality.


-- steve





From: John Knight <jck at virginia.edu<mailto:jck at virginia.edu>>
Organization: University of Virginia
Reply-To: "knight at cs.virginia.edu<mailto:knight at cs.virginia.edu>" <knight at cs.virginia.edu<mailto:knight at cs.virginia.edu>>
Date: Sunday, February 16, 2014 10:02 AM
To: "RICQUE Bertrand (SAGEM DEFENSE SECURITE)" <bertrand.ricque at sagem.com<mailto:bertrand.ricque at sagem.com>>, "knight at cs.virginia.edu<mailto:knight at cs.virginia.edu>" <knight at cs.virginia.edu<mailto:knight at cs.virginia.edu>>, Peter Bernard Ladkin <ladkin at rvs.uni-bielefeld.de<mailto:ladkin at rvs.uni-bielefeld.de>>
Cc: "systemsafety at techfak.uni-bielefeld.de<mailto:systemsafety at techfak.uni-bielefeld.de>" <systemsafety at techfak.uni-bielefeld.de<mailto:systemsafety at techfak.uni-bielefeld.de>>
Subject: Re: [SystemSafety] Logic

Note that I was suggesting concepts that I would like to see included in higher education, not commenting on current practice.

As many have noted, current practice in a variety of industries in several countries rarely (although there are exceptions) includes significant rigour let alone application of formal methods.

-- John

On 2/16/14, 12:11 PM, RICQUE Bertrand (SAGEM DEFENSE SECURITE) wrote:

  *   Engineers are responsible for what they do.
This depends on the countries and their local engineering cultures and legal system. In France engineers are not personally responsible. The boss of the company is responsible. Engineer is not a regulated position such as dentist or lawyer …

  *   Engineering is a profession not some amateur activity.
Yes but you sincerely believe that you are a good professional and have no reason to doubt about that as long as nobody demonstrates you that you are actually an amateur.

  *   Mathematics is an essential component of professional computer engineering.
Yes but :

1.      Having never been thought that they were essential, you sincerely believe you don’t need them as long as nobody demonstrates you that you actually do.

2.      The associated level of maths is more relevant from a master degree than a bachelor degree, which means that, at least in France:

a.       You don’t what to do with the existing automation engineer population

b.      You don’t have the budget to replace bachelors by masters.

Bertrand Ricque
Program Manager
Optronics and Defence Division
Sights Program
Mob : +33 6 87 47 84 64
Tel : +33 1 59 11 96 82
Bertrand.ricque at sagem.com<mailto:Bertrand.ricque at sagem.com>


c.

From: systemsafety-bounces at lists.techfak.uni-bielefeld.de<mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de> [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de] On Behalf Of John Knight
Sent: Sunday, February 16, 2014 5:58 PM
To: Peter Bernard Ladkin; knight at cs.virginia.edu<mailto:knight at cs.virginia.edu>
Cc: systemsafety at techfak.uni-bielefeld.de<mailto:systemsafety at techfak.uni-bielefeld.de>
Subject: Re: [SystemSafety] Logic

Peter,



obviously I agree with much of what you say. But I am discussing with people who believe that we

constitute an exception to much of it.

I think we are talking about different things.  Research projects need software rapid prototypes to support investigation in areas such as AI and robotics.   These are "throw-away" prototypes that should never make it into production and usually don't.

I am talking about software products that are part of engineered computer systems which will subject others (possibly the general public) to risk.  Higher education has a responsibility to prepare professional engineers to perform that engineering.  That education needs to make it clear that:

  *   Engineers are responsible for what they do.
  *   Engineering is a profession not some amateur activity.
  *   Mathematics is an essential component of professional computer engineering.

In response to the comment from Les Chambers:

"We must find a way to bring formal methods out of the lab and into general use."

I generally agree.  But I note that we have industrial strength systems such as SPARK Ada, industrial scope use of such systems such as the NATS iFACTS system, and substantial evidence from Peter Amey and his colleagues that applying such technology is cheaper and better than the informal alternatives.

-- John

#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles, être soumis aux règlementations relatives au contrôle des exportations ou ayant un caractère privé. S'ils ne vous sont pas destinés, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque manière que ce soit le contenu. Toute exportation ou réexportation non autorisée est interdite.Si ce message vous a été transmis par erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or proprietary information and may be subject to export control laws and regulations. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. Unauthorized export or re-export is prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20140216/5631e928/attachment-0001.html>