Browse Prior Art Database

Post generated feature list mechanism

IP.com Disclosure Number: IPCOM000236859D
Publication Date: 2014-May-20
Document File: 2 page(s) / 86K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a post generated feature list mechanism. Following two phases of semantic processing, the post-generated feature list is generated. The first semantic engine summaries policies from standard documents, release notes, product specification and feature list into reference database. Then the second semantic engine parses problem report database and enhancement request database following the reference database to generate the post-generated feature list.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 01 of 2

Post generated feature list mechanism

Product specification and feature list are always in bullet list. There are not enough information or real case for sales, solution teams and clients to answer 'not support' and 'product limitation' for client's questions. Similar questions usually go into other support channel or product development team to get the answer.

    From technical support perspective, numerous problem reports were opened to answer same questions without reasonably "re-using" the existing information.

- As a technote, most of Q&A or similar feature request questions are very short or petty, hardly to be a technote. For example, "Does DataPower support RFCxxxx, option yyyy?"

- Also for some questions, they are asking a real use case that is hardly presented in traditional feature list. For example, "I want to do xxxx, can DataPower support to do this?"

    Key idea : product specification and feature list are usually generated after product is released. They are usually in big scope or in item-list way. After product release, many customers will report their use cases and questions. The first semantic engine summaries policies from standard documents, release notes, product specification and feature list into reference database. Then the second semantic engine parses problem report database and enhancement request database following the reference database to generate the post-generated feature list.

1


Page 02 of 2

2