Abstract | ||
---|---|---|
Just over a decade ago, a paper Ten Commandments of Formal Methods [16] suggested some guidelines to help ensure the success of a formal methods project. It proposed ten important requirements (or “commandments”) for formal developers to consider and follow, based on our knowledge of several industrial application success stories, most of which have been reported in more detail in two books [32,33]. The paper was surprisingly popular, is still widely referenced, and used as required reading in a number of formal methods courses. However, not all have agreed with some of our commandments, feeling that they may not be valid in the long-term. We re-examine the original commandments over ten years on, and consider their validity in the light of a further decade of industrial best practice and experiences, especially with respect to formal notations like ASM, B and Z. We also cover the activities of the UK Verified Software Repository Network (VSR-net) in the context of UK Grand Challenge 6 on Dependable Systems Evolution. |
Year | DOI | Venue |
---|---|---|
2009 | 10.1007/978-3-642-11447-2_14 | Rigorous Methods for Software Construction and Analysis |
Keywords | Field | DocType |
formal methods course,industrial application success story,dependable systems evolution,formal methods project,formal developer,formal methods,uk grand challenge,formal notation,uk verified software repository,industrial best practice,formal method,best practice | Notation,Best practice,Software engineering,Software repository,Simulation,Computer science,Automated theorem proving,Systems evolution,Formal methods,Ten Commandments,Feeling | Conference |
Volume | ISSN | ISBN |
5115 | 0302-9743 | 3-642-11446-6 |
Citations | PageRank | References |
1 | 0.37 | 30 |
Authors | ||
2 |
Name | Order | Citations | PageRank |
---|---|---|---|
jonathan p bowen | 1 | 1519 | 181.76 |
Michael G. Hinchey | 2 | 697 | 91.11 |