Your answers should probably not be much more than a paragraph or two; anything longer and you might be on the wrong path or you might be over-analyzing the question (and trying toguesswhat I'm looking for).
As we've discussed in class, I'm looking for you to think outside of the box on many of these questions. There's a reason why you won't find theexactanswer to a question in the notes: it's because we haven't covered the exact scenario and you'll need to think about how you would address that scenario.
1. Another architect presents a model consisting of boxes and lines. What do those diagram elements generally represent? (Hint: they do not represent services, or data access layers, or clients).
2. In our web service "cookbook" we are presented with the choice between Request-Response and Request-Acknowledge. What are the differences between them in terms of clientandservice implementation?
3. In his 2000 Ph.D thesis, Roy Fielding argues that REST is a logical evolution of existing architectural styles. How does he "create" the REST architectural style from seemingly nothing?
4. A number of criticisms have been levelled against design patterns as described in theGang of Fourbook. One of these relates to the applicability of design patterns to application domain problems. Discuss.
5. Over time design approaches become patterns which in turn become idiomatic. Explain this process and give some examples.
6. There are two correctness measures that we can apply to a software architecture. What are they and why do they apply?