LaQuSo is an activity of Technische Universiteit Eindhoven SQuAVisiT: A Software Quality Assessment and Visualisation Toolset Serguei Roubtsov, Alex Telea,

Slides:

Advertisements

Similar presentations

VirtualSim Inc. Real tools for virtual worlds Presentation.

Advertisements

Making the System Operational

LaQuSo is an activity of 3TU and Radboud Universiteit Nijmegen Maintainability of Front-End commissioned by drs. Reinier Post dr. Serguei Roubtsov Peter.

Company Confidential 1 © 2005 Nokia DBUpgradeTool_ ppt / / JMa A Database Upgrade Tool Nokia Networks Jukka Maaranen.

Test Case Management and Results Tracking System October 2008 D E L I V E R I N G Q U A L I T Y (Short Version)

Software Visualization Using Hierarchical Edge Bundles and Massive Sequence Views Danny Holten and Jarke J. van Wijk Eindhoven University of Technology.

© Chinese University, CSE Dept. Software Engineering / Software Engineering Topic 1: Software Engineering: A Preview Your Name: ____________________.

Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.

NGT Information Technology Technical Discussion Bob DeHoff Info Tech, Inc.

Documentation Generators: Internals of Doxygen John Tully.

Application Architecture T H E S O C R A T E S G R O U P, I N C.

SWE 316: Software Design and Architecture

Building Documentation Generators Arie van Deursen Tobias Kuipers CWI, The Netherlands.

Components and Architecture CS 543 – Data Warehousing.

Application architectures

Introduction to z/OS Basics © 2006 IBM Corporation Chapter 8: Designing and developing applications for z/OS.

1 Integration and Extension Hohmann Chapter 8.

CS2032 DATA WAREHOUSING AND DATA MINING

Chapter 10 Application Development. Chapter Goals Describe the application development process and the role of methodologies, models and tools Compare.

Types of software. Sonam Dema..

Application architectures

Introduction to the new mainframe © Copyright IBM Corp., All rights reserved. Chapter 7: Designing and developing applications for z/OS.

1 Software Maintenance and Evolution CSSE 575: Session 8, Part 2 Analyzing Software Repositories Steve Chenoweth Office Phone: (812) Cell: (937)

Quality analysis of industrial systems. LaQuSo experience Serguei Roubtsov.

Cmpe 589 Spring Software Quality Metrics Product  product attributes –Size, complexity, design features, performance, quality level Process  Used.

Legacy systems overview DT Legacy System definition “Legacy system is deficiency in a system in terms of its suitability to the business, its Platform.

1 TRex Paul Baker 1, Dominic Evans 1, Jens Grabowski 2, Helmut Neukirchen 2, Benjamin Zeiss 2 The Refactoring and Metrics Tool for TTCN-3 Test Specifications.

Systems Design Approaches The Waterfall vs. Iterative Methodologies.

Contents 1.Introduction, architecture 2.Live demonstration 3.Extensibility.

Software Engineering SM ? 1. Outline of this presentation What is SM The Need for SM Type of SM Size Oriented Metric Function Oriented Metric 218/10/2015.

Mastergoal Machine Learning Environment Phase III Presentation Alejandro Alliana CIS895 MSE Project – KSU.

| ©2009, Cognizant Technology SolutionsConfidential All rights reserved. The information contained herein is subject to change without notice. ©2009, Cognizant.

Fundamental Programming: Fundamental Programming K.Chinnasarn, Ph.D.

August, (c) 2005 Opentecnology 1 Synnet:Automatic.NET generator for Advantage/2E History.

Architectural Patterns Support Lecture. Software Architecture l Architecture is OVERLOADED System architecture Application architecture l Architecture.

Metadata Management of Terabyte Datasets from an IP Backbone Network: Experience and Challenges Sue B. Moon and Timothy Roscoe.

McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 4 Computer Software.

International Workshop on Principles of Software Evolution1Vienna, 11 September 2001 Evolution Metrics Tom Mens Programming Technology Lab Vrije Universiteit.

Gordana Rakić, Zoran Budimac

Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.

The IPSO Factor Enriching portfolios with market data.

