Repository logo
Log in(current)
Repository logoMIT Open ScholarshipDSpace@MIT
  1. Home
  2. MIT Open Access Articles
  3. MIT Open Access Articles
  4. Pliability and Viable Systems: Maintaining Value Under Changing Conditions

Pliability and Viable Systems: Maintaining Value Under Changing Conditions

Thumbnail Image
Download
Name

%5bMekdeci et at.%5d %5bPliability & Viability%5d %5bIEEE Systems%5d %5bManuscript ID - ISJ-RE-13-02609%5d %5bFinal%5d.pdf

Size

1.78 MB

Format

Adobe PDF

Checksum (MD5)

9ee45df04915cf1fe972a7b646380732

Author(s)
Mekdeci, Brian Anthony
•
Ross, Adam M
•
Rhodes, Donna H
•
Hastings, Daniel E
Date Issued
2015
Journal
IEEE Systems Journal
Publisher
Institute of Electrical and Electronics Engineers (IEEE)
Citation
Mekdeci, Brian et al. “Pliability and Viable Systems: Maintaining Value Under Changing Conditions.” IEEE Systems Journal 9.4 (2015): 1173–1184.
Version
Original manuscript
Abstract
As systems become more complex and have longer lifespans, they will likely encounter contextual variation or be themselves subject to change. Systems need to not only be feasible but viable as well. That is, they need to be able to continue to provide value in spite of any potential exogenous or endogenous changes. Viability has been defined for other domains, but it has not been defined for engineered systems. This paper defines what it means for an engineered system to be viable and shows that it is related to, but different from, other existing “-ilities” such as survivability and reliability. This paper also addresses the need to ensure that endogenous changes do not inadvertently cause unintended interactions that harm the system overall. A new -ility, i.e., pliability, is introduced, which specifies the limits on how a system can change, without “breaking” or violating an architecture that was intended and validated. Like changeability, pliability increases robustness by allowing systems to voluntarily change in response to dynamic contexts and increases survivability by increasing the likelihood that unintentional changes are still within the set of allowable architecture-defined instances. It also distinguishes allowable changes from those that would require additional validation, reducing the effort required to get those changes approved by a diverse set of stakeholders.
MIT Department
Massachusetts Institute of Technology. Institute for Data, Systems, and Society
Massachusetts Institute of Technology. Department of Aeronautics and Astronautics
MIT Sociotechnical Systems Research Center
Terms of Use
Creative Commons Attribution-Noncommercial-Share Alike
http://creativecommons.org/licenses/by-nc-sa/4.0/
Persistent DSpace Link
http://hdl.handle.net/1721.1/105807
DOI of Published Version
https://doi.org/10.1109/jsyst.2014.2314316
Repository logo
PrivacyPermissionsAccessibilityContact us
Repository logo
Notify us about copyright concerns.