This presentation is about non-functional requirements in application to architectural styles, like REST or microservices. These requirements (which are informally called the "ilities") are fundamental for development of enterprise applications. So, understanding of these requirements is important for development of software. Also, it's important for improving communication between product owner and development team.

1. Quality
characteristics
Anton Hrytsenko

2. Quality characteristics
ISO/IEC 25010:2011
• Functionality
• Reliability
• Usability
• Efficiency
• Maintainability
• Portability
©2016AntonHrytsenko
2

3. Technical processes
ISO/IEC 12207:2008
• Development
 Requirements definition
 Requirements analysis
 Architectural design
 Implementation
 Integration
 Testing
 Installation
 Acceptance
• Operation
• Maintenance
• Disposal
©2016AntonHrytsenko
3

4. Processes and characteristics
Process Characteristic
Development Functionality
Usability
Operation Reliability
Efficiency
Maintenance Maintainability
Portability
©2016AntonHrytsenko
4

5. Roles and characteristics
Role Characteristic
Architect Reliability
Efficiency
Portability
Developer Functionality
Maintainability
Designer Usability
©2016AntonHrytsenko
5

6. Functionality
Sub-characteristic Factor
Suitability Users
Accuracy Users
Security Environments
Interoperability Environments
©2016AntonHrytsenko
6

7. Usability
Sub-characteristic Factor
Operability Environments
Understandability Users
Attractiveness Users
Learnability Users
©2016AntonHrytsenko
7

8. Reliability
Sub-characteristic Factor
Maturity Technologies
Fault-tolerance Environments
Recoverability Tools
©2016AntonHrytsenko
8

9. Efficiency
Sub-characteristic Factor
Time behavior Technologies
Resource utilization Tools
©2016AntonHrytsenko
9

10. Maintainability
Sub-characteristic Effort
Analyzability Identify a change.
Changeability Introduce a change.
Testability Verify a change.
Stability Avoid the negative impact of a change.
©2016AntonHrytsenko
10

11. Portability
Sub-characteristic Effort
Installability Install a product.
Adaptability Support a new specification.
Support a new operating environment.
Replaceability Replace a component.
©2016AntonHrytsenko
11

12. Approaches
• Load balancing
• Stateless protocols
• Redundancy
• Graceful degradation
• Switchover and failover
©2016AntonHrytsenko
12

13. Styles
• Event-driven
• Resource-oriented
• Self-contained
©2016AntonHrytsenko
13