查看“Industry Analysis Report”的源代码

Industry Analysis Report, or [[IAR]] for short. is a document summarizing the technical properties, legal standing, market dynamics, and cultural/ethical considerations of a product type or a specific kind of service. It used as an evolving knowledge base to collect and demonstrate the amount of knowledge about a given industrial topic. It can be ideally authored in a collaborative workflow similar to Wikipedia's content production pipeline, so that many people can get read and write access to its content.

==Key Considerations==
Reading and Writing an IAR must follow some generic and repeatable format, so that it allows readers and writers to quickly get acquainted with multiple instances of [[IAR]]s. We suggest all teams to follow the a generic outline, starting by the following sections:

#Topic of your selected product type or service
#Introduction to the team that wrote this IAR
#An brief history of the product
#Literature Review: showing more recent development that are relevant to your study.
#Trend Analysis: This is where you want to expand on the dynamics of product/service adoption. This is where the S-Curve and Paradigm shift theory comes in play.
#Discussion: What could happen if some alternative solutions or conditions take place in the operating context.
#Conclusion: Articulate or summarize what you believe to be true given the above supporting evidence
#References: Make sure you include well documented references, ideally pointing out the specific pages even section content of your source material.

==What other things should be included==
#A [[Logic Model]] as a Content Map in the beginning
#Table of Content
#Table of Figures
#QR Code pointing to a website that contains links to your content evolution repository and/or your wiki pages.

==What is analytical about IAR?==
Our suggestion is to create a [[logic model]] of your [[IAR]] before your start your analysis. This logic model will spell out the key components of your document, and articulate what your audience will learn from your report. Ideally readers should learn about the history, the ongoing development, and future possibilities of your subject of interest. 
 To analyze something, one should break down the system into various components. 
In the history section, one may divide the product's chronology by talking about the product/service's origin, original creators, key personalities or institutions that have influence on the subject. Legal, cultural, or religious preferences that relate to the product, and finally, the market dynamics of the product. In other words, readers should get a broad picture of the product/service of interest by seeing relationships between people, societies, and technologies in the greater context. It will help communicate the central theme of the report by grounding it with a larger and more generic vocabulary known by a generic crowd.

==What should be included in the Logic Model of IAR==
One should talk about what your IAR will accomplish, not what the product will accomplish. This is useful because it will help the audience to learn about your presentation strategy. Clearly, if you decide to include a logic model for the product or industry, that is fine, too.