Add a comment

 

Re: Re-evaluating software architecture

By "bigger picture" I mean aspects such as the non-functional requirements (ensuring the solution meets the performance/scalability/security/availability/etc goals), technology selection (choosing technologies that are right for the job, compatible, etc), quality assurance, technical leadership, integration of the architecture with other teams in the organisation (DBAs, operations/support, etc), architecture constraints (e.g. choice of platform, interfaces, etc) and so on. This all needs to be done and some of the "bigger picture" has a massive influence on the design of the overall solution. As I said, provided it's all done then that's fine. My experience suggests that this isn't the case though.

Re: Re-evaluating software architecture


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).