Summary

In this chapter, we dived into the details of the system architecture domain. We learned what is expected from a CTA to cover and at what level of detail. We then tackled a mini hypothetical scenario that focused on system architecture, and we solv it together and created some effective presentation pitches.

We had to make several design decisions during the solution, all while making some assumptions and a lot of justifications. In real-life projects, you need to document all of these design decisions to avoid losing any valuable information in the future.

We then came across the challenge of determining the right org strategy, and we provided a clear, justified recommendation based on the shared requirements. We also tacked the challenge of coming up with a mobile strategy. We provided a clear list of required licenses and explained why we believe they are the most suitable ones for each group of users.

Finally, we tackled some other challenges, such as recommending...