 |
|
| VERIFICATION AND VALIDATION FOR SAFETY CRITICAL SOFTWARE
| |
| | |
|
|
The NASA Approach
To order this title, and for more information, click here
By
Doron Drusinsky, Professor, Naval Postgraduate School, Monterey, CA, USA.
Description
Software Validation and Verification (V&V) is the process of checking that a software system meets specifications and that it fulfills
its intended purpose. Simply put, verification is ensuring that the software has been built according to the requirements and design
specs while validation ensures that the software actually meets the users needs and that the specifications are correct in the first
place. In short, verification ensures that you ?built it right? and validation confirms that you ?built the right thing.?
The proposed
book will be the first of its kind to encapsulate technology, process, and financial data associated with a credible large-scale, highly-visible
and complex adaptation of modern ?formal? methods of software validation and verification (V&V), which differs from standard methods
in that standard methods involve dynamic (manual) checking while formal verification involves proving or disproving a mathematical model
or theorem where flawless performance is absolutely necessary.
The book will describe the technology, process and organizational details
associated with the application of state of the art V&V techniques to six of the most visible and safety critical systems in modern history,
namely to NASA missions under development (Constellation projects, James Webb Telescope, Mars Space Lander, Juno, etc.).
This case-study
approach will capture the technology, process, and organizational aspects associated with a complex system success story. The process
will be presented in a straight-forward manner and the book?s chapter sequence will mirror the procedural timeline for the validation
and verification process for complex safety critical software systems.
Audience
Researchers and practitioners working with or interested in developing, implementing and testing trustworthy software, especially those
in complex-critical areas such aerospace, defense, power and utilities, automotive, public transportation, etc. Three types of readers
in each industry: engineers, managers, and decision makers related to testing, verification, and safety.
Actual job titles include:
programmer, design engineer, systems software engineer, software developer, applications developer, software architect, project manager,
systems analyst, software quality assurance engineer, software tester, web developer, lead engineer, etc.
Software Engineers can be
employed by development companies like Microsoft that are dedicated to the production of software for third parties, or can be employed
directly by those third party companies to undertake in-house work within virtually all major professional sectors, including aerospace,
automotive, defense, entertainment, communications, web hosting, and manufacturing, to name just a few.
Contents
TABLE OF CONTENTS:
Chapter 1: Technology Overview
a. Propositional vs. temporal specifications.
b. Natural Language (NL) temporal specifications.
c. UML-statechart temporal assertions.
d. Validating assertions:
e. Assertion architecture:
f. End-goal Purpose: Run-time verification
overview
g. Tools
Chapter 2: System Reference Model (SRM): Domain Model (DM) and Assertion-repositories
Motivation
a. Traffic Light
Controller SRM and assertions example.
b. Juno-Mission SRM example:
d. Orion-Mission SRM example:
e. SRM-based validation:
f. Discovering
specification errors: negotiating specification changes with contractor.
Chapter 3: Organizational changes for effective assertion based
V&V
a. The product-line approach: validation product lines and verification product lines.
b. Tiger teams: validation and reuse tiger
teams.
Chapter 4: Verification
a. Integration with the certified-test equipment.
b. On-line and off-line verification.
c. On-site automatic
test generation and run-time monitoring.
d. Discovering Implementation errors: negotiating implementation changes with contractor.
Chapter 5: Cost-benefit analysis
a. Up-front costs
b. Cost-benefit analysis of early detection of specification errors
c. Cost-benefit analysis of verification-time detection of implementation errors
d. V&V costs associated with older techniques
| Bibliographic details |
Hardbound, 320 pages, publication date: SEP-2011
ISBN-13: 978-0-12-374843-0
Imprint: MORGAN KAUFFMAN
|
| Price and Ordering |
Price:
USD 89.95
EUR 44.99
GBP 65.95
|  |
Books and book related electronic products are priced in US dollars (USD), euro (EUR), and Great Britain Pounds (GBP). USD prices apply to the Americas and Asia Pacific. EUR prices apply in Europe and the Middle East. GBP prices apply to the UK and all other countries.
|
See also information about conditions of sale & ordering procedures, and links to our regional sales offices.
|
077/760
Last update: 5 Sep 2009
|
|
| |
| | |
|
|
| |
Home | Elsevier Sites | Privacy Policy | Terms and Conditions | Feedback | Site Map | A Reed Elsevier Company