Icsm2013 contexts (1)

•

0 likes•210 views

SAIL_QU

How does context affect the
distribution of software
maintainability metrics?
Feng Zhang, Audris Mockus, Ying Zou, Foutse Khomh,
and Ahmed E. Hassan

6
What are the Contexts of Software?
Age
(AG)
Number of Changes
(NC)
Life Span
(LS)
Number of Downloads
(ND)
Application Domain
(AD)
Programming Language
(PL)

7
39 Software Maintainability Metrics
Complexity (14 metrics) Abstraction (5 metrics)
Coupling (8 metrics)
Cohesion (4 metrics)
Encapsulation (4 metrics)
Documentation (4 metrics)

10
31
26
23
29
49
19
16
41
29
14
13
7
7
9
7
Build Tools
Code Generators
Communications
Framework
Games / Entertainmaint
Internet
Network
Software Development
System Administrator
Build & CodeGen
Comm & Internet
Comm & Network
Games & Internet
Internet & SW Dev
SW Dev & Sys Admin
57
85
18
146
14
C
C++
C#
Java
Pascal
Data Description
320
Software
Systems

13
RQ1. Analysis Methods (cont’)
For example
C Java PascalC++ C#
Metric
1
Metric
1
Metric
1
Metric
1
Metric
1
Metric
n
Metric
n
Metric
n
Metric
n
Metric
n
KruskalWallis test
KruskalWallis test

14
Complexity (8/14 metrics) Abstraction (1/5 metrics)
Coupling (5/8 metrics)
Cohesion (2/4 metrics)
Encapsulation (1/4 metrics)
Documentation (3/4 metrics)
YES!! the Contexts Matter!
51 % of metrics are
impacted by all Six
Contexts

15
and Among the Six Contexts …
at least 72 % of
metrics are impacted
by a Single Context

16
Does it mean ALL six contexts
should be considered all the time?

19
RQ2. Analysis Methods (cont’)
C Java PascalC++ C#
Metric
i
Metric
i Mann-Whitney U test
Metric
i
Metric
i Mann-Whitney U test
Metric
i
Metric
i Mann-Whitney U test
Metric
i
Metric
i Mann-Whitney U test
Metric
i
Metric
i Mann-Whitney U test
Metric
i Mann-Whitney U test
Metric
i

20
RQ2. Analysis Methods (cont’)
0.147 0.330 0.474Cliff’s delta
14.7% 33.0% 47.4%% of non-overlap
Small Medium LargeCohen’s standard
0.20 0.50 0.80Cohen’s d

21
RQ2. Findings for
each Category of Metrics

22
Metric AD PL AG LS NC ND
TLOC - - - -  -
TNF - - - -  -
TNC   - -  -
TNM   - -  -
TNS - - - - - -
CLOC - - - - - -
NOM - - - - - -
NIM - - - - - -
NIV - - - - - -
WMC - - - - - -
NMP - - - - - -
CC - - - - - -
NPATH - - - - - -
MNL - - - - - -
Contexts Impacting ‘Complexity’
AD: Application Domain
PL : Programming Language
NC: Number of Changes

23
Metric AD PL AG LS NC ND
CF - - - -  -
CBO   - - - -
ICP - - - - - -
MPC - - - - - -
RFC   - - - -
NMI -  - - - -
FANIN - - - - - -
FANOUT - - - - - -
Contexts Impacting ‘Coupling’
AD: Application Domain
PL : Programming Language
NC: Number of Changes

24
Metric AD PL AG LS NC ND
LCOM  - - - - -
TCC - - - - - -
LCC - - - - - -
ICH - - - - - -
Contexts Impacting ‘Cohesion’
AD: Application Domain

25
Metric AD PL AG LS NC ND
NACI -  - - - -
MIF -  - - - -
IFANIN   - - - -
NOC - - - - - -
DIT  - - - - -
Contexts Impacting ‘Abstraction’
AD: Application Domain
PL : Programming Language

26
Metric AD PL AG LS NC ND
RPA  - - - - -
RPM - - - - - -
RSA - - - - - -
RSM  - - - - -
Contexts Impacting ‘Encapsulation’
AD: Application Domain

27
Metric AD PL AG LS NC ND
CLC - - - - - -
RCCC   - - - -
CLM - - - - - -
RCCM - - - - - -
Contexts Impacting ‘Documentation’
AD: Application Domain
PL : Programming Language

28
Summary of RQ2 Findings
Metric Category AD PL AG LS NC ND
Complexity   - -  -
Coupling   - -  -
Cohesion  - - - - -
Abstraction   - - - -
Encapsulation  - - - - -
Documentation   - - - -
AD: Application Domain
PL : Programming Language
NC: Number of Changes

