Appendix B. Non-Functional Behavior
Whether it is the design of products, integration capabilities, or solutions, more focus is typically given to functional behavior rather than non-functional behavior. A design with less focus on non-functional behavior can cause the entire initiative to fail. In other words, in IT solutions, non-functional aspects should be given equal importance to functional aspects.
This appendix covers some more detail on the non-functional requirements covered in Chapter 7, “System Characteristics.” They include:
• Reliability and availability
• Performance efficiency
• Compatibility
• Maintainability
• Security
Reliability and Availability
Availability is a measure of the time a system or component is available for ...
Get Common Information Models for an Open, Analytical, and Agile World now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
