User: cj Date: 06/01/03 06:54:24 Modified: /specs/www/collaterals/guides/ Comp-analysis.html
Log: Issue number: Submitted by: Reviewed by: File Changes: Directory: /specs/www/collaterals/guides/ ========================================= File [changed]: Comp-analysis.html Url: http://specs.openoffice.org/source/browse/specs/www/collaterals/guides/Comp-analysis.html?r1=1.3&r2=1.4 Delta lines: +60 -6 -------------------- --- Comp-analysis.html 29 Dec 2005 15:14:41 -0000 1.3 +++ Comp-analysis.html 3 Jan 2006 14:54:21 -0000 1.4 @@ -18,25 +18,79 @@ </td> <td colspan="2" bgcolor="white"> <p><b>Last Change:<br> - </b><csobj format="LongDate" h="20" locale="00000409" region="0" t="DateTime" w="203">Wednesday, December 28, 2005</csobj></p> + </b><csobj format="LongDate" h="20" locale="00000409" region="0" t="DateTime" w="165">Tuesday, January 03, 2006</csobj></p> </td> </tr> <tr> <td colspan="3" bgcolor="white"><b>Goal of this document:<br> - </b>This guidline set assists specification authors to accomplish a competitive analysis.</td> + </b>This guideline set assists i-Team to accomplish a competitive analysis (CA).</td> </tr> <tr> <td colspan="3" bgcolor="white"> <p><b>Intended readership:<br> - </b>Specification authors, specification reviewers (Development , Quality Assurance, User Experience)</p> + </b>i-Team Memebers, Project Leads, Specification authors / readers (Development , Quality Assurance, User Experience, Documentation)</p> </td> </tr> </table> - <p> + <p></p> + <ul> + <li><b>Why should we make a CA?<br> + </b>If an i-Team decides that it makes sense to do a CA. As a rule of thumb doing a CA makes sense, if the feature has to follow work flows users expect from other programs. + </ul> + <ul> + <li><b>When should we make a CA<br> + </b>The CA needs be completed before the feature specification work starts + </ul> + <ul> + <li><b>What are the from making a CA?</b> + <ul> + <li>All members of the i-Team are getting the same level of knoweledge + <li>The i-Team learns what currently "State-of-the-Art" is + </ul> + + + + + + + + + + + + - </p> + + + + + + </ul> + <ul> + <li><b>Which products should be analyzed?</b> + <ul> + <li>This depends on the feature are. For example, if you want to gather information about IDE related features analyze Visual Studio, Netbeans and Eclipse. + </ul> + + + + + <li><b>How many products should be analyzed?</b> + <ul> + <li>The minimum is one, but in general it makes sense to compare 2-3 products + </ul> + <li><b>Some general recommendations</b> <ul> - <li> + <li>A CA is "living" document For example, if a feature changes in a newer version the existing CA can be taken again and could be expanded<li>The level of detail depends on the feature requirment + <li>It shouldn't just be a collection of screen shots! + <li>Analyze the workflow of the competitor's product. Try to understand the way it works there. + <li>Analyze which feature part of the competitor's product provides the biggest value for the customer + <li>Take a look at the terminology they've used, measure the performance of the competitive feature. + </ul> + + + + </ul> </body> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
