Abstract

Many engineering systems, especially those required to be particularly dependable, traditionally undergo inspections and assessments of safeness and fitness for purpose. Often some form of ‘certificate’ is provided by the assessment authority. To an increasing degree these systems are beginning to contain software components. The question naturally arises: how can the software component be assessed? This paper explores the feasibility and limitations of software assessment and the link between the process of developing the software and the quality of the resulting software product.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call