Introduction should explain who the hell the target audience or customers are, and what value this product provides to the customers or what customer's problem this product solve.
Your first page contains nothing but technology jargons that has nothing to do with the core values of your software and nobody usually care about it.
It is typical mistake that almost all Korean software vendors make.
Thanks for your feedback. Kraken is not complete product but just another osgi application stack for specific domain. It solves typical problem that software engineer often encounter -- for example, development model, operational issues as I noted above, etc - but it's too general. How can that be addressed properly in developer view? I'm reviewing several open-source project introduction but your advice will be greatly appriciated.
In the first few pages, you need to tell your target customers pretty good reasons why the hell they have to spend time keep reading it. The beginning of the introduction should briefly mention the real problems that your target customers have and declare your product solve them. It doesn't matter whether your product really solves the problems or how to solve the problems in detail.
I think you need to add "Why Kraken" after "What is Kraken".
The possible reason could be... - there is no solution for the problems on the market - there are solutions A, B and C, but they are lacking something - or simply they are too expensive - etc.
I will add some pages for SnortSP that is focused on packet-based network analysis. Many vendors use the term "security platform" for their products, but it has different meaning.
