Lesson 123 - Composite Architecture Characteristics

[@anasanas2365]

that answers a lot of questions in my head

[@mosaed_b]

I think (and please correct me if it is wrong) that many other composing characteristics of a composite characteristic might even be composite. Like in Reliability, I agree that "Is the system up when I need it?" = Availability, but Availability might also have Scalability for the system to be up and available, and Serviceability and Maintainability for the system to be up while repairing and the MTTR is at a specific amount of time, and all of these can also be composing Availability.

[@markrichards5014]

Great observation Masaad, particularly when you ask "how do I measure availability?". The measurement is relatively straightforward, but the root cause is not. So, to your point, availability is measured uptime of a system, BUT the cause could result from a scalability or testability issue.

[@mosaed_b]

@@markrichards5014 Thanks, now I got it. So a composing architectural characteristic can be defined as an indivisible *state* of the system/software, and it can have different causes to it. A composite architecture is a multi-state of the system that is defined as a whole, but can be further divided into its composing characteristics. Also, when we say to provide our measurement for a characteristic we exclude the root cause of this characteristic, or state, of the system and try to measure the condition of the state, not its cause (we look from a higher view for the solution). Thank you for this clarification.