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)
|
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
Principles
[edit]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)
History
[edit]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.
References
[edit]Bibliography
[edit]- "BRAVERY STABLE ARCHITECTURAL PATTERN" (PDF). 2010. Archived from the original (PDF) on 2015-11-17. Retrieved November 13, 2015.
External links
[edit]- Homepage of Dr. Mohamed Fayad at the Wayback Machine (archived 2021-04-12)
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |