Jump to content

Talk:Polyspace

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
[edit]

This article (Polyspace) is now linked from three other Wikipedia articles. These are: List of tools for static code analysis, Dynamic program analysis, and Abstract interpretation. Recommend removing the orphan header from Yobot. Jabraham mw (talk) 14:58, 25 September 2010 (UTC)[reply]

File:Polyspace.gif Nominated for speedy Deletion

[edit]

An image used in this article, File:Polyspace.gif, has been nominated for speedy deletion for the following reason: Wikipedia files with no non-free use rationale as of 14 February 2012

What should I do?

Don't panic; you should have time to contest the deletion (although please review deletion guidelines before doing so). The best way to contest this form of deletion is by posting on the image talk page.

  • If the image is non-free then you may need to provide a fair use rationale
  • If the image isn't freely licensed and there is no fair use rationale, then it cannot be uploaded or used.
  • If the image has already been deleted you may want to try Deletion Review

To take part in any discussion, or to review a more detailed deletion rationale please visit the relevant image page (File:Polyspace.gif)

This is Bot placed notification, another user has nominated/tagged the image --CommonsNotificationBot (talk) 01:24, 14 February 2012 (UTC)[reply]

Introduction

[edit]

The introduction makes four assertions:

  • Polyspace is a static code analysis tool
  • inspired by the failure of the maiden flight of Ariane 5
  • the first example of large-scale static code analysis by abstract interpretation to detect and prove the absence of certain run-time errors in source code for the C, C++, and Ada programming languages.
  • also checks source code for adherence to MISRA C and other related code standards.

There is a reference to a company white paper. However, the Ariane assertion is not supported by the reference at all, and is not mentioned in the rest of the article. The claim that it is the first example is also not mentioned in the remainder of the article and a claim like this needs to be supported by an independent reliable source. Those two assertions, if they can be adequately verified, could go into a History section. Deltahedron (talk) 18:43, 17 May 2014 (UTC)[reply]

History

[edit]

There seem to be some independent reliable sources for the history:

  • Yi, Kwangkeun, ed. (2006). "In Memoriam: Alan Deutch (1965-2006)". Static Analysis: 13th International Symposium, SAS 2006, Seoul, Korea, August 29-31, 2006. Lecture Notes in Computer Science. Vol. 4134. Springer-Verlag. ISBN 3-540-37756-5.
  • Cousot, Radhia; Martel, Matthieu, eds. (2010). Static Analysis: 17th International Symposium, SAS 2010, Perpignan, France, September 14-16, 2010, Proceedings. Lecture notes in computer science: Advanced research in computing and software science. Springer-Verlag. p. 65. ISBN 3642157688. ISSN 1611-3349.
  • Bertot, Yves, ed. (2009). From Semantics to Computer Science: Essays in Honour of Gilles Kahn. Cambridge University Press. p. 558. ISBN 0-521-51825-3.
  • Wilhelm, Reinhard, ed. (2001). Informatics: 10 Years Back. 10 Years Ahead. Lecture Notes in Computer Science. Vol. 2000. Springer-Verlag. p. 152. ISBN 3-540-41635-8.

I think one can probably write:

Polyspace Technologies was established in France in 1989 by Alan Deutsch and Daniel Pilaud in 1999. The product was based on a project conducted by Deutsch and colleagues at INRIA in 1996 after the failure of the Ariane 501 launch.

Deltahedron (talk) 19:14, 17 May 2014 (UTC)[reply]

Quality assurance

[edit]

The text "In organizations where quality assurance is important, Polyspace is used to demonstrate with metrics that specified software quality objectives have been met" is supported by a reference to a paper "Software Quality Objectives for Source Code" for which the web link is now sadly dead. However this reference makes it clear that the paper is a collaboration between the company and some customers which "describes an example of software quality models". Even that reference is written in collaboration with various software manufacturers. It seems doubtful that any of this can be regarded as verification for the text by independent reliable sources. Deltahedron (talk) 20:42, 17 May 2014 (UTC)[reply]