In which phase of TOGAF technology stack and platform(java, .net, mobile etc) is decided

manpreet Best Answer 2 years ago

I am ding">reading about enterprise architecture framework TOGAF and have one query.

I understand that in phase C, application architecture is created. In this phase, application catalog is created and in next phase D (Technology architecture), Networking, hardware and other physical architecture are identified.

My question is, in which phase we define the tech stack for new application (if this is a custom application) and in what depth. Like, if is it going to be mobile, web or hybrid application. Which platform will be used to build it, etc. And if is a ready-made product/service, when do we finalize it.

Thanks In Advance

manpreet 2 years ago

It depends on your needs, basically. It's important to remember that TOGAF is just a framework that needs to be tailored to your current enterprise. You might not need all the stages of ADM to successfully use the framework.

...in which phase we define the tech stack for new application...

Having said that, it's usually Preliminary Phase/Phase A or Phase D: if your main goal of architecture work is to migrate to (or create) specific technology (java, .net, etc) I would advise to settle such decisions in Preliminary Phase or Phase A during development/updating of Architecture Principles. If this is not your main goal, but it supports your Architecture Vision, then it's usually Phase D - one of the outputs is updated Architecture Definition Document, specifically Target Technology Architecture, Version 1.0 (detailed): Technology platforms and their decomposition, showing the combinations of technology required to realize a particular technology "stack".

...and in what depth...

Depth of this definition also depends on your needs: it can be as detailed as you need it to be.

...if is it going to be mobile, web or hybrid application.

This decision is similar to the first one: if your main goal (for example, stated in Request for Architecture Work) to update your application to be mobile-friendly, then it should be settled as early as possible. But this need might also arise during Phase B - your stakeholders might state that it's crucial to make this app mobile-friendly.