曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

development by providing guidance to software developers on addressing the cause of software failures. This
guidance has been packaged as a Code of Practice.
It is anticipated that the Code of Practice will be of particular benefit to two groups:
1 purchasers of safety-critical software who wish to use the Code of Practice for capability determination ie to
assess an organisation or project in order to determine risks to the successful outcomee of a contract,
development or service delivery;
2 developers of safety-critical software seeking practical, cost-effective advice on process enhancement by
identifying strengths and those key areas requiring improvement.
Care has been taken to ensure that the guidance embodied in the Code of Practice is rooted in the real world. To
this end, the PRICES project undertook a survey of current software development practices, and an in-depth field
study investigating the human factors issues in the safety- critical software development process . This information
was used to model the development process, highlighting those areas where errors are most likely to occur. Before it
is issued, a draft the Code of Practice will have been subjected to trials in case studies and the findings fed back to
ensure industry's needs are taken into account.
The Code of Practice will be supported with a justification report, providing the rationale for the advice given, and a
Distance Learning package to assist developers and users in its application.
For a more detailed description see section 8.4, A code of practice for the human dimension, and section 11.3, A
systems approach to human error.
References
[1] J Griffyth, Human Issues in the Development Process - Modelling Their Influence on Productivity and
Integrity, Safety-critical Systems: The Convergence of High Tech and Human Factors, Ed Redmill and
Anderson, 1996, ISBN 3-540-76009-1.
[2] The PRICES Approach to Human Error, Christine Thomlinson, in Safer Systems: Proceedings of the
Fifth Safety-critical Systems Symposium, Brighton 1997, Springer-Verlag, ISBN 3-540-76134-9.
[D17] Baseline of Current Practices used in the Development of Software for Dependable Systems, October
1994,+ D.
[D19] Classification of Software Lifecycles, June 1995,+ D.
[D20] Detailed Process Model, November 1996,+ D.
[D20A] Process Model Commentary, November 1996,+ D.
[D20B] Detailed Process Model, November 1996,+ D.
[D21] Human Factors Study, Interim Report, February 1995,+ D.
[D29] Code of Practice, April 1997,+ D.
[D30] Theoretical Justification of the Code of Practice, April 1997,+ D.
Project number: 9202 Approx. Project Cost: £1m Start date: Nov 1993 End date: Feb 1997
EPSRC Grant number: j18057, j18200
Advances in Safety Critical Systems - Results and Achievements from the DTI/EPSRC R&D Programme. Compiled and edited by Mike Falla.
19
PROMISE Product Monitoring for Integrity and Safety Enhancement
South Bank University
Uncle:
Philips Medical Systems - Radiotherapy.
Contact: Ms J Rogers
CSSE, South Bank University
103 Borough Rd
London SE1 OAA.
Tel: 0171 815 7432 Fax: 0171 815 7550
Email: rogersj@vax.sbu.ac.uk
Summary
The principle aim of the PROMISE project was to establish a framework within which the full potential of product
measurement can be exploited in the production of high integrity software. This framework builds upon the exisitng
QUALMS methodology. The QUALMS tool (developed at South Bank University) inputs flowgraphs which model
software entities and measures aspects of the flowgraph structure
The main innovations have been the application of the QUALMS tool kit to the specific domain of high integrity
systems, the development of probabilistic models to predict product properties and the development of new
testability measurement approaches. The project has also explored the use of product measures other than those
derived from QUALMS and where appropriate incorporated them into the developing framework.
The main project achievements have been:
• New tools for analysing PL/M and C++ code
• An in-depth study of the quality assurance and fault reporting procedures used by PMS-R
• An annotated bibliography of over 250 publications on object-oriented metrics
• New research results in software testability measurement
For further detail on the last two of these see section 10.4, Assessing the impact of object technology in the safetycritical
domain, and section 12.5, Measuring the testability of a system.
Information about PROMISE can also be obtained from the project contact noted above and from the World Wide
Web at: http://www.sbu.ac.uk:80/~csse/promise.hmtl
References
[Bainbridge 94] Defining testability metrics axiomatically, Bainbridge J.R., Software Testing, Verification and
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料25(154)