Dependency Detection and Migration in Software Systems and Libraries

Total Page:16

File Type:pdf, Size:1020Kb

Dependency Detection and Migration in Software Systems and Libraries University of Calgary PRISM: University of Calgary's Digital Repository Graduate Studies The Vault: Electronic Theses and Dissertations 2014-10-01 Dependency Detection and Migration in Software Systems and Libraries Cossette, Bradley Edward Cossette, B. E. (2014). Dependency Detection and Migration in Software Systems and Libraries (Unpublished doctoral thesis). University of Calgary, Calgary, AB. doi:10.11575/PRISM/25551 http://hdl.handle.net/11023/1902 doctoral thesis University of Calgary graduate students retain copyright ownership and moral rights for their thesis. You may use this material in any way that is permitted by the Copyright Act or through licensing that has been assigned to the document. For uses that are not allowable under copyright legislation or licensing, you are required to seek permission. Downloaded from PRISM: https://prism.ucalgary.ca UNIVERSITY OF CALGARY Dependency Detection and Migration in Software Systems and Libraries by Bradley E. Cossette A THESIS SUBMITTED TO THE FACULTY OF GRADUATE STUDIES IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF DOCTOR OF PHILOSOPHY DEPARTMENT OF COMPUTER SCIENCE CALGARY, ALBERTA September, 2014 © Bradley E. Cossette 2014 Abstract Software systems must change over time or risk becoming obsolete, but direct changes can im­ pact dependent functionality. Software developers perform change impact analysis and redress using automated tools to identify dependency relationships affected by change, and to recommend adaptations. However, these tools are restricted in their application: dependency analysis tools are language-specific but many systems are implemented using multiple languages, while recom­ menders are poor at identifying adaptations for change impacts from external libraries. This work proposes using semi-automated approaches for supporting change impact analysis and redress, in which the developer is relied upon to provide key details of dependency syntax or examples of correct adaptations. From such information, tool support can be generated that is appropriately configured for the developer’s software, and that can be further refined by the developer through additional details or examples until it is sufficiently accurate for their needs. Four studies validate this thesis. The first involves the semi-automated DSKETCH tool for polylingual dependency analysis, which requires developers to detail only key syntax using a sim­ plified notation; it then uses this syntax to identify where potential dependencies exist. Devel­ opers were able to successfully configure and use DSKETCH on polylingual systems with only a short period of training. The second study examines how software libraries and their application programming interfaces (APIs) evolve over successive versions. The study found that existing recommenders are generally unsuccessful, and that most observed changes could not be automati­ cally migrated. The third study introduces the UMAMI tool that detects correspondences between the syntactic structure of the old API functionality and possible replacements in the new library version to recommend adaptations for API changes. The fourth study examines how change rec­ ommenders could be hybridized in a flexible fashion, by relying on developer-provided examples of correct redress of API changes to tailor recommendations to a library’s particular characteristics. ii Acknowledgments We cannot tell the precise moment when friendship is formed. As in filling a vessel drop by drop, there is at last a drop which makes it run over; so in a series of kindnesses there is at last one which makes the heart run over. James Boswell, The Life of Samuel Johnson Completing this dissertation has been the story of many kindnesses from friends, family, and God, that helped me on the way. First, I am grateful to my supervisor Robert Walker, for his mentorship, support, and especially his friendship over the last eight years. I could write much about his character, and integrity that I now try to emulate in my own work, but I appreciate most his years of encouragement, and his constant goal of training me to be his colleague, and not just his student: I see echoes of his writing and perspective in my work every day. Many lab-mates have come and gone over the years. Rylan Cottrell, who started his Master’s and PhD degrees with me, and without whom I would have never survived Cryptography, is the first and foremost I must thank. For eight years you were my friend and co-conspirator, and I will miss your boundless willingness to talk about anything: whether God and religion, relationships, research, or the importance of Dr. Who to science fiction. Reid Holmes still acts as my big brother, introducing me to the research community at large, and always willing to offer advice. Puneet Kapur, who is the first programmer and computer scientist I know to also be a medical doctor, was a font of friendship, humour, insight, and wisdom. Thanking the cast of characters in our lab would not be complete without mentioning Craig Schock, Soha Makady, Hamid Baghi, Elham Moazzen, and Mostafa Sayed. Thank you as well to Leanne Wu, Tyson Kendon, Sean Nichols, and everyone else who also shared the joys and travails of grad life with me at Tuesday Tea. I could not have prouder parents in Bernard and Diana Cossette, and an even prouder grand­ mother in Grace Kine, who have supported me financially, emotionally, and through prayer. My grandparents and great-grandparents have loved books, knowledge, and teaching, and it was a spe­ cial moment when I realized that my father was also a published author of technical papers in his iii field; I follow in all their footsteps. My brothers and their wives—Brandon and Christine Cos­ sette, Aaron and Alicia Cossette—have been a comfort and encouragement without fail, and your joy over my accomplishments is a shadow of how proud I am of you and your children (Kael, Courtney, and Isaiah). I am also grateful for my wife’s family: Kent and Susan Dunfield, Michael, Susan, and Jacob Dunfield, and Robert Dunfield, who treated me as one of their own from the day we met, even trying to read my research papers to show their support. Denis and Laura Perron, thank you for your prayers, hospitality, and most of all for introducing me to my wife. Justin and Kellie Agnew Clark, thank you for being so accepting and gracious: your company is always treasured. I am especially grateful for the family of friends and mentors I had at Bethany Chapel in Calgary, who showered me with kindness and grace throughout my studies. But I have saved my deepest thanks for my greatest supporter, my wife Charlotte who fell in love with this PhD student. You chose to walk with me the whole way on this adventure, following me to Calgary from Vancouver, sharing your amazing circle of friends with me, embracing my family, and now following me again to Montreal´ and McGill University. I love you, and you are the only one who knows every joy and sorrow I faced during this degree, because you chose to share for better and worse with me. Sharing this with you is the greatest joy of this degree. Finally, I want to thank my God, and my Saviour Jesus Christ, who has been faithful to carry me through this entire journey, even when I doubted I would ever finish. It was a message from Jeremiah 32:1–15 six years ago that convinced me that God would see me through my PhD; may I always remember His faithfulness to bring me through the impossibilities in life. BRADLEY COSSETTE September 22, 2014 Montreal,´ Quebec´ iv For Charlotte, who took my hand, and walked the way with me. v Table of Contents Abstract ........................................... ii Acknowledgments ...................................... iii Table of Contents ...................................... vi List of Tables ........................................ x List of Figures ........................................ xii 1 Introduction ...................................... 1 1.1 Overview of Related Work .............................. 3 1.2 Semi-Automating Developer Configured Solutions . 6 1.3 Thesis Statement ................................... 8 1.4 Organization ...................................... 9 1.5 Publications ...................................... 10 2 Motivation ....................................... 11 2.1 Proactive Change: Polylingual Dependency Analysis . 11 2.2 Reactive Change: API Migration and Redress . 14 2.3 Summary: Motivation ................................. 18 3 Related Work ..................................... 20 3.1 Change Impact and Dependency Analysis ...................... 21 3.1.1 Formulating Change Impact ......................... 22 3.1.2 Reverse Engineering and Tools For Dependency Analysis . 24 3.1.3 Summary: Change Impact and Dependency Analysis . 30 3.2 Polylingual Dependency Analysis .......................... 31 3.2.1 Lexically-Aware Tools in Polylingual Contexts . 33 3.2.2 Syntactically-Aware Tools in Polylingual Contexts . 34 3.2.3 Semantically-Aware Tools in Polylingual Contexts . 37 3.2.4 Partial-Language Recognition Approaches . 39 3.2.5 Summary: Polylingual Dependency Analysis . 42 3.3 Library Evolution and API Migration ........................ 43 3.3.1 Proactive Library Migration ......................... 45 3.3.2 Reactive Library Migration .......................... 47 3.3.3 Recommending appropriate reactions . 50 3.3.4 Redressing library change impact ...................... 55 3.3.5 Summary: Library Migration and API Evolution . 57 3.4 Empirical Studies of API Change ........................... 58
Recommended publications
  • Lucene in Action Second Edition
    Covers Apache Lucene 3.0 IN ACTION SECOND EDITION Michael McCandless Erik Hatcher , Otis Gospodnetic FOREWORD BY DOUG CUTTING MANNING www.it-ebooks.info Praise for the First Edition This is definitely the book to have if you’re planning on using Lucene in your application, or are interested in what Lucene can do for you. —JavaLobby Search powers the information age. This book is a gateway to this invaluable resource...It suc- ceeds admirably in elucidating the application programming interface (API), with many code examples and cogent explanations, opening the door to a fine tool. —Computing Reviews A must-read for anyone who wants to learn about Lucene or is even considering embedding search into their applications or just wants to learn about information retrieval in general. Highly recommended! —TheServerSide.com Well thought-out...thoroughly edited...stands out clearly from the crowd....I enjoyed reading this book. If you have any text-searching needs, this book will be more than sufficient equipment to guide you to successful completion. Even, if you are just looking to download a pre-written search engine, then this book will provide a good background to the nature of information retrieval in general and text indexing and searching specifically. —Slashdot.org The book is more like a crystal ball than ink on pape--I run into solutions to my most pressing problems as I read through it. —Arman Anwar, Arman@Web Provides a detailed blueprint for using and customizing Lucene...a thorough introduction to the inner workings of what’s arguably the most popular open source search engine...loaded with code examples and emphasizes a hands-on approach to learning.
    [Show full text]
  • Apache Lucene Searching the Web and Everything Else
    Apache Lucene Searching the Web and Everything Else Daniel Naber Mindquarry GmbH ID 380 2 AGENDA > What's a search engine > Lucene Java – Features – Code example > Solr – Features – Integration > Nutch – Features – Usage example > Conclusion and alternative solutions 3 About the Speaker > Studied computational linguistics > Java developer > Worked 3.5 years for an Enterprise Search company (using Lucene Java) > Now at Mindquarry, creators on an Open Source Collaboration Software (Mindquarry uses Solr) 4 Question: What is a Search Engine? > Answer: A software that – builds an index on text – answers queries using that index “But we have a database already“ – A search engine offers Scalability Relevance Ranking Integrates different data sources (email, web pages, files, database, ...) 5 What is a search engine? (cont.) > Works on words, not on substrings auto != automatic, automobile > Indexing process: – Convert document – Extract text and meta data – Normalize text – Write (inverted) index – Example: Document 1: “Apache Lucene at Jazoon“ Document 2: “Jazoon conference“ Index: apache -> 1 conference -> 2 jazoon -> 1, 2 lucene -> 1 6 Apache Lucene Overview > Lucene Java 2.2 – Java library > Solr 1.2 – http-based index and search server > Nutch 0.9 – Internet search engine software > http://lucene.apache.org 7 Lucene Java > Java library for indexing and searching > No dependencies (not even a logging framework) > Works with Java 1.4 or later > Input for indexing: Document objects – Each document: set of Fields, field name: field content (plain text) > Input for searching: query strings or Query objects > Stores its index as files on disk > No document converters > No web crawler 8 Lucene Java Users > IBM OmniFind Yahoo! Edition > technorati.com > Eclipse > Furl > Nuxeo ECM > Monster.com > ..
    [Show full text]
  • Magnify Search Security and Administration Release 8.2 Version 04
    Magnify Search Security and Administration Release 8.2 Version 04 April 08, 2019 Active Technologies, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iWay, iWay Software, Parlay, PC/FOCUS, RStat, Table Talk, Web390, WebFOCUS, WebFOCUS Active Technologies, and WebFOCUS Magnify are registered trademarks, and DataMigrator and Hyperstage are trademarks of Information Builders, Inc. Adobe, the Adobe logo, Acrobat, Adobe Reader, Flash, Adobe Flash Builder, Flex, and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Due to the nature of this material, this document refers to numerous hardware and software products by their trademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by their respective companies. It is not this publisher's intent to use any of these names generically. The reader is therefore cautioned to investigate all claimed trademark rights before using any of these names other than to refer to the product described. Copyright © 2019, by Information Builders, Inc. and iWay Software. All rights reserved. Patent Pending. This manual, or parts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc. Contents Preface ......................................................................... 7 Conventions ......................................................................... 7 Related Publications .................................................................
    [Show full text]
  • Enterprise Search Technology Using Solr and Cloud Padmavathy Ravikumar Governors State University
    Governors State University OPUS Open Portal to University Scholarship All Capstone Projects Student Capstone Projects Spring 2015 Enterprise Search Technology Using Solr and Cloud Padmavathy Ravikumar Governors State University Follow this and additional works at: http://opus.govst.edu/capstones Part of the Databases and Information Systems Commons Recommended Citation Ravikumar, Padmavathy, "Enterprise Search Technology Using Solr and Cloud" (2015). All Capstone Projects. 91. http://opus.govst.edu/capstones/91 For more information about the academic degree, extended learning, and certificate programs of Governors State University, go to http://www.govst.edu/Academics/Degree_Programs_and_Certifications/ Visit the Governors State Computer Science Department This Project Summary is brought to you for free and open access by the Student Capstone Projects at OPUS Open Portal to University Scholarship. It has been accepted for inclusion in All Capstone Projects by an authorized administrator of OPUS Open Portal to University Scholarship. For more information, please contact [email protected]. ENTERPRISE SEARCH TECHNOLOGY USING SOLR AND CLOUD By Padmavathy Ravikumar Masters Project Submitted in partial fulfillment of the requirements For the Degree of Master of Science, With a Major in Computer Science Governors State University University Park, IL 60484 Fall 2014 ENTERPRISE SEARCH TECHNOLOGY USING SOLR AND CLOUD 2 Abstract Solr is the popular, blazing fast open source enterprise search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted search, near real-time indexing, dynamic clustering, database in9tegration, rich document (e.g., Word, PDF) handling, and geospatial search. Solr is highly reliable, scalable and fault tolerant, providing distributed indexing, replication and load-balanced querying, automated failover and recovery, centralized configuration and more.
    [Show full text]
  • Unravel Data Systems Version 4.5
    UNRAVEL DATA SYSTEMS VERSION 4.5 Component name Component version name License names jQuery 1.8.2 MIT License Apache Tomcat 5.5.23 Apache License 2.0 Tachyon Project POM 0.8.2 Apache License 2.0 Apache Directory LDAP API Model 1.0.0-M20 Apache License 2.0 apache/incubator-heron 0.16.5.1 Apache License 2.0 Maven Plugin API 3.0.4 Apache License 2.0 ApacheDS Authentication Interceptor 2.0.0-M15 Apache License 2.0 Apache Directory LDAP API Extras ACI 1.0.0-M20 Apache License 2.0 Apache HttpComponents Core 4.3.3 Apache License 2.0 Spark Project Tags 2.0.0-preview Apache License 2.0 Curator Testing 3.3.0 Apache License 2.0 Apache HttpComponents Core 4.4.5 Apache License 2.0 Apache Commons Daemon 1.0.15 Apache License 2.0 classworlds 2.4 Apache License 2.0 abego TreeLayout Core 1.0.1 BSD 3-clause "New" or "Revised" License jackson-core 2.8.6 Apache License 2.0 Lucene Join 6.6.1 Apache License 2.0 Apache Commons CLI 1.3-cloudera-pre-r1439998 Apache License 2.0 hive-apache 0.5 Apache License 2.0 scala-parser-combinators 1.0.4 BSD 3-clause "New" or "Revised" License com.springsource.javax.xml.bind 2.1.7 Common Development and Distribution License 1.0 SnakeYAML 1.15 Apache License 2.0 JUnit 4.12 Common Public License 1.0 ApacheDS Protocol Kerberos 2.0.0-M12 Apache License 2.0 Apache Groovy 2.4.6 Apache License 2.0 JGraphT - Core 1.2.0 (GNU Lesser General Public License v2.1 or later AND Eclipse Public License 1.0) chill-java 0.5.0 Apache License 2.0 Apache Commons Logging 1.2 Apache License 2.0 OpenCensus 0.12.3 Apache License 2.0 ApacheDS Protocol
    [Show full text]
  • IBM Cloudant: Database As a Service Fundamentals
    Front cover IBM Cloudant: Database as a Service Fundamentals Understand the basics of NoSQL document data stores Access and work with the Cloudant API Work programmatically with Cloudant data Christopher Bienko Marina Greenstein Stephen E Holt Richard T Phillips ibm.com/redbooks Redpaper Contents Notices . 5 Trademarks . 6 Preface . 7 Authors. 7 Now you can become a published author, too! . 8 Comments welcome. 8 Stay connected to IBM Redbooks . 9 Chapter 1. Survey of the database landscape . 1 1.1 The fundamentals and evolution of relational databases . 2 1.1.1 The relational model . 2 1.1.2 The CAP Theorem . 4 1.2 The NoSQL paradigm . 5 1.2.1 ACID versus BASE systems . 7 1.2.2 What is NoSQL? . 8 1.2.3 NoSQL database landscape . 9 1.2.4 JSON and schema-less model . 11 Chapter 2. Build more, grow more, and sleep more with IBM Cloudant . 13 2.1 Business value . 15 2.2 Solution overview . 16 2.3 Solution architecture . 18 2.4 Usage scenarios . 20 2.5 Intuitively interact with data using Cloudant Dashboard . 21 2.5.1 Editing JSON documents using Cloudant Dashboard . 22 2.5.2 Configuring access permissions and replication jobs within Cloudant Dashboard. 24 2.6 A continuum of services working together on cloud . 25 2.6.1 Provisioning an analytics warehouse with IBM dashDB . 26 2.6.2 Data refinement services on-premises. 30 2.6.3 Data refinement services on the cloud. 30 2.6.4 Hybrid clouds: Data refinement across on/off–premises. 31 Chapter 3.
    [Show full text]
  • Final Report CS 5604: Information Storage and Retrieval
    Final Report CS 5604: Information Storage and Retrieval Solr Team Abhinav Kumar, Anand Bangad, Jeff Robertson, Mohit Garg, Shreyas Ramesh, Siyu Mi, Xinyue Wang, Yu Wang January 16, 2018 Instructed by Professor Edward A. Fox Virginia Polytechnic Institute and State University Blacksburg, VA 24061 1 Abstract The Digital Library Research Laboratory (DLRL) has collected over 1.5 billion tweets and millions of webpages for the Integrated Digital Event Archiving and Library (IDEAL) and Global Event Trend Archive Research (GETAR) projects [6]. We are using a 21 node Cloudera Hadoop cluster to store and retrieve this information. One goal of this project is to expand the data collection to include more web archives and geospatial data beyond what previously had been collected. Another important part in this project is optimizing the current system to analyze and allow access to the new data. To accomplish these goals, this project is separated into 6 parts with corresponding teams: Classification (CLA), Collection Management Tweets (CMT), Collection Management Webpages (CMW), Clustering and Topic Analysis (CTA), Front-end (FE), and SOLR. This report describes the work completed by the SOLR team which improves the current searching and storage system. We include the general architecture and an overview of the current system. We present the part that Solr plays within the whole system with more detail. We talk about our goals, procedures, and conclusions on the improvements we made to the current Solr system. This report also describes how we coordinate with other teams to accomplish the project at a higher level. Additionally, we provide manuals for future readers who might need to replicate our experiments.
    [Show full text]
  • Apache Lucene™ Integration Reference Guide
    Hibernate Search Apache Lucene™ Integration Reference Guide 3.3.0.Final Preface ............................................................................................................................ vii 1. Getting started ............................................................................................................. 1 1.1. System Requirements ......................................................................................... 1 1.2. Using Maven ...................................................................................................... 2 1.3. Configuration ...................................................................................................... 3 1.4. Indexing ............................................................................................................. 7 1.5. Searching ........................................................................................................... 7 1.6. Analyzer ............................................................................................................. 8 1.7. What's next ...................................................................................................... 10 2. Architecture ............................................................................................................... 11 2.1. Overview .......................................................................................................... 11 2.2. Back end .........................................................................................................
    [Show full text]
  • Apache Lucene - Overview
    Apache Lucene - Overview Table of contents 1 Apache Lucene...................................................................................................................2 2 The Apache Software Foundation..................................................................................... 2 3 Lucene News......................................................................................................................2 3.1 27 November 2011 - Lucene Core 3.5.0...................................................................... 2 3.2 26 October 2011 - Java 7u1 fixes index corruption and crash bugs in Apache Lucene Core and Apache Solr.............................................................................................................3 3.3 14 September 2011 - Lucene Core 3.4.0......................................................................3 3.4 28 July 2011 - WARNING: Index corruption and crashes in Apache Lucene Core / Apache Solr with Java 7.........................................................................................................4 3.5 1 July 2011 - Lucene Core 3.3.....................................................................................5 3.6 4 June 2011 - Lucene Core 3.2.................................................................................... 6 3.7 31 March 2011 - Lucene Core 3.1............................................................................... 6 3.8 3 December 2010 - Lucene Java 3.0.3 and 2.9.4 available.......................................... 7 3.9 18 June 2010 -
    [Show full text]
  • Open Source and Third Party Documentation
    Open Source and Third Party Documentation Verint.com Twitter.com/verint Facebook.com/verint Blog.verint.com Content Introduction.....................2 Licenses..........................3 Page 1 Open Source Attribution Certain components of this Software or software contained in this Product (collectively, "Software") may be covered by so-called "free or open source" software licenses ("Open Source Components"), which includes any software licenses approved as open source licenses by the Open Source Initiative or any similar licenses, including without limitation any license that, as a condition of distribution of the Open Source Components licensed, requires that the distributor make the Open Source Components available in source code format. A license in each Open Source Component is provided to you in accordance with the specific license terms specified in their respective license terms. EXCEPT WITH REGARD TO ANY WARRANTIES OR OTHER RIGHTS AND OBLIGATIONS EXPRESSLY PROVIDED DIRECTLY TO YOU FROM VERINT, ALL OPEN SOURCE COMPONENTS ARE PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. Any third party technology that may be appropriate or necessary for use with the Verint Product is licensed to you only for use with the Verint Product under the terms of the third party license agreement specified in the Documentation, the Software or as provided online at http://verint.com/thirdpartylicense. You may not take any action that would separate the third party technology from the Verint Product. Unless otherwise permitted under the terms of the third party license agreement, you agree to only use the third party technology in conjunction with the Verint Product.
    [Show full text]
  • Apache Lucene - a Library Retrieving Data for Millions of Users
    Apache Lucene - a library retrieving data for millions of users Simon Willnauer Apache Lucene Core Committer & PMC Chair [email protected] / [email protected] Friday, October 14, 2011 About me? • Lucene Core Committer • Project Management Committee Chair (PMC) • Apache Member • BerlinBuzzwords Co-Founder • Addicted to OpenSource 2 Friday, October 14, 2011 Apache Lucene - a library retrieving data for .... Agenda ‣ Apache Lucene a historical introduction ‣ (Small) Features Overview ‣ The Lucene Eco-System ‣ Upcoming features in Lucene 4.0 ‣ Maintaining superior quality in Lucene (backup slides) ‣ Questions 3 Friday, October 14, 2011 Apache Lucene - a brief introduction • A fulltext search library entirely written in Java • An ASF Project since 2001 (happy birthday Lucene) • Founded by Doug Cutting • Grown up - being the de-facto standard in OpenSource search • Starting point for a other well known projects • Apache 2.0 License 4 Friday, October 14, 2011 Where are we now? • Current Version 3.4 (frequent minor releases every 2 - 4 month) • Strong Backwards compatibility guarantees within major releases • Solid Inverted-Index implementation • large committer base from various companies • well established community • Upcoming Major Release is Lucene 4.0 (more about this later) 5 Friday, October 14, 2011 (Small) Features Overview • Fulltext search • Boolean-, Range-, Prefix-, Wildcard-, RegExp-, Fuzzy-, Phase-, & SpanQueries • Faceting, Result Grouping, Sorting, Customizable Scoring • Large set of Language / Text-Processing
    [Show full text]
  • A Secured Cloud System Based on Log Analysis
    San Jose State University SJSU ScholarWorks Master's Projects Master's Theses and Graduate Research Fall 2015 A Secured Cloud System based on Log Analysis Sindhusha Doddapaneni San Jose State University Follow this and additional works at: https://scholarworks.sjsu.edu/etd_projects Part of the Computer Sciences Commons Recommended Citation Doddapaneni, Sindhusha, "A Secured Cloud System based on Log Analysis" (2015). Master's Projects. 560. DOI: https://doi.org/10.31979/etd.qgq2-2cpa https://scholarworks.sjsu.edu/etd_projects/560 This Master's Project is brought to you for free and open access by the Master's Theses and Graduate Research at SJSU ScholarWorks. It has been accepted for inclusion in Master's Projects by an authorized administrator of SJSU ScholarWorks. For more information, please contact [email protected]. A Secured Cloud System based on Log Analysis A Writing Project Report Presented to The Faculty of the Department of Computer Science San Jose State University In Partial Fulfillment Of the Requirements for the Degree Master of Science By Sindhusha Doddapaneni DECEMBER 2015 © 2015 Sindhusha Doddapaneni ALL RIGHTS RESERVED The Designated Project Committee Approves the Project Titled A Secured Cloud System based on Log Analysis By Sindhusha Doddapaneni APPROVED FOR THE DEPARTMENTS OF COMPUTER SCIENCE SAN JOSE STATE UNIVERSITY DECEMBER 2015 Dr. Melody Moh (Department of Computer Science) Dr. Teng Moh (Department of Computer Science) Mr. John Cribbs (Senior Director @ FICO) ABSTRACT Now-a-days, enterprises’ acceptance over the Cloud is increasing but businesses are now finding issues related to security. Everyday, users store a large amount of data in the Cloud and user input may be malicious.
    [Show full text]