Posts tagged ‘architecture’
I was recently reading various articles about the use of “Evidence” in Management. The basic idea is that it is all too easy to start management initiatives based on a prejudice of what is going on. The result can be that inappropriate action on a situation. An example would be if a manager were to believe that his team were unproductive and needed extra motivation there are actions that might be taken to improve motivation, or apply control to demand more output. The reality of the situation might be very different, with the individuals motivated and wanting to produce more – but being hampered by an inability to work effectively in the environment. The appropriate actions here would be quite different, and action on the perceived problem would have no effect. It could even make it worse. Worse still, the problem might be that the team are productive but too much is expected of them for what is achievable in the situation.
What solution is proposed? Continue reading ‘Evidence in Management and IT’ »
Posted by admin on 02/08/2010 at 19:35 under Implementation.
Tags: architecture, based, Business, evidence, it, management, Strategy, technology
Comment on this post.
I recently needed to consider the state of a System Architecture and consider the changes likely to be needed over time. Thus, I was trying to produce a “Roadmap” for the architecture into the future. The challenge was that the future is uncertain. Some items can be planned for, and others are dependent on the way the business and technological environments develop. These developments can be considered to be the product of various “forces” playing out in the environment of the system. How then can you address this complexity? Continue reading ‘Future Scenarios in Architecture…’ »
Posted by admin on 25/02/2010 at 19:00 under Implementation.
Tags: architecture, Business, environment, future, governance, improved, management, match, prediction, problem, process, scenario, scenarios, Strategy
Comment on this post.
It would seem that “Service Oriented Architecture” (SOA) is taking off as a technology in fashion. As usual, most of the news is generated by people wanting to sell it as the next big thing ready for the prime time. If followed as it is being sold at present, the concept is liable to lead to significant performance problems. SOA is sold on having a large number of “users” who are then often other systems. This is followed all the way back to the real users through an unknown number of tiers. The complexity of managing this sort of architecture increases significantly as the number of tiers increases. If this is then managed without due consideration for managing the system capacity and performance the result will be problems in the future. That is not to say that I don’t see a benefit in the overall technology – there is great potential. Just consider carefully how the performance of operational systems might be proven to be sufficient for the long term.
Posted by admin on 07/04/2006 at 11:20 under News.
Tags: architecture, complexity, hype, News, oriented, performance, problem, service, soa
Comment on this post.