Database Reference
In-Depth Information
Tip
Illities are also known as
non-functional requirements
(
NFRs
).
Depending on the technology platform, the explanation could take up to a couple of pages
or several chapters. Still, they should seem obvious and even quite measurable. (Reliabil-
ity is usually the
Mean Time Between Failure
(
MTBF
) and flexibility is also a time-
based characteristic that displays how fast a system can be reconfigured for other business
requirements.) So, NFRs are also precise technical requirements and not a guide in tech-
nical terms. Looking forward, let's propose a logical hierarchy of the terms, one way or
another related to principles and their areas of application. By the end of this chapter, we
will cover all of them. Your benefit from this exercise will be a clear outline that will
guide you on how to analyze requirements and apply design rules for most of your SOA-
related projects. The following table illustrates the principles and patterns discussed:
Principles and patterns
Quantity
Even being highly generic, the characteristics of generic illities have certain practical implications and materialize in at least six ar-
chitectural frameworks.
7
Technology stack's architectural principles (for SOA design principles) states that every application consists of several technology
areas, the sharing or reuse of components, and composites. For every application, an individual and balanced combination of the
universal principles is the key for successful implementation.
8
Architectural patterns form a pattern catalog, commonly approved as open standard (
.org
). It is the number of concrete patterns
that are recognized.
>85
The following figure explains the preceding principles and patterns:
Search WWH ::
Custom Search