1.5 Architecture background

1.5.1 Design rationale

In this chapter the decisions we made for the implementation and logical view on the architecture and the alternatives are described and weighted, and finally a strategy is chosen.

First, we’ll discuss the decisions that have been made in the data layer of the application. This layer is responsible for retrieving, abstracting and aggregating data from multiple sources in preparation for the actual analysis of the data.
 

1.5.1.1 Data gathering layer

The Data collector layer performs data collection tasks from several systems used by the customer.

The data which needs to be collected are stored in several sub systems. The Data collector queries the subsystem and collects its newest data, to transform them in a simple format for the SNA Layer to perform analytic tasks on them.

These identified systems (tool types) are in general:

·         SVN                :Mercurial

·         WIKI               :Confluence

·         BUG                :  JIRA Bug - tracking

·         IRC                  :  Communications

·         EMAIL            :  Communications

The information about the systems used is gathered through the provided information from the customer.

For the systems used by the customer, we introduce the name tool type. Because the list above lists all tools the customer use for his development process, and these tools are also the basis data stores, from where the Data Collector gathers its raw data’s.

The Data collector Layer can have two different options to store his extracted Data. The extracted data are the data gathered from the different systems mentioned above. The extracted data from every systems will be transformed in a format which gives only the information’s needed and this data will be then stored for further processing through the SNA component. The differences between this option’s and the option used and why is explained in the section below.