commonly reported ones to the IT department and which workers are reporting  what kinds of problems. As you build your UIMA pipeline in ICA Studio and  implement it within a solution, you get to know your content. As we show you in  later sections, you create rules and dictionaries for a specific domain or purpose.  When you implement these resources, the results might not exactly match your  expectations. Trying out your annotator on as wide a range of sample texts as  possible is the best way to learn exactly what kind of content you really have.  When you try out your UIMA pipeline, you probably discover words that need to  be added to your dictionaries. You might also find false hits that need to be  formalized into parsing rules that can validate annotations according to their  context. When your solution enters the production phase, the annotator results  need to be monitored and evaluated, especially when the source or nature of the  content changes. One of the preferred practices for resource development is to repeat small steps  iteratively (see Figure 11-3): ICA Studio supports the iterative process: 1. Start with a small document set. 2. Create a small set of resources. 3. Analyze and validate the results. Check to ensure that the results are as  expected. If not, make appropriate changes. 4. Continue to build and enhance the engine by extending the resources. 5. Repeat these steps. 1. Annotate a collection of documents. 2. Save annotation results. Figure 11-3 Iterative process  Chapter 11. Customizing content analytics with IBM Content Analytics Studio  409 Build Create Modify Analyze Validate