Are You a Software Architect?fleeting
- Référence externe : https://www.infoq.com/articles/brown-are-you-a-software-architect/
architecture definition process seems fairly straightforward. All you have to do is figure out what the requirements are and design a system that satisfies them.
in reality it’s not that simple and the software architecture role can vary wildly depending on how engaged you are and how seriously you view your role
Understanding the non-functional requirements is a crucial part of the role, but there’s a difference between assuming what those requirements are and challenging them
every software system has an architecture, but not every software system has a defined architecture
With the non-functional requirements captured, the next step is to start thinking about how you’re going to solve the problems set out by the stakeholders and define the architecture
If you can test your architecture, then you can prove that it works. And if you can do this as early as possible, you can reduce the overall risk of project failure rather than simply hoping for the best.
important that somebody owns the big picture and sells the vision throughout the entirety of the software development lifecycle, evolving it throughout the project if necessary and taking responsibility for ensuring that it’s delivered successfully
evolve your architecture rather than choosing to hand it off to an “implementation team”
providing technical guidance, making technical decisions and having the authority to make those decisions. As the architect, you need to undertake the technical leadership to ensure everything is taken care of and that the team is being steered in the right direction on a continuous basis.
many project teams don’t get the technical leadership that they need, with architects assuming that a successful delivery isn’t necessarily their problem
why shouldn’t the day-to-day coding activities be a part of an architect’s role? Most architects are experienced coders, so it makes sense to keep those skills up-to-date. In addition, the architect can experience the same pain as everybody else on the team, which in turn helps them better understand how their architecture is viewed from a development perspective