Purpose:
JSpIRIT supports the identification of 10 code smells following the detection strategies: Brain Class, Brain Method, Data Class, Disperse Coupling, Feature Envy, God Class, Intensive Coupling, Refused Parent Bequest, Shotgun Surgery, Tradition Breake.
To prioritize the code smells JSpIRIT provides several kind of rankings that use different criteria such as the history of the application, the relevance of the kind of code smell, or modifiability scenarios.
How this tecnology can be used?
This tool needs to be installed and configured on the project’s work environment. Detailed instructions for getting started with JSpIRIT can be found clicking here.
Prerequisite for use it:
JSpIRIT has been tested in Eclipse Kepler (v4.3.2) with Java 1.7.
Supported TD type(s): Architectural, Code, Design Debts (Code smells).
Supported TDM activity (ies): Identification and Measurement.
Source/Input Artifact(s): Source Code.
Project Context, Programming Language or Domain Application: Java Programms.
Evidence Type(s): Case Study.
Reference: