1. Non-Functional Properties
Software Architecture

2. What Is an NFP?
A software system’s non-functional property (NFP) is a constraint on the manner in which the system implements and delivers its functionality
Example NFPs
Efficiency
Complexity
Scalability
Heterogeneity
Adaptability
Dependability

3. Designing for FPs
Any engineering product is sold based on its functional properties (FPs)
TV set, Blu-ray player, stereo, mobile telephone
Providing the desired functionality is often quite challenging
Market demands
Competition
Strict deadlines
Limited budgets
However, the system’s success will ultimately rest on its NFPs
“This system is too slow!”
“It keeps crashing!”
“It has so many security holes!”
“Every time I change this feature I have to reboot!”
“I can’t get it to work with my home theater!”

4. FPs vs. NFPs – An Example Microsoft Word 6.0 Released in the 1990s
Both for the PC and the Mac
Roughly the same functionality
It ran fine on the PC and was successful
It was extremely slow on the Mac
Microsoft “solved” the problem by charging customers for downgrades
A lot of bad publicity

5. FPs vs. NFPs – Another Example
Linux – “as-documented” architecture
Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

6. FPs vs. NFPs – Another Example
Linux – “as-implemented” architecture
Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

7. Challenges of Designing for NFPs
Only partially understood in many domains
E.g., MS Windows and security
Qualitative vs. quantitative
Frequently multi-dimensional
Non-technical pressures
E.g., time-to-market or functional features

8. Design Guidelines for Ensuring NFPs
Only guidelines, not laws or rules
Promise but do not guarantee a given NFP
Necessary but not sufficient for a given NFP
Have many caveats and exceptions
Many trade-offs are involved

9. Overarching Objective
Ascertain the role of software architecture in ensuring various NFPs
At the level of major architectural building blocks
Components
Connectors
Configurations
As embodied in architectural style-level design guidelines

10. Efficiency
Efficiency is a quality that reflects a software system’s ability to meet its performance requirements while minimizing its usage of the resources in its computing environment
Efficiency is a measure of a system’s resource usage economy
What can software architecture say about efficiency?
Isn’t efficiency an implementation-level property?
Efficiency starts at the architectural level!

11. Software Components and Efficiency
Keep the components “small” whenever possible
Keep component interfaces simple and compact
Allow multiple interfaces to the same functionality
Separate data components from processing components
Separate data from meta-data

12. Multiple Interfaces to the Same Functionality
Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

13. Software Connectors and Efficiency
Carefully select connectors
Use broadcast connectors with caution
Make use of asynchronous interaction whenever possible
Use location/distribution transparency judiciously

14. Distribution Transparency
Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

15. Architectural Configurations and Efficiency
Keep frequently interacting components “close”
Carefully select and place connectors in the architecture
Consider the efficiency impact of selected architectural styles and patterns

16. Performance Penalty Induced by Distance
Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

17. Complexity IEEE Definition
Complexity is the degree to which a software system or one of its components has a design or implementation that is difficult to understand and verify
Complexity is a software system’s a property that is directly proportional to the size of the system, number of its constituent elements, their internal structure, and the number and nature of their interdependencies
What about behavior?

18. Software Components and Complexity
Separate concerns into different components
Keep only the functionality inside components
Interaction goes inside connectors
Keep components cohesive
Be aware of the impact of off-the-shelf components on complexity
Insulate processing components from changes in data format

19. Software Connectors and Complexity
Treat connectors explicitly
Keep only interaction facilities inside connectors
Separate interaction concerns into different connectors
Restrict interactions facilitated by each connector
Be aware of the impact of off-the-shelf connectors on complexity

20. Architectural Configurations and Complexity
Eliminate unnecessary dependencies
Manage all dependencies explicitly
Use hierarchical (de)composition

21. Complexity in Linux
Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

22. Scalability and Heterogeneity
Scalability is the capability of a software system to be adapted to meet new requirements of size and scope
Heterogeneity is the quality of a software system consisting of multiple disparate constituents or functioning in multiple disparate computing environments
Heterogeneity is a software system’s ability to consist of multiple disparate constituents or function in multiple disparate computing environments
Portability is a software system’s ability to execute on multiple platforms with minimal modifications and without significant degradation in functional or non-functional characteristics

23. Software Components and Scalability
Give each component a single, clearly defined purpose
Define each component to have a simple, understandable interface
Do not burden components with interaction responsibilities
Avoid unnecessary heterogeneity
Results in architectural mismatch
Distribute the data sources
Replicate data when necessary

24. Software Connectors and Scalability
Use explicit connectors
Give each connector a clearly defined responsibility
Choose the simplest connector suited for the task
Be aware of differences between direct and indirect dependencies
Avoid placing application functionality inside connectors
Application functionality goes inside components
Leverage explicit connectors to support data scalability

25. Architectural Configurations and Scalability
Avoid system bottlenecks
Make use of parallel processing capabilities
Place the data sources close to the data consumers
Try to make distribution transparent
Use appropriate architectural styles

26. Adaptability
Adaptability is a software system’s ability to satisfy new requirements and adjust to new operating conditions during its lifetime

27. Software Components and Adaptability
Give each component a single, clearly defined purpose
Minimize component interdependencies
Avoid burdening components with interaction responsibilities
Separate processing from data
Separate data from metadata

28. Software Connectors and Adaptability
Give each connector a clearly defined responsibility
Make the connectors flexible
Support connector composability

29. Composable Connectors
Software Architecture: Foundations, Theory, and Practice; Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy; © 2008 John Wiley & Sons, Inc. Reprinted with permission.

30. Architectural Configurations and Adaptability
Leverage explicit connectors
Try to make distribution transparent
Use appropriate architectural styles

31. Dependability
Dependability is a collection of system properties that allows one to rely on a system functioning as required
Reliability is the probability that a system will perform its intended functionality under specified design limits, without failure, over a given time period
Availability is the probability that a system is operational at a particular time
Robustness is a system’s ability to respond adequately to unanticipated runtime conditions
Fault-tolerant is a system’s ability to respond gracefully to failures at runtime
Survivability is a system’s ability to resist, recognize, recover from, and adapt to mission-compromising threats
Safety denotes the ability of a software system to avoid failures that will result in (1) loss of life, (2) injury, (3) significant damage to property, or (4) destruction of property

32. Software Components and Dependability
Carefully control external component inter-dependencies
Provide reflection capabilities in components
Provide suitable exception handling mechanisms
Specify the components’ key state invariants

33. Software Connectors and Dependability
Employ connectors that strictly control component dependencies
Provide appropriate component interaction guarantees
Support dependability techniques via advanced connectors

34. Architectural Configurations and Dependability
Avoid single points of failure
Provide back-ups of critical functionality and data
Support non-intrusive system health monitoring
Support dynamic adaptation