Pragmatic CreativitySoftware Systems Design and Development in Detail

Business requirements define functionality of a system, whereas system architecture allows to implement this functionality. The more sophisticated business requirements are, the more flexible architecture is required. The more flexible architecture is, the more future business needs it may cover. The more specific selected architecture is, in a better way it serves current business needs. The more focused on current business requirements architecture is, the less time to market is achieved. So there should a compromise be found. I would say, fifty-fifty approach will fit most of small to medium projects, while more flexibility to less dedicated solution will fit big projects or projects that will potentially grow in future. Either extreme will go phut eventually and end up with totally new solution. There is nothing new about it, I just wanted to emphasize the importance of such choice, no matter how philosophic the question is.