Business Intelligence,range :Data and information quality

Project description
this is research is not normal can choice the subtitle. please read carefully my document i upload..that is instructions, i need you just give me a sub tittle before Saturday.

Author Guidelines BI Research Paper
Matriculation Number
Abstract. The abstract {style abstract} is a mandatory element that should summarize the contents of the paper and should contain at least 70 and at most 150 words.
Keywords: Please list your 3-5 keywords {style keywords} here. They should be separated by commas.
1    Introduction
You will find here the guidelines for the preparation of the research papers based on Springer’s Lecture Notes in Computer Science (LNCS). Your contribution has to be prepared using this Microsoft Word 2007 template. In essence, we ask you to make your paper look exactly like this document. The easiest way to do this is simply to replace the content with your own material.
2    Preparation of Your Paper
2.1    How to Start Writing a New Document Using the Template
1.    If you have not yet started to write your paper, please open Windows Explorer, se-lect the template file and click New in the file’s context menu to create a new doc-ument that is based on the template (do not open the template out of Word via File?Open. You would edit the template instead of creating a new document that is based on the template).
2.    You can easily find out whether a new document has been created by looking at the window’s title: it should read ‘Document1’ (or Document2, Document3, etc.).
3.    Maybe a security warning will pop up that asks you to activate the template’s ma-cros. You need to click ‘Enable’ to load and enable the template’s custom toolbars. This security warning will pop up every time you open the document.
4.    Save the document and name it with your name and a short form of the title.
2.2    Structuring Your Paper
Headings. Headings {style H 1..4} should be capitalized (i.e., all words except articles, prepositions, and conjunctions should be set with an initial capital). Words joined by a hyphen are subject to a special rule. If the first word can stand alone, the second word should be capitalized. Here are some examples of headings: “Criteria to Disprove Context-Freeness of Collage Languages”, “A User-Friendly and Extendable Data Distribution System”, “Multi-flip Networks: Parallelizing GenSAT”. Headings should, with the exception of the title {style title}, be aligned to the left. Only the first two levels of section headings should be numbered, as shown in Table 1 (this should be done automatically). The respective font sizes are also given in Table 1. Kindly refrain from using “0” when numbering your headings.
Table 1. Font sizes of headings {style table caption}
Heading level    Example    Font size and style
Title (centered)     Lecture Notes     14 point, bold
1st-level heading     1 Introduction     12 point, bold
2nd-level heading     2.1 Printing Area     10 point, bold
3rd-level heading     Run-in Heading in Bold. Text follows     10 point, bold
4th-level heading     Lowest Level Heading. Text follows     10 point, italic
Tables. You should use normal text {style normal text} for any table’s contents. Tables spanning more than one page are to be avoided. If you absolutely have to include a table spanning more than one page, make sure that the table heading is repeated on every page. Tables are to be numbered and captions should always be positioned above the tables.
Normal Text. You should use normal text {style normal text} (Times New Roman, font size 10) for the first paragraph in a chapter or after figures, tables, listings and formulas (without indentation) as well as for all following paragraphs within a chap-ter. Following paragraphs will be indented automatically.
Lemmas, Propositions, and Theorems. The numbers accorded to lemmas, proposi-tions, and theorems, etc. should appear in consecutive order, starting with Lemma 1. Please do not include section counters in the numbering like “Theorem 1.1”.
2.3    Figures
It is essential that all illustrations are as clear and as legible as possible. Vector graph-ics – instead of rasterized images – should be used for diagrams and schemas when-ever possible. Please check that the lines in line drawings are not interrupted and have a constant width. Grids and details within the figures must be clearly legible and may not be written one on top of the other. Line drawings are to have a resolution of at least 800 dpi (preferably 1200 dpi). The lettering in figures and tables should not use font sizes smaller than 6 pt (~ 2 mm character height). Figures are to be numbered and to have a caption {style figure caption} which should always be positioned under the figures.