29
Metric Category Context Groups
Complexity
AD (2) (Framework); and others
PL (3) (C); (Pascal); and others
NC (3) (Low NC;) (moderate NC); and (high NC)
Coupling
AD (3) (Communication, Network); (Build Tools, Code
Generators;) and others
PL (3) (Pascal;) (Java;) and others
NC (3) (Low NC); (moderate NC); and (high NC)
Cohesion AD (2) (Communication, Network); and others
Abstraction
AD (4) (Communication, Network); (Games); (Build Tools,
Code Generators); and others
PL (3) (Java;) (C++); and others
Encapsulation AD (3) (BuildTools); (Communication, Network); and others
Documentation
AD (2) (BuildTools, Code Generators); and others
PL (2) (Java); and others
Guidelines for Benchmarking
Maintainability Metrics

Similar to Icsm2013 contexts (1)

IBM recently announced SMCv2 for SMC-Dv2. SMCv2 defines Shared Memory Communications for TCP/IP connections that span multiple IP subnets. This presentation will introduce how this new capability applies to SMC-Dv2 for z/OS V2R4 and ISMv2 for the IBM z15. The key concepts of the SMC-Dv2 will be introduced along with an overview of how to get started using the new solution with z/OS 2.4. The overview will also cover exploitation and configuration considerations for existing SMC-D users and for new SMC-Dv2 only users. In this presentation, customers will learn about this new capability and how this capability can extend the performance benefits of SMC-D to additional System Z workloads.

Introduction to IBM Shared Memory Communications Version 2 (SMCv2) and SMC-Dv2

zOSCommserver

3 gpp lte-pdcp

Prashant Sengar

Cadence Design Flow.pptx

KunjPatel615667

CS-Core Mobile Network (General)

Hamidreza Bolhasani

LTE-Network-Planning-Huawei-Technologies EMERSON EDUARDO RODRIGUES

EMERSON EDUARDO RODRIGUES

3rd 3DDRESD: Rebit

Marco Santambrogio

Modern computer systems have intricate memory hierarchies that violate the intuition of a global timeline of interleaved memory accesses. In these so-called relaxed-memory systems, it can be dangerous to use intuition, specifications are universally unreliable, and the outcome of testing is both wildly nondeterministic and dependent on hardware that is getting more permissive of odd behaviour with each generation. These complications pervade the whole system, and have led to bugs in language specifications, deployed processors, compilers, and vendor-endorsed programming idioms – it is clear that current engineering practice is severely lacking. I will describe my part of a sustained effort in the academic community to tackle these problems by applying a range of techniques, from exhaustive testing to mechanised formal specification and proof. I will focus on a vein of work with strong industrial impact: the formalisation, refinement and validation of the 2011/14/17 C and C++ concurrency design, leading to changes in the ratified international standard, and ultimately uncovering fundamental flaws that lead us to the state of the art in concurrent language specification. This work represents an essential enabling step for verification on modern concurrent systems

HIS 2017 Mark Batty-Industrial concurrency specification for C/C++

jamieayre

Santhosh Resume

Santhosh Ravisankar

Discrete cosine transform (DCT) is a widely used tool in image and video compression applications. Recently, the high-throughput DCT designs have been adopted to fit the requirements of real-time application. Operating the shifting and addition in parallel, an error-compensated adder-tree (ECAT) is proposed to deal with the truncation errors and to achieve low-error and high-throughput discrete cosine transform (DCT) design. Instead of the 12 bits used in previous works, 9-bit distributed arithmetic. DA-based DCT core with an error-compensated adder-tree (ECAT). The proposed ECAT operates shifting and addition in parallel by unrolling all the words required to be computed. Furthermore, the error-compensated circuit alleviates the truncation error for high accuracy design. Based on low-error ECAT, the DA-precision in this work is chosen to be 9 bits instead of the traditional 12 bits. Therefore, the hardware cost is reduced, and the speed is improved using the proposed ECAT.

Design and implementation of DADCT

Satish Kumar

computer architecture.

Shivalik college of engineering

Software Defined RAN

Open Networking Summit

CDR2(Sajjad Tarahomi)

Sajjad Tarahomi

Sandeep Kumar Yarlagadda_Professional Resume

sandeep kumar yarlagadda

A main issue in the design of automotive communication architectures is that the most important design choices pertaining to the topology of the networks and the technologies to use (protocols, data rate, hardware) have to be made at a time when the communication requirements are not entirely known. Indeed, many functions only becomes available along the development cycle, and vehicle platforms have to support incremental evolutions of the embedded system that may not be fully foreseeable at the time design choices are made. The problem is becoming even more difficult and crucial with the introduction of dynamically evolving communication requirements requiring network re-configuration at run-time. We present how the use of synthetic data, that is data generated programmatically based on past vehicle projects and what can be foreseen for the current project, enables the designers to make such early stage choices based on quantified metrics. The proposals are applied to Groupe Renault's FACE service-oriented E/E architecture with the use of the “Topology Stress Test” feature implemented in RTaW-Pegase.

Early-stage topological and technological choices for TSN-based communication...

RealTime-at-Work (RTaW)

Professor Tierry Monteil, professor in computer science at INSA – University of Toulouse and researcher at LAAS-CNRS presented on OneM2M and the interoperatbility of the IoT as part of the SMART Seminar Series on 13 December 2017. More information: http://www.uoweis.co/event/onem2m-towards-end-to-end-interoperability-of-the-iot/ Keep updated with future events: http://www.uoweis.co/tag/smart-infrastructure/

