17 آبان 1393, 09:44 ق.ظ
سلام
من درس تحمل پذیری خطا دارم میخوننم. همش میگه Formal Methods منظور چیه؟ منظورش چه متدی در برنامه نویسی هست؟ من متن رو میزارم
Formal methods have been used, particularly in the research community,
to improve software dependability during construction. In these approaches,
requirements specifications are developed and maintained using mathemati-
cally tractable languages and tools. Lyu [25] describes four goals of current
formal methods studies: (1) executable specifications for systematic and
precise evaluation, (2) proof mechanisms for software verification and vali-
dation, (3) development procedures that follow incremental refinement for
step-by-step verification, and (4) every work item, be it a specification or
a test case, is subject to mathematical verification for correctness and
appropriateness.
Mathematical specifications of proofs of software properties tend to
be the same size as the program, difficult to construct, and often harder
to understand than the program itself. As a result, they can be just as prone
to error as the software under scrutiny. Because of these concerns, formal
methods have not been generally used on large projects. However, if a spe-
cific part of a system is indicated for risk mitigation, the analyst may find the
size of the component small enough that the use of formal methods on that
component is not prohibitive in terms of cost, time, or other resources.
من درس تحمل پذیری خطا دارم میخوننم. همش میگه Formal Methods منظور چیه؟ منظورش چه متدی در برنامه نویسی هست؟ من متن رو میزارم
Formal methods have been used, particularly in the research community,
to improve software dependability during construction. In these approaches,
requirements specifications are developed and maintained using mathemati-
cally tractable languages and tools. Lyu [25] describes four goals of current
formal methods studies: (1) executable specifications for systematic and
precise evaluation, (2) proof mechanisms for software verification and vali-
dation, (3) development procedures that follow incremental refinement for
step-by-step verification, and (4) every work item, be it a specification or
a test case, is subject to mathematical verification for correctness and
appropriateness.
Mathematical specifications of proofs of software properties tend to
be the same size as the program, difficult to construct, and often harder
to understand than the program itself. As a result, they can be just as prone
to error as the software under scrutiny. Because of these concerns, formal
methods have not been generally used on large projects. However, if a spe-
cific part of a system is indicated for risk mitigation, the analyst may find the
size of the component small enough that the use of formal methods on that
component is not prohibitive in terms of cost, time, or other resources.