Appeal No. 2004-2090
Application No. 09/540,391
tasks, testing and evaluation tasks, or technical documentation tasks, and
that the T&E, QA and documents tracking lists are associated with a
particular product feature. However, Eisner… discloses Test and
Evaluation, Quality Assurance and Documentation. . . .
Appellant argue, on page 7 of the brief, that the combination of the
references do not teach the limitation of “a product feature list user interface by
which a user enters desired features of the product to be released” as recited in
claim 23.
We concur. Claim 23 includes the limitation of a product feature list user
interface and the limitation that all parameters entered by the user into the
engineer task list user interface, the quality assurance interface and the technical
documents list user interface are each defined in terms of a particular one of the
product features. As stated supra with respect to claim 15, we do not find that
the combination of Project user’s guide and Pyron teach or suggest associating
product features with tasks. We find that section of Eisner cited by the examiner
is a text describing many aspects of system engineering to be considered over
the life cycle of system. (See page 156). The cited section of Eisner discusses
the use of quality assurance and technical documentation. However, we do not
find that Eisner teaches or suggests associating product features with tasks as
claimed. Accordingly, we will not sustain the examiner’s rejection of claims 23
and 24.
We next consider the rejection of dependent claim 25. The rejection is set
forth on page 16 of the answer. The rejection of these claims builds on the
10
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 Next
Last modified: November 3, 2007