Software processes are software too
ICSE '87 Proceedings of the 9th international conference on Software Engineering
Process models, process programs, programming support
ICSE '87 Proceedings of the 9th international conference on Software Engineering
Managing the software process
Mathematical foundations of software engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Software Process Modelling and Technology
Software Process Modelling and Technology
Software Metrics: A Rigorous and Practical Approach
Software Metrics: A Rigorous and Practical Approach
ASE '98 Proceedings of the 13th IEEE international conference on Automated software engineering
Software tools for safety-critical software development
International Journal on Software Tools for Technology Transfer (STTT) - A View from Formal Methods 2003 (pp 301-354); Special Section on Recent Advances in Hardware Verification (pp 355-447)
FDA: Between Process and Product Evaluation
HCMDSS-MDPNP '07 Proceedings of the 2007 Joint Workshop on High Confidence Medical Devices, Software, and Systems and Medical Device Plug-and-Play Interoperability
The epistemology of validation and verification testing
TestCom'05 Proceedings of the 17th IFIP TC6/WG 6.1 international conference on Testing of Communicating Systems
An overview of the mensurae language: specifying business processes
ROOM'00 Proceedings of the 2000 international conference on Rigorous Object-Oriented Methods
Formal methods versus engineering
ACM SIGCSE Bulletin
| Hi-index | 0.00 |
As software has invaded more and more areas of everyday life, software certification has emerged as a very important issue for governments, industry and consumers. Existing certification regimes are generally focused on the wrong entity, the development process that produces the artifact to be certified. At best, such an approach can produce only circumstantial evidence for the suitability of the software. For proper scientific evaluation of an artifact, we need to address directly the attributes of the product and their acceptability for certification. However, the product itself is clearly not enough, as we need other artifacts, like requirements specifications, designs, test documentation, correctness proofs, etc. We can organise these artifacts using a simple, idealised process, in terms of which a manufacturer's own process can be "faked". The attributes of this idealised process and its products can be modelled, following the principles of Measurement Theory, using the product/process modelling method first introduced by Kaposi.