User: cj Date: 06/01/04 07:46: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.4&r2=1.5 Delta lines: +49 -27 --------------------- --- Comp-analysis.html 3 Jan 2006 14:54:21 -0000 1.4 +++ Comp-analysis.html 4 Jan 2006 15:46:22 -0000 1.5 @@ -18,35 +18,39 @@ </td> <td colspan="2" bgcolor="white"> <p><b>Last Change:<br> - </b><csobj format="LongDate" h="20" locale="00000409" region="0" t="DateTime" w="165">Tuesday, January 03, 2006</csobj></p> + </b><csobj format="LongDate" h="20" locale="00000409" region="0" t="DateTime" w="186">Wednesday, January 04, 2006</csobj></p> </td> </tr> <tr> <td colspan="3" bgcolor="white"><b>Goal of this document:<br> - </b>This guideline set assists i-Team to accomplish a competitive analysis (CA).</td> + </b>This guideline set assists intergration-Teams (i-Teams) to accomplish a competitive analysis (CA).</td> </tr> <tr> <td colspan="3" bgcolor="white"> <p><b>Intended readership:<br> - </b>i-Team Memebers, Project Leads, Specification authors / readers (Development , Quality Assurance, User Experience, Documentation)</p> + </b>i-Teams, Project Leads, Specification authors / readers (Marketing, Development , Quality Assurance, User Experience, Documentation)</p> </td> </tr> </table> <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. + <li><b>Who decides to make a CA ?<br> + </b>The i-Team decides if it is necessary to make a CA on feature level.<br> + The CA needs to be completed before the feature specification work starts<br> + <br> + As a rule of thumb - making a CA makes sense, + <ul> + <li>if the to be specified feature has to follow workflows users expect from other applications, or + <li>if the to be specified features targets a competitors' features in a special area. + </ul> </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> + <li><b>What are the benefits of 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> + <li>All i-Team members are getting the same level of feature knowledge.<li>The whole i-Team gets an overview of what currently "State-of-the-Art" is.</ul> @@ -67,29 +71,47 @@ </ul> <ul> - <li><b>Which products should be analyzed?</b> + <li><b>Which products should be compared?</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. + <li>This depends on the feature area. - For example, if you need to specifiy an IDE related feature compare Visual Studio, Netbeans and Eclipse. + <li>In case of improving an existing feature it also makes sense to compare the older version of OpenOffice.org to the feature which has to be specified. </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>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. + <li><b>How many products should be compared?</b> + <ul> + <li>The minimum is one, but in general it makes sense to compare 2-3 products. </ul> + </ul> + <p></p> + <hr> + <p> + </p> + <ul> + <li><b>What to address in your CA?</b> + <ul> + <li>List the strengths and weaknesses of the feature <b>from the customer's viewpoint.</b> + <li>List precisely the product name, the product version and the products language. + <li>Compare the workflow of competitors' feature with yours. + <li>Understand the way how the feature works in the competitors' product. + <ul> + <li>The product help of the competing product is in general good source for this + </ul> + + <li>Compare the terminology used in the competing product with the OpenOffice.org terminology. + <li>Measure the performance of the competitors' feature. + <li>A CA is "living" document. Your CA should be updated, if a feature changes in the competitors' product. + <li> + <ul> + <li> + </ul> + <li>The CA level of detail depends heavily on the feature requirement(s). + <li>Do not include just a collection of screen shots! + </ul> </ul> </body> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
