tag message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: My homework for F2F
- From: "Durand, Jacques R." <JDurand@us.fujitsu.com>
- To: <tag@lists.oasis-open.org>
- Date: Mon, 6 Aug 2007 17:38:10 -0700
My workplan for the
F2F:
Starting from the
"Anatomy of a TA" sections in wiki, and based on the related discussion
threads:
Propose to draft a
section of guideline doc that:
- defines in simple
terms a couple of TA patterns: the "predicative" pattern, and the
"event-action" pattern.
- identify the
structure and parts of TAs for these patterns.
- illustrate these
patterns over a few requirements from real specification, using them as guides
to write related TAs.
- show that some TAs
can use a mix of both patterns (e.g. analogous to Event-Condition-Action rule
pattern).
The draft will be 4
pages max, including figures.
I would circulate
the draft at latest the week before the F2F, and will take into account the
current state of discussion threads in "Anatomy of a TA" section at that
date.
I welcome any
cooperation on this.
Other things that
the guideline doc will need but that I do not plan to
address:
- intro section
(justification/rationale material, etc.)
- terminology
section, that also clearly defines the scope of what a TA is / is not. (e.g. w/r
test metadata).
- how to deal with
the test environment, how much of it appears in (is assumed by) a TA
definition. (there are a few things said in wiki on this, in
Discussion/TestEnvirnomentAssumptions, and also by Serm in "Anatomy of
TA")
- possible
complications of TAs: implicit pre-conditions, external referred
specs.
- test
coverage/correction considerations.
-Jacques
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]