Fig. 1.IMIS logo {style figurecaption}
Captions are set in 9-point type. If they are short, they are centered between the mar-gins (Fig. 1 shows an example). Longer captions, covering more than one line, are justified. Captions that do not constitute a full sentence do not have a period.
Text fragments of fewer than four lines should not appear at the tops or bottoms of pages, following a table or figure. In such cases, it is better to set the figures right at the top or right at the bottom of the page. A figure should never be placed in the mid-dle of a paragraph.
If screenshots are necessary, please make sure that the essential content is clear to the reader.
2.4    Formulas
Displayed equations or formulas {style displayed equation} are centered and set on a separate line (with an extra line or half line space above and below {style add space}). Displayed expressions should be numbered for reference {style add eq. num-ber}. The numbers should be consecutive within the contribution, with numbers en-closed in parentheses and set on the right margin. Please do not include section coun-ters in the numbering.
x + y = z    (1)
2.5    Footnotes
The superscript numeral used to refer to a footnote {style footnote} appears in the text either directly after the word to be discussed or – in relation to a phrase or a sentence – following the punctuation mark (comma, semicolon, or period). Please note that no footnotes may be included in the abstract.
2.6    Program Code
Program listings or program commands in the text are normally set in typewriter font {style prog. code}:
program Inflation (Output)
{Assuming annual inflation rates of 7%, 8%, and 10%,… years};
const MaxYears = 10;
var Year: 0..MaxYears;
Factor1, Factor2, Factor3: Real;
Year := 0;
Factor1 := 1.0; Factor2 := 1.0; Factor3 := 1.0;

until Year = MaxYears
2.7    Other Styles
Besides the above mentioned styles there are more useable format specifications:
•    Listings {style bulletitem or dashitem}
•    Numeration {style numitem}
•    Reference {style referenceitem}
•    List Level +/- {style list level + and list level -}
•    Add/Clear Space {style add space and clear space}
2.8    Citations and Bibliography
Authors using software tools for managing bibliographies (like Endnote, Citavi, Men-deley) can apply the preconfigured style format Lecture Notes in Computer Science.
For citations in the text, of tables and figures authors have to use square brackets and consecutive numbers. Numbers should be grouped where appropriate. We would write [1-5] but [1], [3], [5], etc. The numbers in the bibliography section are without square brackets.
References should be published materials accessible to the public. Internal technic-al reports may be cited only if they are easily accessible (i.e. you can give the address to obtain the r
eport within your citation) and may be obtained by any reader. Private communications should be acknowledged (e.g. with a footnote), not referenced. Please base your references on the examples given in the references section of these instructions and write all references using the latin alphabet. If the title of the book you are referring to is, e.g., in Russian or Chinese, then please write (in Russian) or (in Chinese) at the end of the transcript or translation of the title. Word may try to automatically ‘underline’ hotlinks in your references; the correct style is NO underlin-ing. Please make sure that all your sources are correctly listed in the reference section.
The references section at the end of this paper shows a sample reference list with entries for journal articles [1], an LNCS chapter [2], a book [3], proceedings without editors [4] and [5], as well as URLs [6], [7].
1.    Smith, T.F., Waterman, M.S.: Identification of Common Molecular Subsequences. J. Mol. Biol. 147, 195–197 (1981)
2.    May, P., Ehrlich, H.C., Steinke, T.: ZIB Structure Prediction Pipeline: Composing a Com-plex Biological Workflow through Web Services. In: Nagel, W.E., Walter, W.V., Lehner, W. (eds.) Euro-Par 2006. LNCS, vol. 4128, pp. 1148–1158. Springer, Heidelberg (2006)
3.    Foster, I., Kesselman, C.: The Grid: Blueprint for a New Computing Infrastructure. Morgan Kaufmann, San Francisco (1999)
4.    Czajkowski, K., Fitzgerald, S., Foster, I., Kesselman, C.: Grid Information Services for Distributed Resource Sharing. In: 10th IEEE International Symposium on High Performance Distributed Computing, pp. 181–184. IEEE Press, New York (2001)
5.    Foster, I., Kesselman, C., Nick, J., Tuecke, S.: The Physiology of the Grid: an Open Grid Services Architecture for Distributed Systems Integration. Technical report, Global Grid Forum (2002)
6.    National Center for Biotechnology Information, (Accessed: 22.03.2014)