Tuesday 11th October, 2011
3:00pm to 4:00pm
Most organizations have competent project management and they know how to implement and test their systems. We know this from the huge amount of working software that we have today. Many of these organizations have also learned that the effort put into requirements is repaid when the right and appropriate software is built.
However, many of the same organizations fail to grasp the relevance of system and software architecture. Designing a software system without considering the evolutionary path that the system (and its offspring) will follow after delivery is the essence of short-sightedness. Yet we do it all the time. Being a great architect is much more than having vision in the first place; you have to learn to protect that vision in the rough-and-tumble of schedule pressure and project politics.
Sign in to add slides, notes or videos to this session