Automated tests CustomWare.Net. Goals Quality Finding problems before delivering Stability Upgrade projects Downgrade Refactoring Deacreasing of manual.

Software Testing Process

Systems Development Life Cycle (SDLC)

34 Copyright © 2007, Oracle. All rights reserved. Module 34: Siebel Business Services Siebel 8.0 Essentials.

Connecting Architecture Reconstruction Frameworks Ivan Bowman, Michael Godfrey, Ric Holt Software Architecture Group University of Waterloo CoSET ‘99 May.

T EST T OOLS U NIT VI This unit contains the overview of the test tools. Also prerequisites for applying these tools, tools selection and implementation.

Objective ICT : Internet of Services, Software & Virtualisation FLOSSEvo some preliminary ideas.

ImageJ2. Why ImageJ2? ● Support the next generation of image data ● Interoperate and collaborate with other projects ● Broaden the ImageJ community ●

Application architectures. Objectives l To explain the organisation of two fundamental models of business systems - batch processing and transaction processing.

CMS High Level Trigger Configuration Management

User working in web-browser

Project Topic 2: Migration to Java 9

Software Maintenance

Lecture 17 Software Metrics

Populating a Data Warehouse

Alexander Serebrenik, Serguei Roubtsov LaQuSo & SET

Populating a Data Warehouse

ARTIFICIAL INTELLIGENCE IN SOFTWARE TESTING

Populating a Data Warehouse

Software Metrics “How do we measure the software?”

Regression testing Tor Stållhane.

0. Overview of 2-Day Academic .NET Workshop

UFCEUS-20-2 Web Programming

Springshare’s LibInsight: E-Journals/Databases Dataset

Executable Specifications

Presentation transcript:

LaQuSo is an activity of Technische Universiteit Eindhoven SQuAVisiT: A Software Quality Assessment and Visualisation Toolset Serguei Roubtsov, Alex Telea, Danny Holten

SCAM 2007 Paris 1/10/2007 Goals&Means Demo Toolset 2/8 Case study Case Study: ‘Rekenmachine’ An information system of a large insurance company: A middle layer COBOL application MicroFocus 4.1 COBOL runtime Maestro II development environment (2827 COBOL modules, ~1700 KLOCs) supports both online requests and batch execution AIX 4.3 operating system Oracle8i database: 800 tables,30 GB

SCAM 2007 Paris 1/10/2007 Goals&Means Demo Toolset 3/8 Case study Goals Maintenance: assess quality of the ‘Rekenmachine’ source code in order to identify weak spots Migration: identify the possibilities for code or/and architecture reuse during possible migration to a new platform

SCAM 2007 Paris 1/10/2007 Goals&Means Demo Toolset 4/8 Case study Means Quality metrics: system’s maintainability Code duplication detection: restructuring & reuse of code Software structure: restructuring & reuse of architecture

SCAM 2007 Paris 1/10/2007 Goals&Means Demo Toolset 5/8 Case study Means Automatically extract software structure and quality metrics and visualize them Parsing and automated fact extraction Visualisation using a set of third-party tools

SCAM 2007 Paris 1/10/2007 Goals&Means Demo Toolset 6/8 Case study Toolset A toolset that would: parse source code automatically (~2800 modules, ~1.7 MLOCs) calculate quality metrics and produce inputs for visualisation tools allow the user to reproduce the entire cycle (e.g. after new release) be reusable for other code analysis projects, other languages

SCAM 2007 Paris 1/10/2007 Goals&Means Demo Toolset 7/8 Case study SQuAVisiT: Sw Quality Assessment & Visualisation Toolset Extravis TU/e Code Repository Matrix View TU/e Table Vision TU/e Preprocessor A&V Repository *.cob LOC metrics *.cob Complexity metrics Parser & Metric Counter Fact extractors GUI & Control *.prg Call info CCFinder Toshihiro Kamiya Metrics & call files Artifacts: metrics& structural data Converters Artifacts’ DB

SCAM 2007 Paris 1/10/2007 Goals&Means Demo Toolset 8/8 Case study Demo Run SQuAVisiT