<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<item>
  <id>05561575</id>
  <dt>a</dt>
  <an>05561575</an>
  <augroup>
    <au>Ramakrishnan, Sita</au>
  </augroup>
  <ti>VISWAS and on diagnosability with IEEE Std P1522 and UML2.0 testing profile.</ti>
  <so>Petrenko, Alexandre (ed.) et al., Formal approaches to software testing. Third international workshop on formal approaches to testing of software, FATES 2003, Montreal, Quebec, Canada, October 6th, 2003. Revised papers. Berlin: Springer (ISBN 3-540-20894-1/pbk). Lect. Notes Comput. Sci. 2931, 236-251 (2004).</so>
  <py>2004</py>
  <pu>Berlin: Springer</pu>
  <lagroup>
    <la>EN</la>
  </lagroup>
  <ccgroup>
  </ccgroup>
  <utgroup>
  </utgroup>
  <cigroup>
  </cigroup>
  <ligroup>
    <li>doi:10.1007/b95400</li>
  </ligroup>
  <abgroup>
    <ab>Summary: We first describe the work on validating interoperable distributed software and systems -- VISWAS method [1], which extends UML models to include testability aspects with design by contract notions. In VISWAS, automated test sequence generation is produced from the extended Message Sequence Charts (MSCs) and Live State Charts with temporal action propagation list. Since testability is not independent of the diagnostic process, diagnosability was not explicitly stated as part of the SDLC and testing process in VISWAS. Next, we present our current work on capturing diagnosis flows in MSCs, and some discussion on why standards such as IEEE Std P1522, UML 2.0 Testing Profile, MSC2000 and TTCN-3 are useful for consideration in capturing diagnosability aspects in a testing environment.</ab>
    <rv></rv>
  </abgroup>
</item>