In my opinion, engineers are indeed doing architecture when they sit down and think about how they will solve a particular problem, before they start work on actually solving it. Under this definition, many people perform architectural activities, including individual software engineers.
TECHNICAL ARCHITECT ROLES AND RESPONSIBILITIES IN SOFTWARE HOW TO
In my view, a software architect is a person who figures out how to solve a business or technical problem by creatively using technology. Let’s take a look at a pragmatic definition of an architect. It’s not that architects can’t do these things, but you can still be an architect and not do them at all. Many of these definitions involve creating technical standards, planning projects, and doing other activities that are, in my view, not at all central to architecture itself. If you search for “software architect definition,” you will see many alternatives that I believe are useless or, at the least, very confusing. But if everyone is called an “architect,” it certainly makes things confusing. Many of those functions are vital, and saying these people are “not architects” is in no way meant to disparage them or their role. I see many people with the title “architect” who are not what I would call an architect-they actually perform other, distinct, functions.
Many roles in software development tend to be mislabeled as “architects.” Although these roles are just as vital, using incorrect definitions can lead to miscommunication and unrealistic expectations.Īs I work with companies on their digital transformation initiatives, I engage with many software architects, both in those companies and within GlobalLogic.
0 kommentar(er)
