Software Engineering Laboratory, Osaka University

Slides:



Advertisements
Similar presentations
Poster & Project Presentations The Robert Gordon University
Advertisements

Data Mining and Text Analytics GATE, by Joel Bywater.
How do you know if your brochure is effective with the targeted audience? Usability research: explores how users interact with a product such as a brochure.
Semantic Matching of candidates’ profile with job data from Linkedln PRESENTED BY: TING XIAO SARABPREET KAUR DHILLON.
Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University Extraction of.
Investigating JAVA Classes with Formal Concept Analysis Uri Dekel Based on M.Sc. work at the Israeli Institute of Technology. To appear:
Senior Project Database: Design and Usability Evaluation Stephanie Cheng Rachelle Hom Ronald Mg Hoang Bao CSC 484 – Winter 2005.
PaperScope: Visually Exploring the ADS Mark Holliman VOTECH Web Developer University of Edinburgh ADASS XVII, London,
State coverage: an empirical analysis based on a user study Dries Vanoverberghe, Emma Eyckmans, and Frank Piessens.
Visualization By: Simon Luangsisombath. Canonical Visualization  Architectural modeling notations are ways to organize information  Canonical notation.
Software Configuration Management (SCM)
Chapter 11-Multimedia Authoring Tools. Overview Introduction to multimedia authoring tools. Types of authoring tools. Cross-platform authoring notes.
Virginia Science SOL’s  3.1 The student will demonstrate an understanding of scientific reasoning, logic, and the nature of science by planning and conducting.
Software Configuration Management
Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University What Kinds of.
Workshop on Computer-Supported Knowledge Collaboration, Shanghai, July 7, Current Status of Software Industry in Japan.
AGENDA Introduction to Virtual Mechanic Demo Architectural diagram and summary QA steps and user acceptance testing Bugs in the software Feedback from.
Agenda Introduction Overview of White-box testing Basis path testing
SHAREPOINT BRANDING SHAREPOINT PAKISTAN USER GROUP – FEB 2012.
Samad Paydar Web Technology Lab. Ferdowsi University of Mashhad 10 th August 2011.
Software Quality Assurance
Identifying needs and establishing requirements
Lesson 8. Test 1 Topics Browser incompatibility Design Tips Site Navigation Browser- safe color Monitor resolution Content Copyright Use of tables vs.
Creating documentation and metadata: Recording provenance and context Jeff Arnfield National Climatic Data Center Version a1.0 Review Date.
Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University VerXCombo: An.
Presented by: Ashgan Fararooy Referenced Papers and Related Work on:
From Under Sea to Outer Space The video is part of NASA’s Liftoff to Learning. See the Featured Links for a link to NASA’s resources.
Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University IWPSE 2003 Program.
Empirical Estimation Models Based upon historic data Basic Structure E = A + B * (ev) C where A, B, c are empirical constants ‘ev’ is the effort in terms.
Generating Software Documentation in Use Case Maps from Filtered Execution Traces Edna Braun, Daniel Amyot, Timothy Lethbridge University of Ottawa, Canada.
Community Codes Free and shared resource Ongoing distributed development by both research and operational communities – Maintained under version control.
Web 2.0: Making the Web Work for You, Illustrated Unit A: Research 2.0.
1 Evaluating the User Experience in CAA Environments: What affects User Satisfaction? Gavin Sim Janet C Read Phil Holifield.
BTT presentation to SG-6, Osaka, Japan, March Browse Task Team Progress to date, future plan 6th SG Meeting, Osaka Osamu Ochiai (NASDA) Browse Task.
Visualization of version control and issue tracking data as a tool of software analytics.
4. How did you use media technologies in the construction, research, planning and evaluation stages?
Thinking of Drupal 8? Get started with the resources.
Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University Software Ingredients:
Interaction and Animation on Geolocalization Based Network Topology by Engin Arslan.
Systems Development Process and Methodologies Dr. T. Ravichandran.
How to write an effective RFP
Software Configuration Management
Software Project Configuration Management
Writing a sound proposal
A lustrum of malware network communication: Evolution & insights
Chapter 18 Maintaining Information Systems
Chapter 1 Reasons to study concepts of PLs Programming Domains
David Shepherd, Zachary P. Fry, Emily Hill, Lori Pollock, and K
Christopher Scaffidi Center for Applied Systems and Software
Comparison of Social Networks by Likhitha Ravi
CHAPTER 8 Multimedia Authoring Tools
Quicken Tech Support Phone Number One of the top software there is, the quicken software can pose a number of trouble and if you are new.
Ontology Evolution: A Methodological Overview
A Generalized Model for Visualizing Library Popularity, Adoption, and Diffusion within a Software Ecosystem Raula Gaikovina Kula, Coen De Roover, Daniel.
Increased Efficiency and Effectiveness
Basic Statistics Psychologists Marc Brysbaert for Book Tour
Boris Todorov1, Raula Gaikovina Kula2, Takashi Ishio2, Katsuro Inoue1
..
Personal Software Process Software Estimation
Visualizing the Evolution of Systems and their Library Dependencies
Raula Gaikovina Kula, Daniel German, Takashi Ishio, Katsuro Inoue
Document Design Justine Nielsen April 28, 2003
Broadvine Support Portal
Software Engineering I Fall 2017
Overview The World Wide Web has changed the way that people
White Box testing & Inspections
Inductive Clustering: A technique for clustering search results Hieu Khac Le Department of Computer Science - University of Illinois at Urbana-Champaign.
Why do we refactor? Technical Debt Items Versus Size: A Forensic Investigation of What Matters Hello everyone, I’m Ehsan Zabardast I am a PhD candidate.
Session 3.7: Implementing the geospatial data management cycle (Part 6): Data distribution, use, and update MODULE 3: GEOSPATIAL DATA MANAGEMENT Session.
Presentation transcript:

