4. Using formal methods to build a software application
4.1 Software requirements specification
Software requirements must comply with at least three points:
be clear, precise, unambiguous, verifiable, testable, maintainable and achievable;
be traceable to input elements ;
be unambiguous and not open to misunderstanding.
As far as requirements management is concerned, we have presented the concepts and methods...
Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference
This article is included in
Railway systems
This offer includes:
Knowledge Base
Updated and enriched with articles validated by our scientific committees
Services
A set of exclusive tools to complement the resources
Practical Path
Operational and didactic, to guarantee the acquisition of transversal skills
Doc & Quiz
Interactive articles with quizzes, for constructive reading
Using formal methods to build a software application
Bibliography
Bibliography
Websites
CENELEC http://www.cenelec.eu/Cenelec/Homepage.htm
COFRAC http://www.cofrac.fr
EPSF http://www.securite-ferroviaire.fr/
...
Events
ERTSS Embedded Real Time Software and System http://www.erts2012.org/
ESREL http://www.esrel2011.com/
LambdaMU http://www.imdr.fr
Standards and norms
- Applications ferroviaires. Équipements électroniques utilisés sur le matériel roulant - AFNOR EN 50155 - 12-01
- Langage de programmation Ada - ANSI:1983, ANSI/MIL-STD-1815A-1983 - 1983
- Software Considerations in Airborne Systems and Equipment Certification, published by ARINC, DO 178B, and EUROCAE, ED12, édition C - ARINC DO 178:C - 2001
Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference