Evaluating Testing Methods by Delivered Reliability
IEEE Transactions on Software Engineering
Residual test coverage monitoring
Proceedings of the 21st international conference on Software engineering
A formal approach for specification and classification of software components
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
WCT: A Wrapper for Component Testing
FIDJI '01 Revised Papers from the International Workshop on Scientific Engineering for Distributed Java Applications
A framework for component deployment testing
Proceedings of the 25th International Conference on Software Engineering
Towards a composition model problem based on IEC61850
Journal of Systems and Software - Special issue on: Component-based software engineering
Software Component Certification: A Survey
EUROMICRO '05 Proceedings of the 31st EUROMICRO Conference on Software Engineering and Advanced Applications
Intra-component security certification
Proceedings of the International Conference on Advances in Computing, Communication and Control
Data-flow integration testing adapted to runtime evolution in component-based systems
Proceedings of the 2009 ESEC/FSE workshop on Software integration and evolution @ runtime
Software testing research and practice
ASM'03 Proceedings of the abstract state machines 10th international conference on Advances in theory and practice
Component-based software certification based on experimental risk assessment
LADC'07 Proceedings of the Third Latin-American conference on Dependable Computing
| Hi-index | 4.10 |
Most current process-based methods for certifying software require software publishers to"take oaths concerning which development standards and processes they will use." Jeffrey Voas, among others, has suggested that independent agencies驴software certification laboratories (SCLs)驴should take on a product certification role. The authors accept that this approach may work well for certain software distribution models, but they also observe that it cannot be applied to all software development.Third-party SCLs would add unnecessarily to the costs that small developers incur by speculating on the success of a given component. However, supplying complete test sets with components incurs little additional cost because component authors must generate the tests in the first place. Any extra effort adds value to a component because a tested component certainly offers a more marketable commodity.The authors believe that while SCLs have a place in large or safety-critical software projects, there will always be small commercial-software developments for which failure represents a moderate cost. In such cases, the cost of generating and inspecting tests can be justified.