— It has been explored if stability of software is related to the decomposing the class object are related to each other or not. Any part of the project code is suffering from the “Yoyo problem” with multiple issues related to readability of code, understandability of code as well as maintainability of code there is need to rethink, redesign, refactor these pieces of code . So as to find the best way to do is to simplify the inter relationship of class objects in such manner that code becomes concise with Liskov Substitution Principle with the help of decomposition of classes however this may lead to unknown or unwanted of class objects that may turn into stable, low, high, medium categories after the application of decomposition of class objects in such manner that code becomes concise and affecting the stability of overall application we are developing which may even lead to software erosion.
— Design stability, metrics, software architecture, dependency.
Harpreet Kaur is with the Computer Engg Deptt. at K.C. Group of Institutes, Nawanshahr, India (e-mail: firstname.lastname@example.org).
Kashish Sareen is with the Electronics and Communication Engineering Department in K.C. College of Engineering & I.T., Nawanshahr, India (email: email@example.com).
Cite: Harpreet Kaur and Kashish Sareen, " Decomposition of Classes on the Stability of Software Architecture," International Journal of Information and Electronics Engineering vol. 4, no. 4, pp. 308-311, 2014.