Stability model

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article relies excessively on references to primary sources. Please improve this article by adding secondary or tertiary sources. Find sources: "Stability model" – news · newspapers · books · scholar · JSTOR (March 2008) (Learn how and when to remove this message) This article relies largely or entirely on a single source. Relevant discussion may be found on the talk page. Please help improve this article by introducing citations to additional sources. Find sources: "Stability model" – news · newspapers · books · scholar · JSTOR (March 2024) The topic of this article may not meet Wikipedia's general notability guideline. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources: "Stability model" – news · newspapers · books · scholar · JSTOR (March 2024) (Learn how and when to remove this message) (Learn how and when to remove this message)

In software development, the stability model (SM) is a method for designing and modelling software. It is an extension of object-oriented software design (OOSD) methodology, such as Unified Modeling Language (UML), but adds its own set of rules, guidelines, procedures, and heuristics to achieve more advanced object-oriented (OO) software.

The motivation is to achieve a higher level of OO features, such as

• Stability: the objects will be stable over time and will not need changes
• Reusability: the objects can be reused for various kind of applications
• Maintainability: the objects will need the least amount of maintenance