Formal methods

Formal methods are algebraic approaches to analytic software (and hardware) problems at the requirements, blueprint and architectonics levels. Examples of academic methods cover the B-Method, Petri nets, Automated assumption proving, RAISE and VDM. Various academic blueprint notations are available, such as the Z notation. More generally, automata approach can be acclimated to body up and validate appliance behavior by designing a arrangement of bound accompaniment machines.

Finite accompaniment apparatus (FSM) based methodologies acquiesce executable software blueprint and by-passing of accepted coding (see basic bound accompaniment apparatus or accident apprenticed bound accompaniment machine).

Formal methods are a lot of acceptable to be activated in avionics software, decidedly area the software is affirmation critical. Software affirmation assurance standards, such as DO178B appeal academic methods at the accomplished akin of analysis (Level A).

Formalization of software development is bit-by-bit in, in added places, with the appliance of Object Constraint Accent (and specializations such as Java Modeling Language) and abnormally with Model-driven architectonics acceptance beheading of designs, if not specifications.

Another arising trend in software development is to address a blueprint in some anatomy of argumentation (usually a aberration of FOL), and again to anon assassinate the argumentation as admitting it were a program. The OWL language, based on Description Logic, is an example. There is aswell plan on mapping some adaptation of English (or addition accustomed language) automatically to and from logic, and active the argumentation directly. Examples are Attempto Controlled English, and Internet Business Logic, which do not seek to ascendancy the cant or syntax. A affection of systems that abutment bidirectional English-logic mapping and absolute beheading of the argumentation is that they can be fabricated to explain their results, in English, at the business or authentic level.

The Government Accountability Office, in a 2003 address on one of the Federal Aviation Administration’s air cartage ascendancy addition programs,5 recommends afterward the agency’s advice for managing above accretion systems by

establishing, maintaining, and authoritative an accurate, valid, and accepted achievement altitude baseline, which would cover negotiating all authorized, unpriced plan aural 3 months;

conducting an chip baseline analysis of any above arrangement modifications aural 6 months; and

preparing a accurate life-cycle amount estimate, including a accident assessment, in accordance with the Accretion Arrangement Toolset’s advice and anecdotic the akin of ambiguity inherent in the estimate.