Software Engineering Laboratory, Osaka University SoL Mantra: Visualizing Library Update Complexity Through Orbital Layout and Coexistence Coefficient Boris Todorov Master’s Candidate Software Engineering Laboratory, Osaka University

Problem Background Keeping Libraries up to Date Am I using the latest version of a library? Software Developer Software System Bug If I update, what other libraries will be affected? New Features Tracking library evolution supports-color babel-core Library repository glob bluebird NPM Dependencies / Libraries char-spinner mocha

Previous Research Kula et al: Visualized circularly a software’s dependencies with added historical data; Drawbacks: too much information and became overwhelming for inexperienced users Yano et al: Visualized popular library version combinations to assist software maintenance; Drawbacks: was limited to 3 at a time

Basic Concepts The Solar System Metaphor – we selected for our visualization the Orbital Layout powered by D3.Js as our main visualization technique, deriving that a software system is similar to the solar system. Software – the program whose dependencies to other libraries are our concern for visualization; Library – the programs used by the system or other libraries, forming library dependency directed graph; Coexistence coefficient (cc) – a binary relation between two libraries (nodes) in an ecosystem, where those two libraries are used by at least one common library or common system.

Coexistence Coefficient (cc) Library A – Q, D, J, F, E Library B – J, F, E, Z F E J Q A B 𝐶𝐶𝐴(𝐵)= |𝑈𝑠𝑒𝑟𝑠 𝐴 ∩𝑈𝑠𝑒𝑟𝑠 𝐵| |𝑈𝑠𝑒𝑟𝑠 𝐴| D Z 6884 ∩3165 6884 = 3158 6884 ≈0.4587=45.87% Low cc score – safe to update High cc score – high complexity

SoL Mantra Example Model Library A Explanation A and B cc Library B

SoL Mantra General Comprehension Survey Conducted a survey using google forms with 19 participants in total. Survey Goals – test tool comprehension amongst inexperienced audience and how well users understand the coexistence logic. Survey RQ1 – Is the tool intuitive and easy to use? Survey RQ2 – Do the users understand coexistence?

General Tool Comprehension Tasks Results General comprehension tasks 3 simple questions regarding our visual cues: What is the system represented – 100% answered correctly How many libraries does the software system use – 94.7% How many libraries are outdated (if any) – 94.7%

Survey SoL Mantra – “stripe”

Coexistence Coefficient Comprehension Results – Case “mocha” Further Investigate Safe to update

Coexistence Coefficient Comprehension Results – Case “eslint” Further Investigate Safe to update

Post Task Survey Results – Is the tool intuitive or not? Natural Counter-intuitive

Post Task Survey Results – Was the tool easy to understand? Difficult/ Confusing Very easy

Threats to Validity Collected data is based on established projects. The tool was tested only on the NPM ecosystem packages. The tested projects could have specific reasoning for the version used that we are unaware. Survey participants count (19). Survey users are mostly students that don’t have experience in the field.

Summary We created the SoL Mantra tool to visualize library update complexity. We tested empirically with results from 23 projects and presented these results at VISSOFT 2017 in Shanghai We deployed an online survey to validate the usefulness and readability of our tool amongst inexperienced users.