ResearchBib Share Your Research, Maximize Your Social Impacts
Sign for Notice Everyday Sign up >> Login

ICST 2012 - The IEEE Fifth International Conference on Software Testing, Verification and Validation

Date2012-04-17

Deadline2011-11-04

VenueMontreal, Canada Canada

KeywordsSoftware Testing;Software Verification ;Software Validation

Websitehttps://cs.gmu.edu/icst

Topics/Call fo Papers

Fifth International Conference on Software Testing, Verification and Validation

The IEEE International Conference on Software Testing, Verification and Validation (ICST) is the premier conference in all areas related to software quality. Software systems present unique engineering challenges to the tester, not least because they can exhibit non-determinism and emergent behaviour. No other engineering artefact is more closely intertwined with the human activities, resulting in complex hybrid systems that involve software, human judgement and, sometimes, political, legal and social processes.

As a result, software verification & validation, including testing, inspections, model analysis, safety certification, etc. draws upon a wide spectrum of disciplines, including engineering, mathematics and also psychology. It touches on all aspects of computer science and software engineering research and impacts on almost all software activities.

ICST seeks to address the problems in verification and validation, by bringing together researchers and practitioners for a conference that includes all aspects of software testing, as it is most widely construed. Thus, ICST welcomes research papers as well as industrial experience reports from software development and testing practitioners. For the research papers, ICST seeks high-quality original work. For the industrial papers, ICST seeks papers that present real-world experience from which others can benefit. Industrial software testing, verification, and validation pose additional challenges that must be taken into account when setting up new processes and tools successfully such as: the complexity of the system to be developed; evolving software, legacy code; integration of third-party components; requirements from a certification process; version management; product line engineering; agile development processes; distribution of teams and others.

Last modified: 2011-08-22 12:42:39