This week's book giveaways are in the Refactoring and Agile forums. We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line! See this thread and this one for details.
We have a presentation problem in our project,I want to describe it using Analysis mechanism.Following is my draft: 9.2 Analysis Mechanisms Presentation: For all need to display chart,we need identify: Demension: How many dimensions should be displayed? Style:How many kinds of chart used? Refresh frequency: Are the chart more or less refresh? Precision: How to define the precision of the coordinates' value? Volume: Number of charts to display in one page. Synchronicity: Does the chart changing dynamicly according to the database updated? Reliability: Shall the objects survive a crash of the process; the processor; or the whole system? Usability: Developed by ourselves or use other open source project? Use applet or servlet? 9.3 Design Mechanisms Presentatiion: We utilize third party open source project as the way to resolve the above analysis mechanism. Demensiion:2 dimensions,use series as the different value of color. Style: 3 kinds of chart.columnarity,pie,coordinate. Refresh frequency: utilize token as the way to avoid frequency refresh. Precision: decimal places:2 Synchronicity: not synchronicity when data changed,get the newest result by refresh .
but I don't know if it is right,Please help me checking it and tell me how to correct it.thanx a lot.