This paper provides a definition for elegant systems that enables their identification and comparison. DOI: http://dx.doi.org/10.1016/j.procs.2013.01.097

1. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
|
©2013 Stevens Institute of Technology
Date: 22nd of March of 2013
By: Alejandro Salado and Roshanak Nilchiani
Using Maslow’s hierarchy of needs to define elegance
in system architecture
Conference on Systems Engineering Research (CSER’13)
Atlanta, GA (USA)

2. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
|
?
©2011 Stevens Institute of Technology9/18/20152
Option a)
Option b)

3. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology3 9/18/2015
WHY?

4. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology4 9/18/2015
*Source: www.wikipedia.org 03.04.2013

5. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology9/18/20155
*Source: www.wikipedia.org 03.04.2013*Source: www.4gifs.com 03.04.2013

6. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology9/18/20156
*Source: www.wikipedia.org 03.04.2013
Mathematical solution
Simple, yet effective and constructive.
Chemistry
Creative parsimony and versatility in resource
utilization, material manipulation and
effectiveness in synthesis and analysis.
Engineering
Highly effective and simple, solving many
problems at once.

7. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology9/18/20157
*Source: Summit
Elegant software Mundane software
Compact and efficient. Bloated and slow.
It has features that people need and use.
It has features that may look good in paper, but are
useless in practice.
It lets you do what you want to do.
It lets you do what you want to do, as long as you
do it its way.
It does one job and does it well. It does two or more jobs clumsily.
Any user can understand the data structure.
Only programmers can understand the data
structure.
It lets you do things programmers never imagined.
It lets you do only the things it was programmed to
do.
It is configurable by the user.
It is not configurable or too much configurable that
only programmers can configure it.
It protects you from your mistakes. It is affected by your mistakes.
It is self-contained and easy to install and uninstall. It needs several ancillary components.
It works with your machine. It takes over your machine.
It adapts to your working environment.
It needs you to configure your working
environment.
It adapts to the amount of data you have. It has data limitations.
It allows future relaxation of restrictions. Restrictions cannot be relaxed.
It conforms to open standards. It is a closed system.
It is backwards and forwards compatible. It is compatible to few previous versions.
It is virtually free of bugs. Bugs are continuously developing.
In case of bug, it keeps your data safe. In case of bug, it does not care about your data.
Its code works for the right reasons. Its code just happens to work.

8. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2013 Stevens Institute of Technology9/18/20158
Graceful
Solve multiple
problems not
thought to be
inter-related
Versatility in
use of
resources
Creative
parsimony
Effective
Simple
Pleasingly
ingenious
Perfection
when nothing
left to take
away
Do one thing
and do it well
Free of bugs
Backwards
and forwards
compatible
Safe when
there is a bug
Minimum of
unintended
consequences
Efficient

9. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2013 Stevens Institute of Technology9/18/20159
*Source: Verma and Gallois

10. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2013 Stevens Institute of Technology9/18/201510
*Source: Madni
Efficiency
Evolveability
Affordability
Usability
Utility/Impact
Predictibility
Purposivity
Parsimony
Transparency
Scalability
Sustainability
Bonding
1st formal
definition!
Systemic elegance
Minimalist thinking and parsimony
Perceived elegance
Hiding systemic or organizational complexity

11. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2013 Stevens Institute of Technology9/18/201511
Love
Creativity
Friendship(s)
Confidence
Sleep
Sex
Morality
Work
Breath
Security
Family Health
Property
Food
Graceful
Solve multiple
problems not
thought to be
inter-related
Versatility in
use of
resources
Creative
parsimony
Effective
Simple
Pleasingly
ingenious
Perfection
when nothing
left to take
away
Do one thing
and do it well
Free of bugs
Backwards
and forwards
compatible
Safe when
there is a bug
Minimum of
unintended
consequences
Efficient

12. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2013 Stevens Institute of Technology9/18/201512
*Source: www.wikipedia.org on 03.20.2013

13. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology9/18/201513
I want it to work!
… well, what about faster start up?
… ejem, what if it would fail less?
… mmmm, and if it would be
less cumbersome?
… btw, can I upgrade it?

14. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology9/18/201514
Functional needs
The system works, interfaces, etc.
Performance needs
The system works well.
Availability needs
Reliability, maintainability,
supportability, etc.
Efficiency needs
Use of resources, process
efficiency
Adaptability
needs
Flexibility,
modularity,
scalability,
etc.
System of Systems
Society
Operational readiness
and effectivess
Pre-requisites

15. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology9/18/201515
Functional needs
The system works, interfaces, etc.
Performance needs
The system works well.
Availability needs
Reliability, maintainability,
supportability, etc.
Efficiency needs
Use of resources, process
efficiency
Adaptability
needs
Flexibility,
modularity,
scalability,
etc.
System of Systems
Society
Operational readiness
and effectivess
Pre-requisites
Scalable
Integral

16. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2013 Stevens Institute of Technology9/18/201516
Functional needs
The system works, interfaces, etc.
Performance needs
The system works well.
Availability needs
Reliability, maintainability,
supportability, etc.
Efficiency needs
Use of resources, process
efficiency
Adaptability
needs
Flexibility,
modularity,
scalability,
etc.
Scalability, sustainability,
evolveability
Parsimony, transparency, scalability,
efficiency, affordability, utility/impact
Usability, predictability
Purposivity
Purposivity
Bonding
as a
result
Maslow’s peak
experience

17. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
|
?
©2011 Stevens Institute of Technology9/18/201517
Option a)
Option b)
Adaptability needs
Efficiency needs
Availability needs
Performance needs
Functional needs
A
A
A

18. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2011 Stevens Institute of Technology9/18/201518
Functional needs
The system works, interfaces, etc.
Performance needs
The system works well.
Availability needs
Reliability, maintainability,
supportability, etc.
Efficiency needs
Use of resources, process
efficiency
Adaptability
needs
Flexibility,
modularity,
scalability,
etc.
System of Systems
Society
Operational readiness
and effectivess
Pre-requisites
Structure
Hierarchy

19. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
| ©2013 Stevens Institute of Technology9/18/201519
NEXT
Qualitative &
intuitive
Confirm
hierarchy
Quantitative
metrics /
heuristics
Test existing and
future systems

20. ©2011 Stevens Institute of TechnologyP. 2/3 | 01/01/11
|
©2013 Stevens Institute of Technology
Stevens Institute of Technology
Castle Point on Hudson
Hoboken, NJ 07030
w w. s t e v e n s . e d u