Automated Formal Static Analysis and Retrieval of Source Code - JKU

More documents

Recommendations

Info

3.2. INTEGRATION OF MINDBREEZE CODE SEARCH INTO MINDBREEZE ENTERPRISE SEARCH45 The class Icon provides icons specific for every search hit. It contains methods for retrieving a collection of search hits and then provides them icons depending on their categoryclass. • public ContextItem[][] getBulked(Class
46CHAPTER 3. CODE SEARCH INTEGRATION FACILITY INTO MINDBREEZE ENTERPRISE SEARCH Figure 3.7: CodeSearch Context Provider Classes 1. a unique category identifier and category display name; 2. the description of the metadata for each CodeSearch artifact; 3. a graphical icon representing the category in the user interface. These requirements are solved by deploying on the server a category descriptor file and a category icon file, respectively. Moreover, we want that the results displayed to the end users to have context specific information. For this purpose, we have to provide to the Query Service (again by deploying on the server) an appropriate context provider implementation for the CodeSearch data source. Deployment is done by the command line tool mesextension used for the infrastructure configuration. In was created during the MES development and used installing or uninstalling context or authorization provider plug-ins, category descriptors and category icons. Usage: mesextension [OPTIONS] install|uninstall 3.2.3.1 Deploying the CodeSearch Category Descriptor, Category Icon and Context Provider Deploying the CodeSearch Category Descriptor A category descriptor is a XML file which contains the unique identifier, the display name and descriptions for each artifact for the data source CodeSearch. A fragment of the CodeSearch category descriptor (CodeSearchCategoryDescriptor.xml) is listed:
Page 1:
J O H A N N E S K E P L E R U N I V
Page 5: Abstract In this thesis two approac
Page 8 and 9: viii
Page 10 and 11: Chapter 1 Introduction From the han
Page 12 and 13: 3 Contributions of the Thesis The s
Page 14 and 15: Next section starts by describing t
Page 16 and 17: Chapter 2 Program Verification by S
Page 18 and 19: 2.1. BACKGROUND 9 From the practica
Page 20 and 21: 2.1. BACKGROUND 11 A program is see
Page 22 and 23: 2.2. FORWARD SYMBOLIC EXECUTION IN
Page 28 and 29: 2.3. THE SIMPLIFICATION OF THE VERI
Page 30 and 31: 2.4. IMPLEMENTATION AND EXAMPLES 21
Page 36 and 37: Chapter 3 Code Search Integration F
Page 38 and 39: 3.1. BACKGROUND 29 Figure 3.1: Sour
Page 40 and 41: 3.1. BACKGROUND 31 The programming
Page 42 and 43: 3.2. INTEGRATION OF MINDBREEZE CODE
Page 62 and 63: Chapter 4 Conclusions In this thesi
Page 64 and 65: 55 How the database is used. For ea
Page 66 and 67: Bibliography [***] ***. Mindbreeze
Page 68 and 69: BIBLIOGRAPHY 59 [Hoa69] [How73] [KF
Page 70 and 71: BIBLIOGRAPHY 61 [VHBP00] [Wil94] W.
Page 72: Eidesstattliche Erklärung Ich erkl
show all

Automated Formal Static Analysis and Retrieval of Source Code - JKU

Create successful ePaper yourself

Delete template?

Save as template?