very often hear seniors developers complain about the options selected by the architect in their projects. These complaints are often surface when the developer is faced with a major difficulty esteem due to architectural choices.
When satisfied that the architecture is inadequate restraint with developments in demand in the Project one is entitled to ask questions about the legitimacy of the architect.
If the risk was foreseeable, then it is obvious that there was a hole in the paint during the design of the architecture. But how to correct this problem?
To overcome this lack of competence detrimental to the project, a response would be to advise the architect to involve the developer to choose the software solution. Unfortunately, for reasons of cost as well as planning, this solution is not ideal. Indeed, the choice of architecture is often done before the project enters really in the development phase or even before it decided whether the project would be realized or not.
Then remains as a direct solution first approach than requiring a master architect of the development and its problems.
Another solution would be to provide flexibility in achieving design process by making a quick stop after a first phase of development to validate the architecture chosen developers. It has also increasingly often use prototypes serving Proof Of Concept for architecture, on large projects. However, even for this type of project, the architect must have a culture of sufficient development to dialogue constructively with the developer. The architect must have also thought architecture generically enough to fit in the project.
But now we are interested in why the architect does not always have this knowledge development.
Firstly because the qualifying course to become an architect does not necessarily goes through a developer station on the technologies on which it operates. Indeed, some developers on “non-web” technologies have taken refuge in architecture to avoid facing web frameworks (notably JEE) they left the youngest.
But also because the trades of the architectural design and development are sometimes completely exclusive of each other. This is particularly the case of projects which are the subject of public procurement, for which there is a AMOA (Material mastery Assistance) facing the business and functional, but who designs the architecture of the target and SI EOM (mastery of work) that realizes the software. And these two entities (white collar and blue collar workers) are not known for their ability to communicate for the good of the project.
Do you?
At Home How do they live together architects and developers?
No comments:
Post a Comment