SMART Seminar Series: "OneM2M – Towards end-to-end interoperability of the IoT"

SMART Infrastructure Facility

Dpdk applications

Vipin Varghese

Computer_Architecture_3rd_Edition_by_Moris_Mano_Ch_07.ppt

RafiyaKouser2

Microprogrammed of organisation and architecture of computer.pptx

SahithBeats

COA 2.1 Microprogrammed control systems of btech 2nd year students.pptx

SahithBeats

Auto conversion of serial C code to CUDA code

IRJET Journal

Similar to Icsm2013 contexts (1) (20)

Introduction to IBM Shared Memory Communications Version 2 (SMCv2) and SMC-Dv2

3 gpp lte-pdcp

Cadence Design Flow.pptx

CS-Core Mobile Network (General)

LTE-Network-Planning-Huawei-Technologies EMERSON EDUARDO RODRIGUES

3rd 3DDRESD: Rebit

HIS 2017 Mark Batty-Industrial concurrency specification for C/C++

Santhosh Resume

Design and implementation of DADCT

computer architecture.

Software Defined RAN

CDR2(Sajjad Tarahomi)

Sandeep Kumar Yarlagadda_Professional Resume

Early-stage topological and technological choices for TSN-based communication...

SMART Seminar Series: "OneM2M – Towards end-to-end interoperability of the IoT"

Dpdk applications

Computer_Architecture_3rd_Edition_by_Moris_Mano_Ch_07.ppt

Microprogrammed of organisation and architecture of computer.pptx

COA 2.1 Microprogrammed control systems of btech 2nd year students.pptx

Auto conversion of serial C code to CUDA code

More from SAIL_QU

In-app advertisements have become a major revenue for app developers in the mobile app economy. Ad libraries play an integral part in this ecosystem as app developers integrate these libraries into their apps to display ads. However, little is known about how app developers integrate these libraries with their apps and how these libraries have evolved over time. In this thesis, we study the ad library integration practices and the evolution of such libraries. To understand the integration practices of ad libraries, we manually study apps and derive a set of rules to automatically identify four strategies for integrating multiple ad libraries. We observe that integrating multiple ad libraries commonly occurs in apps with a large number of downloads and ones in categories with a high percentage of apps that display ads. We also observe that app developers prefer to manage their own integrations instead of using off the shelf features of ad libraries for integrating multiple ad libraries. To study the evolution of ad libraries, we conduct a longitudinal study of the 8 most popular ad libraries. In particular, we look at their evolution in terms of size, the main drivers for releasing a new ad library version, and their architecture. We observe that ad libraries are continuously evolving with a median release interval of 34 days. Some ad libraries have grown exponentially in size (e.g., Facebook Audience Network ad library), while other libraries have worked to reduce their size. To study the main drivers for releasing an ad library version, we manually study the release notes of the eight studied ad libraries. We observe that ad library developers continuously update their ad libraries to support a wider range of Android versions (i.e., to ensure that more devices can use the libraries without errors). Finally, we derive a reference architecture for ad libraries and study how the studied ad libraries diverged from this architecture during our study period. Our findings can assist ad library developers to understand the challenges for developing ad libraries and the desired features of these libraries.

Studying the Integration Practices and the Evolution of Ad Libraries in the G...

SAIL_QU

Studying the Dialogue Between Users and Developers of Free Apps in the Google...

SAIL_QU

Improving the testing efficiency of selenium-based load tests

SAIL_QU

Studying User-Developer Interactions Through the Distribution and Reviewing M...

SAIL_QU

Studying online distribution platforms for games through the mining of data f...

SAIL_QU

Understanding the Factors for Fast Answers in Technical Q&A Websites: An Empi...

SAIL_QU

Investigating the Challenges in Selenium Usage and Improving the Testing Effi...

SAIL_QU

Mining Development Knowledge to Understand and Support Software Logging Pract...

SAIL_QU

Which Log Level Should Developers Choose For a New Logging Statement?

SAIL_QU

Towards Just-in-Time Suggestions for Log Changes

SAIL_QU

The Impact of Task Granularity on Co-evolution Analyses

SAIL_QU

A Framework for Evaluating the Results of the SZZ Approach for Identifying Bu...

SAIL_QU

How are Discussions Associated with Bug Reworking? An Empirical Study on Open...

SAIL_QU

A Study of the Relation of Mobile Device Attributes with the User-Perceived Q...

SAIL_QU

A Large-Scale Study of the Impact of Feature Selection Techniques on Defect C...

SAIL_QU

Studying the Dialogue Between Users and Developers of Free Apps in the Google...

SAIL_QU

What Do Programmers Know about Software Energy Consumption?

SAIL_QU

Threshold for Size and Complexity Metrics: A Case Study from the Perspective ...

SAIL_QU

Revisiting the Experimental Design Choices for Approaches for the Automated R...

SAIL_QU

Measuring Program Comprehension: A Large-Scale Field Study with Professionals

SAIL_QU

More from SAIL_QU (20)