Your report could follow the structure below (though you do not have to):

Introduction provide the background and purpose(s) of this report. The background need to let readers understand the importance of EA. The purpose needs to be clearly stated to help readers understand what this report is about.

Case Description briefly introduce the case. This part needs to give readers reasonable information of the case, such as which industry it is from, whether it is a large or a small-to-medium organization, products/services provided, etc.

Architecture in the case Discuss the EA framework in the case. In this part you need to discuss different levels (or sections) of the framework, as well as EA components in different levels (or sections).

• You need to use ArchiMate to model a certain service (https://www.wa.gov.au/services). You can pick one which you are familiar with, and model the business layer based upon the information from the site as long as your personal experiences. Then you can make your own assumptions to model the application and the technology layer. Your modeling do not need to cover 100% details (which may not available online), but need to include major services based upon the service you selected.

Comparison Discuss how the EA framework in the case is different from the EA³ cube framework in the textbook (table/figure can be used). In this part you need to compare the levels (or sections) of the case framework with the EA³ cube framework, and describe how these levels (or sections) are similar to or different from each other.

Conclusion State the benefits of the EA framework implemented in the case; Discuss if the EA framework in the case is more appropriate in the context of the case than the EA³ cube framework (if so, why; if not, why not). It is possible that the EA framework in the case is quite similar to the EA³ cube framework. You could argue that it is just an adapted version of the EA³ cube framework. It is preferred that you use the literature to support your argument.