Chapter 3: Kick-Starting Your Enterprise Architecture Repository

When stakeholders introduce an idea of developing a new application to solve some business problems, your job as an enterprise architect is to help them and everyone involved to have a better understanding of what the application is for. Long before starting any designs, you need to identify what service the application is intending to provide, who will be using it, and with which existing applications it will exchange data. Whether you are planning to build this application in-house, hire a contractor to build it, or buy it off the shelf, you still need to develop these conceptual models to help the stakeholders make the right decision – including the decision of approving or rejecting the application altogether. Your role as an enterprise architect is to clarify and formalize the ideas and turn them into requirements for the solutions architect to build and/or deploy the application.

We have a backlog from...