Stability model
Method for designing and modelling software
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 maintenance.
01Principles
The design tries to make use of common sense while guiding through the process of SM based design. It will need minimum amount of rampup time for people to understand new applications and objects once the process and methodology is kept in mind.
The stability model is built using three main concepts:
- enduring business themes (EBT),
- business objects (BO),
- industrial objects (IO).
02History
The SM method of OOSD was formulated by Dr Mohamed Fayad. He has been the editor in chief of the Computer magazine of the IEEE for many years. He has taught OOSD in two US universities and has written and currently writing few books on this subject.
Sources and credits
This article is adapted from the Wikipedia article “Stability model”, written by its contributors and licensed under CC BY-SA 4.0. Fathomly has changed the layout, removed citation markers, navigation and maintenance notices, and adjusted punctuation. This adapted version is shared under the same license. For references, see the original article.
Fathomly is not affiliated with or endorsed by the Wikimedia Foundation. Spotted a problem? Tell us.