1 / 1

Dark Programming and The Quantification of Rationality and Understanding in Software

Dark Programming and The Quantification of Rationality and Understanding in Software Isaac Griffith, Stephani Schielke , and Scott Wahl.

kermit
Download Presentation

Dark Programming and The Quantification of Rationality and Understanding in Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Dark Programming and The Quantification of Rationality and Understanding in Software Isaac Griffith, StephaniSchielke, and Scott Wahl Objective: To restructure software in order to increase the understandability, reusability, and maintainability as a means to quantify the rationality of a program. In effect, unveiling the potentially lost subjective knowledge and processes embedded into the original code of the software 1 Introduction Methodology Continued Results Continued • This work presents an attempt to provide empirical answers to: • Philosophy of Computer Science questions regarding • Rationality of so-called Dark Programming • The connection between subjectivity and objectivity in the program design process and its link to rationality and understanding • Mathematical issues involved with • Analysis of metrics to measure these qualities over the scope of large projects • Definition of graph manipulations representing refactoring techniques • Software Engineering issues dealing with automated refactoring the understandability of software by multiple engineers Resultant UML Documentation Metrics and Measures Program Darkness Program Rationality Subjectivity –Objectivity Connection Maintainability Reusability Understandability Coupling Between Classes Lack of Cohesion in Methods Weighted Methods Per Class Cyclomatic Complexity 3 Results 4 Analysis 2 Methodology • Mathematical • Computational • Philosophical • Evolutionary Algorithm • Randomly apply refactoring to generate different code graphs • Refactoring • Uses graph manipulations to modify source code graph • Move Method (Field) • Pull-Up Method (Field) Class A Class B Class A Class B Move from A to B 5 Conclusions M1 M2 M1 M2 M1 M2 M1 M2 M3 Class A Class A M1 M2 M1 M2 M3 Class B Class B M1 M2 M1 M2

More Related